GitHub user nxsbi closed a discussion: If there are multiple Secondary storage, how does CS decide where to place the next snapshot - related to issue
I created an issue https://github.com/apache/cloudstack/issues/9430 and had some questions around the behind the scene process. QUick summary - I had 1 secondary storage. I added second one, and moved (blanaced) snapshots to second storage. Looked like it all worked. However, the next day onwards, what i observed is that no new snapshots were taking palce for the volumes that went to the new secondary storage. Upon inspection of logs, I noticed that the command is trying to mount the folder on the original storage location (which does not exist anymore because it moved to new store). I looked at the snapshot_store_ref table, and see that all snapshots for the specific volume_id are pointing to the new secondary store. How is it that CS is trying to mount the existing (old) server path? Besides the snapshot_store_ref, is there some other palce that CS is looking - it seems it did still thinks the snapshots live on old path. GitHub link: https://github.com/apache/cloudstack/discussions/9431 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
