09-16-2015 06:43 AM
We are running a single Exchange Server 2013 SU5 running on Windows Server 2012 R2
Backup provided with BackupExec 15 (14.2 rev 1180) running on Windows Server 2012 R2
All went well until we installed the recent Backup Exec "Feature Update". The Exchange backup fails with
Auftrag beendet am Mittwoch, 16. September 2015 um 13:45:38 Abschlussstatus: Fehlgeschlagen Endgültiger Fehler: 0xe0008516 - Die für den Snapshot angegebene Datenbank wurde nicht gesichert, da die Datenbank nicht bereitgestellt war. Endgültige Fehlerkategorie: Systemfehler Zusätzliche Informationen zu diesem Fehler finden Sie unter der Verknüpfung V-79-57344-34070
The linked KB article leads nowhere.
Exchange itself runs without any problems and certainly the database IS provided.
I upgarded all agents and tripple checked the login configuration, rebooted both the backup server and the exchange server. I even created a new full backup job that only selected the entire "Exchange Information Store" with a single "Mailbox Database" and "PublicFolder Database".
Same Error
I did a thorrough research that resulted in "check your VSS writers" most of the time, so I checked the VSS writers with
vssadmin list writers
and I get a list of healty writers, but there is no “Microsoft Exchange Writer” listed as is presumably shuld(?)
I tried with and without the "granular" option.
I'm quite clueless now how to proceede. The backup log is attached for a full backup from before the update that went well and one after the update that failed.
Thanks for any help on this,
Robert
Solved! Go to Solution.
09-16-2015 10:02 AM
Check that the registry key is enabled on the Exchange server HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters\EnableVSSWriter = 1
and then restart the Microsoft Exchange Replication Service on the Exchange server
09-16-2015 10:02 AM
Check that the registry key is enabled on the Exchange server HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters\EnableVSSWriter = 1
and then restart the Microsoft Exchange Replication Service on the Exchange server
09-16-2015 09:20 PM
In addition to above, preferable to backup Exchange (Information Store) in a separate job with AOFO unchecked.
09-17-2015 12:36 AM
Bull's eye!
This one seems to solve my problems. The "Microsoft Exchange Writer" suddenly shows up in the "vssadmin list writers" command and the backup streams gigabytes of data right now.
It still makes me wonder what happened during this "Feature Pack 1" upgrade, since installing this on the backup server certainly did not change the registry on the exchange server nor did it recycle the service. Maybe that problem had existed before and BE stopped using some workaround for it.
Anyway, in a couple of minutes I will probably have a full backup again.