DRM pool migrate between tape libraries

yazoo

Newcomer
Joined
Jan 4, 2024
Messages
2
Reaction score
0
Points
0
Hello

We would like to migrate date from the one tape library to the new library and then dispose of the old library as soon as possible.
Therefore, we would like to get advice on how to migrate from DRM pool between libraries (migration from ts35xx to ts45xx)
or what would be the best method for this type of migration for a DRM pool to move the data as quickly as possible.
Please advice.
Thanks
 
Yazoo,

Things done before we move any data out of the old DRM pool.
Define new tape library to the SP Server.
Make sure that the SP Server is able to communicate with the new library .
ie: backup db devclass=devclassname_new_library type=full
Define new DRM storage pool.
Update the "prepare" to use the new tape library.
Update the recovery plan with the new tape library and any information that need to be updated.


1. Update the DRM to use the new DRM tape pool.
When the next schedule "prepare" runs, the data should be going to the new DRM pool.
NOTE: During this time part of the data will be in the old DRM pool.
Over time all the data in the old library will expire.
When all the data have expire in the old DRM pool, then remove the old DRM storage pool and the old library.

Primary pool -> Stop data being copy to -> Old DRM pool
Primary pool -> Start data being copy to -> New DRM Pool

... move the data as quickly as possible.

Then this option you may not want to do.


2. Migrate all the data from the old DRM pool to the new DRM pool.
Bring back ALL the DRM tapes from the vault location.
Check in ALL the DRM tapes into the old library, update the volume access to "readonly".
On the old DRM tape pool update the "next pool" to point to the new DRM tape pool.
Then issue "MIGrate STGpool pool_name LOmig=90".
Once the process complete, rerun the "mig stg" command with lo=80, repeat the process until we
reach zero (0)
Be sure that there are plenty of scratch tapes in the new tape library.

Primary pool -> Stop Data being copy to -> Old DRM Pool -> Migrate data to -> New DRM Pool
Primary pool -> Start data being copy to -> New DRM Pool


3. Delete ALL the DRM volumes in the old tape library.
NOTE: This will leave you vulnerable if a disaster happen during this period.

When we run DRM process, all the data will be backed up to the new DRM stgpool.
Be sure that there are plenty of scratch tapes in the new tape library.

Delete ALL DRM volumes in the old DRM pool
Primary pool -> Start data being copy to -> New DRM Pool

Good Luck,
Sias
 
but question is if migration to "next pool" will works for copy pool?
 
Opps! My bad.

Thanks Trident!


For those who are not familiar with the application.

Copy Storage Pool

When an administrator backs up a primary storage pool, the data is stored in a copy storage pool.

A copy storage pool can use only sequential access storage (for example, a tape device class or FILE device class).

The copy storage pool provides a means of recovering from disasters or media failures. For example, when a client attempts to retrieve a file and the server detects an error in the file copy in the primary storage pool, the server marks the file as damaged. At the next attempt to access the file, the server obtains the file from a copy storage pool. For details, see Restoring Storage Pools, Backing Up Storage Pools, Recovering a Lost or Damaged Storage Pool Volume, and Maintaining the Integrity of Files.

You can move copy storage pool volumes offsite and still have the server track the volumes. Moving copy storage pool volumes offsite provides a means of recovering from an onsite disaster.

Basically, the copy pool is just a backup of the backup.
We can delete some or all the volumes that are define to the copy pool.
When then the next schedule or if we manually issue "backup stg" the missing volumes will be recreated.




Screenshot 2024-01-09 082453.png

The "nextpool" option is not available for copy pool.

- Sias
 
Back
Top