DPM 2010– SQL transaction log backup failing
DPM was protecting SQL databases configured for SQL transaction log shipping.
DPM detects the log shipping when starting to protect a database.
So when you enable log shipping for a database which is already protected by DPM, DPM won’t notice this and will continue with incremental backups which will eventually break log chain sequence.
DPM had no issues protecting the databases configured for transaction log shipping.
But due to network issues the transaction log shipping was stopped.
DPM didn’t notice the transaction log shipping was stopped.
So nor DPM nor the log shipping was cleaning the logs, which kept on growing.
DPM needed to do transaction backup logs again.
To do this, I stopped the protection for the databases and deleted all recovery points on disk. (wasn’t able to retain data due to storage limitations , don’t know if it will work)
After re-adding the databases to the protection group and creating manual incremental recovery point, DPM noticed transaction log backup was needed.
But all Sync jobs failed with the following errors: (express fulls completed successfully)
SQL Error:
BackupMedium::ReportIoError: write failure on backup device 'F:\SQLLOG_PROD\DPM_SQL_PROTECT\VP-SQL01\PROD\PRODUCTION_log.LDF\Backup\Current.log'. Operating system error 112(error not found).
BACKUP failed to complete the command BACKUP LOG PRODUCTION. Check the backup application log for detailed messages.
BACKUP failed to complete the command BACKUP LOG PRODUCTION. Check the backup application log for detailed messages.
Error: 60001 Severity: 16 State: 1 BACKUP LOG is terminating abnormally.
DPM Error:
Creation of recovery points for VP-SQL01\PROD\PRODUCTION on VP-SQL01 have failed. The last recovery point creation failed for the following reason: (ID: 3114)
Execution of SQL command failed for VP-SQL01\PROD\PRODUCTION on VP-SQL01 with reason : BACKUP LOG is terminating abnormally.
Write on "F:\SQLLOG_PROD\DPM_SQL_PROTECT\VP-SQL01\PROD\PRODUCTION_log.LDF\Backup\Current.log" failed: 112(error not found)
. (ID: 30173)
The transaction log shipping ended with a failure. It was possible that the log was corrupted due to this.
We changed the database recovery model from full to simple, and shrunk the log file.
Afterwards we set the database recovery model back to full.
After performing an express full backup the incremental backups worked again!
Both backups were working without a problem now.