![]() ![]() Also, since it must refer to a previous backup with a specific CBT value, Iperius cannot “append” new backups to the existing ones, because the CBT has been reset, so it will continue to return the error. If an error occurs in the backup of the virtual machines within Iperius, and the error is with the CBT, it will be necessary to perform a further operation (as well as reset the CBT in the virtual machine settings) on the destination folders of the incremental/differential backup. How to restart Iperius virtual machine backups after a CBT error: Of course, for this operation it will be necessary to make sure that there are no active snapshots and perform the operation with the virtual machine turned off. After performing this operation, if we need to perform incremental or differential backups, we will have to re-enable the CBT by resetting it to true. This procedure may be necessary if, for example, errors occur during incremental or differential backups. Re-enable CBT for incremental backup of virtual machines: All subsequent incremental / differential backups will refer to the IDs of the changes generated after the full backup. Note: the first backup that is performed after restoring the CBT is a full backup. If you use a backup application that uses the Changed Block Tracking feature (see: Backup of ESXi, vCenter, ESXi Free and Replica with Iperius Backup), you must reactivate the CBT manually. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |