Hi,
An old case came into my mind where Veeam support told me this:
if a cluster performs a failover between the image-level backups, VBR will not detect the change in configuration, resulting in the Log backups addressing wrong nodes for the database T-log backups.
My question is:
Has this been fixed in new versions?
Or what is best practice when you are patching nodes of the failover cluster and you don't want to lose a whole day of T-log backups and a new image backup isn't an option?
Dries
-
- Influencer
- Posts: 19
- Liked: never
- Joined: Feb 05, 2019 9:59 am
- Full Name: DBeerts
- Contact:
-
- Product Manager
- Posts: 14316
- Liked: 2890 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: SQL Always On cluster: What happens with the T-Log backup chain when the cluster performs a failover
Hello,
and welcome to the forum. Can you please share the case number for further investigations?
Best regards,
Hannes
and welcome to the forum. Can you please share the case number for further investigations?
Best regards,
Hannes
-
- Veeam Software
- Posts: 21070
- Liked: 2115 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SQL Always On cluster: What happens with the T-Log backup chain when the cluster performs a failover
Hi Dries, to proceed with logs backup after failover, new VM image-level backup is required. The best practice would be to plan the VM backup as a part of nodes maintenance.
Who is online
Users browsing this forum: No registered users and 76 guests