NuKVM/xen-orchestra
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(backup_troubleshooting): unexpected key/full (#7023)

Browse Source 
Co-authored-by: Jon Sands <fohdeesha@gmail.com>
This commit is contained in:
Julien Fontanet 2023-09-08 09:56:21 +02:00 committed by GitHub
parent bcc62cfcaf
commit 52114ad4b0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/backup_troubleshooting.md
View File

@ -10,6 +10,18 @@ While a backup job is running, you should see activity in the "Tasks" view (Menu
Another good way to check if there is activity is the XOA VM stats view (on the Network graph).
## Unexpected key (full) export
_Incremental Backup_ and _Incremental Replication_ usually produce delta exports after the initial seed.
Nevertheless, there may be some reasons for XO to trigger a key (full) export instead:
- the configured [_Full backup interval_](https://xen-orchestra.com/docs/incremental_backups.html#key-backup-interval) advanced setting has been reached for this VM
- the _Force full backup_ is enabled for the current schedule
- a new disk has been added to the VM (only this disk is completely exported)
- the reference snapshot for this backup job on the source VM is missing
- the previous exported backup/replication is either missing or corrupted
## VDI chain protection
Backup jobs regularly delete snapshots. When a snapshot is deleted, either manually or via a backup job, it triggers the need for Xenserver to coalesce the VDI chain - to merge the remaining VDIs and base copies in the chain. This means generally we cannot take too many new snapshots on said VM until Xenserver has finished running a coalesce job on the VDI chain.