I'm trying to clone savesets manually using the NMC, by clicking on Media -> Save Sets -> Query Save Set (fill out the criteria) -> Save Set List (choose savesets).
This operation works for NDMP savesets but not for "regular" savesets.
However, it used to work when we were running NetWorker version 7.4.5.
We performed a version migration (reinstalled server on Solaris 10, installed NetWorker 7.4.5, restored the configuration from bootstrap, than updated to 7.6.5).
The error message we get when we try to clone any regular savesets is:
Oct 10 15:08:05 bakserver root: [ID 702911 daemon.notice] NetWorker media: (notice) no matching devices on `netappfiler' for clone recover by client `bakserver'
Oct 10 15:08:05 bakserver root: [ID 702911 daemon.notice] NetWorker media: (notice) enable or check device(s) on `netappfiler'; volume CAN028 needed
Why does it mention our NetApp Filer for a regular saveset clone operation?
If instead, we perform the same operation on the command line, here is what we get:
bakserver# nsrclone -S 3343546846
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone: CAN028 (Regular)
39077:nsrclone: error, no matching devices on `netappfiler'
39077:nsrclone: error, Cannot open nsrclone session with bakserver. Error is 'No source device is available for the cloning operation.'
79625:nsrclone: Failed to clone any Regular save sets
39077:nsrclone: error, Some of the clones failed
Please check the attached image files for the client resource tabs of our NetWorker server.
What is says is that storage node netappfiler can't mount your source volume. It also says that source volume is regular type so this was either DSA backup or regular one (in which case filer is probably not where you want to clone of course). This is typical configuration issue.
It all depends how this is set (recover storage node in storage node client resource) and from where it is run (read hostname). nsrclone has options for this to be set; for example -J will set recover storage node (read) and -d target storage node (write).
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone: CAN078 (Regular)
Oct 11 12:18:46 bakserver root: [ID 702911 local0.alert] NetWorker media: (waiting) Waiting for 1 writable volume(s) to backup pool 'TEST CLONE' tape(s) on bakserver
There you go... so now trick is that you set this in NMC too and you are done (and yes, that includes recover storage node too - otherwise some defaults are used which due to device/architecture restrictions won't work for you).
bingo.1
1 Rookie
•
2430 Posts
3851
0
Posted October 10th, 2013 09:00
You should at least specify the destination pool. If not, NW will determine it automatically.
As you usually have assigned devices to a pool, NW would then use the wrong devices and these can be attached at the wrong (NDMP) storage node.