Impact when a full backup is created by executing incremental backup task in boot environment

Details

Our products create a full backup instead of an incremental one when the backup target disk's configuration changes, as the incremental chain cannot continue. This also applies to backups executed in a boot environment.

When creating a Deploy USB or boot environment using Deploy Media Creator, a full backup task deletes the previous image set (both full and incremental backups) before starting anew. The latest full backup is saved in the second volume’s root folder (labeled "Image Data").

However, if specific conditions arise during incremental backup, a full backup is created without deleting the earlier image set.

Conditions for the issue to occur

Before running an incremental backup, the following steps are performed to modify the disk layout:

- Use [Disk Management] to shrink the C drive and create a new volume in the unallocated space.

- Delete the recovery volume at the end and extend the C drive.

Then, boot into the boot environment and run the incremental backup task to generate the backup file.

Issues

If earlier image sets remain, Error -702 (insufficient space in destination) may occur. 

- When there is enough space, a full backup is created. In the root folder of the second volume ("Image Data").

- If both full + incremental backups from earlier generations and the latest full backup exist, deploying will use the latest incremental from the earlier generation.

- If both the earlier full backup and the latest full backup exist, deploying will show a "target disk not identical to source" message, causing the deployment to fail.

The Behavior with multiple image sets 

The following occurs, but applying the workaround ensures smooth backup operations: 

- Move or delete the latest image set. Deployment then uses the latest incremental backup from the earlier generation if only the older image set remains.

- When creating a new incremental backup, it uses the latest backup image for subsequent increments. 

Example: After creating an incremental backup:

-The top two files belong to the earlier generation.

- The bottom two files are the latest image set.

- ".aiv" is a full backup, and ".aii" is an incremental backup.

  A953C99C-4B5A-42A1-B594-297498564B4C_6430305F30303030315F6930303030302D3030303030.aiv
  A953C99C-4B5A-42A1-B594-297498564B4C_6430305F30303030315F6930303030312D3030303031.aii
  A953C99C-4B5A-42A1-B594-297498564B4C_6430305F30303030325F6930303030302D3030303030.aiv
  A953C99C-4B5A-42A1-B594-297498564B4C_6430305F30303030325F6930303030312D3030303031.aii

After creating a full backup with the latest backup image, performing incremental backups again (with more than one incremental backup created) resolves the issue. Deployment will then successfully use the latest incremental backup. 

Workaround

To resolve the issue, move or delete the earlier generation image set and run a full backup task in the boot environment.  

Operating Procedures

1) Right-click the Windows Start menu > Disk Manager. If the second volume "Image Data" lacks a drive letter, assign one.  

2) Open Explorer, select the assigned drive, and do one of the following:  

 - Create a sub-folder and move the earlier generation image set there.

 - Move the earlier generation image set to the Desktop.

 - Delete the earlier generation image set.

Target Product

- ActiveImage Deploy USB 4

- Actiphy Rapid Deploy Deploy Media Creator

(39984790244505)