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.

move a client node to a different policy domain for better retention settings

Discussion in 'TSM Client' started by unixandtsm, Aug 21, 2012.

  1. unixandtsm

    unixandtsm ADSM.ORG Member

    Joined:
    Feb 9, 2011
    Messages:
    307
    Likes Received:
    0
    Hi all,

    to move a client node to a different domain with better retention settings, i updated client with domain=new_domain as below
    Code:
    update node <node_name> dom=new_domain_name
    
    is this enough ? or are there anymore steps to be followed ?
    the new domain has better retention settings (ver exists, ver deleted etc) than old one so will the data backed up earlier be there for restores if needed ?

    thanks in advance!
     
  2.  
  3. rmazzon

    rmazzon ADSM.ORG Senior Member

    Joined:
    Dec 6, 2004
    Messages:
    207
    Likes Received:
    17
    Occupation:
    TSM Managed Services Lead
    Location:
    NC
    That should be all you need to do provided that all of the management classes the node used in the original domain/policyset exist in the new domain/policyset. If management classes are missing then data bound to those missing classes will be governed by the default MC.

    And barring a rebinding to a class with a lower retention your data should still be there.
     

Share This Page