Kevin,

        You may have to connect to the TSM Server via the backup agent on
'Ash' while emulating the backup agent 'Phxrst03' by using the
VIRTUALNODENAME option when you invoke dsmc ie: "dsmc
-virtualnodename=Phxrst03"

Rick

-----Original Message-----
From: Reed, Kevin: [mailto:kreed AT PPCO DOT COM]
Sent: Monday, September 23, 2002 3:34 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backupset from other client?


I'm attempting to restore a couple files from a backupset that was made on a
client before it was moved to a new box and had its name changed.  Both the
clients were connected to the same tsm server.

When the backupset was made, the client was called :  phxrst03.  That backup
set still exists on the tsm server
but I can't seem to get to it from the "new" box.

        Old Name        Phxrst03
        New Name        Ash
        Backupset       PHXRST03_FULL_BACKUPSET.10462763

When I issue the restore command on the new box (Ash), it says it can't find
the backupset.

tsm> restore backupset PHXRST03_FULL_BACKUPSET.10462763 /apps/temp/* /tmp/
-loc=server

The error is: ANS1934E Backup set 'PHXRST03_FULL_BACKUPSET.10462763' not
found

However, the tsmserver the client is connected to does have the backupset
and can see it:

Node Name        Backup Set Name                          Date/Time
Retention  Device  Description
-----------  -------------------------------------------
-----------------------  ----  ---- ------------------
PHXRST03 PHXRST03_FULL_BACKUPSET.10462763  09/18/02  09:19:35  180  LTO  No
Description

I think I am missing a step here.  Even though the tsm server can see the
file, the client "ash"
doesn't seem to know about it.

What do I need to do to get the ash client to access the backupset made by
phxrst03??

--
Kevin W. Reed - Unix Systems Engineer
ConocoPhillips