How can we help you today? How can we help you today?

Assertion Failure When Verifying Backup

Hi,

I have worked around this issue, but on searching the forums I could find only one post relating to assertion failures, which mentioned that they were a rare occurrence, so I thought I'd post details of the error in case they are useful for anybody or for Red Gate.

The error occurred trying to validate a transaction log backup file. I was able to manually validate the file and thus preserve the log chain. It is the first time I have seen the failure, and subsequent backups have all completed successfully.

The details are listed below.

SQL Version: SQL2008 R2 64-bit (10.50.2500.0)
SQL Backup: 6.5.1.9

From the log file:
SQL Backup log file 6.5.1.9

-SQL "BACKUP LOG [CAAP] TO DISK = 'D:\SQLBackup\<AUTO>.sqb' WITH ERASEFILES_ATSTART = 71h, MAILTO_ONERRORONLY = '<email removed>', PASSWORD = 'XXXXXXXXXX', DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 2, COPYTO = '<network path removed>', KEYSIZE = 256, VERIFY "
ERRORS AND WARNINGS


26/03/2012 12:00:03:
26/03/2012 12:00:03: Verifying files:
26/03/2012 12:00:03: D:\SQLBackup\<filename removed>.sqb
26/03/2012 12:00:03:
26/03/2012 12:00:34: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed.
Check that the SQL Server instance is running, that you have the SQL Server System Administrator server role;
and that no other processes are blocking the backup or restore process;
or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
26/03/2012 12:00:34:
...
26/03/2012 12:00:34: Assertion failure (D:\SQL Backup\Components\SDAC 4.10.0.10\Source\OLEDBAccess.pas, line 2183)
26/03/2012 12:00:34:
26/03/2012 12:00:34: Memory profile
26/03/2012 12:00:34: Type Maximum Minimum Average Blk count Total
26/03/2012 12:00:34:
26/03/2012 12:00:34: Commit 838508544 4096 688997 5903 4067151872
26/03/2012 12:00:34: Reserve 1068429312 4096 2223767 3397 7554138112
26/03/2012 12:00:34: Free 6871925653504 4096 20476623931 429 8784471666688
26/03/2012 12:00:34: Private 1068429312 4096 1383206 8246 11405918208
26/03/2012 12:00:34: Mapped 4567040 4096 331223 89 29478912
26/03/2012 12:00:34: Image 51802112 4096 192635 965 185892864
26/03/2012 12:00:34:
26/03/2012 12:00:34: Validation of all backup files failed.

From the event logs:
SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=1988. Thread=2272. Client. Instance=. VD=Global\SQLBACKUP_FB216EC9-9DA5-4F4F-98EC-FF399A3503A5_SQLVDIMemoryName_0.
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1988. Thread=2272. Client. Instance=. VD=Global\SQLBACKUP_FB216EC9-9DA5-4F4F-98EC-FF399A3503A5_SQLVDIMemoryName_0.
MattS
0

Comments

3 comments

Sort by
  • Eddie D
    Hi MattS

    Sorry that you not received a reply.

    Can you please try downloading and applying a patch to SQL Backup V6.5.1.9.

    The patch includes a fix to a problem that a small number of customers have encountered when closing the backup VDI process and opening the VDI for the verify process.

    The patch can be downloaded using this link.

    To apply the patch, please follow the steps below:

    1. Stop the SQL Backup Agent Service.
    2. In the Server Components Install folder, which by default is C:\Program Files (x86)\Red Gate\SQL Backup 6\(local) or <SQL Instance Name>, locate the V6.5.1.9 versions of SQBCoreService.exe and SQLBackupC.exe.
    3. Rename the V6.5.1.9 versions of SQBCoreService.exe and SQLBackupC.exe (for example) to OLDSQBCoreService.exe and OLDSQLBackupC.exe .
    4. Copy in the V6.5.2.18 SQBCoreService.exe and SQLBackupC.exe files extracted from the patch zip file.
    5. Restart the SQL Backup Agent service.
    6. Perform your backup and restore tasks to ensure that all is OK.

    Many Thanks
    Eddie
    Eddie D
    0
  • ChrisAVWood
    Eddie,

    I know that V 7 is just about to be released but the 6.5.2.18 fix sounds like it might help a situation we see on occasion. The backup hangs and then has to be cancelled. It appears that this is happening in the verify part of the job. I had upgraded to 6.5.2.9 with Pete Yeoh's help and added a VERIFYINTERVAL parameter but the issue still persists every so often.

    Thanks

    Chris
    ChrisAVWood
    0
  • Christopher D
    please visit this site . I think it is helpful to you thank you explaining-all-services-sql
    Christopher D
    0

Add comment

Please sign in to leave a comment.