Skip to main content

vMProtect - Impact of rolling back to previous instance of a .TIB file.

Thread needs solution

We have had to rollback a vMProtect .TIB file to a previous version (using rsnapshot) due to an 'operator error' with the master .TIB File that vMProtect was backing up to. Accidently deleted.

The backup job was configured to use CBT.

QUESTION: How will vMprotect deal with this re-backing up changed blocks to this rolled back .TIB file?

Can vMprotect's CBT usage deal with this and re-backup all changed blocks? I'm assuming yes as my understanding of CBT is that every block is date/time stamped and vMprotect should be able to identify changed blocks on source disk relative to the date/time stamp of what is the (rolled back) .TIB file.

ANY GUIDANCE WOULD BE REALLY APPRECIATED....

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Greg,

Each recovery point in the backup archive contains CBT ID in its meta details. This CBT ID is compared with the current CBT ID (created during snapshot) of the backed up VM and thus the backup is able to track down the changes of the VM no matter what you do to the archive (as long as it contains at least one recovery point). The situation you describe is similar to simple deletion of some of the recovery points from the existing archive, and in this situation CBT is not lost, so your new backups should be running fine.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager