1 Rookie
•
25 Posts
0
42
Filesystem backup failing
Hi @all,
I am having issues backing up the filesystem from RHEL server. I can see below error when I perform backup:
181407:save: Step (1 of 7) for PID-1611877: Save has been started on the client 'nppf-db-srv1-dc.nppf.org.bt'.
174412:save: Step (2 of 7) for PID-1611877: Running the backup on the client 'nppf-db-srv1-dc.nppf.org.bt' for the save set '/NWclient'.
180569:save: Identified a save for the backup with PID-1611877 on the client 'nppf-db-srv1-dc.nppf.org.bt'. Updating the total number of steps from 7 to 6.
174920:save: Step (3 of 6) for PID-1611877: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '/NWclient'.
175297:save: Unable to set up the direct save with server 'nppf-networker-srv1-dc.nppf.local': Client 'nppf-db-srv1-dc.nppf.org.bt' is not properly configured on the NetWorker Server..
175024:save: Cannot open a save session with NetWorker server 'nppf-networker-srv1-dc.nppf.local': Client 'nppf-db-srv1-dc.nppf.org.bt' is not properly configured on the NetWorker Server..
174921:save: Step (4 of 6) for PID-1611877: Unable to connect to the target media device through the nsrmmd process for the save set '/NWclient'.
Has anyone solved the issue?
Regards,
Durga Mukhia
fabian_o
1 Rookie
1 Rookie
•
23 Posts
0
June 14th, 2024 10:40
Looks like a DNS or NetWorker naming problem to me.
This KB-article may help.
Durga Mukhia
1 Rookie
1 Rookie
•
25 Posts
0
June 14th, 2024 11:28
@fabian_o thank you for the article. In fact the networker was trying to refer to another name of the client. Once I added the correct alias, the backups are running fine.
Thank you once again for your valuable input. Appreciated!
Regards,
Durga Mukhia