ADSM-L

Solution to "Weird One - Restore goes to original client"

2000-03-29 13:47:53
Subject: Solution to "Weird One - Restore goes to original client"
From: Gary Ison <Gary.Ison AT MAIL.STATE.KY DOT US>
Date: Wed, 29 Mar 2000 13:47:53 -0500
Hi Again Folks,

        Thanks to Mile Dile and Daniel Thompson, the problem (see below) is
solved.  You must use the "restore to following location" and "restore full
path" options to achieve the intended result - restoration of the Host A
file(s) to Host B.  This is true even after renaming (TSM name) Host B and
granting access to B on Host A.

        My thanks to both Mike and Daniel for their help.

Original Problem Posting
===================

        I have just encountered a totally weird phenomenon - a client
restoring a file causes the file to restore on the client that originally
backed it up.  Here is the scenario.

1.      Host A (NT 4.0, 3.7.1.0 client) backs up a directory with two files.
2.      Host A deletes the backed up directory and all files.
3.      Host B (NT 4.0, 3.7.1.0 client) restores the directory using GUI,
selecting directory level.
4.      Restore completes with no errors.
5.      Directory and files are restored to the original host - Host A.
Nothing is present on Host B.

        Both hosts have the identical options files (meaning each host is
the same *SM name).
        Each host has independent IP addresses and DNS names.
        Each host is on the same network at the same time.
        Only one host has *SM session active at a time.
        Server is 3.1.2.40 on OS/390 MVS 2.4

        When the originating host (Host A) is disconnected from the network
(NIC is unplugged), the GUI gives an error ANS1410E - Unable to access the
network path.

It appears that the user does not have labels on the disk drives and the
client uses the NT universal share of Drive-letter$ (i.e. C$) as the drive
name and prefixes it with the DNS host name.  This constructs as filespace
name of \\DNS-name\Drive-letter$(Drive-letter:)
<\\DNS-name\Drive-letter$(Drive-letter:)>  or \\Host-A\C$(C:)
<\\Host-A\C$(C:)>  in this example.  When the restoring client picks an
object for restore in the filespace with the unlabeled drive, the DNS name
is extracted and that becomes the target destination of the restore.

Has anyone seen this before and does this explanation make any sense?
Thanks.

        Gary L. Ison
        Governor's Office for Technology
        101 Cold Harbor Drive
        Frankfort, Ky.   40601
        Phone:  (502) 564-8724
            Fax:  (502) 564-6856
E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
DOT us>
<Prev in Thread] Current Thread [Next in Thread>
  • Solution to "Weird One - Restore goes to original client", Gary Ison <=