With tapes, there is only one way - you must use nsrclone -m (which is nsrstage actually) to moved ssid from one volume to another.  Once this is done, you can relabel older volumes.

How would you go about doing that? Are you able to move data within the same pool? In my case it would be "1 year" to "1 year" to consolidate tapes. Do you also have to move bootstraps and indexes?

First of all, you need at least (a jukebox) with 2 tape drives.

In general, you must apply the command per save set but you can also supply a save set list.

I recommend to use nsrstage as this command for sure can be used to migrate the save sets to the any pool (including the same pool).

   Important: Always specify the ssid along with the cloneid - otherwise you will and up with only one instance!

So the general procedure - for each pool - is this:

1. Query the information for the source save sets 

      mminfo -q "ssretent>09/01/2014,volume= "

                  -r "client,name,level,savetime,totalsize(15),volume,ssid,cloneid" -xc, >>

  - Repeat this again for all source save sets.

or

      mminfo -q "ssretent<09/01/2014,volume= "

                  -r "client,name,level,savetime,totalsize(15),volume,ssid,cloneid" -xc, >>

  - Repeat this again for all source save sets.

2. Import into a spread sheet and remove duplicate SSIDs

3. Add the column "totalsize" for each volume and find out which save sets are faster to migrate

   (which ones are smaller, in total).

4. Export the columns "ssid" and "cloneid" to a text file.

   The format must read " / ". One entry per line. No header.

5. Protect all tapes you need to read from:               nsrmm -o full

6. Migrate the save sets as follows:                         nsrstage -b -m -S -f

7. Optional: Un-protect the tapes you read from:       nsrmm -o nonfull

Please read the Command Line Reference for the full set of options.

-------------------------------------

If you only have one tape drive

In this case I recommend that you manually clone to the specific pool and that you delete the 'wrong' save sets from the source tapes. However, in this case the sources must still reside on disk.

The procedure is pretty similar::

1. Query the information for the source save sets 

      mminfo -q "ssretent>09/01/2014,volume= "

                  -r "client,name,level,savetime,totalsize(15),volume,ssid,cloneid" -xc, >>

  - Repeat this again for all source save sets.

or

      mminfo -q "ssretent<09/01/2014,volume= "

                  -r "client,name,level,savetime,totalsize(15),volume,ssid,cloneid" -xc, >>

  - Repeat this again for all source save sets.

2. Import into a spread sheet and remove duplicate SSIDs

3. Add the column "totalsize" for each volume and find out which save sets are faster to clone

   (which ones are smaller, in total).

4. Export the column "ssid" to a text file.

   The format must read " ". One entry per line. No header. NW will no use the disk as source.

5. Protect all tapes which do not want to write to      nsrmm -o full

6. Clone the save sets as follows:                           nsrclone -b -S -f

7. Delete the 'wrong' tape save sets from the media index as follows       nsrmm -d -S

Please read the Command Line Reference for the full set of options.

Looks more complicated than it is. Good luck

Thanks! Everything looks good except I'm getting the error "Can only backup data to backup clone pools". Does this imply that my destination pool type needs to be a "Backup Clone"? Can I use Archive or Backup pools for the destination pool?

The error you mention "Can only backup data to backup clone pools" is contradictory as there is no backup involved at all - just clone or stage processes.

So when exactly do get this error? Trying which command?

As pools will not mix data types, backups must go to a 'backup' pool, clones must go to a 'backup clone' pool.

In the above example, I was attempting to move a saveset that ended up in the Default pool (backup), but should have gone to a 10 year pool (archive). I will have to look at how things are configured and why it was sent to the default pool in the first place. I should be able to go from a backup pool to another backup pool thought right?

So I'm running the following command "nsrstage -b destination_pool -m -S SSID/CloneID"
This is what I get as a result:

39078:nsrstage: SYSTEM error: Can only clone backup data to backup clone pools.

5777:nsrstage: Cannot open nsrstage with archive-srv1

5882:nsrstage: Failed to clone any save sets

The message means that you obviously can only use 'nsrstage' to move save sets from a clone media to a clone media.

I personally have never seen it. This might well be an issue which has been corrected with a later NW version.

'nsrclone -m' will work as well ... if you use a version where the option '-m' exists. According to the Command Line References it has obviously been introduced with NW 7.6.1 (... or NW 7.6.0.x because the docs could be a bit behind).

I verified in the Release Notes a huge change for the clone features in NW 7.6.1 but not a detail about the new nsrclone option '-m'.

So make sure that you use a NW version which already has this option implemented.

Also do not forget that when you migrate you should always use the cloneid along with the ssid - otherwise you will end up with only one instance left.