UNSOLVED

cpevery

updated

13 years ago

C

cpevery

4 Posts

0

3595

January 8th, 2014 10:00

Recover Session for Cloning Operation

Hello,

I have daily cloning sessions between data domain devices in Networker 8.0. All of a sudden one of clone jobs popped up with a recover session for with a client name of cloning session and a simultaneous error of "Waiting for 1 writable volume(s) to backup pool 'clone pool name' disk(s) on storagenodename" and I know this media is mounted and the size in use is decreasing so I'm not sure what it wants from me. I can't kill the job and I can't respond to the media request.

Any help would be appreciated.

Doug

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1085

    0

    Posted January 8th, 2014 11:00

    One occasion where I saw this is usually when there is core dump with nsrmmd which was supposed to be used for target operation - you can check on storage nodes in /nsr/cores/nsrmmd if you have core dumps to check if this is your case or not.

  • cpevery

    4 Posts

    1090

    0

    Posted January 8th, 2014 14:00

    I have checked all of the storage nodes and could not find any core dumps hiding around.

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1090

    0

    Posted January 9th, 2014 00:00

    Cool - one thing less to worry. How do you clone - automatic or manual?  You can check nsrtask.raw which will contain log for scheduled clones or /nsr/tmp/sg/ / for manual ones (at least in NW7, in NW8 I didn't check).

  • cpevery

    4 Posts

    1090

    0

    Posted January 9th, 2014 06:00

    Automated.

    I rebooted the Networker/NMC server and the storage node that had the affected device last night. Cloning will start in a few minutes and I will see if the same error pops up.

  • CarlosRojas

    1 Rookie

    •

    1693 Posts

    626

    0

    Posted January 10th, 2014 03:00

    Hey Doug,

    What NW server and Storage Nodes are you using?

    I would recommend to go for the latest build available to avoid any known issues.

    Could you please attach the daemon.raw from NW server and the storage node facing the issues? (if too big please attach just part of the daemon when problem is coming up).

    Thank you,

    Carlos

  • Diego.Palopoli

    1 Rookie

    •

    32 Posts

    1092

    0

    Posted November 29th, 2016 15:00

    Hi Hrvoje, I am sorry to bother you with this, but we have same problem (clone jobs goes from clone session tab to recover sessions tab and then, the whole clonning process stops).

    So, I would like to also see "nsrtask.raw" (because this happens without a clear pattern, it means, sometimes clone jobs works and ends right and others stops/freeze, going/migrating to recover sessions) but that log (nsrtask.raw) is not in our Networker server environment and I didn t find how to configure independently of daemon.raw. If you have some "tip[or]trick" to do that, I really appreciatte you to share.

    From Command Reference Guide 8.2 I found this:

    NAME nsrtask -> execute an action based on NetWorker resource

    ...

    FILE /nsr/logs/daemon.raw -> log file containing messages from running the nsrtask program.

    NAME nsrvim -> client binary for commnunicating with VMware VirtualCenter

    ...

    FILE /nsr/logs/nsrtask.log -> log file containing execution messages routed through nsrtask

    From AdminGuide 8.2 I found... nothing but nsrtask with recover jobs.

    Thanks a lot for any help you may give us!

    Regards.

  • bingo.1

    1 Rookie

    •

    2430 Posts

    1092

    0

    Posted November 30th, 2016 06:00

    I don't know where you got the idea about a separate log file.

    From the 8.2 Command Line Reference:

    FILES    /nsr/logs/daemon.raw      Log file containing messages from running the nsrtask program. daemon.raw also

                                                      contains other log messages from other NetWorker binaries.

    And it is the same paragraph as stated in the very first NW 8.2.0 CLR.

  • Diego.Palopoli

    1 Rookie

    •

    32 Posts

    1092

    0

    Posted April 22nd, 2017 03:00

    Hi  bingo, thanks! I totally agree with you, there is only daemon.raw, my question was related to what Hrvoje said, who mention nsratsk.raw.

    Just to do a try on answer your question, maybe it comes from previous 8.x versions, could be? (somebody also named "bingo" answered about nsrtask.raw some years ago here --> "Cloning task completion report" :-D ).

    darcidino, is the issue still there?

  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    1092

    1

    Posted April 26th, 2017 02:00

    Diego.Palopoli wrote:

    Hi  bingo, thanks! I totally agree with you, there is only daemon.raw, my question was related to what Hrvoje said, who mention nsratsk.raw.

    As mentioned already, if you have scheduled cloning (or staging) you will have this log filled with info.

  • 831

    0

    Posted October 24th, 2017 17:00

    Hi Diego,

    Did you find a solution to this issue?  I'm seeing something similar with NetWorker 8.2.4.9 cloning.

    Luke