Resize vhdx

[mr2nut123]

Just a quick question. When I resize a gen2 machine on the fly (shrink from disk management inside the vm, then shrink in Hyper-V Manager), Veeam backups then fail because the block size is different. Is there any way to update that backup job to succeed rather than having to create a new job?

[Vitaliy S.]

Try to initiate a new full job pass for this VM, in this case new job creation might not be required.

[mr2nut123]

Cheers. Is that a case of right clicking the job, then selecting active full..?

[Vitaliy S.]

Yes, that's right. Please be aware that it will initiate full backup for all VMs in the job. Please let us know how it goes.

[mr2nut123]

Thanks, I'll give it a try next time I'm at the clients. Feel free to close the thread now

[jhowlett]

As the topic states really, I have not really found a concrete answer to this, does it invalidate your backups?

Or will it just carry on backing up as normal?

[DGrinev]

Hey James and welcome to the community!

You should initiate an active full run or the job will fail.
Please review this thread for additional information. Thanks!

[jhowlett]

Thanks good to be here!

So.. after a full backup all my history and backups will still be intact?

[DGrinev]

James, can you elaborate a bit, did you resize the disk when the machine was turned off or on?

[jhowlett]

OK no problem, so a bit of background, We have Veeam B&R 9.5 and we have a HyperV cluster which is backed up with Veeam, we also have LUNs which are backed up by Veeam and everything looks good.

The question is:

If I expand any of the backed up sources HyperV or Agent LUNS "which will change the drive geometry" will Veeam see this as a new disk and not the original thus causing it to remove all current history / snapshots and backups etc?

I have not actually tried this yet luckily but would like to think this is a normal operating model and did not want any surprises

[DGrinev]

There are 2 possible scenarios:
1. Expand was initiated on the live system - in this case, it's mandatory to shutdown the VM by using Hyper-V Manager (don't reboot it via Guest Restart), then manually initiate an Active Full.
2. Expand has been performed on the turned off machine - this way you can continue the backup process without triggering a new active full. Thanks!

[jhowlett]

Thats great thank you

[jamesbranch]

Hi all,

Just a quick one... if/when a volume/disk changes size on a VM, do we need to take a new FULL backup??

Thanks
James

[Natalia Lupacheva]

Hi James,

It is not required to run Full backup after disk resize.
The first backup process after disk resize will be run as usual incremental backup.

Thanks!