Bob wrote:
> VanguardLH wrote:
>
>> Also, .pst files (and Outlook) were not designed for access across a
>> network. When the network connection is lost, there is no graceful release
>> of the file. The slamming close of the file due to a lost handle can result
>> in corruption of the .pst file. All .pst files should be on local drives
>> where Outlook is ran. So it is possible the user corrupted their .pst file
>> although they were probably just obeying what they were told to do by
>> someone that setup to archive files on networked drives (shame on you).
>>
>> http://support.microsoft.com/kb/297019
>
> Concerning .pst files staying on users desktops. They still must be backed
> up, desktops are not backed up, only servers by Symtec Backup Exec 12.5. In
> house users store their data in their user folder on a file server.
It's been around 4 years since I was at a company that used the enterprise
version of Symantec Backup. It has a client that runs on the workstations
to connect to their backup server. This allows the workstations to get
backed up (usually with incremental backups). Of course, it probably costs
so much for each seat or each block of seats so maybe your company went with
an enterprise-level backup program but went cheap on not getting the
licenses for the clients to put on your workstations.
> The only option I see is to use the Microsoft Backup on their desktops (XP
> professional), run a scheduled backup to - "Choose a place to save your
> backup", and put the archive.pst file on a server that way.
>
> Does that sound better/more safe and just pointing archive.pst file right
> to the server during the auto archive ?
If Outlook is *closed* at the time the backup is made then you have a good
copy of the .pst file to save to backup. If the users NEVER open their
archive.pst file then archiving to that file won't leave an open file handle
on it which means a backup will work (the file won't be inuse). However,
later when the user wants to use that .pst file, you will need to copy it to
their local host so then can open it with the instance of Outlook that is
running local on that host.