Los siguientes síntomas se notifican en el registro del demonio.
19.04.2021 16:36:39 retrying mmd reservation request!!!
19.04.2021 16:36:49 Received reservation request status as 'rejected'. Retry check mmd-request status: count is 5(out of 5).
19.04.2021 16:36:49 Sending cancel broker request 460
19.04.2021 16:36:49 Request 460 was cancelled.
Se intentó habilitar y deshabilitar los nodos de almacenamiento, actualizar nsrmmd habilitando y deshabilitando el nsrmmd dinámico, reiniciar todos los servicios de NetWorker e iniciar el trabajo de clonación. Se pudo ver que el dispositivo no se monta cuando se inicia el clon y que se ve lo mismo en el registro del demonio.
0 19.04.2021 16:35:26 nsrd NSR notice 04/19/21 16:35:26.204079 broker_find_usable_save_mmd: Unable to find device for volume 511ABQL7. --------àthis volume is available in tape library
160814 19.04.2021 16:35:26 nsrd NSR warning Failed to allocate save mmd since it was not started. Reject request id 456 .
98307 19.04.2021 16:35:26 nsrd NSR severe There are no available devices for client `server.domain.com' on all usable storage nodes for the requested save operation.
0 19.04.2021 16:35:29 nsrd NSR notice 04/19/21 16:35:29.168450 Total broker requests created by preprocess 2.
199745 19.04.2021 16:35:29 nsrclone NSR warning Received reservation request status as 'rejected'. Retry check mmd-request status: count is 1(out of 5).
116284 19.04.2021 16:35:29 nsrclone NSR notice Sending cancel broker request 456
70495 19.04.2021 16:35:29 nsrd NSR warning User cancelled request 456.
180876 19.04.2021 16:35:29 nsrclone NSR info Request 456 was cancelled.
116283 19.04.2021 16:35:39 nsrclone NSR notice retrying mmd reservation request!!!
0 19.04.2021 16:35:46 nsrd NSR notice 04/19/21 16:35:46.275930 broker_find_usable_save_mmd: NSRATTR_CLONE_SAVE_VOL_HINT not set in the request.
160814 19.04.2021 16:35:46 nsrd NSR warning Failed to allocate save mmd since it was not started. Reject request id
Este problema se debe a un defecto de código que se rastrea con el problema n.º 330893.
Este problema se aborda en NetWorker 19.4.0.3 y versiones posteriores. Para solucionar este problema, actualice a la versión más reciente de NetWorker.