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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot determine status of the backup process. 1

Status
Not open for further replies.
May 21, 2004
21
US
Host OS: Red Hat Linux
Client OS: Windows 2000

I have a Windows client that will not backup successfully (out of about 100 others). It writes the backup to the tape then it fails when it tries to write the index and gets the following error: "Cannot determine status of the backup process. Use mminfo to determine job status."

I went through the EMC documentation and everything points to the space available on the client but there is plenty of space. I even uninstalled and re-installed the client.

Any ideas?

 
Is the client behind a firewall or something similar?
Run a nsrck -L3 check in the index for the problem client, perhaps it´s a bit corrupted. Try and backup just one small file and see if you still get the same problem. Also, try a manual save from the client and see if that works.

Cheers!
Maverick
 
Hi - Please check the NetWorker Error Message Guide for help with this problem. There is a good explanation for this error, as well as some troubleshooting tips.

-ag100
 
Maverick, thanks for the information. I was able to complete a manual save from the client but I am not able to run a scheduled backup from the server.

AG100, the error guide points to a space problem but both the client and server have plenty of disk space. Thanks.



 
Ok, so manual save works from the client. If you have a firewall between the server and client, i´ll bet my money that´s where the problem is. Please verify if you have a FW and we´ll go through that process. If you have no FW then the problem is most likely name resolution related. I´m betting the server cannot do a reverse lookup on the clients ip adress. If you have a DNS, use nslookup from the backup server to verify the name resolution. If you get incorrect answers, correct the DNS entry.

nslookup short_client_name
nslookup long_fqdn_client_name
nslookup ip_adress
ping -a ip_adress

If you don´t use DNS, make sure the hosts files on both server and client are populated with the correct info:

ip_adress short_name long_name

Make sure that the /nsr/res/servers file contain all known names for the backupserver, short AND long name on separate rows.

Cheers!
Maverick
 
Maverick, all of the problems I have ever had with Windows clients have been DNS related. When this occurs I usually add their entry to the hosts file on the server. But on this particular client I added the name of the server into the client hosts file, and it worked.

Thanks for help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top