Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
mesheree
Starting Member
2 Posts |
Posted - 2012-09-19 : 17:14:21
|
I have a new SQL Server 2012 AlwaysOn Availability Group on Windows Server 2008 R2 Ent SP1. I'm creating a Maintenance Plan on the Primary Replica which is supposed to do Full (non-copy-only) backups of the only User database.The task is succeeding, the subplan is succeeding, but there is no backup file when it's done.I get the same results when I delete the Maintenance Plan and re-create it from scratch. 'FailPackageOnFailure' and 'FailParentOnFailure' are both set to True on the Subplan and the task. I have also tried enabling 'ignore Replica Priority' in the task, which didn't help.All log entries (SQL Server Log, SQL Server Agent Log, Windows Application Log) only show generic success messages; and I'm not sure where I'd go to get more verbose information. There are other backup jobs, both in this Maintenane Plan and in others, which work fine.What am I missing here?Thanks in advance! |
|
mesheree
Starting Member
2 Posts |
Posted - 2012-09-20 : 20:36:08
|
Turns out this is an AlwaysOn Availability Groups thing.1. The only replica that is capable of Full, non-copy-only backups is the primary replica.2. The default backup preference setting is 'Prefer Secondary'.3. The 'backup' portion of the Maintenance Plan's T-SQL is encapsulated in an IF block which checks the 'preferred replica' flag.So, it looks like I have 3 options:1. Set the primary replica as 'preferred' (and be forced to do the log backups on the primary as well);2. Use T-SQL instead of a 'Backup Database' task (and then I'm the only person on my team that can fix it); or3. Decide that copy-only fulls are good enough, because those can be done on the secondary.None of these scenarios is optimal, and I think it's a little screwy that normal fulls can't be done on a secondary replica in the first place. I hope Microsoft irons this out in the near future. |
|
|
|
|
|
|
|