Backup Exec Agent for Microsoft SQL Server
Most Popular | Most Recent
Version : Environment :
Backup Exec 2010 R2 Enhancements and Issues resolved Release Notes
Doc. ID: TECH137044 | 2013-11-20
When restoring a SQL Server Database, the job fails with message "Final error: 0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again".
Doc. ID: TECH162549 | 2013-11-20
Restore job may be executed on an unexpected server when using IP addresses
Doc. ID: TECH209411 | 2013-11-19
When attempting to restore a Microsoft SQL database to a point in time that has been duplicated to a different device, the last backup set available will only be available from the duplicate
Doc. ID: TECH203524 | 2013-11-18
How to change the default staging location for Granular backup and restore jobs.
Doc. ID: TECH171749 | 2013-11-11
After applying Hot fix 38 for Backup Exec 11d or upgrading to Backup Exec 12.x, differential backups fail when using the SQL Agent to backup the Backup Exec Database (BEDB)
Doc. ID: TECH59669 | 2013-11-03
A SQL Point in time restore fails with error 'The log in this backup set begins at LSN xxxxxxxxx, which is too recent to apply to the database. An earlier log backup that includes LSN xxxxxxxxxxx can be restored.
Doc. ID: TECH211899 | 2013-10-25
Backup Exec for Windows Servers (BEWS) SQL (Full Instance) Database Maintenance fails with Error "Dump Database failed."
Doc. ID: TECH161849 | 2013-09-06
Does Backup Exec back up the data from Microsoft SQL .ndf files, as well as the .mdf and .ldf files?
Doc. ID: TECH176833 | 2013-08-29
Database backups performed with the Backup Exec Agent for Microsoft SQL are observedly less than the combined total of the .mdf, .ldf. and .ndf files.
Doc. ID: TECH176831 | 2013-08-27
Redirected restore of SQL 2005 database fails with "Final error 0xe0008492 - Database Query Failure."
Doc. ID: TECH128692 | 2013-08-26
A differential backup of SQL database may report ' Cannot perform a differential backup for database "<name>", because a current database backup does not exist. Perform a full database backup by reissuing BACKUP DATABASE, omitting the WITH DIFFERENTIAL option.'
Doc. ID: TECH128673 | 2013-08-19
SQL Backup failing error "0xe0008443 - one or more SQL Databases consistency checks have failed"
Doc. ID: TECH144230 | 2013-08-14
After a successful restore of a SQL Database, the database is left un-attached when the option for "Leave the database nonoperational" is selected.
Doc. ID: TECH198181 | 2013-07-25
SQL Redirect Restore fails with error "Unclosed quotation mark after the character string 'G:\SQL_D'"
Doc. ID: TECH198367 | 2013-07-25
Clustered SQL resources not listed under cluster name in backup selections
Doc. ID: TECH202542 | 2013-07-25
After upgrading to Backup Exec 2012, individual backup sets are not available for selection when attempting to restore a Microsoft SQL database(s) via FQDN
Doc. ID: TECH188033 | 2013-07-25
The restore wizard for a SQL server, only shows the last 100 SQL backups sets and hence does not allow to run restores from older backup sets.
Doc. ID: TECH190468 | 2013-07-25
During the restore of a SQL database with multiple backup sets the Backup Exec job engine may crash
Doc. ID: TECH198587 | 2013-07-25
SQL server may hang up if some VSS error occurs
Doc. ID: TECH198700 | 2013-07-25