Make sure that you are not using the Directive "System_State:\" on a Win2K3
server.
There is a new directive (in NB 5.? ) for the Windows 2003 servers. If you
are not using "All_LOCAL_DRIVES", there is a new directive for the Win2K3
that get everything (It is something like System_Shadow_State:\). I
"stumbled" across the reference to it while looking up something else for a
5.1 server rollout.
According to the docs, you can't fully restore a Win2K3 server if you
specify "System_State:\" in the file list.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Paul
Keating
Sent: Friday, June 17, 2005 9:19 AM
To: Veritas List
Subject: RE: [Veritas-bu] status 156 snapshot error
Ok....a little more research here may be uncovering something.
I'm backing up a cluster, which has two physical nodes...each physical node
as C: and D: local drives, as well as R:, S:, T: and U: which are data
stores. Each data store is made available as a file share via a virtual node
on the cluster.
In other words:
phys_file_srvr_1 C:\ D:\
phys_file_srvr_2 C:\ D:\
virt_file_srvr_a R:
virt_file_srvr_b S:
virt_file_srvr_c T:
virt_file_srvr_d U:
So I am backing up R, S, T, U via their respective virtual names, so that
regardless of which side of the cluster (phys_1 or phys_2) the service is
living on, I can back it up cleanly.
I back up C, D, and System_State:\ via BOTH phys nodes.
Since I'm backing up all or R, S, T and U simultaneously, I'm thinking it
may be possibly an issue of backing up U:, and netbackup is trying to write
the VSP snapshot of U to a drive that is being backed up by another job.
Reading the manual, it says you cannot create a snapshot on a drive that
already has it's own snapshot on another disk.....as when you are backing up
two drives simultaneously....you cannot snapshot C to D and D to C.
So I guess I need to set the jobs to snapshot everything to one drive, say
D:, then turn off snapshots for backup of the D: drive.
Paul
> -----Original Message-----
> From: Shyam Hazari [mailto:shazari AT gmail DOT com]
> Sent: June 17, 2005 9:01 AM
> To: Jim Langston
> Cc: Paul Keating; Veritas List
> Subject: Re: [Veritas-bu] status 156 snapshot error
>
>
> I do get them once in a while. This was caused by VSP.
>
> I try to cleanup _vrts_frzn_img_xxx folders from C:\Program
> Files\Veritas\NetBackup\Temp\
>
> -Shyam
>
> On 6/17/05, Jim Langston <jlangston AT northeastmedical DOT org> wrote:
> >
> > Paul,
> >
> > I get several times a week. I'm using 5.0MP4 on W2K.
> >
> > I can't seem to find why I get them. Anyone have any idea?
> >
> > Thanks,
> >
> > Jim
> > ________________________________
> > From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> > [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Paul
> > Keating
> > Sent: Friday, June 17, 2005 8:26 AM
> > To: Veritas List
> > Subject: [Veritas-bu] status 156 snapshot error
> >
> >
> > anyone get this often? occasionally?
> >
> > recommended remedy?
> >
> > Win 2003 cluster client
> >
> > Solaris 8 NBU 5.0 MP4
> >
> > I've got it twice this week on the same client.
> >
> > Paul
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
