Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clone problem

Status
Not open for further replies.

paulmeta

Technical User
Mar 20, 2007
11
HK
NWS 7.3.2 on Win2K3 R2 with ADIC Autochanger 2 drives/24 slots

Dedicate Storage Node on Clients A,B and C


We have the following devices under the library:

\\.\Tape0
\\.\Tape1
rd=client_A:\\.\Tape0
rd=client_A:\\.\Tape1
rd=client_B:\\.\Tape0
rd=client_B:\\.\Tape1
rd=client_C:\\.\Tape0
rd=client_C:\\.\Tape1


For some reasons, we removed the Networker S/w on client_C,
we perform "nsrclone" on NWS and got the following messages:

C:\>nsrclone -v -b test_clone hdd102
Automatically copying save sets(s) to other volume(s)

Starting cloning operation...
...from storage node: client_C
NSR server NWS_Server: busy
nsrclone: waiting 30 seconds then retrying
NSR server NWS_Server: busy
nsrclone: waiting 30 seconds then retrying
nsrclone: nsrclone command has retried 2 times.


After I disable both "rd=client_C:\\.\Tape0" and "rd=client_C:\\.\Tape1"
we perform "nsrclone" on NWS and got the following messages:

C:\>nsrclone -v -b test_clone hdd102
Automatically copying save sets(s) to other volume(s)

Starting cloning operation...
...from storage node: client_C
nsrclone: error, no matching devices on `client_C'
nsrclone: Cannot open nsrclone session with NWS_Server
nsrclone: Cannot open nsrclone session with NWS_Server. Error is 'no matching devices on `client_C''
nsrclone: Failed to clone any save sets



After deleting both "rd=client_C:\\.\Tape0" and "rd=client_C:\\.\Tape1",
the job completed successfully, but it used the tape devices (local and remote) randomly.

The problem are:
1. Why "nsrclone" requires the availability of the device of client_C ("rd=client_C:\\.\Tape0" and "rd=client_C:\\.\Tape1") even I already disabled them.
and the volume "hdd102" contains no saveset of client_C

2. Can we assign the local tape devices (\\.\Tape0 and \\.\Tape1) to perform the nsrclone? cos when using remote devices, the speed degrade dramatically


Thanks
 
For question 1:
Most likely the reason is that you selected a device for the pool. Although this is possible, it is generally not recommended.
But if you do this, you instruct NW to only use certain devices, those which have been selected.


For question 2:
Sure you can do this.
- Do not select devices for your backup pool.
- Then make sure that you also have media for the clone pool at the server site
- And do not forget to remove the "Clone storage node" attribute of the client
 
I already selected those local device (\\.\Tape0 and \\.\Tape1) for the clone pool, but the clone operation still use a local device and a remote device no matter I clone by GUI or nsrclone on command line.

Any suggestion?
 
With nsrclone you may explicitly specify the destination pool with "-b pool".

From the GUI, you do not have this option. In this case you must adjust the client's "clone storage node" attribute.

Do not forget that some save sets (bootstrap) must be cloned at the NW server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top