I would have to agree in part with Itzik.  However, if you use the nslookup 
command, you will most likely find that your reverse DNS is where the problem 
is.  You do not have to use local hosts files within your NT network so long as 
all DNS settings are correct on the server.  The only time you should have to 
use local hosts is if perhaps you are running two nics both on separate 
networks for load balancing.

We encountered a very similar issue and by investigating / correcting the 
reverse lookup values, our issue was resolved.

Good luck,

Carter Fowler 
Hardware Service Technician 
The City Of London 
600 - 380 Wellington St. 
London, ON, CA, N6A 5B5 
Off: 519.661.5711 
Cel: 519.870.4956 
Em: cfolwer AT city.london.on DOT ca 


-----Original Message-----
From: imeirson AT MBI.CO DOT IL 
Sent: Thursday, September 19, 2002 2:57 PM
To: imeirson AT MBI.CO DOT IL; NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: Windows 2K Cluster backups extremely slow - 96 hrs for 130GB

Dan,
In this case I would believe Legato....
If you are using DNS, a bad primary server can cause a constant delay for
every and each name resolution.
As you are on NT, I would suggest you add the server to the clients host file
and the clients to the Networker server hosts file.
This way the name resolution for Networker purposes will always be done
locally.
More over, this could be a proof that Legato is right and your DNS setup
should be investigated or alternatively provide you with the definite answer
to Legato's claim about name resolution.
HTH,
        Itzik

-----Original Message-----
From: Dan Francis [mailto:x_franc AT YAHOO.CO DOT UK] 
Sent: Thursday, September 19, 2002 17:29
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Windows 2K Cluster backups extremely slow - 96 hrs for
130GB


Sorry if you have seen this raised before.

I have a Windows NT backup server running 6.1.2 of Legato, backing up a
Windows 2000 cluster, containing three problematic drives.

Profiles 18GB 780000 files.  :- Causes high CPU util and never takes over 48
hours to do 2.5gb.  We know the small files problem will cause some overhead,
but this takes the p*$$.

User Data 130GB :- Backs up over 96 hours and will complete, again the full
finishes just in time for another one.

Shared Data 130GB :- About 80 hours and will complete.

Note : All servers involved are at 100MB Full Duplex.

This has been reported to Legato who blame name resolution !!!! If name
resolution was the problem, we wouldn't get a backup at all.

Any ideas ?????

Regards,

Dan Francis

AT & T Business Services

--
Note: To sign off this list, send a "signoff" command via email to
listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also view and
post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or 
the 
sender immediately and do not disclose the contents to any one or make copies.

** eSafe scanned this email for viruses, vandals and malicious content **
**************************************************************************************************

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=