I use Retrospect with the open file backup add-on.  PST's, along with the
desktop, .nk2 file, and signatures get backed up once a week.

 - Andy O. 
________________________________________
From: Kevan Dickinson [mailto:[email protected]] 
Sent: Wednesday, March 25, 2009 11:30 AM
To: NT System Admin Issues
Subject: RE: Can not open PST files


Thank you to all that have replied offering advice.
We rebooted the server but still could not access the PST files so we have
begun copying the PST Files to users local drives.

What can people suggest as the best way to now backup these PST files to the
network.

As a temporary measure I have installed the Microsoft PST backup tool that
copies the PST Files up to the Network when a user closes Outlook.

Running a logoff script could also copy the files, but what are other people
doing?

Regards

Kevan Dickinson
Network Manager
NSF-CMI
23 Lodge Road
Hanborough Business Park, Long Hanborough,
Oxford, OX29 8SJ, UK
 
T:+44 01993 885661
E:[email protected]
W:www.nsf-cmi.com
 
 
________________________________________
From: Scott Kaufman at HQ [mailto:[email protected]] 
Sent: 24 March 2009 14:03
To: NT System Admin Issues
Subject: RE: Can not open PST files

As other esteemed members have said, get the PST’s off the network server &
back to local machine.  Follow that up with a backup procedure for just the
PSTs.  Microsoft never intended for PSTs to be used across the network.

For starters, configure your Anti-Virus solution on the file server to
exclude .PST files.

We ran into the same situation with a large x86 2k3 file server, and the
following set of registry key changes has made a considerable performance
difference for users.  Please note, that if your file server is performing
any other role, these changes could adversely affect the functionality of
those roles… YMMV.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
SystemPages : Reg_Dword 
Default:  0x3c00
Changed: 0xFFFFFFFF

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
HeapDeCommitFreeBlockThreshold : Reg_Dword
Default: 0x0
Changed: 0x00040000

The next two were changed based on
http://support.microsoft.com/default.aspx/kb/312362

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
PagedPoolSize : Reg_Dword 
Default:  0x0
Changed: 0xFFFFFFFF

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management
PoolUsageMaximum: Reg_Dword 
Default:  0x0
Changed: 0x3c

You will have to reboot the server for these changes to take effect.

Scott Kaufman
Lead Network Analyst
ITT ESI, Inc.

From: Kevan Dickinson [mailto:[email protected]] 
Sent: Monday, March 23, 2009 8:50 PM
To: NT System Admin Issues
Subject: Can not open PST files


Since Friday afternoon I have been having some people report that they can
not open their PST files.
All PST files are stored in users home drives on the Network.  
When trying to open the file from within Outlook they are told that they do
not have permission to open the file. However they have full read and write
access to the file. I reapplied permissions just in case.  If I copy the PST
locally then the file can be opened.

I know that Microsoft does not support PST’s on a Network drive but we have
worked this way for many years and I know that lots of other people do as
well. 

Anyone any idea what may be happening here? It’s affecting about 10% of our
users at the moment and as I said earlier started happening on Friday
afternoon.  The clients are running a mixture of Office 2003 and Office
2007.  We use Exchange server 2003.

Any help or suggestions would be appreciated.

Kevan Dickinson
Network Manager
NSF-CMI
23 Lodge Road
Hanborough Business Park, Long Hanborough,
Oxford, OX29 8SJ, UK
 
T:+44 01993 885661
E:[email protected]
W:www.nsf-cmi.com
 
 

****************************************************************************
****
    ***Disclaimer***
The contents of this Email may be privileged and are confidential. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may
be unlawful.
Should you wish to use Email as a mode of communication, NSF-CMi Ltd and its
subsidiaries are unable to guarantee the security of Email content outside
of our own computer systems.
This footnote also confirms that this Email message has been checked by
MailMarshal for the presence of computer viruses. Whilst we run anti-virus
software, you are solely responsible for ensuring that any Email or
attachment you receive is virus free. We disclaim any liability for any
damage you suffer as a consequence of receiving any virus.
NSF-CMi Ltd
Registered in England No: 1899857
Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW
****************************************************************************
******
 

 
 

 
 
****************************************************************************
****
    ***Disclaimer***
The contents of this Email may be privileged and are confidential. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may
be unlawful.
Should you wish to use Email as a mode of communication, NSF-CMi Ltd and its
subsidiaries are unable to guarantee the security of Email content outside
of our own computer systems.
This footnote also confirms that this Email message has been checked by
MailMarshal for the presence of computer viruses. Whilst we run anti-virus
software, you are solely responsible for ensuring that any Email or
attachment you receive is virus free. We disclaim any liability for any
damage you suffer as a consequence of receiving any virus.
NSF-CMi Ltd
Registered in England No: 1899857
Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW
****************************************************************************
******
 

 
 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to