SQL backups fail with: Run a new Full backup then run this job again.

[silverskater]

Using BackupExec 2014.1 Rev 1786

Backing up a SQL server with a weekly full and nightly differentials - no log backups as it is not a production server.  The nightly differential backup fails occassionally with: The last full backup of database xxxx was not made by this application.  Run a new Full backup then run this job again.

The differential will then successfully run at the next scheduled runtime without a full backup being run.  A differential manually started will also successfully run.

A sql query that pulls back information regarding all backups of the databases shows only BackupExec backups and there are no backups running of the virtual host.

All the technotes and other incidents regarding this error have referred to another backup being run between log backups but that is not the case here and there are no other backups running.

Any help in explaining this oddity would be very welcome.

[pkh]

If your SQL databases are in a VM and you are doing VM backups, the VM backups will interrupt the sequence of the SQL backups.  You must not run any VM backups between the full and differential SQL backups. Running the VM backups before the full SQL backups is o.k.

[Colin_Weaver]

To add an extra point to pkh's answer

Just because you SQL server is not in production does not mean you should not do log backups - you should only not do log backups based on what SQL Recovery model you have got set.

[silverskater]

Thank you - I omitted to say that the databases are on simple logging.