- Posts: 13
- Liked: 4 times
- Joined: Jul 13, 2010 12:14 am
- Full Name: Justin Grote
I've noticed that if I resize a VMDK, the next time a backup or replica job runs, it has to transfer the entire VM all over again. Why is this? Is this something that is being actively addressed? Is there a workaround like temporarily turning off CBT so that Veeam does the comparison work?
This gives me pause because I have a customer with a particular file server that is very low change rate but high capacity, and they prefer to expand the disk often without downtime instead of reserving a ton of space ahead of time. Unfortunately their WAN link is kind of anemic so the initial sync had to be done out-of-band, and I worry that a VMDK resize would trigger all the data being resent on the next backup or replica job.
- Product Manager
- Posts: 24697
- Liked: 2037 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
This behavior is documented in the Release Notes under Backup and Replication section. Moreover, as far as I know disk re-sizing would invalidate the changed blocks, meaning that the full run will be required anyway.
Not sure that turning off CBT would help either.
Could you please elaborate why your customer doesn't want to use thin disks?
- SVP, Product Management
- Posts: 27723
- Liked: 4719 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Why would not they use thin-provisioned VMDK for this file server? This exactly how thin-provisioning works... but in automated fashion (not a manual process), and without affecting our product. Thanks!jgrote wrote:This gives me pause because I have a customer with a particular file server that is very low change rate but high capacity, and they prefer to expand the disk often without downtime instead of reserving a ton of space ahead of time.
- VP, Product Management
- Posts: 5758
- Liked: 2601 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
Storage execs seem to understand this better than storage customers. Of course, if your a large customer that adds storage every few weeks, well thin provisioning might be for you, since you're always growing your storage anyway, however, for those of us who are a little smaller, and by big storage only every few years, thin provisioning is a curse that means making emergency budget requests for more storage (exactly what the storage vendors want) because you "thin provisioned" what should have been 3 years worth of capacity, only to find it used in 90 days because "it was there".