-
- Expert
- Posts: 244
- Liked: 37 times
- Joined: Jun 15, 2009 10:49 am
- Full Name: Gabrie van Zanten
- Contact:
Fail-over interfered by backup jobs
Hi,
Learned the hard way that a fail-over can be interfered by standard backup jobs. When you start a planned fail-over, the actual job consists of a number of sub-jobs that each again have to wait for backup resources to be available. So what happened is that just before the end of the first sync, the backups started and took up so much resources that the second sync hung until a number of backup jobs had finished (or killed by me).
Would be great if a failover job, once running, could get priority over backup jobs for the sub-jobs.
(This was all on Hyper-V)
Learned the hard way that a fail-over can be interfered by standard backup jobs. When you start a planned fail-over, the actual job consists of a number of sub-jobs that each again have to wait for backup resources to be available. So what happened is that just before the end of the first sync, the backups started and took up so much resources that the second sync hung until a number of backup jobs had finished (or killed by me).
Would be great if a failover job, once running, could get priority over backup jobs for the sub-jobs.
(This was all on Hyper-V)
-
- Product Manager
- Posts: 14287
- Liked: 2877 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Fail-over interfered by backup jobs
Hello,
what do you mean with "sub jobs" as Veeam does not have "sub jobs"?
Could you describe your job configuration a little bit more in detail? Because in general "restore" has priority over "backup".
Thanks,
Hannes
what do you mean with "sub jobs" as Veeam does not have "sub jobs"?
Could you describe your job configuration a little bit more in detail? Because in general "restore" has priority over "backup".
Thanks,
Hannes
-
- Expert
- Posts: 244
- Liked: 37 times
- Joined: Jun 15, 2009 10:49 am
- Full Name: Gabrie van Zanten
- Contact:
Re: Fail-over interfered by backup jobs
When you perform a failover of a VM (replication) a session is started. In the session you see jobs / steps / actions like: "Applying failover snapshot" or "power on replica" or "performing incremental replication".
What I meant is that in between two of those tasks suddenly the Hyper-V host (source or target I'm not sure) was no longer available because of backup jobs running.
What I meant is that in between two of those tasks suddenly the Hyper-V host (source or target I'm not sure) was no longer available because of backup jobs running.
-
- Product Manager
- Posts: 14287
- Liked: 2877 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Fail-over interfered by backup jobs
Hello,
I just tested whether a backup job an interfere a planned failover and I could not see any issues. I expect that you still talk about "planned failover" and not simple (unplanned) failover. The backup job knows that the VM is in failover state and does no backup.
To investigate what happend with your Hyper-V host, I suggest to open a case at Microsoft. You can also open a Veeam case, but not sure whether Veeam support can help if a Hyper-V host is not available.
Best regards,
Hannes
I just tested whether a backup job an interfere a planned failover and I could not see any issues. I expect that you still talk about "planned failover" and not simple (unplanned) failover. The backup job knows that the VM is in failover state and does no backup.
Code: Select all
Machine is locked by another task
Error: The operation is not allowed in the current state.
To investigate what happend with your Hyper-V host, I suggest to open a case at Microsoft. You can also open a Veeam case, but not sure whether Veeam support can help if a Hyper-V host is not available.
Best regards,
Hannes
-
- Expert
- Posts: 244
- Liked: 37 times
- Joined: Jun 15, 2009 10:49 am
- Full Name: Gabrie van Zanten
- Contact:
Re: Fail-over interfered by backup jobs
Ah, I see the confusion.... no it is not the backup of VM A that interferes with the failover of VM A, but the the backup job of VM B.
A Hyper-V host running VM A and VM B, has only a limited amount of concurrent tasks it can run, if I start failover of VM A it will start the sync and then take a "slot" on that host to perform its task. Then the backup of VM B, C, D, E will start and also take a number of slots, as much as possible. If now the failover of VM A has finished the first sync and is working to start the next sync, the backup of VM F could kick in and take that last available slot. Now the failover has to wait for the backup of either B,C,D,E,F to finish.
A Hyper-V host running VM A and VM B, has only a limited amount of concurrent tasks it can run, if I start failover of VM A it will start the sync and then take a "slot" on that host to perform its task. Then the backup of VM B, C, D, E will start and also take a number of slots, as much as possible. If now the failover of VM A has finished the first sync and is working to start the next sync, the backup of VM F could kick in and take that last available slot. Now the failover has to wait for the backup of either B,C,D,E,F to finish.
Who is online
Users browsing this forum: dbeerts, Google [Bot] and 260 guests