Toddman214
3 Argentum

Manual expiration of savesets via gui?


Hi all,

I'm running EMC DPS 8.2.1.4, and trying to expire several large savesets that I created when setting up and testing my DPS suite. I do not need these savesets, but I greatly need to reclaim the space on my DataDomains. I've looked, and yet to locate a method for manually expiring savesets through the GUI. Is there such a way to do this? I have the ssid's that I need to expire, and I can expire through cli, but prefer gui for this if possible.

Thanks!

Todd

36 Replies
bingo.1
4 Ruthenium

Re: Manual expiration of savesets via gui?

There no way to expire certain save sets from the GUI.

However, the fastest way is simply to relabel the volume.

  !!! This of course only makes sense if no other valuable save sets are stored on the same volume. !!!

For such case, simply use the command line. This is usually a 2 step process:

1. Check the ssid (the cloneid will ensure that a potential duplicate on tape will not be deleted as well)

   mminfo -q "family=disk,<other_criteria>" -r "ssid,cloneid" -xc/ [> file]

2. Delete the save set

   nsrmm [-y] -d -S ssid[/cloneid]

Of course you can script that.

For more details please read the Command Line Reference.

0 Kudos
Toddman214
3 Argentum

Re: Manual expiration of savesets via gui?

Hello bingo. I did ultimately end up using command line, but not quite with the results I was seeking, so I may have missed a step. I should not be comparing Netbackup with Networker, but it's where I'm coming from, so it's a good tool. In Netbackup, you can query the client or dataset using multiple variables, right-click on the images you want to remove, and select "expire now." Then, you can refresh the DataDomain intereface, and see that the size was instantly reclaimed as "cleanable" space. Not "available", but "cleanable".  That actual space will not become "available" until the next cleaning runs against the DataDomain.

So, on the Networker server, I ran  ~>nsrmm -d -S 1707395804 against that ssid, it asked me "Delete file and media index entries for save set `1707395804'?", I confirmed, and it did become no longer available when I ran another search for it in Networker. I did the same thing against the clone ID's. However, the "cleanable" space showing in my DataDomin interface did not change. The saveset was approx 14tb in size, so I feel as though the metadata was removed from Networker, but the space is still used on the DataDomain. Do you think I missed a step?

0 Kudos
bingo.1
4 Ruthenium

Re: Manual expiration of savesets via gui?

There are several 'cleaning' processes which run automatically but not right away.

For NW, you could also start the "Index Manager" (nsrim) manually. This should reclaim the space on the NW disk volume.

The default cleaning cycle for the DD is setup for tuesday - I do not know any way to start it from Networker. I think this is a good idea in general as it will not cause contention with other backup/restore jobs.

Of course you can also manually start this process on the DD admin GUI at any time.

0 Kudos
ble1
7 Thorium

Re: Manual expiration of savesets via gui?

The cleanable part in NW runs every 23 hours.  I do not recall the name on Windows (could be the same as on UNIX/Linux), but in /nsr/mm there is file called nsrim.prv.  Whenever NetWorker group finishes with its run, NW will check if 23 hours have passed since timestamp of that file and if timestamp is >23 hours, it will run nsrim which goes through mdb, marks if ssids expired and removes index entries and does device cleanups.  As in NB, you can run this manually in NW as well by several methods:

a) you can remove this file and as soon as one group finishes it will be created and nsrim will run

b) you can manually run nsrim against device(s) from which you removed ssids (if you don't specify device, it will go through all devices just as regular nsrim does)

Normally, if not in hurry, I would expire ssids by setting their ssbrowse and ssretent value to now and leave NW to handle it. If in hurry, like you need DD space, you can either do the same or remove them and then run nsrim [by either a) or b) ]. Last, would be to start cleanup on DD.

0 Kudos
masonb
3 Zinc

Re: Manual expiration of savesets via gui?

Todd,

It’ shard when you’re not familiar with a product and within NetWorker (and I am sure NetBackup also) there are several ways to achieve the same result – determining which best suits you is the trick!

If you have already deleted the saveset manually then NetWorker has no way of letting the Database know during its housekeeping that the saveset is gone and you have overridden the process which should have let the Data Domain know it can release the space from the saveset. It’s best to set is to recyclable and then the housekeeping process which mark savesets for expiry/deletion will take effect and tell the Data Domain the file can be released for cleaning.

You can recover from this situation, I would recommend running the following command: - nsrstage –C -V

Volume name is where the savesets were (hopefully you know this).

This should compare the file system entries and the Media Database entries on DD/NW and sync back up between the hardware/software.

Regards,

Bill Mason

0 Kudos
ttobey
2 Bronze

Re: Manual expiration of savesets via gui?

I may be repeating what has already been said? This is the process I use.

Manual Cleanup.

(Please note auto cleanup runs every Tuesday.)

In the GUI you can select a volume, look at the savesets that are older and can be purged. Please note the Saveset ID, and see that the status is browseable. Then, you can run the following command:

nsrmm  -o recyclable -S SSID

This should make the saveset recyclable. Repeat the process for other savesets that can be recycled.

You can run nsrim -X

after recycling the savesets. That should show as cleanable space immediately. That should save you 24 hrs..

Filesys show space        

It should show how much data can be cleaned under the Cleanable GB Column.

Filesys clean start

To start the cleaning process.

Filesys clean watch

To watch the cleaning progress.

Repeat as necessary.

Toddman214
3 Argentum

Re: Manual expiration of savesets via gui?

William,

If I understand you, then what I had already done was remove the savesets, but Networker doesnt know that I have, and will not tell DataDomain to make that space reusable? I ran the nsrmm -d -S command, pointing at a txt file containing many ssid's, and ran that through a batch file to delete them all.

If I have done this wrong, then I need to run nsrstage –C -V PDCVMFS01 (<-volume name), to resync whats in the datadomain with what is in the Networker index. Correct? If so, I cannot get that command to work. I may be missing some switches here. Netbackup spoiled me, and I'm not much of a command line dude....yet.

C:\>nsrstage –C -V PDCVMFS01

39094:nsrstage: must specify one of -m or -C.

usage: nsrstage [-v] [-F] [-d] [-s server] [-J storage-node] [-b pool] [-y retention time] -m -S [-o] {[-I] -f file | ssid...}

   or  nsrstage [-v] [-s server] [-J storage-node] [-y retention time] -C -V volume

ttobey,

Can the nsrmm  -o recyclable -S SSID command be used with a text file of ssid's to make many recyclable at once? When I need to expire images manually, its never going to be one....it will be thousands.

Thanks again, all!

Todd

0 Kudos
ble1
7 Thorium

Re: Manual expiration of savesets via gui?

- I doubt you need to run post cleanup as nsrim runs will take care of that in subsequent runs

- use nsrclone -P -V <volume name>

- you can use -o recyclable too - but you can also use what you used so far

0 Kudos
masonb
3 Zinc

Re: Manual expiration of savesets via gui?

Todd,

I will try and explain some terms to you first to see if this helps your understanding: -

Client File Index (CFI) has the details if a specific clients saveset backups (all files included in a particular backup including timestamps, directory path etc). Until a saveset passes its browse period the details of the files etc are retained then removed once passed from the CFI. We still have the data until its passed its retention period but no longer have all the file details so without manual action to recover CFI or knowing the exact path required we would recover the whole saveset as the detail is not there.

Media Database (MDB) has all the details of the backups for all the savesets from client backups and which volumes they are associated with. We don’t store individual file details here but do have different information regarding the no of files, size, various timestamps (backup, browse, retention, clone times) etc.

Nsrim process runs daily and looks for savesets which are passed their browse period also those which are passed their retention period.

Ones passed browse have the CFI entries removed and their status changed from browsable to recoverable, ones passed retention with no dependancy’s are marked as eligible for recycle. On Advanced File System/file devices and DDBoost devices this the trigger to release the space on the device and allow the disk space to be freed up and the MDB entry is removed also (on DDBoost this works slightly different as the Data Domain cleaning has to run but the cleanable space value should show what is possible to be released on the Data domain itself). For tape volumes – all savesets on a tape must be recyclable before it is eligible to be re-used. When a tape is relabeled all the savesets on that volume are removed from the MDB and the volume information is updated (new volid, label date etc – it appears like a delete and create).

So in your case when you ran the script you deleted the Media Database entries manually so they now no longer exist and therefore cannot be processed by nsrim. This is why you need to do the extra step of running the nststage command as this compares what the DD has for the volume and then if there is no entry in the MDB within NetWorker tells the DD that the savesets are no longer required. This will free up the space.

I am not sure why the command is not working if you volume name is specified correctly – are you running this from the NetWorker server? If so it should work without any extra flags.

If you have ram the nsrmm command to mark the savesets as recyclable rather than doing a delete no further actions should have been necessary as the next automatic run of nsrim would have processed all these and informed he Data Domain we no longer required.

If you cannot get the command to run I would suggest opening a call with EMC Support – it should be quick to resolve.

Regards,

Bill

0 Kudos