Create the new copy storage pool, if you use them.Ĩ. Update your old stgpool NEXTstgpool setting to go to the new stgpool.ħ. Next we will migrate the data off of the old library.Ħ. Validate and Activate the policy sets after making the changes to the copy destinations. If your copygroups go directly to tape, then change those now as well. If your backups go to a Disk stgpool and then migrate to OLDPOOL, update the disk stgpool to point to NEWPOOL as well, without changing copygroup setting. Change the copygroup DESTination setting from your OLDPOOL to point to NEWPOOL. It depends on how much data you have and what daily processing is going on at the time, but it is recommended to mark the OLDPOOL volumes 'read only' at this point.Ĥ. disable sessions & events so that backups will not go to old stgpool. See the TSM Admin guide / quick start guide for procedure.ģ. Once it is defined to the O/S and TSM, create a new stgpool (NEWPOOL) using the new library. Physically attach the new library to the server and define it in the TSM server.Ģ. This procedure can be used to move data from any devclass to any other devclass.ĭata needs to be migrated to alternate library hardware.ġ. Procedure to migrate any TSM data that resides in Storage Pools from one library to another library. 9juil/13 Migrating TSM Node Data from one Library to Another
0 kommentar(er)
