Networker

Re: [Networker] NSR problem backing up Windows 2000

2003-11-07 21:07:41
Subject: Re: [Networker] NSR problem backing up Windows 2000
From: "Narkinsky, Brian" <Brian.Narkinsky AT DEP.STATE.FL DOT US>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Fri, 7 Nov 2003 21:07:34 -0500
Check your switch and cables.  I'll bet that you are locked on your end but,
not on the switch side.  Or you have a bad cable or something like that.
 
Brian

        -----Original Message----- 
        From: Rohrich, James [mailto:James.Rohrich AT UOP DOT COM] 
        Sent: Fri 11/7/2003 5:47 PM 
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU 
        Cc: 
        Subject: Re: [Networker] NSR problem backing up Windows 2000
        
        

        You said the nics are specific, but what about the port settings.
Have you
        verified with the network people that the port settings are set the
same and
        again it should not be auto.
        
        -----Original Message-----
        From: Stan Horwitz [mailto:stan AT TEMPLE DOT EDU]
        Sent: Friday, November 07, 2003 1:16 PM
        To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
        Subject: [Networker] NSR problem backing up Windows 2000
        
        
        Hello NetWorker users;
        
        We have a Windows 2000 server here that refuses to allow full
backups.
        This server has a C:\ and a D:\ drive. Sometimes, the C:\ drive
backups up
        fully, other times, it doesn't. We got the C:\ drive to do a full
backup
        twice today, but the D:\ drive continues to present a problem.  The
D:\
        drive fails to back up almost all the time for full backups.
Incrementals
        seem okay. The previous date when both disk drives received a full
backup
        was October 16.
        
        I have placed this server in its own savegroup just for testing
purposes.
        When that savegroup finishes, the nwadmin GUI still shows backup
activity
        for this particular host and it continues for about half an hour
before
        the save streams time out due to inactivity.
        
        The usual troubleshooting measures such as verifying reverse look ups
on
        the Windows client and our Solaris 9 Legato server. Both client and
server
        can nslookup each other. Our Network services people say they have
dropped
        their firewall for this server. There's no local software firewall
        software running on the server or client. The client's NIC driver is
        current and the settings on the NIC are specific, not auto-detect.
        
        Both the Legato client and the Legato server are running version
6.1.3 of
        the Legato software and all backups are done via our Legato server's
        gigabit card. The Legato server is a Sun Enterprise 450 running
Solaris 9.
        We're not having problems with other clients of this nature.
        
        We get errors such as:
        
        * this_server.temple:C:\ save: RPC error: Unable to send
        11/07/03 13:51:39 savegrp: this_server.temple:C:\ will retry 0 more
time(s)
        11/07/03 13:51:40 savegrp: killing pid 21140
        * this_server.temple:D:\ save: RPC error: Unable to send
        
        Any ideas on how to troubleshoot this issue would be appreciated.
        
        --
        Note: To sign off this list, send a "signoff networker" 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 networker" 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.
        =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
        

<Prev in Thread] Current Thread [Next in Thread>