Discussions specific to the VMware vSphere hypervisor
- Posts: 53
- Liked: 1 time
- Joined: Oct 12, 2012 12:28 am
- Full Name: Mike Godwin
I restored a VMDK for one of our VMs that got infected with cryptolocker. That part worked great. The problem I ran into was when the off-site backup copy job ran, it sees the restored VMDK as new data (I assume), and it starts backing up the entire thing instead of changes. Is there any way to prevent this in the future? It would save an extra day of driving back and forth to the data center and doing a local sync of the off-site job.
- Posts: 51
- Liked: 10 times
- Joined: Apr 17, 2014 8:25 am
- Full Name: Jens Siegmann
The restored VMDK does not have CBT information, so yes, it needs to be re-read entirely - which does not mean that everything needs to be written and transferred again.
- Product Manager
- Posts: 23005
- Liked: 1560 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Maik is correct, this disk has to be re-read, however only difference should be transferred. What are your read and transferred counters for this disk?
Users browsing this forum: Google [Bot] and 12 guests