Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to determine the status of the backup process

Status
Not open for further replies.

mahalingam1

IS-IT--Management
Dec 7, 2007
75
hi all, I have a problem with a backup on suse server.

When we start a backup on this server from the legato's console, the backup don't finish saccessfully and the server go to an locked state.

I was looking in a legato logs in the client and i found the following message:

09:25:03 nscd: 7940 cannot create /var/run/nscd/passwd; no persistent database used
09:25:03 nscd: 7940 cannot create /var/run/nscd/group; no persistent database used
Jun 4 09:25:03 xinetd[7938]: xinetd Version 2.3.13 started with libwrap loadavg options compiled in.
Jun 4 09:25:03 xinetd[7938]: Started working: 3 available services



In the backup server i found in the daemon.log the following message:


04/06/2008 9:30:30 nsrd media notice: Save set (1732657597) bakup_server:<saveset> volume 000030L3 on \\.\Tape1 is being terminated because: inactivity timeout
38714 04/06/2008 9:30:30 nsrd <backup server>:<saveset> done saving to pool 'Prueba' (000030L3) 8503 MB


and in the daemon.raw of the backup server:

Cannot determine status of backup process. Use mminfo to determine job status, relative to this saveset

On the other hand we have started the same backup with
the same saveset on the client via "save" command Forwarding the output to a file Obtaining:


save: <saveset> level=full, 32 GB 00:20:36 40863 files

We can do the backup via "save" command on the client but we can't do the same backup via legato's console.

We thought that the problem was due authentication between backup server and the client (cannot create /var/run/nscd/passwd), but we can do a backup of another saveset on the same client.


Please anyone can help me???

Thanks in advance and regards
 
Not so easy - a ncsd daemon does not exist for EMC NetWorker. Also, to the best of my knowledge, there is no /var/run directory it must read /var/nsr/run. And there will not be any subdirectories.
Are you running an OEM version?

For me it seems like the NW server cannot really contact the remote device at the Windows server. An inactivity timeout usually points to a network related problem (including reverse name resolution).

Most likely, if you run a manual backup, it will use another drive (at the server?) and succeed.
 
Hi 605, the first thank you very much for your information.

We have two diferents entries for the same backup client in the DNS. We will delete one of them and then we will try to do a backup from the server. The DNS has reverse name resolution enabled.

Thanks and regards

 
Hi 605, we deleted one entry of the client in DNS but we have the same problem (we have reverse name resolution enabled). We can do a backup from the client via "save" command and finished successfully. On the other hand when we try to do the same backup via "savegrp" command on the backup server but the client become to an locked state. the backup start correctly but few minutes later the backup is aborted by the server.

I don't think the problem is due to the drive in use for this backup because we have done a backup of other saveset via legato console.

regards
 
Well - i am still looking for an explanation why you think the info comes from a NW log file. See my first response:

"Not so easy - a ncsd daemon does not exist for EMC NetWorker. Also, to the best of my knowledge, there is no /var/run directory it must read /var/nsr/run. And there will not be any subdirectories.
Are you running an OEM version?"

Googling for 'ncsd' finds the 'name server cache daemon'. You will find a lot of entries describing its functionality and considerations.

Worst case, you may temporarily use hosts files for further tests. If these will run fine, this once again points to a name resolution problem.
 
Hi 605, I imagine to enable host file in nscd only i must edit the /etc/nscd.conf file and change the line

enable-cache hosts no

for this one

enable-cache hosts yes

and restart the nscd daemon -service nscd restart- (suse server)

it's ok?

thank you very much and regards

Juan
 
I am not a network specialist and can not verify it right away. But you will find lots of info in the web.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top