UNSOLVED

Celio1

updated

13 years ago

C

Celio1

1 Rookie

•

16 Posts

0

12521

October 10th, 2013 08:00

Unable to clone manually using NMC or nsrclone

Hello,

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.

5 Attachments

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

  • MoinMansuri

    2 Intern

    •

    147 Posts

    3852

    0

    Posted October 11th, 2013 04:00

    Hi,

    As per error issue with drive (drive selection)  or Media pool.

    Check media pool created for it and allocate correct drive for it.

    Moin

  • Celio1

    1 Rookie

    •

    16 Posts

    3851

    0

    Posted October 11th, 2013 05:00

    I do choose a destination pool on the NMC, and on the command line, here's what happens:

    nsrclone -s bakserver -b "TEST CLONE" -S 3142953149

    80470:nsrclone: Following volumes are needed for cloning

    80471:nsrclone:         CAN078 (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, Cannot open nsrclone session with bakserver.  Error is 'No source device is available for the cloning operation.'

    39077:nsrclone: error, Some of the clones failed

  • Celio1

    1 Rookie

    •

    16 Posts

    3862

    0

    Posted October 11th, 2013 05:00

    Yes, but why would the netappfiler want to mount the source volume in order to do a recover clone of a regular saveset?

    How do you correct this configuration issue? Which NetWorker resources should be corrected?

    Thank you.

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    3851

    0

    Posted October 11th, 2013 05:00

    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.

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    3862

    0

    Posted October 11th, 2013 05:00

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

  • Celio1

    1 Rookie

    •

    16 Posts

    3862

    0

    Posted October 11th, 2013 06:00

    The recover storage node in storage node client (NetWorker server) resource is empty check 10-10-2013 16-32-13.png

    The manual clone operation is run from a client computer which has the NetWorker Management Console installed.

    On the command line with nsrclone, if the -J and -d are specified, it does work.

    # nsrclone -s bakserver -J bakserver -d bakserver -b "TEST CLONE" -S 3142953149

    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

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    3863

    0

    Posted October 11th, 2013 06:00

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

  • Celio1

    1 Rookie

    •

    16 Posts

    3863

    0

    Posted October 11th, 2013 08:00

    But how do you exactly do that?

  • Celio1

    1 Rookie

    •

    16 Posts

    1290

    0

    Posted October 11th, 2013 10:00

    If I do a verbose command line nsrclone, this is what I get:

    # nsrclone -vvvvvvvv -S 3243714141

    Job 'nsrclone of group ' has jobid 7872650.

    Obtaining media database information on server bakserver

    generate_snodes_from_ss:

    parms val: 3243714141

    add_to_snodes:

    loc_volid:

      volname: CAN026

      using v_location: LIB1

      volume_location: netappfiler.

      hostname netappfiler added

      volid 3897971355 added

    vallist_add_ssid:

      ssid: f069a42d-00000006-c157265d-5257265d-01400014-4fc479a8

      cloneid: 1381442967

    80470:nsrclone: Following volumes are needed for cloning

    80471:nsrclone:         CAN026 (Regular)

    79632:nsrclone: Cloning the following Regular save sets (ssid/cloneid):

            3243714141

    5874:nsrclone: Automatically copying save sets(s) to other volume(s)

    79634:nsrclone:

    Starting Regular cloning operation...

    6217:nsrclone:   ...from storage node: netappfiler

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

    clone_ids before:

            1381442967

    clone_ids after:

            1381442967

    cloneid in new list = 1381442967

    cloneid 1381442967 in old list matched

    generate_clone_result(): 0 savesets successfully cloned.

    generate_clone_result(): failed to clone 1 savesets.

    79625:nsrclone: Failed to clone any Regular save sets

    39077:nsrclone: error, Cannot open nsrclone session with bakserver.  Error is 'No source device is available for the cloning operation.'

    39077:nsrclone: error, Some of the clones failed

    snl_src_snode: netappfiler

    loc_volid:

    Any clues as to why does this volume belong to a NDMP storage node even though the volume has no NDMP savesets? And how to correct this behavior?