Agent for Microsoft SQL Server

The following issues relating to the Agent for Microsoft SQL Server are known to exist in this release:

• If an error message appears when you restore and move a database that uses a long file name, rename the database files using shorter file names and perform the restore operation on the database.
• The Arcserve Backup manager and the Arcserve Backup Client Agent must be stopped before uninstalling and reinstalling Arcserve Backup Agent for Microsoft SQL Server if they are installed on the same server as the Agent.
• If a TCP/IP connection fails, or if the Port number has changed, restart the Universal Agent Service.
• To support pass-through authentication of account logon events for computers in a domain, the NetLogon service must be started.
• Due to the Microsoft requirement, when you log into Microsoft SQL Server using Windows authentication to perform Virtual Devices-based backup and restore operations, you must have system administrator rights for Microsoft SQL Server.
• If you uninstall a Microsoft SQL Server instance, some components used by other Microsoft SQL Server instances on the machine may be deregistered, including the Virtual Devices mechanism used to perform backups. If this occurs, the Agent generates Backup Agent Error 511 ("Error creating Virtual Device Interface: COM class not found") within the error AE50015 ("Backup Failed"), or AE51004 ("Restore Failed"). To address this error, perform the following procedure:
  1. Locate the version of sqlvdi.dll that belongs to the newest version of Microsoft SQL Server on the machine.
  2. From a command prompt, change to the directory containing the selected sqlvdi.dll, and enter the following command to re-register the Virtual Devices component and re-enable backup operations:
  3. regsvr32 sqlvdi.dll
• On a primary Server running remote SQL, backup jobs submitted via backup manager to the member Server may run slowly.
• Starting with release 12.0, the Agent for Microsoft SQL Server is now a push Agent. To include SQL database files during a backup job, set the BackupDBFiles registry key to 1. The SkipDSAFiles registry key no longer applies to SQL database files. For more information, see the Arcserve Backup Implementation Guide or the Arcserve Backup Agent for Microsoft SQL Guide.
• When restoring a SQL session, the session size shown in the Restore Manager may be larger than the size of the actual session.
• The Arcserve Backup Agent for Microsoft SQL Server does not support backing up and restoring SQL Server databases where the sum of the characters representing the instance name, the database name, the file group name, and the data file name exceeds 170 characters.
• Installing two or more instances of SQL Server concurrently on the same machine creates multiple versions of the SQLVDI.DLL file, which causes conflicts resulting in database backup job failures. To resolve any SQLVDI.DLL conflicts, ensure all instances of SQL Server are at the same Service Pack, security patch or Hotfix level. You may also restart the failed SQL Server instance to reload the new SQLVDI.DLL file or reboot the machine.
• When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored because Restore by Tree packages all sessions into a single node, while Restore by Session packages all sessions into different nodes.
• After upgrading Microsoft SQL Server or installing additional instances, you must run the Account Configuration utility to update the Agent with the appropriate changes. If you do not run the Account Configuration utility, Arcserve Backup Agent for Microsoft SQL Server will be unaware of the new or changed instances and does not provide you access to additional instances or the additional features of the updated instance. Perform your first backup of the upgraded or new instances immediately after running the Account Configuration utility. For information about account configuration, see the Agent for Microsoft SQL Server Guide.
• In a cluster environment, run the Universal Agent as a Domain Administrator, rather than as LocalSystem to prevent a conflict of access privileges between the Agent and Microsoft SQL Server when backing up Microsoft SQL Server databases.
• When you restore databases to an alternative location, the restore operation can fail and return the following messages:
• Failed to restore backup session. (EC=VDI message: An abort request is preventing anything except termination actions.)
• Or
• Failed to restore backup session. (EC=Microsoft SQL Server Error 3634 (ODBC State = "37000"): [Microsoft][ODBC SQL Server Driver][SQL Server]The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLServer\MSSQL\DATA\test2.mdf'.)
• To prevent this behavior from occurring, perform one of the following actions and then resubmit the restore job:
• Provide full control permissions when you access the following path:
• C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLServer\MSSQL\DATA\test2.md
• Open the SQL Server Agent service, apply the local system account, and then restart the SQL Server service.
• When you perform full backups of data on SQL Server AAGs, the secondary replica Server uses the copy_only backup option when processing the job. The copy_only option cannot record the backup operation on the secondary replica SQL Server because secondary replica Servers do not have write permission to the databases. When the next differential backup starts, SQL Server searches for and locates the most recent full backup data on the primary replica Server. At such time, SQL Server dumps the differential backup data to the most recent full backup data on the primary replica Server. Therefore, when you need to restore data from differential sessions of secondary replica Servers, restore the full backup from the primary replica Server before you restore the differential backup from the secondary replica Server.