Discussions specific to the VMware vSphere hypervisor
Post Reply
afarz
Novice
Posts: 3
Liked: never
Joined: Mar 21, 2015 2:49 am
Contact:

Backup Impact on Converting Disk from MBR to GPT

Post by afarz » Sep 05, 2018 5:28 pm

For various reasons, we're going to have to convert a disk from MBR to GPT in order to expand the drive beyond 2TB in vSphere & Windows. This VM is backed up nightly via a reverse incremental scheme. We're going to do a new full backup before we do the conversion (just in case...more backups the better) but what kind of impact would the change have on backups going forward.

While I assume we could do file level restore from the previous backups; would volume or whole disk restore have to come from a new backup chain? Is it possible to continue on with the backup chain that we currently have or just start a new one? Are there any other considerations I'm not thinking of?

Appreciate any help or guidance. Thanks.

We are using VBR 9.5.

skrause
Expert
Posts: 381
Liked: 75 times
Joined: Dec 08, 2014 2:58 pm
Full Name: Steve Krause
Contact:

Re: Backup Impact on Converting Disk from MBR to GPT

Post by skrause » Sep 05, 2018 8:39 pm

If you restore the entire disk from an old chain, you should be ok on the disk type as it should just overwrite the entire vmdk file.

But you may want to do a test run with a dummy machine to see how VBR reacts to the change in disk type.
Steve Krause
Veeam Certified Architect

Andreas Neufert
Veeam Software
Posts: 3392
Liked: 596 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Backup Impact on Converting Disk from MBR to GPT

Post by Andreas Neufert » Sep 06, 2018 7:57 am

Veeam Backup & Replication backup on image VM level. This backup process do not care about the filesystem or disktype used.
So you can always restore a disk or VM to the stage of backup.

In case of File Level Recovery and Explorers, Veeeam support GPT disks. There should not be any problem with changeing the disk format.
If you want to be on save side, please create and Active Full with the current Job. Specifically if you do disk size changes. Veeam should detect them anyway and trigger a new full from the disk/VM with Change Block Tracking reset.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Exabot [Bot] and 13 guests