Moving HSM stub files to another client node

[dmarsee]

Greetings.



Is there an easy way to move just HSM stub files from

one client node to another? Our machine with the stub

files is being deactivated, so I need to move those

stubs to another client node and have it access the

files just like the previous machine did. Same filesystem

names, same everything, just different machine (with a

different node name - NOT new hardware with the old

node name) owning the stubs. Both machines are clients

of the same server. I'm not an HSM wiz, so is this a

piece of cake, or a pain?



Thanks,



Darryl

 

[sgabriel62]

Daryl

Yes it can be done and its relatively easy or dependent on your environment.

What you need to do if you have not done so already, is to download the Users Guide

IBM Storage Manager for Space Management for UNIX.



Once you get this - proceed to page 66, or Chapter 6 and there are steps and commands to follow.



Boils down to one command really

dsmc restore - restoremigstate=yes -sub=yes <filesystem>

and your off and running.



But do some homework before you start



Good Luck



Steven

 

[PJ]

Steven,



I don't see how this could work with different TSM nodenames. It would at least require a -fromnode during restore. Just restoring the stubfile would then have to copy data within the TSM Server from one filespace to another - and I don't believe TSM can do this. Setting that aside, just restoring the stubs doesn't work anyway. I observed that the client always restores all data. The only diffeence between restoremigstate yes and no is, that restoremigstate=yes just writes stubs to disks (while still reading ALL data from tape, taking huge amounts of time depending on data und infrastructure).



Peter