You can configure to select an availability replica on which to run a backup.
When an availability database is replicated across multiple availability replicas in an availability group, a mechanism is required to select a single replica on which to run a backup operation instead of backing up all replicas. This mechanism can also offload the backup from a primary replica to a secondary replica for load balancing. When databases failover, backups must continue to run from other replicas for high availability.
Microsoft SQL Server 2012 provides a set of configuration options that enable these functions. You can use the Tivoli® Storage FlashCopy® Manager GUI to set these options.
To specify whether scheduled backups are run on the primary or secondary replica at the availability group level:
tdpsqlc backup TestDb1 full /ALWAYSONPriority
When this scheduled backup command is run, Tivoli Storage FlashCopy Manager queries the SQL Server to determine the highest-priority availability replica that is active or online, ordered by preference. If the replica meets the specified criteria, the replica is backed up. Otherwise, the backup operation ends and a message is added to the log to indicate why the replica was not backed up.
An administrator can create a common backup schedule to run on all availability replicas. When the backup schedule starts, each tdpsqlc command queries each replica to determine whether it is to run the backup. Only one of the scheduled backups runs the backup.