We have a main server and a off-site backup one, both are running PVE. We are using pve-zsync & crontab to snaphsot containers subvols from the main server to 3 pools on the backup (pull mode):
Now, we would like to be able to migrate services temporarily on the backup server to upgrade the main, and therefor in case of failure on the main. So we would like to setup Replication on the backup node (which is no-more a real backup), but we would like to keep pve-zsync jobs for back-in-time.
According to the documentation, this shouldn't be a problem:
We just would like to be sure that our setup is OK for that, or if we have to move pve-zsync away from rpool/data before dealing with Storage Replication
Thanks.
Bash:
rpool/data/daily
rpool/data/weekly
rpool/data/monthly
Now, we would like to be able to migrate services temporarily on the backup server to upgrade the main, and therefor in case of failure on the main. So we would like to setup Replication on the backup node (which is no-more a real backup), but we would like to keep pve-zsync jobs for back-in-time.
According to the documentation, this shouldn't be a problem:
PVE Storage Replication and pve-zsync work completely independent and do not harm each other, as long the following requirements are followed:
- The destination pool / subset are different.
- You do not migrate a guest to an other node.
We just would like to be sure that our setup is OK for that, or if we have to move pve-zsync away from rpool/data before dealing with Storage Replication
Thanks.