We have about total of 50 to 80 VM of RHEL 7 that needs to have scheduled image backup with VDP 6.1
I read that VDP 6.1 has its limitation of scheduling at most 8 concurrent back task at a time.
Is it 1 x backup job with at most 8 x VM in it or 8 x backup job concurrently running???
Also, I read that VDP 6.1 does not scale well and backup job requires regular checking to make sure they won't be stuck at 9x% without completion.
Can anyone comment on how many instance of VDP 6.1 that needs to backup a total of 50 to 80 VM???
It's 8 concurrent VM backups. If my memory of this legacy product serves right, then if you have Job1 with 10 VMs and Job2 with 4 VMs and you happen to kick off both the jobs, 8 would run and the rest would be Waiting - queued
Progress in GUI tends to hang at 92 percent. And you can monitor it by using mccli activity show --active
# Suhas
Can anyone comment on how many instance of VDP 6.1 that needs to backup a total of 50 to 80 VM???
Basically, the answer here is zero. Reason being that VDP went End of Availability over a year ago and is essentially a dead product. So you shouldn't be using it at this time if you don't already have it deployed.
It's 8 concurrent VM backups. If my memory of this legacy product serves right, then if you have Job1 with 10 VMs and Job2 with 4 VMs and you happen to kick off both the jobs, 8 would run and the rest would be Waiting - queued
Progress in GUI tends to hang at 92 percent. And you can monitor it by using mccli activity show --active
# Suhas
I think you are better of with adding another instance of VDP. We have three VDR at this moment.
------------------------------------------------------------------------------------------------
https://tgw.onl/digitalocean/ https://tgw.onl/siteground/ https://tgw.onl/ipage/