SQL AlwaysON Jobs

Availability for the Always-On Enterprise

SQL AlwaysON Jobs

Veeam Logoby stb74 » Sat Jul 01, 2017 8:48 pm

Moving to a new Datacentre and changing the native SQL backups to veeam application aware. Had Created two separate ackups jobs for each SQL node as they are in different datacentres but the causes an issue with the Transaction logs if the AlwaysOn fails over to secondary node.

I have came across the odd post that it is recommended to put both SQL nodes in the same job to handle the transaction logs but can't seem to fins any documentation in this, can anyone help out and point me in the right direction thanks.

I have Case # 02207486 opened up with support but I think this is more of an understanding of the configration.
stb74
Lurker
 
Posts: 2
Liked: never
Joined: Mon Oct 19, 2009 4:47 pm

Re: SQL AlwaysON Jobs

Veeam Logoby DaveWatkins » Sun Jul 02, 2017 3:58 am

You absolutely need them in the same job. I tried only having one of our nodes in a job since we only technically need to put one to tape. I can't remember if it failed to truncate logs properly or the backup itself failed, but I do remember it not working as intended
DaveWatkins
Expert
 
Posts: 263
Liked: 61 times
Joined: Sun Dec 13, 2015 11:33 pm

Re: SQL AlwaysON Jobs

Veeam Logoby stb74 » Sun Jul 02, 2017 7:58 am

It all works until the database fails over to the second node, then when the Transactions logs are being backed up they can't as they have been started by the first job. It is a feature I believe to stop other jobs affecting the log backups. I looking for official article/documentation so I can show management why I have changed the setup.
stb74
Lurker
 
Posts: 2
Liked: never
Joined: Mon Oct 19, 2009 4:47 pm


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], rweis and 30 guests