Hi,
=20
The system reading the tape is the one that needs to have the clone =
storage node field set appropriately, not the client who originated the =
data.
=20
Unfortunately, there are a few "it depends" on this one; this is because =
you have to determine which system is doing the reading to determine =
which client object in NetWorker to set.
=20
Here are two examples:
1. Changer shared between backup server and storage node.
When you start cloning, backup server reads the tape. Target storage =
node is determined by the clone storage node field for the backup =
server's client object.
=20
2. Two changers, one for server, one for storage node.
In this case, set the storage node's clone storage node (not the =
original client's client object!), and it'll clone to itself.
=20
Note that the source clone tape is determined by the "read hostname" =
setting for the autochanger, while the target is determined by the clone =
storage node setting for the host that is doing the reading of the tape. =
This assumes that there are not pool related restrictions, of course!
=20
Dave
=20
Date: Mon, 7 Mar 2005 10:34:28 -0500
From: Karen <klehr < at > OPTONLINE.NET>
Subject: Cloning on Storage Node
Hi All,
Has anyone been able to clone to a storage node device? We are running
NetWorker 7.2, on HPUX, with an IBM3584 library. In the Client setup we
have the Storage Node and Clone Storage Node attribute set to the =
storage
node device, but the cloning still goes to the server.
Thanks
Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
