Hi,

all of our Networker Policies include a step for cloning the completed backups to a second Data Domain.
Primary System is also a DataDomain. We're using DDBoost over LAN. FC is not in use.

We're getting "Volume marked full" and "Verify Label on unload" messages for the Volume mounted in
the DD used as clone target. Triggering networker to wait for another volume in the clone pool.

But the usage of the DD pools is constantly between 50-60 %. So they we're never full. Even when
Networker terminates the affected nsrclone jobs, subsequently running clones from following policies
succeed without troubleshooting. If Networker doesn't terminate the affected job, it won't help to reset
the full flag on the DD clone volume. Networker still waits for another volume in the pool, leaving all
the currently running nsrclone jobs stuck indefinately. We then have to terminate them by "kill -9".
Then the volume wait event goes away leading to the same result as when Networker had terminated
them itself.

Can this somehow be the result of concurrency between clone jobs trying to duplicate the same
savesets? But why we're then getting the volume marked full messages?