Forum Discussion

Stephen_Roberts's avatar
Stephen_Roberts
Level 2
15 years ago

PST Corrupt File

I have been getting the PST Corrupt file error on several employees for some time now. I’ve been documenting whose PST file is effected and notice there is a pattern with only a few (happens all the time) and the rest seem to happen at random times. This happens to 16 people in an office of 70 people. The problem is that at least ten of the people turn their computers off (that I was able to verify) when they go home and our backup is scheduled at night. The PST files are on a network share to the data server.
 
Anybody have any idea what would cause this behavior for those who turn their computers off at night?
12.x and Earlier
Backup and Recovery
Backup Exec
  • Stephen_Roberts's avatar
    Stephen_Roberts
    15 years ago
    Thanks for the replies.
     
    I know about the registry edit solution. In fact I had that implemented for a time until it was pointed out to me that there was a danger that the PST files could be corrupted and we needed to monitor which ones were being flagged. It is essential that these files get backed up. From what I see these files are not corrupted as I periodically go around to each computer and run a repair and compact on them.
     
    It appears that the solution would be to have two jobs sharing the same tape. One job would use AOFO and the other would append to that tape the backup of the database servers and exchange server. Because of the complex environment we have to ‘juggle’ the sequence in which server is first and so on. We back up to disk and to tape every night. Because we take the tapes off site and they are kept across town we backup essential data that would need to be quickly restored. Therefore we stagger the backup selection on both jobs to avoid trying to backup the same server at the same time. We also have servers that need to be backed up after a certain job runs on that server. As you can see this can be like juggling knives. Adding another backup job to the mix would make it that much more difficult.
     
    The best solution would be for Symantec to allow you to choose which servers to use AOFO in a single backup job and not have this a blanket option for the entire job. This could be implemented the same way the exchange server agent works. You install the AOFO agent on the servers you want to use it on and those that don’t have it are backed up with whatever agent you have installed such as the regular agent or exchange agent.
     
    Again I thank everyone for their input.

6 Replies

Sort By
  • CraigV's avatar
    CraigV
    Moderator
    15 years ago
    Hi there,

    If you're running AOFO this will take care of the files. If not, you can expect to end up with these errors.
    BE 12.5 ships with an AOFO license, but earlier versions like 11D will need it to be licensed.
  • michelangelo10's avatar
    michelangelo10
    Level 3
    15 years ago
    Hi Stephen,

    An easier way to control this, is to have Microsoft add-in (Personal Folders Backup) installed. This way users can have the PST locally stored on their laptop, while another copy will be backed up to a network share using this add-in. This way you can backup the PST files from the network share, without being affected when the backup exec runs the job for the PST files.

    Hope this helps.
    www.microsoft.com/downloads/details.aspx

     

  • Stephen_Roberts's avatar
    Stephen_Roberts
    Level 2
    15 years ago
    Thanks for the quick replies.
     
    I do have BE12 but the AOFO doesn’t play well with the exchange server and Oracle databases. The solution to create several backup jobs isn’t an option for us so we don’t use it although I might revisit this option again since we have made several changes since last trying to use it.
     
    I’ve looked into the add-in as well but most of the people whose PST file is causing the error are ‘over-achievers’ with many PST files and many of those maxed out. I rather not flood the network with their archival methods. Also many would not be able to handle the ‘extra steps’ to fire off the backups.
     
    I was hoping to find out why Outlook doesn’t close the PST files when the user shuts off their computers. I was wondering if the backup was looking at the archival bit or something making it believe the file was open when it wasn’t. I’ll keep digging. This may be a Microsoft problem and not BE.
  • CraigV's avatar
    CraigV
    Moderator
    15 years ago
    Stephen: Symantec tell you not to run AOFO with Exchange as it doesn't clear logs. I tell anybody that when I read they're backing up Exchange with AOFO.
    However, I use it across the board, have restored a crashed server completely, and have all my logs clearing. What works for me, doesn't necessarily work with anybody else.
    Not too sure with Oracle, but I don't use AOFO with our SQL backups we have.
    If you really need to backup those *.pst files, there is the DLO (Desktop, Laptop Option) that comes with Backup Exec. Not sure on the licensing for 12.0, but 12.5 ships with 5 free licenses. This would allow the users to backup their *.psts to a network share, and it would backup the changes.
    However, a quick fix will be to put in an exclusion for those *.pst files. Leave them off the backups if they are not needed.
  • Dev_T's avatar
    Dev_T
    Level 6
    15 years ago
    Hello,

    You can try:

    1  : Open thr registry editor
    2  : HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec\Engine\Backup
    3  :     In the right window, double-click Fail Jobs on Corrupt Files
    4  : Change the     Value Data to 0
    5  : Restart backup exec srvices and perform a backup

    It is not recomended to use AOFO on any databases such as Exchange, SQL, oracle.....etc
  • Stephen_Roberts's avatar
    Stephen_Roberts
    Level 2
    15 years ago
    Thanks for the replies.
     
    I know about the registry edit solution. In fact I had that implemented for a time until it was pointed out to me that there was a danger that the PST files could be corrupted and we needed to monitor which ones were being flagged. It is essential that these files get backed up. From what I see these files are not corrupted as I periodically go around to each computer and run a repair and compact on them.
     
    It appears that the solution would be to have two jobs sharing the same tape. One job would use AOFO and the other would append to that tape the backup of the database servers and exchange server. Because of the complex environment we have to ‘juggle’ the sequence in which server is first and so on. We back up to disk and to tape every night. Because we take the tapes off site and they are kept across town we backup essential data that would need to be quickly restored. Therefore we stagger the backup selection on both jobs to avoid trying to backup the same server at the same time. We also have servers that need to be backed up after a certain job runs on that server. As you can see this can be like juggling knives. Adding another backup job to the mix would make it that much more difficult.
     
    The best solution would be for Symantec to allow you to choose which servers to use AOFO in a single backup job and not have this a blanket option for the entire job. This could be implemented the same way the exchange server agent works. You install the AOFO agent on the servers you want to use it on and those that don’t have it are backed up with whatever agent you have installed such as the regular agent or exchange agent.
     
    Again I thank everyone for their input.