Volume change - MBR to GPT

[gatorheelz]

We had a 2 TB MBR volume that we needed to increase in size. We successfully changed the volume from MBR to GPT with GPT Fdisk (https://sourceforge.net/projects/gptfdisk/) and then increased beyond 2 TB.

Since the change, we ran an incremental Veeam backup job and everything seems fine, only the following (expected) informational messages:

4/22/2018 11:40:09 AM :: Disk [datastore1-r10] BackupJob.vmdk size changed, entire virtual disk must be read

4/22/2018 11:40:57 AM :: CBT data is invalid, failing over to legacy incremental backup. No action is required, next job run should start using CBT again. If CBT data remains invalid, follow KB1113 to perform CBT reset. Usual cause is power loss.

Doing the conversion was preferred for us because we have an application installed on this volume, so although moving the data to a new volume and re-mapping network shares wouldn't have been an issue, the application would have been. Also, we wanted to avoid creating a new full backup chain.

Are there any risks with this from a backup integrity standpoint?

[Dima P.]

Hi gatorheelz,

It looks expected: disk layout was modified and, in such case, the full read is required to reset the CBT. The next job run should be ok.