Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

687

September 2nd, 2015 04:00

Expiring save set and keeping clones

We are cloning between two Data Domains (CCR) and keep the same retention and browse period the same for both original save sets and the cloned save sets.

Now there is a need to expired the original save sets earlier and keep the clones for the original retention period, but

as soon as we change the status of the original save sets (nsrmm -o) or changing the browse and retention periods (nsrmm -e -w)

the cloned save sets also changes as well.

Even if a save set is deleted via the nsrmm -d -S xxxxx command, the cloned save set is also removed.

Are we doing something wrong? I was under the impression that the cloned save set could be set to expire at a different time than the original.

Is there a way to expire the original save sets without immediately expiring the clones as well?

Any help would be appreciated!

116 Posts

September 2nd, 2015 05:00

Hi,

You have to specify -S ssid/cloneid for nsrmm operations! If you use only the ssid then you are referring to all instances of the saveset.

(You can get the cloneid with mminfo).

Regards,

Istvan

September 2nd, 2015 06:00

How did I miss something so simple?

Thank you, I tested and it work 100%.

No Events found!

Top