Numéro d’article: 534251

printer Imprimer mail E-mail

save failed to authenticate with nsrmmd on host : Timed out..

Résumé: Backup are failing with timeout error

Produit principal: NetWorker 9.2.1

Produit: NetWorker plus…

Dernière publication: 12 mars 2020

Type d’article: Break Fix

État publié: En ligne

Version: 3

save failed to authenticate with nsrmmd on host : Timed out..

Contenu de l’article

Problème


Backup failing with below error:
 
175297:save: Unable to set up the direct save with server 'NW_server_name': 
Unable to connect to the storage node on host <storage_node_name>: 
save failed to authenticate with nsrmmd on host <NW_server_name>: Timed out..
Cause
nsrmmd was in hung state, and the server parallelism was set 32 (default); due to which no additional processes could be started for backups. The existing jobs were failing with timeout error.
Résolution
Stop NetWorker services to remove all the processes in hung state. Kill jobs manually if the process does not stop when services are stopped.
Linux: 
Stop Services: nsr_shutdown
Confirm all processes have stopped and collect the PID of any processes that do not stop: ps -ef | grep nsr
Kill any hung services: kill -9 PID
Start services: service networker start

Windows:
Stop Services: net stop nsrexecd /y
Confirm all processes have stopped and collect the PID of any processes that do not stop: tasklist | findstr nsr
Kill any hung services: taskkill /PID PID /F
Start services: net start nsrd && net start gstd
 
Increase parallelism to higher range and initiate the backup. Server --> Server Properties --> General
Note: View --> Diagnostic View must be enabled:

User-added image
The server parallelism attribute controls how many save streams the server accepts simultaneously. The more save streams the server can accept, the faster the devices and client disks run. Client disks can run at their performance limit or the limits of the connections between them. The default Server parallelism is 32 you can configure the parallelism up to 1024. When increasing values it should follow: 32, 64, 128, 256, 512, 1024.

Server parallelism is not used to control the startup of backup jobs, but as a final limit of sessions accepted by a backup server. The server parallelism value should be as high as possible while not overloading the backup server itself.
 
Notes

Problème


Backup failing with below error:
 
175297:save: Unable to set up the direct save with server 'NW_server_name': 
Unable to connect to the storage node on host <storage_node_name>: 
save failed to authenticate with nsrmmd on host <NW_server_name>: Timed out..
Cause
nsrmmd was in hung state, and the server parallelism was set 32 (default); due to which no additional processes could be started for backups. The existing jobs were failing with timeout error.
Résolution

Stop NetWorker services to remove all the processes in hung state. Kill jobs manually if the process does not stop when services are stopped.
Linux: 
Stop Services: nsr_shutdown
Confirm all processes have stopped and collect the PID of any processes that do not stop: ps -ef | grep nsr
Kill any hung services: kill -9 PID
Start services: service networker start

Windows:
Stop Services: net stop nsrexecd /y
Confirm all processes have stopped and collect the PID of any processes that do not stop: tasklist | findstr nsr
Kill any hung services: taskkill /PID PID /F
Start services: net start nsrd && net start gstd
 
Increase parallelism to higher range and initiate the backup. Server --> Server Properties --> General
Note: View --> Diagnostic View must be enabled:

User-added image
The server parallelism attribute controls how many save streams the server accepts simultaneously. The more save streams the server can accept, the faster the devices and client disks run. Client disks can run at their performance limit or the limits of the connections between them. The default Server parallelism is 32 you can configure the parallelism up to 1024. When increasing values it should follow: 32, 64, 128, 256, 512, 1024.

Server parallelism is not used to control the startup of backup jobs, but as a final limit of sessions accepted by a backup server. The server parallelism value should be as high as possible while not overloading the backup server itself.
 

Notes

Article Attachments

Pièces jointes

Pièces jointes

Propriétés de l’article

Première publication

mer. juin 05 2019 12:59:51 GMT

Première publication

mer. juin 05 2019 12:59:51 GMT

Noter cet article

Précis
Utile
Facile à comprendre
Avez-vous trouvé cet article utile ?
0/3000 characters