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

add smart backup page

Browse Source
This commit is contained in:
Olivier Lambert 2016-09-13 12:27:31 +02:00
parent 31846074a2
commit 07ba868a26
2 changed files with 42 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/SUMMARY.md
View File

@ -24,12 +24,13 @@
* [VM import and export](vm_import_export.md)
* [XenServer Patching](patching.md)
* [Docker support](docker_support.md)
* [Backups](backups.md)
* [Backup and DR](backups.md)
* [Full backups](full_backups.md)
* [Rolling snapshots](rolling_snapshots.md)
* [Continuous Delta backups](delta_backups.md)
* [Continuous Replication](continuous_replication.md)
* [Disaster recovery](disaster_recovery.md)
* [Disaster recovery](disaster_recovery.md)
* [Smart Backup](smart_backup.md)
* [User authentication](authentication.md)
* [Built-in](built-in.md)
* [LDAP](ldap.md)

39
docs/smart_backup.md Normal file
View File

@ -0,0 +1,39 @@
# Smart backup
There is two ways to select which VMs will be backup:
1. Multiple VM selector
1. Smart backup
Picking VMs manually can be a limitation if you environment is moving fast (ie having new VMs you need to backup often). Because you needed to edit the previous job and add it.
But thanks to *smart backup*, you have now more flexibility: you won't select specific VMs, but VMs status/tag/placement **at the time backup job will be executed**. Let's see some examples!
## Backup all VMs on a pool
This job will backup all VMs on a pool "Lab Pool" when scheduled:
![](https://xen-orchestra.com/blog/content/images/2016/08/xo5smartbackup1.png)
It means: **every VM existing on this pool at the backup schedule will be backup**. Doesn't matter if you create a new VM, it will be backup too without editing any backup job.
**You can now plan a smart backup on a production pool when only important VMs are**.
Want to narrow the job a bit? See below.
## Backup filters
You can also:
* backup only running (or halted) VMs when the job is executed
* backup only VMs with a tag
Remember the Prod VMs? I added a tag "prod" for each of them:
![](https://xen-orchestra.com/blog/content/images/2016/08/xo5smartbackuptag.png)
Now if you do this:
![](https://xen-orchestra.com/blog/content/images/2016/08/xo5smartbackup2.png)
It means any VMs on "Lab Pool" with the "prod" tag will be backup.