Unsolved
This post is more than 5 years old
1 Rookie
•
29 Posts
0
10817
August 8th, 2018 20:00
Savesets that have gone past the retention date not getting removed from data domain
We are on Networker 9.2.1.3. I have a issue with some savesets not being removed from EMC data domain. Savesets that have a retention time of 10 months back (xx/09/2017) are still present on the data domain device. The flag on these savets is set to "cb".
If I run the following command the "Clone retention time" does not change on these savesets:-
nsrmm -e "08/07/2018" -y -S xxxxxxxxxx
But if I run following command then the saveset is removed from the data domain volume:-
nsrmm -d -y -S xxxxxxxxxx
But from the command refference guide I understand that this only removes refferences to this saveset and trims the networker database.
But it seems like that it does not remove the data from data domain. Is my understanding correct?
And if so then how can I remove these savesets from data domain to free up space?
bingo.1
2.4K Posts
0
August 9th, 2018 07:00
"nsrmm -e -S #####" might not do anything. However it depends an the status the save set currently has.
If you want to set a save set to "recyclable" you better use
nsrmm -o recyclable -S #####
"nsrmm -d -S #####" will definitively delete the save set (all instances) from the media index and from a disk media.
Of course, it cannot delete the save set instance from tape.
To verify that just run
mminfo -q "ssid=#####" -r "ssid,volume"
after that.
Do not forget that to really free space the DD has to run its internal garbage collection which by default is just done once a week.
SurajPujari
155 Posts
0
August 9th, 2018 10:00
check for the "Server Protection" group which runs expiration job on NetWorker. What is the status of this job?
Are these savesets residing on a single volume which is no more in mounted state?
Actual data deletion happens on DD through its cleaning cycle till that time it just gets marked as eligible for deletion.
Deb_PS
156 Posts
0
August 9th, 2018 11:00
@mc_7, As you mentioned some save sets are having the issue, so I am assuming most of the save sets are getting expired, as the situation will change if no save sets are getting expired.
If no save sets are getting expired then check if the Expiry job is getting successful at all or not?
If the issue is with some of the save sets, then make sure you are considering all the clone copying of the save set, please check using the mminfo / index query so you make sure all clone retention of all the copies is over against the problematic save set is over.
ble1
2 Intern
•
14.3K Posts
0
August 23rd, 2018 04:00
Most likely there is some ssid which is depend on it and therefore status in not changed. Check the whole chain for the given saveset. If you really decided to remove it regardless, -d will remove it and nsrim -X (or nsrclone -P -W should tag it as removed as well)... then this will be removed from DD upon next file system cleanup (depending when it is scheduled on your system).