05-28-2012 08:36 PM
I am getting this error on my exchange server after each backup with BE 2012. Full log below.
I ran "VSSADMIN LIST WRITERS" on my exch server and all writers were stable with no errors. I can only find threads on this that mention exch 2003.
Detailed log below:
Backup- EXCHS01
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\EXCHS01\Microsoft Information ...Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS...
Backup- \\\EXCHS01Microsoft Information Store\Mailbox Database1
V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full b...V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the...
05-28-2012 08:50 PM
Try running a full backup of your Exchange.
05-28-2012 11:21 PM
Yes a full backup has been run previously using the RAW for exchange. It was fully successful. As I am in the testing phase of familarising myself with the new 2012, i have also run a VM-level backup of this server which is first to run an incremental after the weekly full backup (using the RAW/agent), so is it possible that because I am running 2 backups of this server (one being agent-only, the other being the whole VM) that the incrementals running with the agent are getting confused as its expecting a FULL backup was done last?
05-28-2012 11:34 PM
I don't know whether your situation is similiar to that when you backup a SQL database in a VM. In that case, when you backup the VM, the last backup is not recorded as being done with BE, so the next incremental or log backup of the SQL database using the agent fails. The backup sequence cannot include a VM backup.
I would suggest you do not include a VM backup in your backup sequence of Exchange using an agent.
05-28-2012 11:51 PM
...I'd suggest you do 1 of the following, even if your Writers aren't showing any errors:
1. Reboot the server.
2. Reregister the VSS *.dlls:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
It could be that the Writers are giving an error, and somehow returning to a running state. I've had that once!
If the backup server isn't the Exchange server, run the vssadmin command on the backup server too in order to make sure its writers are stable!
Thanks!