Veritas made a change in the consistency check - I think at 5.1 MP4
where it will actually move the image to a temporary holding place if it
thinks it is bad.  Incidentally if you have any jobs running it will
also kill the jobs because it thinks the image is bad. I am wondering if
it tried to do anything with the images for the disk backups?  

I know you aren't supposed to run the consistency while a backup is
running but I have some 24/7 masters.  I asked VERITAS engineering to
provide a consistency check that runs while backups are running or at
least provide an option to not move images.

Monte

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Rob
Worman (home)
Sent: Saturday, May 27, 2006 10:50 AM
To: Esson, Paul
Cc: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Catalog Inconsistency with DSSU

Paul-

Bottom Line: What you are seeing is nothing to worry about.
This is a cosmetic bug in the "bpdbm -consistency 2" command.

What's happening is, bpdbm is encountering the "pseudo-images" that are 
part of the DSSU relocation operation.  (you can tell from the 
"__DSSU_POLICY_" prefix...)

These are NOT normal backup images, but bpdbm -consistency doesn't seem 
to know that and so it reports errors as if they were normal backup 
images.

I am pretty certain this behavior has already been fixed in one of the 
most recent patch releases.

HTH
rob

On May 26, 2006, at 11:31 AM, Esson, Paul wrote:

> Folks,
>
>
>
> I have a 5.0 MP4 installation on a Windows 2000 SP4 server that has a
> SATA array attached and configured for disk staging.  Backups appear
to
> be working okay but I ran a bpdbm -consistency 2 check recently in
> preparation for a proposed upgrade to v5.1 and have discovered the
> following for which I cannot find any reference on the Symantec web
> site.  Has any one got any thoughts as to what has occurred here?  
> There
> are multiple entries of this type for a number of images.
>
>
>
> checking image file <__DSSU_POLICY_unix_full_1147475093_FULL>
>
>>> PRIMARY_COPY is set to an invalid copy
>
>>> EXPIRATION is not set to the next valid copy to expire
>
>
>
> Regards,
>
>
>
> Paul Esson
> Redstor Limited
>
> Direct:          +44 (0) 1224 595381
> Mobile:         +44 (0) 7766 906514
> E-Mail:         paul.esson at redstor.com
> Web:            www.redstor.com
>
> REDSTOR LIMITED
> Torridon House
> 73-75 Regent Quay
> Aberdeen
> UK
> AB11 5AR
>
> Disclaimer:
> The information included in this e-mail is of a confidential nature
and
> is intended only for the addressee.  If you are not the intended
> addressee, any disclosure, copying or distribution by you is
prohibited
> and may be unlawful.  Disclosure to any party other than the
addressee,
> whether inadvertent or otherwise is not intended to waive privilege or
> confidentiality.
>
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu