In testing I've done, the modified date is updated on a .PST file just by opening and closing outlook. Some info I've found on a newsgroup stated:
"PST files initiate a locking mechanism when you access them (access, not necessarily open). A PST file is a database. This database is continuously interrogated with searches and sorts by Outlook to get the data it needs to display, import,... whatever. There is a special reserved area in the database Outlook writes to when it accesses the file. Information about the user and computer currently accessing the file is placed here. This allows other processes on that particular computer (invisible queries to build the folder hierarchy in the Outlook Folder List, for example) to access the file while effectively locking-out access to anyone else until the file is closed. Without this exclusive access, a PST could be easily corrupted by someone changing parts of that database at the same time. Without the ability to record in the PST file itself who has access to it right now, there is no way to lock out others while allowing the "right" person access." So along with breaking up the .PST files, you may also have to make them read-only. Some of our users have setup a separate archive pst for each year, then they are only modifying the most recent one. Tim Rushfoth City of Winnipeg -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 2:54 PM To: [EMAIL PROTECTED] Subject: Re: Outlook PST files If your users broke their .pst files up into half a dozen or so then this may reduce the amount of subfile data moved. What is probably happening is that they are compressing the things making everything be sent. -----Original Message----- From: Bruce Lowrie [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 1:23 PM To: [EMAIL PROTECTED] Subject: Outlook PST files All, Each day, roughly 99% of the changed data on my Windows file and print servers is attributable to .pst files. For my Wan clients I have implemented Adaptive subfile differencing but still running marathon backups of some these clients. So given that pst files dramatically impact WAN (and to some degree LAN) backups, how can I address this? * Don't backup .pst? (Most likely not an option) * Force .pst archive rules * reduce frequency of .pst updates (e.g., limit to 1/week; wishful thinking would be this would occur on Fri so that large backups would occur on weekend) * reduce size of .pst by creating new pst files every "so often" * Storing .pst files centrally rather than locally. * Other - thoughts, anyone? I am looking to for suggestions on how to cope with this ever growing menace. Bruce E. Lowrie Sr. Systems Analyst Information Technology Services Storage, Output, Legacy *E-Mail: [EMAIL PROTECTED] *Voice: (989) 496-6404 7 Fax: (989) 496-6437 *Post: 2200 W. Salzburg Rd. *Post: Mail: CO2111 *Post: Midland, MI 48686-0994 This e-mail transmission and any files that accompany it may contain sensitive information belonging to the sender. The information is intended only for the use of the individual or entity named. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information is strictly prohibited. Dow Corning's practice statement for digitally signed messages may be found at http://www.dowcorning.com/dcps. If you have received this e-mail transmission in error, please immediately notify the Security Administrator at <mailto:[EMAIL PROTECTED]> ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________
