A NetBackup for Microsoft SQL Server agent backup fails sporadically with status code 6.
|Article:TECH204104|||||Created: 2013-03-20|||||Updated: 2013-10-28|||||Article URL http://www.symantec.com/docs/TECH204104|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
A NetBackup for Microsoft SQL Server agent backup fails sporadically with status code 6 (the backup failed to back up the requested files) reported. Most often, but not always, this occurs in larger, busy environments.
Specifically, the following error is returned in the dbclient log on the SQL server:
INFO No rows found in SQL request <SELECT replace(convert(varchar, s.backup_start_date,111),'/','') + replace(convert(varchar, s.backup_start_date,108),':',''), replace(convert(varchar, s.backup_finish_date,111),'/','') + replace(convert(varchar, s.backup_finish_date,108),':','') FROM msdb.dbo.backupset s inner join msdb.dbo.backupmediafamily m ON s.media_set_id = m.media_set_id WHERE s.database_name = 'BIGDB' AND m.physical_device_name = 'VNBU0-7568-11744-1347420635' ORDER BY s.backup_finish_date>.
SQL Server 2005
SQL Server 2008
SQL Server 2008 R2
NetBackup 7.1.0.x or 7.5.0.x (through 22.214.171.124)
This issue occurs because NetBackup is attempting to read a particular entry from a system table in SQL server. That entry, however, is related to the backup itself and, on a busy server, may not be generated in a timely fashion. By default, NetBackup will retry (to read the entry) for 5 seconds and, if still unable to read the entry, the above message is returned and the backup fails.
The formal resolution for this issue (Etrack 3060398) is included in the following release:
- NetBackup for SQL Agent 7.5 Maintenance Release 5 (126.96.36.199)
NetBackup 188.8.131.52 is now available - please access the Related Article linked below for download and README information.
Backup fails because the SQL agent can't get the SQL Server backup timestamp within the default wait timeout window.
the backup failed to back up the requested files
Article URL http://www.symantec.com/docs/TECH204104