GitHub user Jayd603 edited a comment on the discussion: Restoring volume snapshots from secondary storage in new CS cluster
Looks like if I want to keep both sites mostly separate, I will need to do some scripting to keep snapshots in the db up to date. Otherwise I need to do a full multi-region installation and connect the actual mariadb machines with replication etc. etc. Do-able but now there are greater odds of database issues. Not sure I want to do all this for just snapshot copying to a remote zone. Update: Looks like the process of doing this is quite agonizing , much has to be created in the second clusters db in order to get any UI functionality to restore snapshots from a remote systems storage. It even wants vm instance IDs etc. I realize I can probably just use the qcow2 images to create new VMs but obviously I was hoping for something a little easier and done through the UI. Perhaps the NAS backup functionality will work better for this type of thing - checking that out... ```Users should ensure that the entry for the expunged or unmanaged instance is not purged from the database, as the backup framework relies on it to function correctly.``` So.. if I have backups from "NAS Backup" plugin on one cluster and want to restore to another - I can't without modifying the database with the old records from the original cluster? Gross I was trying to keep these two clusters completely separate and still have a viable restore option if the original cluster is completely lost. Perhaps if I try to restore a backup from backup and restore it will still prompt for all the needed information and be able to restore, I guess all I can do is try that. GitHub link: https://github.com/apache/cloudstack/discussions/12254#discussioncomment-15261629 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
