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.

Moving a TSM HSM managed filesystem to a new host machine with different Filesystems

Discussion in 'Hierarchical Storage Management' started by mguery, May 16, 2013.

  1. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    My client asked me migration stub files from a Sun Sparc server with VxFS to a AIX server with JFS2.

    I read the article http://www-01.ibm.com/support/docview.wss?uid=swg21286977.

    But this applies only to of identical filesystems (ie VxFS to VxFS, or JFS2 to JFS2).

    Is there a way to do it , without recall or restore ?
     
  2.  
  3. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    As the article says, the file systems must be the same. Now you could check out using VxFS for AIX and see if that will work. I would call IBM and ask them if there is a migration path between Solaris and AIX for the HSM data.
     
  4. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    IBM said that there is no solution, and we must completely restore the data (over 17 TBytes ...)
     
  5. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    Ouch, that has to hurt. That is a lot of data to bring back and then migrate out again.
     
  6. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    Yes, it is clearly unrealistic and that's why my question.
     
  7. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    I had a customer that lost data and it took 18 months to get everything back on HSM. Of course if you work around the clock you could do it in a year.
     
  8. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    In this case, it is a hospital, and an archive of radiology images and scanner, which are still in use (in production) ... So if we lose these images, we can not recreate ...
    So we can not really play with these data ... But we can not keep data on a system being phased out.
     
  9. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,814
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    If I would implement a move like this, I would build the new system, copy the data over the new system. 're-index' (meaning rebuild the HSM), run in parallel, slowly move users over to the new system, observe and then decommission the old one.

    Easier said than done but I believe that this is the only 'easy' way.
     
  10. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    The big problem is the volume: 17 TBytes and more than 2 million files. All files belong to the same user and same group.
    And we can't stop HSM more than three or four days, because these files are used by practitioners and radiologists to treat patients.
    Imagine the delay to restore 17 Tbytes from LTO5.
     
  11. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,814
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I understand the size as mentioned earlier. Don't you have copies of the tapes? If you have, you can use these to restore the data on the new AIX server.
     
  12. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    Yes, there is a "tape backup pool" and "Tape_Copy_Pool" for these files.
     
  13. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    Sounds like we are dealing with BLOB files here. Moon-buddy, can he really restore the solaris data from a VxFS file system to an AIX JFS2 file system? I think that I would set up the new AIX box and have AGFA go to the new box and a specific date. That way all new data would start to accumulate on the new system. The old system could stay up and you would have to recall the data and then move it over to the new system. It will take a while, but no one would be down.
     
  14. Mikey D

    Mikey D ADSM.ORG Member

    Joined:
    Mar 21, 2007
    Messages:
    272
    Likes Received:
    8
    Location:
    Southeast Michigan
    In my opinion and working in the same sort of environment where we've used HSM for the same type of data... Your best bet here is to involve the RPACS vendor and do an archive to archive migration, you'll have an outlay of funds for the RPACS vendor contract and the new AIX system but this avoids any downtime at all and will allow you to throttle the migration of studies in to the new archive area.

    Now if you didn't want to go that route when we switched from AIX JFS to JFS2 files systems we had to restore all our stub files, there's a tech article on IBM's site but you may be able to do this from Solaris to AIX. I know the restore GUI will allow you to restore between these two system.

    http://www-01.ibm.com/support/docview.wss?uid=swg21286426
     
  15. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    Yeeeessss , Rallingham, you are the winner !!!
    These are BLOB files from AGFA.
     
  16. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,814
    Likes Received:
    358
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Yes I think it can be moved. These images are digitized so it should be transparent. These should be no different than handling other data.
     
  17. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    OK, suppose we lose all stub. In this case, the command "dsmc restore ..." should be able to recreate them: Is it true?
    If I generate a node (AIX) , with the same dsm.opt and dsm.sys files on the SUN, then create FS (JFS2), with the same mount point, I should be able to recreate the STUB, without restoring data using the following command:

    # dsmc restore "/archive/*" -su=yes -replace=no -restoremigstate=yes

    In this case, TSM should restore stub files (but not the data files) on the AIX file system (JFS2), even if the original system was VxFS.

    Is that true?
     
  18. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    I am not sure about the ARCHIVE you have put in there but the manual says:

    To restore stub files rather than backup versions of your files, for example if one or more of your local file systems is damaged or lost, use the backup-archive client restore command with the restoremigstate option. To restore the stubs of HSM managed files with the backup-archive client, the dsmrecalld daemon must be running. Your migrated and premigrated files remain intact on the Tivoli Storage Manager server, and you need only restore the stub files on your local system. However you cannot use the backup-archive client to restore stub files for your migrated files, if they have been backed up before the migration. Instead use the HSM client dsmmigundelete command to recreate stub files for any migrated or premigrated files that are lost.

    Here is an example: dsmc restore -restoremigstate=yes -sub=yes "/home/*"
     
    Last edited: May 18, 2013
    mguery likes this.
  19. mguery

    mguery ADSM.ORG Member

    Joined:
    Jan 8, 2003
    Messages:
    16
    Likes Received:
    0
    Occupation:
    AIX & TSM Consultant
    Location:
    Ile de La Réunion
    Sorry "/archive" is the mounting point for the BLOB files.
     
  20. rallingham

    rallingham ADSM.ORG Senior Member

    Joined:
    Dec 16, 2003
    Messages:
    583
    Likes Received:
    28
    Occupation:
    Sr. TSM Solutions Specialist
    Location:
    Greater Niagara Region. Welland
    I should have remembered that. Some use another directory in front of that.
     

Share This Page