IC55047: RESTORE/RETRIEVE TO ALTERNATE SYSTEM USING FROMNODE OR VIRTUALNODENAME REQUIRES DESTINATION FILESPEC

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as suggestion for future release.

Error description

  • TSM manuals do not clearly document the default behaviour
    when attempting to restore/retrieve to an alternate
    system.
    
    If no destination filespec is specified, TSM client will
    attempt to restore/retrieve to the original filesystem
    where the objects were backed up/archived from.
    
    Online help and TSM manuals should document the need for
    a destination filespec in sections detailing how to
    recover objects backed up from one system to an alternate
    system.
    
    In the 5.5 TSM B/A Client Installation and User's Guide:
    ***
    Restoring or retrieving files from another client node
    After users grant you access to their files on the server,
    you can restore or retrieve those files to your local system.
    You can display another user's file spaces on the server,
    restore the other user's backup versions, or retrieve the
    other user's archive copies to your local file system, by
    following these steps:
    
    Click Utilities from the main window.
    Click Access Another Node. The Access Another Node window
    appears.
    Type the node name of the user's host machine in the Node name
    fi
    eld.
    Click the Set button.
    If you are using commands, use the fromnode option to indicate
    the node. You must also use the file space name, rather than the
    drive letter, to select the restore-retrieve drive you
    want to access. Include the file space name in braces and use it
    like a drive letter. For example, to restore cougar's files from
    the \projx directory on the d disk file space to your own \projx
    directory, enter:
    
      dsmc restore -fromnode=cougar  \\cougar\d$\projx\* d:\projx\
    
    Use the query filespace command to display a list of file
    spaces.
    For example, to display a list of cougar's file spaces, enter:
    
       dsmc query filespace -fromnode=cougar
    
    For more information about using the fromnode option with the
    restore command, see Restore. See Retrieve for the retrieve
    command.
    For more information about the fromnode option,
    see Fromnode.
    ***
    .
    
    ***
    Restoring or retrieving your files to another workstation
    When you are using a different workstation, you can restore
    or retrieve files you backed up from your own workstation.
    Your backup versions and archive copies are stored according
    to your node, not your specific workstation. Your Tivoli
    Storage Manager password protects your data.
    
    To restore or retrieve files to another workstation, use the
    virtualnodename option to specify the node name of the
    workstation from which you backed up the files. You can use
    the virtualnodename option when starting Tivoli Storage Manager
    or place the option in your client options file, dsm.opt, on
    the workstation. If you are using a workstation other than your
    own, use the virtualnodename option with the dsm command. For
    example, if your node name is cougar, enter:
    
       start dsm -virtualnodename=cougar
    
    You can then restore or retrieve files as if you were working
    on your original workstation.
    
    You can use virtualnodename on commands also. For example,
    if you want to restore your \projx files to your local
    c:\myfiles directory,
    enter:
    
       dsmc restore -virtualnodename=cougar \\cougar\d$\projx\*.*
                    c:\myfiles\
    
    If you do not want to restore or retrieve the files to the
    same directory name on the alternate workstation, enter a
    different destination.
    ***
    FROMNODE and VIRTUALNODENAME options do not document the
    need to specify a destination filespec to prevent TSM client
    from trying to recover data to the orignal system's filespace.
    
    TSM GUI online documentation:
    ***
    Accessing Another User's Stored Data
    You can display another user's filespaces on the server. You
    can then restore the other user's backup versions (excluding
    Windows system objects and System State) or retrieve the other
    user's archive copies to your local drives.
    Note: You can display another user's stored data only if the
    other user has authorized you to do so by using the Node Access
    List window.
    
    To access another user's stored data:
    
    
    1.  Select the Access Another Node choice from the Utilities
        menu.
        The Access Another Node window appears.
    2.  Type the user's node name in the Node Name field.
    3.  Click the Set button.
    
    Considerations:
      To display your own filespaces, click the Default button in
       the Access Another Node window.
      You can also use the virtualnodename option in the client
       options file to restore or retrieve another user's stored
       data using the other user's node name and password.
    
    Example: virtualnodename puma
    
    Restart the client after you add the virtualnodename option
    to the options file. You are prompted for the password assigned
    to the other user's node, if a password is required. If you
    enter the correct password, you have access to all backups and
    archives that originated from the specified node.
    
    You cannot access another user's filespaces on the server
    using the Access Another User window if you are operating with
    client node proxy support in which your client node is an agent
    node acting on  behalf of the target node.
    ***
    All of the above sections should detail the need for a
    detsination filespec for restore/retrieve to recover objects if
    the intention is to recover to the alternate system.
    
    Affected Levels:  All supported TSM clients
    Initital impact: Low
    Additional Keywords:
    

Local fix

  •  Always specify a UNC name for restore/retrieve destination when
     attempting to recover files backed up from a different system
    
    to make sure the files are recovered to the expected filesystem.
    

Problem summary

Problem conclusion

Temporary fix

Comments

  • The need to specify a destination in the case where the data
    comes from a different machine name is documented in chapter 10
    "Restore".
    
    It is understood that this is a frequent area of confusion,
    and alternative means of improving usability or documentation
    in this area will be considered for a future release. However,
    a comprehensive solution to this usability issue is beyond the
    scope of a documentation APAR fix.
    

APAR Information

  • APAR number

    IC55047

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    55W

  • Status

    CLOSED SUG

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-01-28

  • Closed date

    2008-03-28

  • Last modified date

    2008-03-28

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

55W

Reference #:

IC55047

Modified date:

2008-03-28

Translate my page

Machine Translation

Content navigation