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

SQL Errors 3201 & 3041 appear in Error Log

jcricegpjcricegp Posts: 18 Bronze 3
edited July 7, 2010 7:57AM in SQL Backup Previous Versions
I have SQL Backup v6.4.0.56 installed on a SQL Server 2008R2 Enterprise cluster. The following errors are recored in the Error Log:

Error: 3201, Severity: 16, State: 7.
Cannot open backup device 'SQLBACKUP_BA81D3DC-AE92-409B-9801-3BC9CC60A451'. Operating system error 0x80070002(The system cannot find the file specified.).
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP DATABASE CMS_Batch_Archive. Check the backup application log for detailed messages.

The Red-Gate Backup log for this database is as follows:
SQL Backup log file 6.4.0.56

-SQL "BACKUP DATABASE [CMS_Batch_Archive] TO DISK = '\\GBYQFINP02\J$\REMOTE_BACKUPS\GBYQFINP01_CREDIT_PROD\FULL_GBYQFINP01_CREDIT_PROD_CMS_Batch_Archive_20100705_183059.sqb' WITH ERASEFILES_ATSTART = 4h, COMPRESSION = 1 "

PROCESSES COMPLETED SUCCESSFULLY

7/5/2010 6:30:59 PM: Backing up CMS_Batch_Archive (full database) on CREDIT_PROD instance to:
7/5/2010 6:30:59 PM: \\GBYQFINP02\J$\REMOTE_BACKUPS\GBYQFINP01_CREDIT_PROD\FULL_GBYQFINP01_CREDIT_PROD_CMS_Batch_Archive_20100705_183059.sqb

7/5/2010 6:30:59 PM: Deleting old backup file: \\GBYQFINP02\J$\REMOTE_BACKUPS\GBYQFINP01_CREDIT_PROD\FULL_GBYQFINP01_CREDIT_PROD_CMS_Batch_Archive_20100704_173820.sqb
7/5/2010 6:30:59 PM: BACKUP DATABASE [CMS_Batch_Archive] TO VIRTUAL_DEVICE = 'SQLBACKUP_AA33C3E6-9EB2-41C9-A00F-E1AB79267E59' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (CMS_Batch_Archive), 7/5/2010 6:30:59 PM',
DESCRIPTION = N'Backup on 7/5/2010 6:30:59 PM Server: GBYQFINP01\CREDIT_PROD Database: CMS_Batch_Archive', FORMAT

7/5/2010 6:42:34 PM: Database size : 77.230 GB
7/5/2010 6:42:34 PM: Compressed data size: 17.788 GB
7/5/2010 6:42:34 PM: Compression rate : 76.97%

7/5/2010 6:42:34 PM: Processed 8608824 pages for database 'CMS_Batch_Archive', file 'cms_batch_archive_Data' on file 1.
7/5/2010 6:42:34 PM: Processed 3 pages for database 'CMS_Batch_Archive', file 'cms_batch_archive_Log' on file 1.
7/5/2010 6:42:34 PM: BACKUP DATABASE successfully processed 8608827 pages in 694.752 seconds (96.806 MB/sec).
7/5/2010 6:42:34 PM: SQL Backup process ended.


There does not appear to be a problem with Red-Gate. I have also restored the database successfully and a DBCC does not report any errors.

I have seen the SQL Errors (3201 & 3041) reported in other versions, but in all cases the backups failed. Can I safely ignore these errors?

Thanks,

John Rice

Comments

  • Options
    Eddie DEddie D Posts: 1,790 Rose Gold 5
    Thank you for your post into the forum.

    I suspect that you have encountered a SQL Backup VDI Error 1010. Looking at the SQL Backup log file for the backup task will confirm this, right click the entry in the SQL Backup GUI Activity History and select Show Log.

    When SQL Backup encounters a VDI error, SQL Backup will reattempt the backup task upto and including 4 retries in case one of the following as occurred:

    1. Insufficient continous memory in the SQL Server memory space.
    or
    2. VDI Timeout has occurred. SQL Backup when issuing the backup command to SQL Server, creates the VDI and waits for a reply from SQL Server. By default, SQL Backup will wait for 30 seconds and if no reply is received generate a VDI Error 1010.

    I suspect it is the latter that has occurred, as this error message has been generated:
    Cannot open backup device 'SQLBACKUP_BA81D3DC-AE92-409B-9801-3BC9CC60A451'. Operating system error 0x80070002(The system cannot find the file specified.).

    And the fact that the backup completed successfully. This is expected behaviour so indicates that SQL Backup is operating correctly.

    If you wish to try extending the VDI Timeout time, please follow the instructions below:

    By default the The VDITimeout registry key is not created at install time and cannot be set from the GUI. It needs to be set manually.

    To configure the The VDITimeout registry key:
    Open the registry editor, locate the SQL Backup entries for that SQL Server instance e.g. For 32-bit machines, HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName], For 64-bit machines, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]and add a DWORD entry named VDITimeout. Enter the number of seconds that you feel is adequate for SQL Server to respond, in your circumstances. Note that the default format for the value is in hexadecimal.

    I hope the above helps.

    Many Thanks
    Eddie
    Eddie Davis
    Senior Product Support Engineer
    Redgate Software Ltd
    Email: support@red-gate.com
  • Options
    jcricegpjcricegp Posts: 18 Bronze 3
    I added the reqistry entry for VDITimeout. Apparently it was not enough time to correct the error. I have changed it to 90 seconds.

    By changing the registry setting, I am now getting the VDI 1010 error. And I am see where the backup is being retried and succeeding.

    John Rice
Sign In or Register to comment.