Is it possible to rename a volume collection without creating orphaned snapshots on the DR side?

[nathanielbrand41]

We want to rename one of our volume collections.  However, we're currently replicating to an off-site DR via a VPN link.  If we rename the volume collection, will it orphan the snapshots on the DR side?  And if so, is there a way to rename the volume collection without orphaning the snapshots on the DR side?

Same goes for snapshot schedules - if we were to change a snapshot schedule (say the hours it takes place in, or the number of snapshots being taken, or what time the snapshot is taken), will that orphan the data on the DR side?  As with the first question, if so, is there a way to do so without orphaning data on the DR Nimble?

Thanks for the help!

[rugby0134 · Accepted solution]

In order to change the name of the volume collection, the "replicate to" field of each schedule must first be set to "none".

After you edit the volume collection, you can set the replicate to field back to the replication partner.

The volumes do not need to be re-seeded on the downstream array because they are already there. However, the snapshots belonging to the old volume collection name will be orphaned. This means that they will need to be manually removed from the downstream array as time progresses since they no longer fall under the current retention schedule.

You will be able to locate these snapshots under the individual volumes. The new volume collection will only show the newly replicated snapshots.

[chris24]

You can change the volume collection name and schedule without any issues, no need for reseeding.

However all the snapshots prior to the name change will become orphans / un-managed and need to be manually deleted.

Infosight > Wellness tab will list all the affected volumes, if there is a lot of them you can script the deletion.