Hi@Dsantibanez , Check if this saveset is already present in the destination disk that you are trying to lone to? Also make sure you have a drive free for reading the saveset from the Tape.

Hi @crazyrov , when i tried to look   pool Default clone , i figureout that this pool wasnt propertly mapped to a disk volume and device, so a created a new device and the mmd error dissapear.Thanks, without your suggestion , I had never seen if the savedset was in the default clone pool and  I might have never discovered it.

Now the  log shows me this, because the client isnt there , How do i resolve this ? Thanks in advance.

97023:nsrrecopy: Unable to start recover session with server nwserver for dag1server:: Client 'dag1server' is not properly configured on the NetWorker Server

Another method is to create a fake entry in your hosts file and recreate the missing client. Make sure that it will not be backed up.

Right know the library is busy , so i going to try the alias tip then @bingo.1  suggestion.

Thanks a lot, put de alias on the client works for me.

Question: before the update from NW 9.1 to 19.2 

i can send several nsrclone commands to cmd with out issues, it 's was and standalone process and worked like a charm, but with 19.2 after a fiew commands  nsrclone fail with this error.  One solution is to restart the NW server.

116283:nsrclone: retrying mmd reservation request!!!

116284:nsrclone: Sending cancel broker request 18357

PD: Do I open a new forum  thread?

Thanks.

Thanks @crazyrov  i going to try to edit that config on tape devices (the issue is only in the clone to tape process)

Thanks in advance.

Hi @Dsantibanez 

What did you do with the tape devices config to fix this? I think I am seeing the same issue when one of my tape drives in the library is busy (I have 2 drives).

CLEB

Hi, after nearly 5 months, the issue persist, DELL EMC told us tha we have to run an update.We are waiting a backup windows to do it.

But i have to restart every time that i clone to a different pool.

Ok thanks for the info. I am using v 19.0 and I haven't had the issue with changing clone pool or are you talking about multiple tape clone pools? I only use one.

I found this article which isn't very informative

https://www.dell.com/support/kbdoc/en-uk/000050305/ccr-cloning-to-dr-data-domain-fails-with-mmd-reservation-error-messages-nsrclone-being-aborted-since-broker-request-for-mmd-reservation-failed-with-nonretryable-error

wrg to cloning to tape you might also want to look into RPS (recover pipe to save) as according to your logs it is enabled.

This RPS feature might still not be working as good and effective as it was intended to be, when it was introduced. There have been multiple KB articles stating it to be set to disabled ("Disable RPS Clone" attribute of NW server properties). Depending on certain settings when upgrading to nw19 it will be either left enabled, but if it was set to disabled, it will be left disabled.

Cloning of VMware image level backups will use RPS method automatically anyways, regardless if you have en/disabled it on NW server level.

"

180171:nsrclone: Step (3 of 16): NSRCLONE_INIT_PHASE_THREE: Performing Recover Pipe to Save enabled cloning.

"

from the nw19.4 manual:

"Cloning of saveset is not supported from a non-Data Domain device to a DD Cloud Tier device. Cloning fails with the following error:
Failed to get mmd reservation with err: Clone saveset(s) operation from a nonData Domain device to a DD Cloud Tier device is not supported.
● When you perform a fresh installation of NetWorker Server 19.4, RPS cloning is disabled by default.
● If you have NetWorker 19.4 server installed, Dell EMC recommends that you maintain parity with the NetWorker 19.4 storage node in both the RPS Enabled and Disabled mode. However, if you have compatibility and migration challenges and want to maintain earlier versions of the storage node, that is, the N-2 version, then Dell EMC recommends that you use the RPS Disabled mode for cloning. In cases where VMware vProxy save sets are used for cloning, RPS Enabled mode is supported by default. Therefore, Dell EMC recommends that you maintain NetWorker server and storage node compatibility and configure clone actions with the appropriate storage node based on the workloads."

So even regardless of what the recommended RPS state would be, depending on what you use in a NW environment might lead to less than optimal settings, if for example you'd have DD to DD and DD to CB in the same environment. So then you'd have to set RPS to disabled on NW server level.

UPDATE:

I again, yesterday we upgraded both networkers sites from NW 19.2.1.2 to 19.3.0.4 

early cloning jobs  says that the issue is gone (we hope), tapes are mounting faster and the GUI-console is faster too.

May I suggest that you also read this thread: https://www.dell.com/community/NetWorker/retrying-mmd-reservation-request/td-p/7859085