Restore TSM client data across nodes

Posted by on in Storage Management
  • Font size: Larger Smaller
  • Hits: 1066
  • 0 Comments
  • Subscribe to this entry
  • Print

This article describes several methods to restore TSM (Spectrum Protect) client data between nodes (set access, fromnode, virtualnodename). This can be convenient if machine A crashes and you’ll need to restore machine A’s data on machine B. That’s just one example and there are different use cases for this. As you found this article, you’ll have a good reason for it.

The information provided in this article is not new – it is actually very old. VIRTUALNODENAME is used for restoring or retrieving (some or all) files to another workstation. FROMNODE is used for restoring or retrieving files from another client node and access needs to be granted. You can be very specific in the authorization rules.
There is some overlap between the provided methods, so you have to pick the best one in your scenario.

Let’s assume these 2 nodes: HANNIBAL and FACE. In all 3 methods, HANNIBAL backups a testfile and FACE needs a way to restore that file on its own system. Replace their names with the names of your machines.

 

METHOD 1 – NODENAME
Just change the NODENAME option in dsm.opt (dsm.sys on *IX). On FACE, adjust it so it reads HANNIBAL. Reset the password (if unknown to you because the password expiration period has passed and PASSWORDACCESS GENERATE is used) on the TSM server. After this identify switch, upon the first connection the TSM client will ask for the password for HANNIBAL. Enter it, and on the FACE system you’re now able to restore as HANNIBAL:

001

METHOD 2 – VIRTUALNODENAME
This is like changing the NODENAME option directly (method 1), but with a subtle difference. In this method, when using the CLI option, the original configuration doesn’t have to be touched. Again, let’s assume HANNIBAL backed up a file and FACE needs to access it. This is how it looks without any configuration or options – it’s just node FACE connecting to the TSM server:

002

DSM.OPT
Now add the option VIRTUALNODENAME HANNIBAL to DSM.OPT (be aware, even in *IX, it has to be dsm.opt, not dsm.sys).

003

Now on the FACE system, the TSM client connects to the TSM server as HANNIBAL. As stated, this behavior is the same as just editing the NODENAME option directly. You’ll still need to reset the password (if unknown to you because the password expiration period has passed and PASSWORDACCESS GENERATE is used) on the TSM server.

004

CLI
No need to edit dsm.opt. Invoke dsmc with the –virtualnodename parameter:

005

Or built the whole restore command at once:

006

Type the password when requested.

GUI
Invoke the GUI with the –virtualnodename parameter, or change dsm.opt before starting the GUI. Type the password when requested. Now restore the files from HANNIBAL to the FACE system.

006_5

007

008

For Windows this will just work. But for *IX it is stated in the documentation:

“….For the Java™ GUI, the virtualnodename option only works if you are root user. If you need to use the virtualnodename option with a non-root user account, use the command-line client.”

Method 3 – SET ACCESS
Now for something more sophisticated. With set access one can authorize another node to restore their files through so-called authorization rules. This command is not issued on the TSM server, but on the local TSM client. The TSM server keeps track of the set authorization rules in the database. The owner of HANNIBAL can specify which node can restore (or retrieve) what files. This can be done per file, per directory, per filespace or for all filespaces. In this case, the owner of HANNIBAL wants FACE to be able to restore all files in the root of the directory /TSM, and sets an authorization rule for that:

set access backup /TSM/* face

009

Authorization rules can be checked with ‘query access’ or deleted with ‘delete access’:

010

Now switch to the FACE system and start the TSM client. By using the –fromnode option, you can first have a look at HANNIBAL’s filespaces:

query filespace -fromnode=hannibal

011

Then you can restore the file:

restore /TSM/testfile1 /tmp/ -fromnode=hannibal

When using –fromnode, a destination for the files to restore to is mandatory.

012

The GUI equivalents of ‘set access’, ‘query access’ and ‘delete access’ can be found through the menu items: Utilities – Node Access List:

013

014

015

The GUI equivalent of ‘-fromnode-‘ can be found through the menu items: Utilities – Access Another Node:

016

017

Enter the nodename, click set and now the restore window on FACE shows the files that can be restored from HANNIBAL:

018

Do you know another, better or more (creative) method to restore data from another client node? Please let me know so it can be added to the list. And as always, feel free to comment. Thanks for reading.

—- Tommy Hueber

Original author: tommy
0
Comments are not available for public users. Please login first to view / add comments.