Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
T
Thierry101
2 Intern
•
326 Posts
0
750
August 4th, 2013 16:00
clone to tape
Hi All
I have a situation.
Exch DAG backups are saved to 1st-DD. Then that is cloned to 2nd-DD and resides in Clone pool using Nwkr clone controlled.
I need to clone from 2nd-DD to tape. So i ran a mminfo query to get just the ssid/cloneid which resides on 2nd-DD only.
Have verified all comes from 2nd-DD devices(by checking pool name,devices and ssid/cloneid) . Entered that in clone job called Clone2Tape under Clone Specific save sets (save set ID/Clone ID field). Storage node to WRITE save set: is the one that have access to 2nd DD devices and the clone device.
When the job is started, it is trying to mount the DD devices from 1st DD for clone operation. I am curious at this stage as none of the ssid/cloneid have any ref to 1st-DD. Retention is up to Sept 13 for all save sets.
Any thoughts on why Networker behaves like that when have enforced on what cloneid to pickup from? Thank you
Nwkr7.6.3.7
win2k8r2
Thierry101
2 Intern
•
326 Posts
463
0
Posted August 4th, 2013 19:00
hi Tim
SSID/CLONEID...CLONEID that resides on 2nd-DD
For whatever reason it still want to load the original backup device....tried using command line too:-
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone: DDB_IDXCL-01.RO (Regular) - 2nd DD
80471:nsrclone: DDB_DEFCL-19.RO (Regular) - 2nd DD
80471:nsrclone: DDB_DEF-25.RO (Regular) - 1st DD
80471:nsrclone: DDB_DEF-27.RO (Regular) - 1st DD
5872:nsrclone: The volume(s) below already contain the requested save sets(s).
5873:nsrclone: They will not be considered as cloning targets at this time: ??
DDB_DEF-25.RO
DDB_DEF-27.RO
TimQuan
6 Operator
•
1242 Posts
463
0
Posted August 4th, 2013 18:00
Did you specify SSID/CLONEID or just SSID?
You must specify SSID/CLONEID queried from 2nd-DD instead of SSID.