We have PST files on the network. Users are getting the access denied errors when accessing their PST's. One of the reasons that we need it on the network is to back up the PST's. Is their a better way to do this? I also noticed on the file server where the PST's reside that there is excessive paging. The server has 2GB of RAM but a custom size of 384-768 MB of ram. Would it be better to set this to the recommended amount or just allow the system to manage the page file? Thank you, Leto the just

Are you registering hard faults? If not, then how are you determining you have excessive paging? Users should have all rights to the pst's. Doesn't sound like they do or the backup has them open when they try to access.

PST files are not designed to be stored on network storage and accessed very often as well as not be shared. A PST file can only be accessed by 1 client at a time; all others will be given "access denied" regardless of security permissions.

PST are designed to be accessed from DAS storage NOT over NFS. This isnt a supported scenario by MS and highy discouraged because of corruption. If your users require archived data they should be using a third party solution like GFI or Symantec Enterprise Vault ( Or better yet Exchange 2010 :-) ) And im not surpised theres heavy amounts of I/O as users are accessing PST's from that box. You can adjust the paging file and ensure it is static. But the best practice to prevent disc queue lengths and excessive swapping is simply more RAM. Assuming that box is 32bit it will see 4GB. Enterprise edition can see more but wether that can be addressed is another kettle of fish.