Since XOA runs as a virtual machine,
you can take all the normal steps available to assure the safety of a VM:
- Make a backup regularly (full or incremental)
- Duplicate the VM through a Disaster Recovery or Continuous Replication job
- Take a snapshot
Specific steps for XOA VM:
- Use the XOA XO Config feature to backup your XOA settings to be able to restore them on any XOA VM
Now that your XOA VM is secured, let's see the best way to manage losing your XOA VM:
If you lose the host supporting your XOA VM
- If the XOA VM was on a shared storage, then you should be able to restart it on another host on your pool
- If the XOA VM had been stored locally on your host or your host was alone in its pool, then you will need to deploy another XOA VM (this step can be taken preemptively, you are not limited in the number of XOA VM that are running on your infra structure). The new XOA VM will need to be registered with the same Vates Account and to be updated. Once this is done if needed you can migrate your XOA license from the old VM to the new one.
- If your running XCP-ng 8.3 you can also use XO-lite directly by connecting to you master host IP to manage your VMs.
Other important notions:
- XOA free is providing all the VM management features without impacting anything in your main XOA VM. All the communication and actions taken at VMs level are done through API calls to the pool master so anything done through one XOA will be directly visible to any XOA in your infrastructure.
- Never use multiple XOA to do backup on the same VMs as this could cause the backup to fail
- Duplicate the VM through a Disaster Recovery or Continuous Replication job
- Take a snapshot
Specific steps for XOA VM:
- Use the XOA XO Config feature to backup your XOA settings to be able to restore them on any XOA VM
Now that your XOA VM is secured, let's see the best way to manage losing your XOA VM:
If you lose the host supporting your XOA VM
- If the XOA VM was on a shared storage, then you should be able to restart it on another host on your pool
- If the XOA VM had been stored locally on your host or your host was alone in its pool, then you will need to deploy another XOA VM (this step can be taken preemptively, you are not limited in the number of XOA VM that are running on your infra structure). The new XOA VM will need to be registered with the same Vates Account and to be updated. Once this is done if needed you can migrate your XOA license from the old VM to the new one.
- If your running XCP-ng 8.3 you can also use XO-lite directly by connecting to you master host IP to manage your VMs.
Other important notions:
- XOA free is providing all the VM management features without impacting anything in your main XOA VM. All the communication and actions taken at VMs level are done through API calls to the pool master so anything done through one XOA will be directly visible to any XOA in your infrastructure.
- Never use multiple XOA to do backup on the same VMs as this could cause the backup to fail