Unsolved
1 Message
0
971
error during cloning
I have got this error during clonning:
2/3/2021 6:08:27 AM Total time taken to replicate ssid file /SUHistoricoSemanal1/SEMANAL.003/68/93/fe6b4342-00000006-d819db3b-6019db3b-01291500-de4cd65d is 16 seconds.
2/3/2021 6:15:07 AM Failed to close clone save session for ssid 3625573179: RPC receive operation failed; peer = 10.XX.XXX.XX:8205, errno = A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2/3/2021 6:15:07 AM Cloning failed for save set : <3>E:\[NO BORRAR] PST EXCH (ssid 3625573179)
2/3/2021 6:15:07 AM Total size cloned so far: 96 GB.\n
2/3/2021 6:15:07 AM Unable to end clone save session with server: RPC send operation failed; peer = 10.30.248.32:8205, errno = An existing connection was forcibly closed by the remote host.
2/3/2021 6:15:07 AM Unable to perform clone of client saveset. Error: proxy_clone_rs failed.
2/3/2021 6:15:08 AM Concurrent proxy clone completed for sevice type DD.
2/3/2021 6:15:08 AM Total size cloned: 4875 GB.
2/3/2021 6:15:08 AM DD cloning failed
2/3/2021 6:15:08 AM Proxy clone failed to clone all or few savesets
2/3/2021 6:15:09 AM No input savesets!
2/3/2021 6:15:09 AM No valid backend job 1
2/3/2021 6:15:14 AM 02/03/21 06:15:14.354610 Cloned save set list:: 924440369/1612306225, 957994801/1612306225, 790222651/1612306234, 605673315/1612306275, 572118887/1612306278, 857331512/1612306232, 723113793/1612306241, 555341675/1612306283, 538564466/1612306290, 588896102/1612306278, 706336581/1612306245, 739891007/1612306239, 672782156/1612306252, 471455621/1612306309, 991549233/1612306225, 370792475/1612306458, 840554297/1612306233, 806999865/1612306233, 823777081/1612306233, 756668221/1612306237, 622450513/1612306257, 354015278/1612306478, 6560
2/3/2021 6:15:14 AM Unprocessed/pending input work items exist.
2/3/2021 6:15:14 AM Action clone 'clone' with job id 192391 is exiting with status 'failed', exit code 1
2/3/2021 6:15:14 AM NSRCLONE failed for one or more savesets.
We tried to launch clone at different hours and it starts ok but finally fails.
JChan2020
18 Posts
0
March 4th, 2021 19:00
You should post to the NetWorker forum for this clone issue.
barry_beckers
393 Posts
0
May 3rd, 2021 14:00
did you actually look at the failed ssid's being reported clearly? what has happened sometimes is that if a clone fails, it might have partially cloned ssid's that are on the target dd, and hence it will be unable to clone the source ssid's again. not all nw versions were able to cleanup such a mess and then cloning would be always failing for those ssid's while for all other ssid's it was just working fine. it could even onlyh occur for one ssid, and becauses of that would report all clone jobs to fail, only for one and the same ssid each and every time...
the ssid's on the target dd are then very likely to show that they are not cloned OK. so for example look at the ssflags and clone flags within NW using mminfo to see if it shows any of the failed ssid's already being cloned to the target device. as on one and the same volume, only a ssid is allowed once, trying to clone the same ssid to it will fail.
I tend then to delete the incorrectly cloned ssid's on the target (so do not touch the ones one the source!) by specifically specifying the ssid/cloneid combination of the ssid on the target to be deleted. and then retry the clone job again.
unlike nw9.x, nw19.3 seems to be able to better deal with these kind of clone failures, as it appears to cause failures now and then still, but appears to address the issue by being able to get rid of the partially cloned faulty ssid on the target so that next clone job will be able to clone the earlier failed ssid.