VMware Cloud Community
scotty_p
Enthusiast
Enthusiast

Map Disk Region - VCB

We use VCB to back up our VMs. We're running ESX 4.0 on our hosts. On a couple of the VMs, during the VCB backup, we get a ton of Map Disk Region events for about 1.5 - 2 hrs, before the backup completes. I've read the vmware articles about this possibly being related to snapshots, but we use vReplicator and some of the VMs have open snapshots all the time. The weird thing is that this doesn't happen on all VMs with open snapshots - only a couple. Has anyone seen this before?

Thanks,

Scott

Tags (3)
0 Kudos
6 Replies
AntonVZhbankov
Immortal
Immortal

That's ok. This is how Changed Block Tracking for VM with hardware 7 works.


---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
scotty_p
Enthusiast
Enthusiast

But the problem is that the VCB backups of our other servers is only taking 10 - 15 minutes and the VMs with map disk region events are taking up to 2 hours. Is there a way to correct this?

Thanks,

Scott

0 Kudos
AntonVZhbankov
Immortal
Immortal

I think you should contact Vizioncore support.


---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
0 Kudos
scotty_p
Enthusiast
Enthusiast

It seems like it's more of a problem with VCB than vReplicator. I've got other snapshots open on other VMs and they're backing up fine. Has anyone else seen this issue?

Thanks,

Scott

0 Kudos
AmarPatel
Contributor
Contributor

I use VCB and I'm getting this as well, I've just started a backup and will update this thread as soon as the backup finishes.

Amar

0 Kudos
timemachine
Enthusiast
Enthusiast

vreplicator and most of other backup softwares that work with vmware have this issue, at times what happens is that the backup software that creates snapshots as part of their backup process are not able to delete the snapsots successfully after the backup completes, this creates teh open snapshots that ur talking about and the next time when the backup is run it takes a long time to first commit the existing snaps and then work on the new snapshots taken for backup process.

So this is a question that the 3rd party vendor has to answer and they need to give a root cause as to why at times their s/w failsto delete the snapshots after the backup completes.

TM

0 Kudos