NetBackup agent for the SQL Database
Most Popular | Most Recent
Version : Environment :
MS-SQL Backups failing with status 636
Doc. ID: TECH197144 | 2015-01-19
Restores of SQL databases that contain space characters fail.
Doc. ID: TECH227625 | 2015-01-15
Attempts to perform backup of specific databases whose names contain non-ANSI characters can fail.
Doc. ID: TECH227201 | 2014-12-18
A backup or restore of an MS-SQL FILESTREAM database runs very slow or appears to hang without further processing.
Doc. ID: TECH227154 | 2014-12-17
A comprehensive list of solutions for the most common NetBackup for Microsoft SQL Server database agent backup and restore issues
Doc. ID: TECH74475 | 2014-12-02
DOCUMENTATION: How to create a single MS-SQL-Server NetBackup policy which contains multiple schedules with different retention levels
Doc. ID: TECH90544 | 2014-12-01
Attempting to create a move template to perform an alternate client SQL restore with the NetBackup for SQL but no MOVE and TO stanza pairs are created.
Doc. ID: TECH226719 | 2014-11-29
NetBackup for Microsoft SQL Server browse operation fails with "Gave up trying to open image file."
Doc. ID: TECH226654 | 2014-11-26
NetBackup 7.x Database Agent Compatibility List
Doc. ID: TECH126904 | 2014-11-19
How to manually create a SQL database restore script when having issues creating the restore script using NetBackup Microsoft SQL client GUI
Doc. ID: TECH34223 | 2014-11-18
MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 184.108.40.206 maintenance release.
Doc. ID: TECH215866 | 2014-11-11
NetBackup restores of SQL Server databases fail when the database name contains special characters.
Doc. ID: TECH217094 | 2014-11-04
When the STANDBYPATH batch parameter is commented out in the MOVE script, the NetBackup for SQL agent doesn't fail the restore and reports a successful parent job even though the restore has failed.
Doc. ID: TECH225038 | 2014-11-04
Most common issues and solutions to NetBackup for SQL backups that fail with Status Code 2.
Doc. ID: TECH75456 | 2014-08-28
SQL restore fails with a status 5; dbclient log shows "Error in VxBSAAddToMultiObjectRestoreList: 3."
Doc. ID: TECH224033 | 2014-08-26
SQL Move Script Causes dbbackex.exe Application Fault
Doc. ID: TECH223519 | 2014-08-05
SQL child job fails with the specified client does not exist in the specified policy(239)
Doc. ID: TECH213800 | 2014-06-12
Standby DB's were not skipped during VM with ASC enabled backups and cannot be restored.
Doc. ID: TECH217601 | 2014-05-29
BUG REPORT: NetBackup SQL or Oracle database agents, or user initiated backups are failing with Status Code 41 after upgrading to NetBackup 6.5 or 7.0.
Doc. ID: TECH58164 | 2014-04-28
Status code 23 is reported on SQL backup informational (parent) jobs, even though all child jobs complete successfully reporting status code 0.
Doc. ID: TECH212410 | 2014-04-18