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
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