Microsoft SQL Server databases have the following limitations:
According to Microsoft, the replication capability of Microsoft SQL Server is not specifically designed to accomplish hot backups. See the Microsoft SQL Server Database Administrator Guide for more information about how to back up and restore in a replication scenario.
The Agent for Microsoft SQL Server has a pre-defined set of rules that governs how databases ineligible for backup are recognized and handled. Backup eligibility is determined by database status and other properties. CA ARCserve Backup posts an error or warning and marks the job as Failed or Incomplete, depending on the following factors:
The following information organized by database status is provided to help you recognize default behavior and, if needed, change the default responses by adding controller values to the Agent settings in the Windows Registry on the computer on which the CA ARCserve Backup Agent for Microsoft SQL Server is installed. For each database status, the default behavior is listed for each selection type, as well as the setting name that changes it. The procedure for creating and setting DWORDS follows the table.
|
Database Status |
If Database is Selected |
If Whole Instance is Selected |
|---|---|---|
|
Standby (read-only, waiting to receive additional restores) |
Message Type: Error Job Result: Failure Setting Name: Standby Explicit |
Message Type: Warning Job Result: Successful Setting Name: Standby Implicit |
|
Mirror (SQL 2005 or later) Failover Mirroring |
Message Type: Warning Job Result: Incomplete Setting Name: Mirror Explicit |
Message Type: n/a Job Result: Successful Setting Name: Mirror Implicit |
|
Suspect (damaged or missing files) using Simple Recovery Model |
Message Type: Error Job Result: Failure Setting Name: Suspect Explicit |
Message Type: Error Job Result: Failure Setting Name: Suspect Implicit |
|
Off-line |
Message Type: Error Job Result: Failure Setting Name: Offline Explicit |
Message Type: Error Job Result: Failure Setting Name: Offline Implicit |
|
Loading |
Message Type: Error Job Result: Failure Setting Name: Loading Explicit |
Message Type: Error Job Result: Failure Setting Name: Loading Implicit |
|
Recovering (in the middle of processing restored data) |
Message Type: Error Job Result: Failure Setting Name: Restoring Explicit |
Message Type: Error Job Result: Failure Setting Name: Restoring Implicit |
|
Missing (database selected for backup no longer exists) |
Error Message Posted Job Result: Failure Setting Name: Restoring Explicit |
Message Type: n/a Job Result: n/a Setting Name: n/a |
|
Inaccessible (specified user cannot access database for some other reason) |
Message Type: Error Job Result: Failure Setting Name: Inaccessible Explicit |
Message Type: Error Job Result: Failure Setting Name: Inaccessible Implicit |
Note: SQL 2005 Point-In-Time Snapshots are strictly ignored.
To change behavior:
0 = Use Agent's default behavior
1 = Warning message posted. Job result is set to Successful
2 = Error message posted. Job result is set to Failure.
3 = Warning message posted. Job result is set to Incomplete.
4 = Error message posted. Job result is set to Incomplete.
Note: Removing a value entry is the same as setting a value to 0.
When the entire instance is selected, Mirror databases do not appear on the database list, and are ignored. For a Mirror database to be explicitly selected for backup, it would have been selected while it was the Principal (Active) member of the Mirroring partnership, and entered the Mirror state due to a subsequent fail-over.
When a database using the Full or Bulk-Logged Recovery Model is in the Suspect state, the Agent automatically attempts to perform a Transaction Log Backup with No Truncation. If this matches the backup options selected, then the results of this backup are the only indicator. If a different backup method is selected, a Warning is posted that a Transaction Log Backup with No Truncation is being attempted instead of using the selected options.
Because the database list is enumerated dynamically when the entire instance is selected, the Agent for Microsoft SQL Server has no knowledge of databases that have been removed from the SQL Server instance.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |