Skip to content

Commit d65a3b9

Browse files
author
João Jandre
committed
add backup chain by schedule details
1 parent 64421f1 commit d65a3b9

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

source/adminguide/kboss_plugin.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,9 @@ Backup Chain Management
106106
-----------------------
107107

108108
The size of the incremental backup chain is determined by the `backup.chain.size` zone-wide configuration; furthermore, it may be overridden on the
109-
offering level. Once the backup chain reaches the configured size, the next backup will be a full backup and a new chain will start.
109+
offering level. Once the backup chain reaches the configured size, the next backup will be a full backup and a new chain will start. Moreover, the backup chains
110+
are currently separated by schedule ID, with manual backups having their own backup chain. Thus, if a user has a VM with two backup schedules, and also takes manual backups of the VM, it will have three
111+
concurrent backup chains.
110112

111113
If users wish to finalize the backup chain early, the **finishBackupChain** API may be used. It is also available through the VM instance interface on the GUI.
112114
Additionally, this API can also be used when the VM is in the `BackupError` state to normalize it. Most times ACS is able to normalize it; however, the VM may be unable to be recovered

0 commit comments

Comments
 (0)