Availability database backup operations
IBM Storage Protect Snapshot backs up each availability database as a single object, regardless of which availability replica is used for backup and restore operations.
An AlwaysOn Availability Group (AAG) requires SQL Server instances on Windows Failover Cluster
nodes. An availability group can have a number of replicas. For example, availability group
1 might have replicas node1, node2, and
node3.
A cluster node might be a replica for one or more availability groups. For example,
node1 might be a replica for availability group 1 and another
availability group.
The AlwaysOn Node is used to manage backups of availability databases. When you work in an IBM Storage Protect environment, the AlwaysOn Node is to be common in a Windows Failover Cluster. This presence enables the management of backups of an availability database in a single location, regardless of the replica that is used to complete the backup.
- Full VSS backups of the primary availability replica
- VSS copy-only full backups of availability replicas
- Microsoft does not support legacy full backups on
secondary replicas. However, IBM Storage Protect Snapshot for SQL Server, does permit you to run a
fullbackup of a secondary replica based on IBM Storage Protect policy. If you use Microsoft SQL Server Standard Edition, Microsoft does not support backups of secondary replicas in an AAG. To back up secondary replicas in an AAG, you must use SQL Server Enterprise Edition. For information, see .
When you run a
fulllegacy backup of a secondary replica, the underlying implementation of IBM Storage Protect Snapshot for SQL Server is to back up the data ascopyfull. However, IBM Storage Protect Snapshot for SQL Server detects the intended full backup operation and applies the IBM Storage Protect policy that is associated with thefullbackup type.Microsoft Management Console (MMC) and CLI views honor the IBM Storage Protect policy that applies to the backup type and in this instance, show the backup type as
full. For information, see Active Secondaries: Backup on Secondary Replicas (AlwaysOn Availability Groups).
For all backup operations of secondary availability replicas, the secondary replicas must be in the synchronized or synchronizing state.
To assist you with scheduling and load balancing, scheduled backup preference settings of availability groups are also available.