Timeline and versioning policy

Backup policies should be managed for configuration changes and recovery points. Each time a data scope, exclusion rule, encryption key, object storage, or retention policy is adjusted, a new configuration version should be formed and the reason for the change should be preserved.

Recommended Practices

1. Use app.toml, bak.toml, prj.toml, and the necessary request file as a configuration snapshot.
2. Copy the snapshot before modification and record the time, operator, changes, and applicable backup tasks.
3. After the configuration changes, execute dry-run before generating a new backup point; do not overwrite the old configuration or the old backup point.
4. Record the configuration version along with the item identification, time, and remote key of the backup file.
5. When restoring, first select the restore point that matches the target data time, and verify with the corresponding configuration snapshot.

Retention and rollback

Local and remote retention policies should be set separately and at least one historical version validated for recovery should be retained. Before rolling back the configuration, perform it in the test directory to confirm that the path, permissions, key, and object storage destination are available.

The timeline policy is used in conjunction with the scheduling and retention policy. For the actual command, see Command Reference.