Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

997

June 12th, 2009 13:00

Diskbackup Cleanup

Networker 7.3.2
Win2k3
SCSI attached SATA (file type device)
Storagetech SDLT L80 Library

Had a post last year on this. Thanks to "brerrabbit" for help with batch programming. Basically the batch file runs the following "nsrmm" command to delete savesets from disk to recover space.
nsrmm -d -y -S {list os savesets}
My problem is after running the above command the savesets aren't browsable any more. Is there a way to remove savesets from a "file type" device, leaving the savesets (clones) still browsable for recovery until retentioned off?

13 Posts

June 13th, 2009 13:00

keep in mind the following:

the save set SSID after it is cloned but not deleted
will exist with several cloneid

for example, ssid 34567000 is written to disk
and cloned to tape (but not staged or deleted)
Then
you have ssid 34567000 with three cloneid

cloneid #1 on the write enabled AFTD
cloneid #2 on the write protected AFTD

cloneid #3 on the tape (this exists only if you clone ssid/cloneid#1 )

so you can do the following to "move" the save set to tape and keep the indexes
(for the duration of the browse policy of course)

a) stage ssid as mentioned which takes care of the cloning to tape
and deleting from disk

or

b) you can clone ssid 34567000/cloneid#1 to tape
at which point you have the three cloneid of ssid 34567000
and after the cloning you can also proceed if you wish to
either
cloneit again
or stage it
or delete the save set from disk (without ) removing the index -- how?

remove the ssid/cloneid#1 <--- this is cloneid of the original backup to disk
example, assume in this example
cloneid #1 is 1238990
cloneid #2 is 1246990
cloneid #3 is 1257990

then to delete cloneid#1 use

nsrmm -d -S 34567000/1238990

You must specify the cloneid# of the write enabled aftd cloneid
this will ensure that you remove
*only *
that instance (or clone or copy) of that ssid

*without* removing all instances and
therefore without removing the indexes.

Comments: you might use option 2) if you wnated to clone it once
before staging it, thus producing two tape clones instead of one before removing
ssid from disk

Otherwise, it is simpler to use option 1)

June 12th, 2009 13:00

For my part we do not delete it. but stage it to tape with the nsrstage command.

2K Posts

June 13th, 2009 08:00

I agree: the best way would to stage it off rather than clone and then run batch commands to delete save sets.

1.1K Posts

June 15th, 2009 03:00

Since you have a backup-to-disk device and a physical tape library I am assuming you want to move the data from the initial backup target to the physical host. There are two options:

* cloning - data remains on the original location
* staging - data is removed from original location after being moved to the new location

You should always exercise caution when using nsrmm to delete stuff; normal retention period settings should be able to take care of removing volumes for reuse as and when needed.

19 Posts

June 25th, 2009 14:00

Thanks to all for your input. I'm cloning to get the data off-site, and want to keep the data on disk for a least a week for possible restores. Also want to keep browsable for a month. I hate having to scan. Adding the clone ID to the nsrmm command did the job. Thanks again.
No Events found!

Top