Hello!

I set up a backup jobs for the secondary AlwaysON replicas on each of my SQL servers as discussed here 

http://social.technet.microsoft.com/Forums/en-US/642a1574-dbec-414e-87a8-d8fa262d0fa8/alwayson-backup-question?forum=sqldatabaseengine

...and database (called "Resources") and log backups were being created properly while the primary replica was a server named Guest1 and the secondary replica was a server named Guest2:

But after exchanging the roles (Guest1 now is the secondary and Guest2 is the primary) the maintenance plan being run on Guest1 now generates the error that even does not show up in the SQL log - the only evidence of this error is the 12291 event in the Windows Application log, which does not tell much of what's caused the error:

Q1: Given that each SQL server has its own maintenance plan containing a backup job to be run on a secondary replica must I do anything to make a backup job continue to run on a new secondary replica or this must happen automatically?

Q2: What should I check to find out the cause of the error?

Thank you in advance,

Michael

• Edited by MF47 Wednesday, September 10, 2014 9:04 AM typo

Hi

Thank you for your question.

I am currently looking into this issue and will give you an update as soon as possible.

Thank you for your understanding and support.

Regards,

Hi Sofiya,

Thank you for the reply!

Regards,

Michael

?

Regards,

Michael

You would need to configure Backup Preferences of AlwaysON availability Group to perform on any replica or other options which suits your requirement.

http://msdn.microsoft.com/en-us/library/hh710053.aspx

http://blogs.msdn.com/b/sqlgardner/archive/2012/07/21/sql-2012-alwayson-and-backups-part-2-configuring-backup-preferences-and-automating-backups.aspx

"You would need to configure Backup Preferences of AlwaysON availability Group" - of course I did it...

If I understand the lack of the answer correctly it's a bug... ???

Regards,

Michael