Veritas-bu

[Veritas-bu] Verify my bug? v6.0.4 bpimagelist and retention levels

2007-09-27 18:41:03
Subject: [Veritas-bu] Verify my bug? v6.0.4 bpimagelist and retention levels
From: <Mark.Donaldson AT cexp DOT com>
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Thu, 27 Sep 2007 16:22:38 -0600
I think I've found a bug, can somebody verify in a different
environment?

I create a primary backup using a standard filesystem policy with a
one-month retention (rl=3 in my environ).  I then use bpduplicate to
create a six-month copy (rl=5).  Your levels may vary, of course.

I now have two copies, one rl=3, and copy 2, rl=5.

If I use bpimagelist and look for rl=5 images, this backup is not found.
I'd argue it's a rl=5 backup and it should be found, even if it's not
the primary copy.

Once the primary copy, copy 1, expires and copy 2 is all that's left,
bpimagelist still will not list it, the primary IMAGE record for the
backup has the old rl=3 recorded in it.

It seems that bpimagelist only searches the IMAGE records for the
retention levels, not the COPY/FRAG records, and that once the retention
level field is populated in the IMAGE record, it's never updated by the
image deletion/copy promotion process.

I'd argue that the image should be printed by bpimagelist if *any* copy
of it has a retention of 5 (or what's being searched for) and that the
IMAGE record's retention field should be also updated when the primary
copy expires and the secondary, longer retention copy, is promoted.

I've been through the fix list for MP5 and this doesn't seem to be on
it.  Don't know if 6.5 has the problem or not.

Below, this is a backup that was orignally a rl=3 copy, a copy 2 was
created with rl=5. Now rl=3 is expired, the copy count for this image
correctly shows one copy.  The bpimagelist command only seems to check
the IMAGE record, not the individual copies when searching for specific
retention levels.  The IMAGE header shows rl=3 even though it's tracking
the rl=5 copy now.  See my <<notes>> in the output.

This, to me, is a bug, but I'd like verification before I report it to
Veritas.

Client:            Exchange-01
Backup ID:         Exchange-01_1175420896
Policy:            Exchange
Policy Type:       MS-Windows-NT (13)
<snip>
Retention Level:   1 month (3)    <<<< Original image was rl=3 >>>
Backup Time:       Sun Apr 01 2007 03:48:16 (1175420896)
Elapsed Time:      19439 second(s)
Expiration Time:   Thu Oct 04 2007 03:48:16 (1191491296) << Correct for
rl=5, not =3 >>
Encrypted:         no
Kilobytes:         143450427
Number of Files:   31
Number of Copies:  1             <<<< Primary copy is expired, this
tracks duplicate >>>
<snip>
Files File Name:   Exchange_1175420896_UBAK.f

Copy number:       2             <<<< Copy to was first duplicate >>>
 Fragment:         1
 Kilobytes:        1075200
 Remainder:        0
 Media Type:       Media Manager (2)
 Density:          hcart2 (14)
 File Num:         6
 ID:               003276
 Host:             uscobrmfa-ug-50
 Block Size:       262144
 Offset:           80032
 Media Date:       Sat Apr 14 2007 14:00:17 (1176580817)
 Dev Written On:   8
 Flags:            0x0
 Media Descriptor:        ?
 Expiration Time:  Thu Oct 04 2007 03:48:16 (1191491296)
 MPX:              1
 retention_lvl:    6 months (5)  <<<<<  rl=5, six month retention  >>>>
 checkpoint:       0
 resume num:       0

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

<Prev in Thread] Current Thread [Next in Thread>