How can I duplicate backup settings to a different XO instance? Should I?
-
I have XO running in a few different places. One of them handles backups and I think of that XO as my main version. It occurred to me that if I lost that instance for some reason then it might be tough to restore one of my backups. Therefore, does it make sense to somehow duplicate the backup configuration to other installs of XO so they can see the backups or would they just be confused because they have no record of the ID used for the backup.
Would it make sense to use the XO Config under settings to just copy the entire XO config from one install to another? Is there a downside to that?
It's my intent that the various XO installs all manage the same pool. I certainly don't want them all performing the same backups though so I'd obviously have to disable those backups on the other installs.
Good idea? Bad idea?
-
I do this but its not so that I can have an exact copy of the XOA. I just use it in the rare event I want to modify my XOA like give it more core or more ram. Its easy enough to spin up a community edition XO and then use it to add remove resources, Also I keep my XOA and my XO from source on different host in case one goes down. Nice easy lazy way of still being able to manage my VM's
-
@austinw I have three instances, all on different hosts, one on a host that isn't running XCP.
Is that a weird form of the 3, 2, 1 rule for backups? 3 instances on 2 different host OSs, 1 outside the xcp pool.
I've had times that I needed to tweak the XO instance so it's definitely nice to have another one to do it with. I just realize that if that XO instance went down, like if I lost the host it's running on, then I'd have a tougher time restoring backups because the other instances don't know about the backups. Note, the host running that XO instance is not one my main hosts for the pool, it doesn't run any business critical VMs. Lest someone chastise me for handling backups on the hardware that's running the VMs being backed up.
-
@CodeMercenary I use the paid for XOA and it backups up its config to the cloud so it wouldn't be a problem for me to restore. You can easily set something like that up by backing up to a store location then having that backup to a cloud storage location.
As far as having the XO instances running Im not sure how that would work. I know with NBD storage you should be able to connect to the hard drive with multiple XO's (I think) but the problem I ran into quickly was the fact that when I made a backup using my XOA, the XO from source would see it as a backup without an associated job. If you had three XO's running with 3 different remote storage locations I don't think you'd have a problem with that. Instead you might run into the XO's seeing the 3 different backup jobs running , 2 of which, they don't know about.
I use XOA to backup to a different storage array, then I have that storage backup to the cloud. My backups aren't really up to "standard" but thats all I can do for now. My plan is to make backups to a different storage pool on the same central storage I run my VM's on, back that whole unit up to an off site unit with ZFS replication, then back that backup to the cloud with StorJ. Right now Ive just got the one backup on the same Storage server and the StorJ.