Backup Exec 2012 - Exchange 2010 backup fails

Hi

Please check the link below ,& try to add the keys in registry as mention in the documents ,Also note the link is for the issue in in BE 2010 but then you can try as it could be also a case that it could be an issue in BE 2012

http://www.symantec.com/docs/TECH186423

Thanks

Hi..

May be this link can solve your problem

http://www.symantec.com/business/support/index?page=content&id=TECH128187

Do you have another backup or  replication software running in between the full or incremental, the error generally indicates that between Full and incremental something else may have caused a mismatch in the logs, which generally happens when something else is touching your Exchange database in between your two backups

The backups are written to a Datadomain storage System DD610. Is is connected by CIFS. The CIFS folder is exclusive for the backup job. After the backup is done the Datadomain replicates the backup to an offsite second Datadomain system.

First I will try to run a new full backup and a new incremental backup.  If this does not solve the problem I will take a look at the register keys.

 

I'm having the same issue, been trying to fix this with a Symantec engineer for over a month.  Tried both links above, to no success.  I'm being asked to run a repair on the DB, though it's only been in service for a couple of months.

If you run a full backup non-GRT, then a full with GRT, the incremental will then run successfully, but only ONCE.  I've never had any more luck than that.

Just curious:  OP was your BE2012 a full install or just an upgrade?

Mike

Hi MikeKaro,

We did a fresh install of BE2012 and Windows 2008 R2. 
This weekend the backup ran but failed again.This time  there was a problem with the VSS writer. 

Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status.

The backup job is currently running again. I changed the VSS writer to Microsoft VSS Writer.

JvL235, so does that mean you're incrementals are working now?

Mike

We have also found that our Exchange server gets into this VSS writer funk after a few backups with BE2012 and rebooting the exchange server fixes the problem. When you changed the VSS Writer did you also reboot the server? If so, it may have been the reboot that actually 'fixed' it.

Thanks for the replies. Very helpfull.

After re-register the VSS and reboot the VSS problem are gone. I dsuccesfully did a full backup of Exchange 2010 last night. I started a new incremental backup a few minutes ago. I'll keep you posted.