1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

How to move TSM HSM client to a new machine without backup?

Discussion in 'Hierarchical Storage Management' started by avv, Jan 11, 2017.

  1. avv

    avv Active Newcomer

    Joined:
    Mar 7, 2016
    Messages:
    5
    Likes Received:
    0
    Hi,

    my current setup is based on tsm server 7.1,
    hsm client 6.3 and gpfs 3.5. it works well.

    I have to move hsm client to another machine
    with change from SLES to RedHat.

    The standard procedure is to migrate all data
    to tape, backup and then restore stubs from
    backup on the new machine.

    I have total of 8 space-managed GPFS filesystems
    however 4 of them are not backup'ed up. They
    are also very large so it is not possible to backup
    them just for sake of migration.

    The question is if the following procedure would
    work:

    1. stop hsm client on the old machine.

    2. map gpfs luns on disk array to the new machine.

    3. export gpfs on the old machine.

    4. import gpfs on the new machine.

    5. setup hsm client on the new machine in the same
    way as it was on old one (same tsm server, same node
    name, same config files, etc...)

    6. start hsm client on a the new machine.

    What can go wrong?

    Thanks in advance!
     
  2.  

Share This Page