Best practices include tips and recommendations to help you use Backup Exec 12.5 Agent for Microsoft SQL Server (SQL Agent) effectively. For more information about the SQL Agent, see the Backup Exec for Windows Servers Administrator’s Guide.
The following best practices help you use the SQL Agent effectively:
Back up the entire Microsoft SQL Server.
Include the following in the backup job:
Run a consistency check either before or after a SQL backup and after a SQL restore. If you back up a database, transaction log, or file group that contains errors, these errors still exist when the backup is restored. In some cases, these errors can prevent a successful restore. Backup Exec lets you check the logical and physical consistency of the data before and after a backup. SQL reports any consistency check failures in the Backup Exec job log.
Symantec recommends that you run regular database consistency checks to verify the integrity of the database.
Use database, differential, and log backups to maximize your backup window. Combine these backup methods with backup strategies that address the following issues:
How much data loss can you accept if a failure happens between the time of the last backup and the time the loss occurred?
What are your users' expectations when a recovery is required? For example, do they expect a full recovery to the point at the time when the data loss occurred?
Use only the SQL Agent to perform SQL full, differential, and log backups. If you use a third-party application, Backup Exec fails the differential and log backup jobs until you make a new full backup with the SQL Agent.
The following best practices help you with security and database access with the SQL Agent:
Ensure that the Windows user account that you use to back up the SQL instances has System Administrator privileges.
Ensure that Backup Exec has rights to the following registry keys:
Do not apply the credentials that you use to make SQL backup and restore selections to an actual SQL instance. The credentials that you use to make SQL backup and restore selections must be applied to the Windows computer where SQL is installed.
Note:
If you use SQL-generated credentials, you must apply those credentials at the SQL instance level.
| System: Ref.# | Description |
| Vasont ID: v11567209_corsicaweb |
Professional, Server
Windows NT Small Business Server
2000
Windows XP
Pro 5.1, Pro 5.1 64 bit SP1, Pro 5.1 64 bit SP2, Pro 5.1 64-bit, Pro 5.1 SP1, Pro 5.1 SP2
Windows Server 2003
DataCenter, DataCenter (IA64), DataCenter (x64), DataCenter SP1, DataCenter SP1(IA64), DataCenter SP1(x64), DataCenter SP2, Datacenter SP2(x64), Enterprise (IA64), Enterprise (x64), Enterprise SP1(IA64), Enterprise SP1(x64), Enterprise SP2, Enterprise SP2(x64), Enterprise Server, Enterprise ServerSP1, R2, Standard Server, Standard Server SP1, Standard Server SP1 (x64), Standard Server SP2, Standard Server SP2 (x64), Standard Server(x64), Storage Server, Storage Server SP1, Storage Server SP2, Web Server, Web Server SP1, Web Server SP2
Windows Server 2008
DataCenter (x64-64bit), DataCenter (x86-32bit), Enterprise (x64-64bit), Enterprise (x86-32bit), Itanium, Standard (x64-64bit), Standard (x86-32bit), Web Server (x64-64bit), Web Server (x86-32bit)