Unsolved
This post is more than 5 years old
47 Posts
0
874
Unix servers backup are in queue for more than 4 days..
Hi All,
Unix servers backup are in queue for more than 4 days for few clients and it is not going to active or running state even after rerunning the group also it is going to same state.Please let us know what should be the cause for this??
ble1
14.3K Posts
0
September 1st, 2015 08:00
Do you have any pending messages on the backup server like requesting volume for some pool?
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
September 2nd, 2015 01:00
In addition to what H has suggested you might want to check the state of the NetWorker client services, if possible restart the services on the client too.
Also, try a client initiated back to the same pool as the scheduled group.
sokundu
47 Posts
0
September 2nd, 2015 03:00
Hello all,
We have no pending message on the backup master server and also we have restarted the services in clients and triggered backup but the issue still exists.Please help me on this....
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
September 2nd, 2015 06:00
Check if there are "save" processes running on the client machine, kill if any and re-try backup.
Have you tried a client initiated backup using "save" ?
What is the version of NetWorker on your server ?
Has this client ever successfully backed up before ?
sokundu
47 Posts
0
September 3rd, 2015 00:00
Hi
I have not tried client initiated backup but i have tried to run it in debug mode but getting same issue.
We are using Networker version 8.1.2.7.
Yes client has successfully backed up before it is failing from last week only.
ble1
14.3K Posts
0
September 3rd, 2015 04:00
Run save in debug from client first and see where that gets you. At the same time monitor daemon.raw on server and normally these two should give you an idea of what is going on.
bingo.1
2.4K Posts
0
September 3rd, 2015 12:00
On the NW server ...
- try to kill the job(s) with "jobkill".
maybe you must stop NW and delete the temp directory before restarting it.
- run "nsradmin -p nsrexec -s nw_client" to test the connection.
If the program does not respond it is most likely that the firewall settings on the UNIX/Linux client have changed.
We have that from time to time - update processes on a client app might be responsible for that.
On the NW client ...
- run "save -vvv -s nw_server [-b pool] /etc"
This should give you enough information. Do not use the debug mode if you do not know what exactly to look for.
Castromotorbox
217 Posts
0
September 7th, 2015 02:00
Hi All,
we have the same issue here with Networker 8.1.3.2. So far, the only way we have found to solve that is, after having stopped Networker Service on the Networker Server and cleaned the tmp and NSR peer information, to reboot Networker Server.
This happen by us from time to time (maybe twice a year). We are backing up about 40 Linux Server with Agent.
Hope it will help.
Cheers.
Greg