jaspreet101
IS-IT--Management
Hi,
I'm writing a script for to clone the data and having issues reset the browse and retention policy of the original media.
Here's what I'm trying to achieve:
1. mminfo to query the data having savesets having one copy and backed up in last 24 hours.
2. nsrclone (with the list of ssid/cloneid generated) to clone the data onto the clone pool at a different tape library.
3. After the cloning completes, I want to reset the browse and retention time of save sets on original (Source) Media from "2 months" to "1 day". However, the issue is that the ssid/cloneid for two instance (original and clone copy) of same data is exactly the same. Is there any way we can differentiate between the two copies. I know that the volid for each instance will be different but it can not be used in nsrmm -S -e -w command.
I also thought to set the browse and retention time (for backup) to be 1 day and have clone pool retention to be higher, but incase the cloning process fails for some reason, the original backup copy could potentially be lost and hence ignored that option.
Any help is highly appreciated.
I'm writing a script for to clone the data and having issues reset the browse and retention policy of the original media.
Here's what I'm trying to achieve:
1. mminfo to query the data having savesets having one copy and backed up in last 24 hours.
2. nsrclone (with the list of ssid/cloneid generated) to clone the data onto the clone pool at a different tape library.
3. After the cloning completes, I want to reset the browse and retention time of save sets on original (Source) Media from "2 months" to "1 day". However, the issue is that the ssid/cloneid for two instance (original and clone copy) of same data is exactly the same. Is there any way we can differentiate between the two copies. I know that the volid for each instance will be different but it can not be used in nsrmm -S -e -w command.
I also thought to set the browse and retention time (for backup) to be 1 day and have clone pool retention to be higher, but incase the cloning process fails for some reason, the original backup copy could potentially be lost and hence ignored that option.
Any help is highly appreciated.