What are the challenges you face when working across database platforms? Take the survey
Options

log shipping error after switched recovery to simple and ful

mweredgate2mweredgate2 Posts: 2
edited June 4, 2015 10:51PM in SQL Backup Previous Versions
We switched a database using log shipping from full to simple recovery while doing some processing and then switched it back. Now the sqlagent job for the backup log command is giving errors:
Backup Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP LOG dbname. Check the backup application log for detailed messages.
and there are SQLVDI errors in the windows log:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2120. Thread=4820. Client. Instance=. VD=GlobalSQLBACKUP_FF2BF300-47EE-482C-BF9C-77697A32869C_SQLVDIMemoryName_0.
SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=2120. Thread=4820. Client. Instance=. VD=GlobalSQLBACKUP_FF2BF300-47EE-482C-BF9C-77697A32869C_SQLVDIMemoryName_0.
Not sure what the correct procedure to do in SqlBackup is for this.
Thankyou,
Mike

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Best guess is that you have not made a full backup since you switched the recovery mode from simple to full.

    Could you please post the contents of the log for the last backup job? SQL Backup generates a log file for each process that it runs. The default folder where the logs are stored is C:Documents and SettingsAll UsersApplication DataRed GateSQL BackupLog<instance name> on Windows 2003 and older, and C:ProgramDataRed GateSQL BackupLog<instance name> on Windows Vista and newer.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.