The Legacy SQL Agent is the client-side installed agent used to protect SQL 2000 and SQL 2005 Instances on Windows XP. As well to protect Sql 2000 instances installed on windows 2003 and 2008(r2) servers only. This is installed with 8.2 and older Windows agents only
Restores for these versions of the applications can be done with all versions of the Unitrends software.
For protection of SQL 2005 Standard and higher databases, use the SQL configuration in the appliance UI.
Did not find any databases for this SQL Server instance
- Verify that there is a connection to the SQL Server instance where the database being backed up/restored was created.
- Verify the SQL Service is running
- By default SQL 2005 doesn't have SQL writer enabled this must be enabled to see the SQL databases
Failure occurs during SQL Server database backup or restore
- Verify above troubleshooting is completed.
- Check the Windows Application Event log for indications as to the nature of the failure.
Failure to connect to SQL Server
- Verify that SQL Server is running on your machine.
- Verify the BPAgent Service is running on the SQL server and that you have checked Community KB 2450 for possible network connection issues to the agent service.
- Verify the Appliance hostname and correct IP is in the local hosts file of the Windows client.
Failure on SQL differential or transaction backups indicating a new full must be performed
- Verify that only the Unitrends Agent is protecting SQL. SQL backups cannot be used concurrently with Maintenance plan Backup, 3rd party SQL tools or other forms of dumps.
- Verify the SQL Tempdb was not removed or cleared
- Verify major maintenance (shrink, reindex, reorg, etc) has not been performed on the DB
- After a cluster failover event, a new full is required.
- After a restore of a database (even to an alternate database), a new full is required
- Perform a new full backup of the SQL database and confirm the issue does not return.
FATAL - Device open failed fileset validation failed[tape #, fileset #] attempting to restore database
- Confirm that the database is being restored to the same device type that was used to back up the database.
No servers listed in the list of backup server names when launching legacy
SQL Server agent
- Confirm that the client’s hosts file has been updated to include the backup system name and IP address.
Changes to the SQL Server agent backup schedule not automatically applied to the existing associations where the modified schedule was assigned (legacy SQL)
- Delete the current database schedule association and reassign the schedule. Modifications to the backup schedule do not affect associations that were created prior to the modification.
SQL Server transaction log shows status as successful but the system manager shows status as (Restoring)
- If this state occurs, restore the database to the latest possible time and perform the restore again. This could have occurred due to a backup and restore of another database taking place at the same time. Ensure a SQL restore is done only when no other backups are taking place.
Restored SQL Server database shows as loading in the Enterprise Manager
- If the SQL Server Agent is being used in conjunction with another SQL Server maintenance plan, the transaction logs get out of sequence. The database is then seen in loading state. This database should be removed and a full restore along with any differentials must be performed. This restores the transaction log chain.