Backup Chain Cannot Trigger the Rentention Policy

Discovered Version: V8.1

Question

The backup data cannot trigger the retention policy for merging properly, resulting in a long backup chain.

Answer

Root cause

• Due to copy/archive job failed or the running time of the copy/archive job is relatively long, overlapping with the running time of the backup job, continuously occupying timepoints, preventing retention policy from triggering.

• For Vinchin v8.1: Please check if there is a corresponding restore job created. If there is, and it is in a non paused state, the restore job will occupy the timepoint, making it impossible to trigger the retention policy.

• For Vinchin v9.0 and higher: Please check if there is a corresponding restore job created. If there is, the restore job will occupy the timepoint, making it impossible to trigger the retention policy.

Resolution

For copy/archive job:

1. Stop the copy/archive job.

2. Manually run backup job once.

3. After backup job completes, retention policy will trigger merge normally.

For v8.1 restore job:

1. Stop the corresponding restore job.

2. Manually run backup job once.

3. After backup job completes, retention policy will trigger merge normally.

For v9.0 and higher:

1. Delete the corresponding restore job.

2. Manually run backup job once.

3. After backup job completes, retention policy will trigger merge normally.

Notes

To ensure that the backup chain can be merged properly, please resolve the error of the copy/archive as soon as possible after manually triggering the merge, and fundamentally solve the merge problem.