SQL AlwaysOn failover and transaction log backup

[Henrik.Grevelund]

Hi,

I can't seem to find how Veeam is suppose to react if a SQL AlwaysOn has a failover ?

We have a setup running with 1 Daily(application aware) VM backup, and transaction log log backup every second hour.
Works fine normally, but if we do a planned failover the transaction log backup starts ignoring the databases that changed the primary host, and just takes the local model database(which also is in Full recovery mode)

So my question is, what is Veeam suppose to do ?

I would expect that is would just continue after the failover according to this line in the documentation:
At each log processing interval, Veeam Backup & Replication chooses the AlwaysOn Availability Group node for which transaction logs will be backed up.

[PetrM]

Hi Henrik,

Looks like you've already got the answer, you may also refer to this page for the full list of criteria that a node must meet to become a source for transaction log backups.

Thanks!

[Henrik.Grevelund]

Hi Petr,

So if it doesn't backup the transaction log after the failover its a bug ?
Is there any reason to why it shouldn't ?

The customer did a planned failover on another setup, and it continued with the transaction log afterwards, not like the other setup.

[PetrM]

Hi Henrik,

Sounds like a technical issue, please open a support request and share case ID for our reference.

Thanks!

[Henrik.Grevelund]

Hi Petr,

The server that failed/ignored the transaction log backup is a Standard edition using Basic availability groups, the one that contunied is a developer edition using Always On Availability Groups.
Does this matter on how veeam should react.

[PetrM]

I don't think it matters, let's wait for what our support team can find out.

Thanks!

[Henrik.Grevelund]

Hi Petr,

The support case is # 04848026.

The answer from support is :
while in failover, we will not be able run backup and truncation activities again the second node due to the known MS limitation. Warning about inability to truncate logs can be ignored. Removal of the warning has been planned for one of the future releases.

[PetrM]

Hi Henrik! Thanks for the feedback!

[Henrik.Grevelund]

Hi Petr,

Even though support says it works as designed, i still think its a wierd behaviour and it should be fixed.

[PetrM]

Hi Henrik,

As far as I understood, the answer from support was that the behavior will be changed in future releases:

Removal of the warning has been planned for one of the future releases.

Or are you asking about a different issue?

Thanks!

[Henrik.Grevelund]

Hi Petr,

That wasn't how i understod her. I understod that it will continue to NOT backup the transaction log, and remove the warning in the backup job.
So it will SILENTLY just ignore the databases until the next VM backup.

I hope i am wrong.

[PetrM]

Hi Henrik,

Ok, thanks. I'll look into this behavior deeper with our QA. The first idea which comes to me is to make a dedicated informational message about the limitation for basic AON groups instead of warning.

Thanks!