You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Multiple secondary storage in one zone; problem with volume snapshots #9734
We are planning to add multiple NFS secondary storages for backup purpose. And I don't understand the principle of distribution of storage snapshots among secstors.
I created 10 Intsances in one Account and all their volume snapshots exept one were copied to the first secstore. Only one volume snapshot was copied to the second NFS secstore, but I can't create addiditinal snapshots of this volume. I attach logs in comments.
STEPS TO REPRODUCE
Add multiple NFS secondary storages, try to create volume snapshots of different instances
EXPECTED RESULTS
Snapshots are copied based on free space allocation mode to all secstores
changed the title [-]Multiple secondary storage in one zone; problem with volume spanshots[/-][+]Multiple secondary storage in one zone; problem with volume snapshots[/+]on Sep 26, 2024
@Pearl1594 if I set first secstore Read-Only, snapshots are copied to the second secstore. But after I unset Read-Only all snapshots are copied to the first secstore again
when creating the volume snaphots, were they are initiated at the same time i.e, either via API or through recurring snapshot schedule. If that was the case, this could possible happen because the stats collector would not have run to has updated the stats of the secondary store(s) to make the decision that store1 has capacity < than store2. Marking store1 to read only excludes it from the list of stores to which snapshot would be backed up to - expected behaviour.
Activity
top-secrett commentedon Sep 26, 2024
Example of successful snapshot to the first secstore
top-secrett commentedon Sep 26, 2024
Example when first volume snapshot was copied to the second secstore and I try to create the next volume snapshot
[-]Multiple secondary storage in one zone; problem with volume spanshots[/-][+]Multiple secondary storage in one zone; problem with volume snapshots[/+]Pearl1594 commentedon Sep 26, 2024
Regarding the first issue of all/most snapshots going to one store, it would be helpful knowing the following:
top-secrett commentedon Sep 27, 2024
@Pearl1594 1. the same capacity. Second is a copy of first
2. firstfitleastconsumed
top-secrett commentedon Sep 27, 2024
@Pearl1594 if I set first secstore Read-Only, snapshots are copied to the second secstore. But after I unset Read-Only all snapshots are copied to the first secstore again
Pearl1594 commentedon Sep 27, 2024
when creating the volume snaphots, were they are initiated at the same time i.e, either via API or through recurring snapshot schedule. If that was the case, this could possible happen because the stats collector would not have run to has updated the stats of the secondary store(s) to make the decision that store1 has capacity < than store2. Marking store1 to read only excludes it from the list of stores to which snapshot would be backed up to - expected behaviour.