We have a Veeam Worker for every node in the VME cluster.
However, if we have a backup job that includes multiple instances across multiple hosts then it appears the job only selects a single worker for the whole job.
This means that VMs on the same host as the worker get backed up 'hot-add' style and the rest are 'NBD'. This generates the 'Performance may be affected' warning.
Is it possible to use multiple workers per job, to get the best performance and possibly run the streams in parallel?
-
phil_nz
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Mar 12, 2018 12:57 am
- Full Name: Phil Snowdon
- Contact:
-
EvgenyBaev
- Veeam Software
- Posts: 51
- Liked: 5 times
- Joined: Apr 11, 2019 11:06 am
- Full Name: Evgeny Baev
- Contact:
Re: [BETA] [HPE] HPE-VME Single Worker per Backup Job?
Hello phil_nz
Thank you for your insightful question. You have identified a bug in our worker selection logic.
Unfortunately, there is currently no feasible workaround without rebuilding the plugin. However, we will address and resolve this behavior in the upcoming 1.0 release, ensuring it works as expected.
Thank you for your insightful question. You have identified a bug in our worker selection logic.
Unfortunately, there is currently no feasible workaround without rebuilding the plugin. However, we will address and resolve this behavior in the upcoming 1.0 release, ensuring it works as expected.
-
Sloan
- Enthusiast
- Posts: 32
- Liked: 3 times
- Joined: Jan 14, 2013 6:40 pm
- Full Name: Sloan Essman
- Location: Houston, TX
- Contact:
Re: [BETA] [HPE] HPE-VME Single Worker per Backup Job?
I was wondering about this same behavior in my testing. Good to hear that it should be addressed in the official release.
Sloan Essman
Lead Specialist - Backups and Data Protection
Energy Transfer Partners
Lead Specialist - Backups and Data Protection
Energy Transfer Partners
Who is online
Users browsing this forum: Chris.E and 1 guest