|
Re: [Veritas-bu] Shadow Copy Components failing!
2010-07-21 03:15:19
|
What happens if you try using an NTBackup on the "local"
Server and writing the backup to disk for System State?
Do you get any errors in the Event Log?
Have you tried to disable the AV?
Apologies if any of this has been covered
already.
S.
Hi,
windows team resolved issue with system state backup at their end and is
running fine locally,
we tried testing the Shadow copy component in Netbackup and it completed
with below skipped files
WRN - can't open object:
Shadow Copy Components: (BEDS 0xE000FECB: A failure occurred accessing
the backup component document.)
WRN - can't open object:
Shadow Copy Components:\System Service\Removable Storage Manager\Removable
Storage Manager (BEDS 0xE000FEDD: A failure occurred accessing the object
list.)
WRN - can't open object:
Shadow Copy Components:\System Service\Windows Management
Instrumentation\WMI (BEDS 0xE000FEDD: A failure occurred accessing the
object list.)
WRN - can't open object:
Shadow Copy Components:\System Service\Event Logs\Event Logs (BEDS
0xE000FEDD: A failure occurred accessing the object
list.)
Any idea , what how to
proceed now?
Regards
Sac
On Sat, Jul 17, 2010 at 11:42 AM, Len Boyle <Len.Boyle AT sas DOT com>
wrote:
Hi
Sachin
This is my
understanding,
The Shadow
copy components/system state backups for current windows systems always use
vss for the backup.
The Shadow
copy components/system state backups are a two stage process. The first stage
backups up the components to files written to the system drive. The second
stage has netbackup backing up the files created in stage 1.
The 71 error
is because the first stage failed to write out the files that the second stage
backup was looking for.
To find the
problem look at the windows system and app event logs to find the vss and
other windows errors related to the backup.
Another
method is to try to do a Shadow copy components/system state backup using the
built in windows backup command. If that backup fails then you know that
netbackup has nothing to do with the problem. You can have ntbackup write the
backup data to disk, so it should be easy to set up the test.
If you have
not done so you might want to look for any pending vss patches and dcom
patches. Most of them are in the latest fix pack for windows. If your level of
windows has a fix pack.
We found that
we had problems with windows boot volumes that were netapp luns if certain
rules were not followed and vss used the netapp hardware provider feature for
vss.
Let us know
how this works out for you.
len
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
SACHIN ARORA
Sent: Saturday, July 17, 2010 11:12
AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu; veritas-bu-request AT mailman.eng.auburn DOT edu
Subject:
Re: [Veritas-bu] Shadow Copy Components failing!
I have already reinstalled netbckup on server many
times, however, no luck.
Also , I read below doc , but still the same response, it
fails;
=> I initiated the backup of Shadow copy components:\
with Disable snapshot and continue . Result - backup failed with error
71
=> I initiated the backup of Shadow copy components:\
with Abort on Error . Result - backup failed with error 71
=> I initiated the backup of Shadow copy components:\
with WOFB disabled, Result - backup failed with error 71
====================================
On Fri, Jul 16, 2010 at 11:11 AM, <judy_hinchcliffe AT administaff DOT com> wrote:
Document ID: 327105
http://support.veritas.com/docs/327105
A potential for System State data loss has been
discovered in NetBackup Server / Enterprise Server 6.5.4. This occur when the
System State is selected for backup and snapshot error control is changed from
the default setting to "Disable snapshot and Continue". This issue only
affects Windows clients.
Im facing an issue here. We have a server Windows
2003 SP2 (Netbackup 6.5.4),
Master server - solaris - netbackup 6.5.4
Policy of this server was configureed with backup selection
as ALL_LOCAL_DRIVES.
backup was completing succesfully , however, Shadow Copy
Components was not getting backed up, which we realised today only when we got
a restore tkt for it
we tried for multisreaming , but backup failed with : none
of the files in the file list exist:
ul 15, 2010 7:54:36 PM - Error bptm (pid=17241) media
manager terminated by parent process
Jul 15, 2010 7:54:37 PM - Error bpbrm
(pid=17216) could not send server status message
Jul 15, 2010 7:54:39 PM -
end writing
none of the files in the file list exist (71)
This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England |
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|
