Forum Discussion

NightSteel's avatar
NightSteel
Level 2
15 years ago
Solved

VSS Snapshot error

I'm having a problem with backup of Exchange public folders:

 

- AOFO: Initialization failure on: "\\$server\PUBLIC FOLDERS". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

 

V-79-10000-11219 - VSS Snapshot error. The volume or snapped volume may not be available or may not exist. Check the configuration of the snapshot provider, and then run the job again.

 

There are no problems with backing up any other information stores.  I've noted, though, that there is an item that seems to be corrupted in the public folders; it refuses to back up and I can't seem to access it any other way:

 

Unable to open the item \\$server\PUBLIC FOLDERS\$Room Schedule\Day_xf8ff_Week_xf8ff_Month-166426484.EML - skipped.

 

I've used ESEUTIL and ISINTEG to check the public folder store for problems, and some were repaired, but the seemingly corrupted item persists, and so does the VSS error.  I've done a lot of Googling on this issue and haven't found anything relevant.

 

Anyone run into anything like this?

  • Hello,

     

    I hope this document helps : http://www.symantec.com/docs/HOWTO24117

    Another flaw of using a AOFO with Exchange agent is that, you wont be able to redirect restore the database. To redirect a snapshot you need the same server name, organisation name and same database name and database path !!

    Thats why I normally call it not recommended :) But in the end its the users choice.

    Hope your backups are still working, if yes request you to mark this as solution, incase no, you can still continue to post and we will be glad to help.

  • 1. Are you using a exchange agent to backup the Exchange database with PF's?

    2. Open file option is not recommended to backup Exchange DB and PF if you are using a Exchange agent.

    3. Is this a share location which you are trying to backup, If yes then AOFO does not backup shares, they directly backup from the drive location.

    Could attach the job log in htm format to review.

  • Yes, I am using an Exchange agent.  Not recommended to use OFO and an Exchange agent, hm?  Well then, I'll turn it off and see what that does.  Thanks.

  • I've had two successful backups, so I guess it's okay now.  Still, I would have rather solved the problem than worked around it.  Thanks.

    Can you perhaps point me to the documentation that says OFO and Exchange agents should not be used concurrently?

  • Please double check to see if the current Windows backup in BE clashed or running at the same time with disk defragmentation or any other VSS process (eg. Virtual machine migration and such).

  • Hello,

     

    I hope this document helps : http://www.symantec.com/docs/HOWTO24117

    Another flaw of using a AOFO with Exchange agent is that, you wont be able to redirect restore the database. To redirect a snapshot you need the same server name, organisation name and same database name and database path !!

    Thats why I normally call it not recommended :) But in the end its the users choice.

    Hope your backups are still working, if yes request you to mark this as solution, incase no, you can still continue to post and we will be glad to help.