Start a Conversation

Unsolved

Closed

P

1 Rookie

 • 

19 Posts

511

April 3rd, 2023 09:00

3 from 9 savesets during clone fail

I have one workflow with constant error message for a long time... the cure for now is to restart the job manually.

It's CLONE job... once or twice per week it's error free.

I see the same pattern - the error shows 6 from 9 savesets succeded. 3 failed.

Among these 3 could be different savesets from different servers. What this magic number 3 means?

Why always 3... and from different machines. If it was from the same machine it could point to something particular.

Also, it's a clone job... so the data is on DD storage.

This is the message:

suppressed 28724 bytes of output.
2023-04-03 6:22:30 AM 4197091271/1680508872, 4213868487/1680508872,
2023-04-03 6:22:30 AM 4180314074/1680508890;
2023-04-03 6:22:35 AM Step (15 of 16): NSRCLONE_TERMINATE_PHASE_FOUR: The nsrclone verification detected some failures.
2023-04-03 6:22:35 AM 04/03/23 06:22:35.548778 Save set list count: 9, successful count: 6, failed count: 3



Any idea where to look... ?3 failed Data Sets CLONNING - Copy.JPG

4 Operator

 • 

1.3K Posts

April 5th, 2023 02:00

@pob579 , Well the number 3 might just be a coincidence. You might need to understand the error by by looking the daemon.raw. Also we might need some more information to help you better -

  • What do you have as the source and destination device?
  • Do a manual clone using nsrclone command and see what the outcome is.
  • Do you see an specific error may related to timeout or disconnects that might be caused by the firewall ?

The errors that you get on the console are usually very generic and might not give you the whole story of the issue.

April 11th, 2023 07:00

https://www.dell.com/community/NetWorker/starting-troubleshooting/m-p/8362849/highlight/true#M65321 states some Dell docs to look into wrg to cloning issues.


You seem to be cloning from DD towards tape? No experience with that anymore as we only clone between DD's using NW CCR. No cloning to tape anymore.

But is a restart structurally "solving" the issue? Alas retries is not supported for clone jobs.
https://www.dell.com/support/manuals/en-us/networker/nw_p_vmware_integration_19.8/create-a-clone-action-in-networker-administration?guid=guid-d081b547-e879-4f4c-a325-9701f7aeeaac&lang=en-us

"NOTE Although the Retries, Retry Delay, or the Inactivity Timeout options appear, the clone action does not support these options and ignores the values."

https://www.dell.com/support/kbdoc/en-us/000189901/cloning-from-dd-to-tape-unavailable-mmd-reservation-failed-after-upgrade-to-19-4-0-1-build-95
"NetWorker: Cloning to tape fails with MMD reservation errors on versions of NetWorker before 19.4.0.3" would no longer apply as you already run nw19.4.0.6.


But as you are running nw19.4, you didn't consider a higher version? We went for nw19.5.0.6 until recently and now will skip nw19.6 altogether in favor of nw19.7.0.3 (as we had to wait anyways for a memory leak fix for nw19.6 that was fixed in nw19.6.1.3 onwards, but as nw19.6 hasn't yet any fixes for various DSA's we went for nw19.7.0.3 next).


No Events found!

Top