
This Error is seen in Backup Exec 20.6 and 21.
The error is seen in the following Scenario 1,2,3,4. Fix is for 1 and 2. Scenario 3 and 4 are working as designed.
A private binary is available for (BE 20.6) Scenario 1 and 2. It can be obtained by contacting Technical Support.
A public fix is available for the error received for Scenario 1 and 2 in BE 21.1
It is recommended to upgrade to BE 21.1 inorder to fix this error.
NOTE - Scenario 3 and 4 are normal behavior of the product where, if a full expires (due to less retention) then next incremental would run as full.
Scenario 1 -
Full backup of Hyper V/VMware ran on Day 1
While the next Full backup was running, the Day 1 full backup expired.
This error will be seen for the full backup of Day2
Expected Behavior - Full should not fail if earlier full is deleted or expired
Scenario 2 -
Full Backup of HyperV/VMWare was run on Day 1.
Diff 1 backup was run the next day.
When Diff2 backup was running, Diff1 expired and got deleted. Then Diff2 fails with this error.
Expected Behavior - Diff2 should not fail of earlier Diff1 is expired/deleted. The latest Diff would depend
on Full set so intermediate Diff should not cause the subsequent Diff to fail.
Scenario 3 -
Full Backup of Hyper V/VMWare was run
Incremental backups 1 - 2 - 3 were run as normal
When Incremental 4 was running , the full expired/deleted then this backup would fail and next Incremental should run as full. This is normal behavior.
Scenario 4 -
Full Backup of HyperV/VMware was run
Incremental Backup 1 - 2 - 3 were run as usual
Full expired before Incremental 4 was to start, then Increment 4 would run as full.
This is normal behavior.