Sorry not sure, I haven't seen anything
like that before.
Does the tape prefix of SSO mean shared
storage option? Maybe something going on with that, but I don't use
SSO and I am not very familiar with it.
Jared
"rascal" <rascal1981 AT gmail DOT com>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
03/06/2008 03:31 PM
|
To
| Jared.Seaton AT mylanlabs DOT com
|
cc
| veritas-bu AT mailman.eng.auburn DOT edu, veritas-bu-bounces AT mailman.eng.auburn DOT edu
|
Subject
| Re: [Veritas-bu] Netbackup client failing
on daily incremental but ok on the weekly fulls; weird |
|
I guess that could help huh? Sorry about that but
here it is:
3/5/2008 8:06:47 PM - started process bpbrm (4508)
3/5/2008 8:06:47 PM - connecting
3/5/2008 8:06:48 PM - connected; connect time: 00:00:01
3/5/2008 8:06:48 PM - mounted
3/5/2008 8:06:48 PM - positioning SSO352 to file 3
3/5/2008 8:07:05 PM - positioned SSO352; position time: 00:00:17
3/5/2008 8:07:05 PM - begin writing
3/5/2008 8:10:01 PM - Error bpbrm(pid=1352) from client SSHMKTFIL02: ERR
- failure reading file: C:\WINNT\system32\wbem\Logs\FrameWork.log (WIN32
13: The data is invalid. )
3/5/2008 8:21:35 PM - Error bpbrm(pid=1352) socket read failed, An existing
connection was forcibly closed by the remote host. (10054)
3/5/2008 8:21:48 PM - end writing; write time: 00:14:43
file read failed(13)
3/5/2008 8:21:49 PM - Error bpsched(pid=6352) suspending further backup
attempts for client SSHMKTFIL02, policy XXX-XXXXXX-XXX, schedule DailyIncr-XXX
because it has exceeded the configured number of tries
3/5/2008 8:21:49 PM - Error bpsched(pid=6352) backup of client XXXXXX exited
with status 13 (file read failed)
A couple of notes;
1. The error always reports in NB as error code 13
2. Sometimes the line about the failure reading file C:\..... is
in there, sometimes not but it fails regardless
Let me know what your thoughts are on this!
On Thu, Mar 6, 2008 at 2:07 PM, <Jared.Seaton AT mylanlabs DOT com>
wrote:
Could you provide the actual errors you are getting.......
Jared
Good afternoon everyone,
I thought I would send this out and see what the group has
to say regarding this. I have the following configuration:
1. W2K SP2 Netbackup 5.1 master
2. W2K SP1 Netbackup 5.1 MP4 client
3. Weekly full backup job and daily incremental job
4. Simple OS level backup
The problem I have is that the weekly full job works fine
on this client while the daily incremental fails. Time doesn't seem
to be a factor as I have tried different times for running the incremental.
Both the client and server can communicate just fine during the incremental
and there is no firewall, filter, etc... between the two. In the
event viewer I did find the following:
2/16/08 - Daily incremental backup fails
2/16 - 7:48:?pm - backup start
2/16 - 7:48:27pm - Volume Shadow Copy svc start
2/16 - 7:48:27pm - Volume Shadow Copy svc running
2/16 - 7:48:33pm - MS Shadow Copy provider svc start
2/16 - 7:48:33pm - MS Shadow Copy provider svc running
2/16 - 8:31:31pm - Volume Shadow Copy svc stop
2/16 - 8:34:32pm - MS Shadow Copy provider svc stop
2/16 - 9:01:46pm - WMI Performance adapter svc start
2/16 - 9:01:46pm - WMI Performance adapter svc running
2/16 - 9:04:00pm - WMI Performance adapter svc stop
2/16 - 10:16:44pm - WMI Performance adapter svc start
2/16 - 10:16:44pm - WMI Performance adapter svc running
2/16 - 10:19:00pm - WMI Performance adapter svc stop
2/16 - 10:19:44pm - WMI Performance adapter svc start
2/16 - 10:19:44pm - WMI Performance adapter svc running
2/16 - 10:22:00pm - WMI Performance adapter svc stop
2/17 - 11:00:00am - backup fails
While the weekly full looks like this:
2/17/08 - Weekly full backup successful
2/17 - 7:48:16pm - backup start
2/17 - 7:48:24pm - Volume Shadow Copy svc start
2/17 - 7:48:25pm - Volume Shadow Copy svc running
2/17 - 7:48:32pm - MS Shadow Copy provider svc start
2/17 - 7:48:32pm - MS Shadow Copy provider svc running
2/17 - 8:38:53pm - WMI Performance adapter svc start
2/17 - 8:38:53pm - WMI Performance adapter svc running
2/17 - 8:41:00pm - WMI Performance adapter svc stop
2/18 - 8:12:50am - backup complete
2/18 - 8:15:44am - Volume Shadow Copy svc stop
2/18 - 8:18:43am - MS Shadow Copy provider svc stop
The only thing I can think of, and I haven't found a link just yet is that
there is a problem with the VSS/WMI services that might be causing this.
Other than that, I can't really find a good correlation.
Any hints anyone?
--
Matthew MCP, MCSA, MCTS, OCA
rascal1981 AT gmail DOT com
Define Trouble:
Why did you apply THAT patch??.... _______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted
with it may contain legally privileged, proprietary and/or confidential
information intended solely for the use of the addressee. If you
are not the intended recipient, you are hereby notified that any review,
dissemination, distribution, duplication or other use of this message and/or
its attachments is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of the original message and its attachments. Thank you.
==============================================================================
--
Matthew MCP, MCSA, MCTS, OCA
rascal1981 AT gmail DOT com
Define Trouble:
Why did you apply THAT patch??.... _______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you.
==============================================================================
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|