moving a node/data from one TSM Server to another TSM Server

[tsmhelum]

I need to move a node and it’s data from one tsm to another

Move SNI265 on tsm server A to >>> TSM server b what is the quickest way to accomplish this.

TSM Server Saber= TSM Version 5.5.3.0

TSM Server Pluto= TSM version 5.5.3.0


So after the move is complete it will now be backing up on TSM Server Pluto.

P.S.- I know others have done this but I have never performed this task.

Also it will be using a storage pool called H3592pool



Thanks for any help in advance

 

[heada]

If you don't want to keep backup history, just change the option file to point to the new server and register the node. If you want to keep all the history, you'll need to export the node and then import it on the new server. This will take quite a bit of time as it has to write all the backups/archives out to tape again and then read them in on the new server.

-Aaron

 

[nenifled]

only one command

If you don't want to keep backup history, just change the option file to point to the new server and register the node. If you want to keep all the history, you'll need to export the node and then import it on the new server. This will take quite a bit of time as it has to write all the backups/archives out to tape again and then read them in on the new server.

-Aaron

If the two TSM-servers can "see" each other, the export and import can be done in one command.

3.23.2.2 EXPORT NODE -- directly to another server
Use this command to export client node definitions or file data directly
to another server for immediate import.

 

[tsmhelum]

Thanks heada, nenifled for your replies

here is the command I came up with ( I want to retain the backup history)


Export node SNI265 filedata=all to server=pluto H3592Pool

I would enter the command on tsm server a

Please feel free to comment on the command and suggest any corrections

Thanks again

 

[quinstear]

I am in the process of doing this currently for some archive data. You command looks fine. One thing I found was to register the node name on the target server and assign it to the correct domain first. Before I did that the import was picking up a domain that did not have enough space.

 

[tsmhelum]

quinstear Thanks for the quick response!

once I register the node on the Target TSM Server and then enter the command it will just transfer information to it correct?

Thanks again

 

[quinstear]

Yes. That's what I have found. I have a console window open on both servers and can see

On target server
ANR0984I Process 50 for IMPORT (from Server LTSM01) started in the BACKGROUND at 10:25:38.
ANR4711I IMPORT SERVER (DATES=ABSOLUTE REPLACEDEFS=NO MERGE=NO PREVIEW=NO) by administrator

On Source Server
ANR2017I Administrator ADMIN issued command: EXPORT NODE ltsm01 filespace=/group03 filedata=archive
toserver=ltsmarchive01
ANR0984I Process 113 for EXPORT NODE started in the BACKGROUND at 10:25:38

When the export/ import completed I have something like
On target server
ANR0611I IMPORT (from Server LTSM01) started by ADMIN as process 45 has ended.
ANR0986I Process 45 for IMPORT (from Server LTSM01) running in the BACKGROUND processed 446617
items for a total of 179,362,040,129 bytes with a completion state of SUCCESS at 10:14:44.Hope you get it sorted

 

[tsmhelum]

quinstear thanks

One thing I noticed was you also included a import command on the target server.

ANR0984I Process 50 for IMPORT (from Server LTSM01) started in the BACKGROUND at 10:25:38.
ANR4711I IMPORT SERVER (DATES=ABSOLUTE REPLACEDEFS=NO MERGE=NO PREVIEW=NO) by administrator

Do I need to do that? or for my situation I just need

Export node SNI265 filedata=all to server=pluto

Thanks

 

[quinstear]

No these are not commands. These are the output from the TSM console or you can get them from "q act" quering the activity log. The command I have used is

[FONT=&quot]export node ltsm01 filespace="/group01" filedata=archive toserver=ltsmarchive01[/FONT]

The import is taken care of in this command with the option "toserver="

 

[quinstear]

another point is that you can see it working in the console window. Also you can run "q ses" and see the progress of the data transfer

1,235 Tcp/Ip Start 0 S 241.2 G 196 Admin AIX-RS/- ADMIN

 

[tsmhelum]

Thanks for your help quinstear! I'll let you know the results

 

[tsmhelum]

quinstear

Seems the export completed successfully

ANR0986I Process 352 for EXPORT NODE running in the BACKGROUND processed 37160 items for a total of 104,586,677,985 bytes with a completion state of SUCCESS at 12:23:51. (SESSION: 152854, PROCESS: 352)

Export node SNI265 filedata=all to server=pluto

I had to take off the devclass=h3592pool at the end of the command kept getting the following error.

ANR0555E EXPORT NODE: The DEVCLASS parameter cannot be specified when the TOSERVER parameter is specified.


Now I have to do a move nodedata command is this correct?

move nodedata sni265 fromstgpool=tapepool tostgpool=h3592pool

How do I find out what pool the data went to if I am not sure in order to move it to the h3592pool?.


thanks

 

[tsmhelum]

quinstear

Also, on the target server I did notice this in the server log

ANR2147E REGISTER NODE: Node SNI265 is already registered.


No big deal I guess, got that message cause I registered the node before hand.

 

[nenifled]

it should be OK

Hello

Since you used "filedata=all" all data should have been moved.

you could try theese two commands on both your TSM-servers and compare the results:

q occu SNI265

or....

select sum(num_files) files, sum(PHYSICAL_MB)/1024 GB from occupancy where node_name='SNI265'


Now just remember to change your dsm.opt to start making backup to the new TSM-server.

 

[MrStormy]

q occupancy <node_name> will show you where your data is.

 

[tsmhelum]

Hi nenifled, MrStormy....Thanks for the commands

Also, nenifled - Your right thanks for the reminder I have to change the TSM Server IP in the dsm.opt file to point to the new TSM Server.

Also, I guess once I do that (or before) I should either remove the node from our Backup Schedule on the orginal TSM Server. Or I can delete it altogether including files spaces Since it will be backing up on the new TSM SErver.

Thanks for your replies!

 

[axisminden]

Hi,
i will start this call again.
i have to do this job to. in my case we have a server where the backup is 450gb for the
first time only. connection between the server and us is 6000 dsl . the backup will work forever.
so i do setup a tmp tsmserver and ba the data directly.
as next i export the data to the real tsmserver.
what for me is not clear,
how it works with the security between the tsm server?
comes up a prompt to ask for "who is it".?
The node is already exist on the real tsmserver.

michael

 

[heada]

You import the node from the temp TSM server into the real TSM server.

tsm: TSM>help import node
3.29.2 IMPORT NODE (Import client node information)

Use this command to import client node definitions from a server or
sequential media to a target IBM Tivoli Storage Manager server.



The imported nodes are associated with the same policy domain as they
were on the source server, if you specify the domain and if that policy
domain exists on the target server. Otherwise, imported nodes are
associated with the STANDARD policy domain on the target server.

IBM Tivoli Storage Manager servers with retention protection enabled do
not allow import operations.

Note:
      1. If target and source server levels are not compatible, the
         operation may not work. See the Administrator's Guide for
         server compatibility requirements.
      2. Importing data from a CENTERA device class is not supported.
         However, files being imported can be stored on a CENTERA
         storage device.

You can use the QUERY ACTLOG command to view the status of the import
operation. You can also view this information from the server console.

This command generates a background process that can be cancelled with
the CANCEL PROCESS command. If an IMPORT NODE background process is
cancelled, some of the data may already be imported. To display
information on background processes, use the QUERY PROCESS command.

For a server that has clients with support for Unicode, you may need to
have the server convert the file space name that you enter, or use the:
*  HEXFILESPACE parameter
*  UNIFILESPACE parameter

Don't underestimate the bandwidth of a car full of tapes.

-Aaron

 

[axisminden]

[/code]Don't underestimate the bandwidth of a car full of tapes.

-Aaron[/QUOTE]

Hi Aaron,
Thank's for answer. i will have a look to that .


michael

 

[mgarcez]

How can I use more than 1 process to do export node

Hello guys!

How can I use more than 1 process to do export node?

I need to do this in a little bit time!

Thx!