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

Problems Backing up Domain Controller

Status
Not open for further replies.

nishai

MIS
Apr 29, 2003
8
US
I have UNIX workstation and I'm trying to backup a Windows 2000 domain controller server using NW 7.0. This server hangs the backup and fails with this error:

client1: All 5 retries attempted
client1: All nsrexec: authtype nsrexec
client1: All type: NSR client description;
client1: All pools supported: Yes;
client1: All browse time support: Yes;
client1: All multiple balanced streams supported: Yes;

Any insight would be greatly appreciated. I've been having this problem for awhile.

nisha
 
It lloks like a "network related problem", which is most often due to name resolution.

As a usual procedure, may i suggest to start the group from the command line:

savegrp -v -l level -G groupname

Look for error codes here. If the backup ssems to hang, let NW try to abort this
(default is 30 mins).

Does a manual backup work?
 
I just tried it and the manual backup worked great. The server immediately responded and ran an incremental backup.
 
What is the difference between when the command is ran via the command line versus automated in the gui? I don't understand why one would work and the other wouldn't.
 
During a manual backup, the client contacts the server.

During an automatic backup, the server contacts the client.

In your case, the name resolution is not always the same.


If you start a process from the command line, you have a lot of more options.
For example "-v" will inform you about each single step which is much better for
troubleshooting. However, the result should be the same.
 
I had the ADIC technician come out for our Scalar 1000 and he ran diagnostics on all of our drives. It turns out that they all were bad, or were working in a degraded form. We had them replaced and we've seen a dramatic increase in throughput as well as the issue with our tapes becoming full prematurely and spitting all kinds of errors like "No Recorded Entity Found" and tape_rewind wind failed disappearing. If anyone else runs into this problem, please check out your hardware!
 
Name resultion.
Check all name resultion and nsr\res files servers file, hosts file and lastly aliases tab in the client
 
The problem is that it backs up from time to time, then it'll fail giving that error...so I don't know what it could be. Is it possible that it can some resolve itself and then other times have issues?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top