What about a file called networkr.cfg in the root of the NT servers C:
drive? This is created by Networker User when editing local directives.
Maybe it's excluding N:, etc.
When did N: stop being backed up, or has it never been backed up? Is it an
NT4 server or Win2K? If 2K has Change Journal been enabled for all drives?
--Shawn
----- Original Message -----
From: "James Edwards" <jedwards AT SOS.STATE.TX DOT US>
To: <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
Sent: Wednesday, August 27, 2003 11:17 AM
Subject: Re: [Networker] Zero bytes on one drive backup
> N: is a local drive but F: and above are actually one a fiber raid array.
> They are directly attached to this server. I checked for .nsr files but
> there are none that I can find.
>
> It's a mystery to me.
>
> Jim Edwards
>
> -----Original Message-----
> From: Ed Guenther [mailto:eguenthe AT us.ibm DOT com]
> Sent: Tuesday, August 26, 2003 9:46 AM
> To: Legato NetWorker discussion; James Edwards
> Subject: Re: [Networker] Zero bytes on one drive backup
>
>
>
> is N:\ a local drive? Did you check for "nsr.dir" files that may exclude
> it from being backed up?
>
> -Ed.
>
>
>
>
>
> James Edwards
>
> <[email protected]. To:
> NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>
> TX.US> cc:
>
> Sent by: Legato Subject: [Networker]
Zero
> bytes on one drive backup
> NetWorker discussion
>
> <NETWORKER@LISTMAIL.
>
> TEMPLE.EDU>
>
>
>
>
>
> 08/26/2003 10:32 AM
>
> Please respond to
>
> Legato NetWorker
>
> discussion,James
>
> Edwards
>
>
>
>
>
>
>
>
>
> I have a Solaris box backing up and NT box. I'm running the latest
version
> of Networker 6 on the Solaris box and the latest version of the Networker
> client on the NT box.
>
> However, when I run the backup, I get the following output.
>
>
> *ntcache: E:\ level=full, 14 GB 01:41:22 452335 files
> ntcache: N:\ level=full, 0 KB 00:01:48 0 files
> txsos-3: index:ntcache level=full, 407 MB 00:01:00 115 files
>
> Notice the N: drive. The N: drive has GBs of files on it but even on a
> full
> backup it backs up zero bytes. If I look at the daemon.log, it starts and
> end the backup of this drive in two seconds. The E: drive backs up
> correctly every night with no problem. Both the N: and E: drives are
> direct
> connected to this server.
>
> As I was typing this, I decided it would be a good idea to check a few
> other
> drives above E:. Turns out it won't backup the F: drive either. There
are
> no error messages in any of the logs I can find.
>
> Anyone else seen this behavior?
>
> Jim Edwards
> Systems Manager
> Texas Secretary of State
>
>
>
>
> --
> 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|