If this only happens sporadically I assume that all available devices are used for the pool. Consequently NW will wait for one to finish the job and continue with the with the clone operation.
One obvious reason could be that you have selected device(s) for a specific pool. If you do that, you will of course exclude the device to server other pools. Keep in mind: "Enablers are also disablers".
So the best practice is to not select/assign a device to a pool. Do not forget that NW will not do that automatically Besides that, we would need to know a bit more about your configuration.
bingo.1
2.4K Posts
0
December 23rd, 2021 05:00
If this only happens sporadically I assume that all available devices are used for the pool. Consequently NW will wait for one to finish the job and continue with the with the clone operation.
One obvious reason could be that you have selected device(s) for a specific pool. If you do that, you will of course exclude the device to server other pools. Keep in mind: "Enablers are also disablers".
So the best practice is to not select/assign a device to a pool. Do not forget that NW will not do that automatically Besides that, we would need to know a bit more about your configuration.
PrinceAijaz
1 Rookie
•
38 Posts
0
December 24th, 2021 06:00
What types of devices you are using. DD or Tape?
Also are you using separate SNs for clones ?
barry_beckers
393 Posts
0
December 24th, 2021 10:00
Also the NW version matters as there is a never ending stream of fixes related to cloning. As others have said, what are we dealing with here?
figodido
2 Posts
0
December 28th, 2021 04:00
Hi,
DD
Also are you using separate SNs for clones - YES
NW version 19.3.0.4