Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Moving savesets ? 1
- Thread starter denisfr
- Start date
-
1
- #2
That's what staging is for. Use
nsrstage -S ssid -b pool_name
It is in fact a clone process but it will delete the reference of the old sav e set from the media db.
------------------------
Another posibility is to change the retention date with
nsrmm -e "new_retention_date"
------------------------
If you do not need this SS any longer you may of course delete his entry from the media db
nsrmm -d -S ssid
nsrstage -S ssid -b pool_name
It is in fact a clone process but it will delete the reference of the old sav e set from the media db.
------------------------
Another posibility is to change the retention date with
nsrmm -e "new_retention_date"
------------------------
If you do not need this SS any longer you may of course delete his entry from the media db
nsrmm -d -S ssid
- Thread starter
- #3
NW does not allow you to clone or copy to a specific media ... if it is not the only media for a pool. There is a good reason for that:
If you tell any program to use a specific media, there is
no alternativity. But if the media is not available or in
use by another process or even full, no program can use
this media - the problem is not NW specific.
So pools make sense - and there is no option to specify a certain media from a pool.
There are two major reasons for pools:
- to separate save set data for various reasons
- to group save sets by their retention policies
---------------------
Staging to the same pool is possible. However, what would be the result? - You only move the save set with a long retention policy to another media in the same pool. This does NOT make sense as you just move but not solve your problem.
If you tell any program to use a specific media, there is
no alternativity. But if the media is not available or in
use by another process or even full, no program can use
this media - the problem is not NW specific.
So pools make sense - and there is no option to specify a certain media from a pool.
There are two major reasons for pools:
- to separate save set data for various reasons
- to group save sets by their retention policies
---------------------
Staging to the same pool is possible. However, what would be the result? - You only move the save set with a long retention policy to another media in the same pool. This does NOT make sense as you just move but not solve your problem.
- Thread starter
- #5
This does NOT make sense as you just move but not solve your problem.
It have sense for me ;-)
Everyday, I eject (manually, I'm not alphastor provided) tapes from my silo.
But, last night, NW was hungry of tape, so he took 3 tapes for saving clients. But, due to a problem, he did not fill the 3 tapes in the same way : 2 were greatly filled, and the last was ridiculously filled. So I wanted to migrate my little saveset to one of the 2 tapes in order to eject 2 tapes, and relabelling the third tape for this night, thus saving a tape (SDLT-320).
I confess I mis-ask (!) my problem... The real reason was not the ssretent...
It have sense for me ;-)
Everyday, I eject (manually, I'm not alphastor provided) tapes from my silo.
But, last night, NW was hungry of tape, so he took 3 tapes for saving clients. But, due to a problem, he did not fill the 3 tapes in the same way : 2 were greatly filled, and the last was ridiculously filled. So I wanted to migrate my little saveset to one of the 2 tapes in order to eject 2 tapes, and relabelling the third tape for this night, thus saving a tape (SDLT-320).
I confess I mis-ask (!) my problem... The real reason was not the ssretent...
- Status
Similar threads
- Locked
- Question