Hi,
We are just setting up two SQL2012 Servers that will be clustered to use Availability Groups. Because some of the databases are large we still want to use Red Gate SQLBackup as we use split backups and SQLBackup gives us uniquely named backup files that maintenance plans will not do. From what I understand if we create a database on one node or restore to it and then take a full backup it would automatically replicate to the other node(s) in the Availability Group. This could be a long process for large databases.
Is anybody using SQLBackup with SQL2012 Availability Groups that could give advice on best practices?
Thanks
Chris
We are just setting up two SQL2012 Servers that will be clustered to use Availability Groups. Because some of the databases are large we still want to use Red Gate SQLBackup as we use split backups and SQLBackup gives us uniquely named backup files that maintenance plans will not do. From what I understand if we create a database on one node or restore to it and then take a full backup it would automatically replicate to the other node(s) in the Availability Group. This could be a long process for large databases.
Is anybody using SQLBackup with SQL2012 Availability Groups that could give advice on best practices?
Thanks
Chris