1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link 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 message will disappear after you have made at least 12 posts. Thank you for your cooperation.

TSM client for restore purposes

Discussion in 'TSM Client' started by piedone, Nov 16, 2012.

  1. piedone

    piedone New Member

    Joined:
    Jun 27, 2009
    Messages:
    10
    Likes Received:
    0
    Hi,

    I installed a TSM client only for restoring. For this I would need to dsm.opt doesn't store the restorable node's name. I would like to configure the client to it asks the nodename and its password all time and open its backed up data.
    If I write only the tcpserveraddres to dsm.opt it doesn't work.

    How can I do this?

    Thanks!
    BR
    Gabor
     
  2.  
  3. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,177
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    DSM.OPT file is needed:

    TCpserveraddress <TSM_IP_addr_or_DNS_name)
    TCpport <if_other_than_1500>
    NOdename <registered_node_name>
     
  4. piedone

    piedone New Member

    Joined:
    Jun 27, 2009
    Messages:
    10
    Likes Received:
    0
    Hi,

    Yes. But I want to use it without nodename row. I want to use it on a computer which isn't used for backup. Only for restoring.

    Thanks!
     
  5. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,177
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Without the nodename you cannot connect to the TSM server.

    Having the nodename in the dsm.opt file does not mean it will run the backup! The backup runs IF you tell it to. Now, if there is another node out there that has the same nodename and active, you have to disable the TSM scheduler for that node while running a restore on the new node.

    Restart the TSM schedulers after restore is complete.
     
    Last edited: Nov 16, 2012

Share This Page