whosbetterthanme
asked on
PST file management
All, we have an Exchange server (2003) and many users with huge pst files. We have them stored on the network via a SAN and not stored locally. I know that storing pst files on a network/WAN is not recommended. However storing pst files locally presents backup challenges. We have been experiencing many issues that I believe are tied to pst files on our network.
What do recommend for managing pst files properly so that there is no impact on the network, and files can be backed up?
What do recommend for managing pst files properly so that there is no impact on the network, and files can be backed up?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yeah - ive read that article before, we take the risk and havent had any issues, but again thats due to us keeping the file size under control.
What speed is your LAN, or WAN (depending on where your server and clients are). Obviously accessing a PST over a slower WAN link is asking for trouble.
What speed is your LAN, or WAN (depending on where your server and clients are). Obviously accessing a PST over a slower WAN link is asking for trouble.
ASKER
Our setup is 10 Mbps between locations so I don't think that's the issue. I wonder if there are any 3rd party solutions?
are your client and servers in the same location ?
ASKER
Some are. The email server is here, and there are users here, but also at remote locations.
What about the servers hosting the network pst files, is that on a file server and do they go over the WAN link too.. or is it local ?
if you are accessing large PST files over a 10 meg link thats the cause for your speed issues, 100meg its less of a problem, 1 GB and the issues vanish almost entirely. You could either host a file serve mirror (maybe using windows DFS ) locally, or store the PST files locally. You could use backup software with Client agents such as backup exec, or netbackup to backup client machines (and thus PST's).
Or you could setup syncronisation to sync users home profile at login/logoff to your network share (allowing backup) but so outlook is accessing locally.
Or you could setup syncronisation to sync users home profile at login/logoff to your network share (allowing backup) but so outlook is accessing locally.
ASKER
Woolnoir, maybe you misunderstand. We went from a T1 (1.5Mbps) to 10Mbps. Speed not an issue. It's something else. It's been happening more and more lately.
Either way, I was hoping that their may be a 3rd party solution, or a more reliable workaround. Storing the files locally and running backups on everyone's pc to backup the pc seems like such a hassle with many break points. We're pondering going to a cloud based email solution.
Thanks for all your help.
Either way, I was hoping that their may be a 3rd party solution, or a more reliable workaround. Storing the files locally and running backups on everyone's pc to backup the pc seems like such a hassle with many break points. We're pondering going to a cloud based email solution.
Thanks for all your help.
How many users do you have? Is there any reason you haven't considered using an Exchange server?
With an Exchange server you sort of get the best of both worlds where mail can be cached locally but still remail on the server for backups etc.
With an Exchange server you sort of get the best of both worlds where mail can be cached locally but still remail on the server for backups etc.
Another great solution for those wonderful PST's we love so much with Exchange 2003 0r newer is to use Enterprise vault from Symantec. This will eliminate the need for pst files all together. There is no magic fix for pst's which is why Microsoft says they are not supported on across a network.
ASKER
It makes sense via the asrticle below:
http://blogs.technet.com/b/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx