Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

VMWare Backup with Agent installed cause SQL backup

Created: 14 Dec 2012 • Updated: 12 Feb 2013 | 2 comments
This issue has been solved. See solution.

Backup Exec 2012 R3, all patch.

We are backuping our sharepoint infra thru the sharepoint agent. In the policy, we are doing:

·         a weekly full database backup

·         a daily differential database backup

·         a daily logs backup

We were also doing VM backups with another policy:

·         VM Full backup on a weekly basis

·         VM incremental on a daily basis

The VM daily backup is causing a major problem; as the agent is installed on this server because of the need of SQL backup, the VM backup is causing a SQL full backup. This is caused by BeVSSProvider, and seems to be as by-design.

This SQL backup is leading to a error:

Final error: 0xe0000363 - The Backup Exec SQL Agent was not used to create the last full, differential, or log backup of this database. You must use the SQL Agent to run a full backup before you can run a differential backup or transaction log backup.

As a workaroud, I changed the VM policy and choose to backup the VM once a week with a full backup, which runs between the last SQL Log backup and the SQL weeky Full backup.

Were we wrong in the way of backuping also the VM on a incremental daily basis? Or is it possible to avoid BeVssProvider to backup SQL (I think for having the system quiesced)?

Thanks in advance.

Comments 2 CommentsJump to latest comment

pkh's picture

You can change the BE provider such that it will do a copy and thus not interrupt the SQL backup sequence.  See Colin Weaver's comment in this discussion

and this document

Service Informatique's picture

Thanks a lot pkh and sorry for the delay.

Adding the -copy flag let me do a log backup everyday!