This is a multipart message in MIME format.
--=_alternative 0018CF4665256C05_=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
----------------------------------------------------------
Any opinions, express or implied, presented are solely those of the author and
do not necessarily represent those of Standard Chartered Group.
---------------------------------------------------------
--=_alternative 0018CF4665256C05_=
Content-Type: text/plain; charset="us-ascii"
Hi,
I have configured a daily schedule with media retention level 3 (1 month).
And to my surprise, here is the output of "bpmedialist -mlist -U":
id rl images allocated last updated density kbytes
restores vimages expiration last read <------- STATUS
------->
--------------------------------------------------------------------------------
UNIX01 3 41 07/01/2002 20:00 07/02/2002 00:46 dlt 46494989
0 41 08/02/2002 00:46 N/A
UNIX02 3 36 07/02/2002 20:00 07/03/2002 00:47 dlt 46544454
0 36 08/03/2002 00:47 N/A
UNIX03 3 35 07/03/2002 20:00 07/04/2002 00:45 dlt 46666072
0 35 08/04/2002 00:45 N/A
..............
..............
Note: 1> Tape-labels are based on the day_of_month. So on 1st day of the
month, UNIX01 will be used, etc..
2> DLTs are of 40/80 GB capacity.
Now when I will use same media, say UNIX01 on Aug 1, 2002, NetBackup will
create a second image on UNIX01 because image on that is going to expire
only on 2nd Aug. Obviously that will result in tape getting full and hence
it will result in not all clients being backed up. This appears dumb to me
as I would expect that image (UNIX01 in this case) will expire on the last
day of the month. So that I can reuse it completely as a fresh tape.
Is there any workaround for this? Or I will have to expire these images
manually (or thru script).
Regards,
Vivek
--=_alternative 0018CF4665256C05_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I have configured a daily schedule with
media retention level 3 (1 month). And to my surprise, here is the output of
"bpmedialist -mlist -U":</font>
<br><font size=2 face="sans-serif"> </font>
<br>
<br><font size=2 face="sans-serif"> id rl images
allocated last updated
density kbytes restores vimages
expiration last read
<------- STATUS -------></font>
<br><font size=2
face="sans-serif">--------------------------------------------------------------------------------</font>
<br>
<br><font size=2 face="sans-serif">UNIX01 3 41
07/01/2002 20:00 07/02/2002 00:46 dlt 46494989
0 41 08/02/2002 00:46
N/A</font>
<br>
<br><font size=2 face="sans-serif">UNIX02 3 36
07/02/2002 20:00 07/03/2002 00:47 dlt 46544454
0 36 08/03/2002 00:47
N/A</font>
<br>
<br><font size=2 face="sans-serif">UNIX03 3 35
07/03/2002 20:00 07/04/2002 00:45 dlt 46666072
0 35 08/04/2002 00:45
N/A </font>
<br><font size=2 face="sans-serif">..............</font>
<br><font size=2 face="sans-serif">..............</font>
<br><font size=2 face="sans-serif">Note: 1> Tape-labels are based on the
day_of_month. So on 1st day of the month, UNIX01 will be used, etc..</font>
<br><font size=2 face="sans-serif">
2> DLTs are of 40/80 GB capacity.</font>
<br>
<br><font size=2 face="sans-serif">Now when I will use same media, say UNIX01
on Aug 1, 2002, NetBackup will create a second image on UNIX01 because image on
that is going to expire only on 2nd Aug. Obviously that will result in tape
getting full and hence it will result in not all clients being backed up. This
appears dumb to me as I would expect that image (UNIX01 in this case) will
expire on the last day of the month. So that I can reuse it completely as a
fresh tape.</font>
<br>
<br><font size=2 face="sans-serif">Is there any workaround for this? Or I will
have to expire these images manually (or thru script).</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif">Vivek</font>
--=_alternative 0018CF4665256C05_=--
|
