10 Posts
0
914
March 23rd, 2021 09:00
Can I safely delete Disk Volume with no backup sets?
I have an old Disk Volume that was used for some old backups jobs that are no longer needed. It's reporting 41TB, but I've expired all of the save sets and purged them with nsrim -X. Now the volume says no save sets, cleaning is running on the data domain, but the volume is still showing up as 41TB in the Networker Mgmt Console. What's the best practice to safely delete this volume?
No Events found!
bingo.1
2.4K Posts
2
March 23rd, 2021 10:00
If you are sure that there are no save sets in this volume (verify with mminfo), let me suggest that you relabel it. This will delete all save set files. Then unmount the volume and delete it.
BenRadHMX
10 Posts
0
March 23rd, 2021 10:00
That seems to have worked, have to wait and see once the cleaning process on the DD finishes. Thanks for your help.
barry_beckers
393 Posts
0
March 26th, 2021 11:00
KB article 61068 talks about a mismatch occurring for showing the amount of "written" data, which is said to be calculated by :
written=last known volume size - total space recovered from the volume
Apparently this can run out of sync, especially with volumes that are in use for some time. We run into it often when decommissioning volumes, that it still shows data on it according to mminfo -m output. We check, double check, check again, validate, check again. But in the end simply delete it.
Above KB article states to set /nsr/debug/force_disk_usage
and then to run nsrim -X or wait until index maintenance has run.
Above is specifically reported fro AFTD's in the KB article (I also guess it is a very old KB article, but as Dell has (yet again!) started renumbering the KB articles without mentioning in which NW version this is an issue, it is almost impossible to know) but I tried it recently with ddboost devices that appeared out of sync in a nw18.2 environment, reporting much more data on it than when we calculate what is on it.
However leaving the option in place, turned things around and some time later it showed much less data on it according to mminfo output, then was actually located on it. But possibly I should only have run media maintenance once, instead of keeping it active for a couple of weeks. This as after the first runs it did not appear to result in showing the actual size yet. Heheh...
But then again, I just was trying, assuming that ddboost devices being also disk-based devices, might possibly have the same issues as aftd devices.