Update rolling_snapshots.md
This commit is contained in:
parent
c0b2be170b
commit
7e443c8aef
@ -8,4 +8,10 @@ This feature is close to Backups, but it creates a snapshot when planned to do s
|
||||
|
||||
[Read more about it](https://xen-orchestra.com/blog/xen-orchestra-4-2/#schedulerollingsnapshots).
|
||||
|
||||
> Advice: due to space usage, rolling snapshots should be avoided for large VMs on non-thin provisioned storages.
|
||||
> Advice: due to space usage, rolling snapshots should be avoided for large VMs on non-thin provisioned storages.
|
||||
|
||||
Example:
|
||||
|
||||
* schedule a nightly snapshot for a group of VM, let's say at 4:30 in the morning. With a max snapshot at 7, you'll have a week of revert possibility
|
||||
* schedule a snapshot every week, but precisely Sunday at 11 PM, with 4 snapshots max. This will let you a month max of revert
|
||||
* and so forth!
|
Loading…
Reference in New Issue
Block a user