Veritas-bu

[Veritas-bu] db extention and schedules.

2003-01-13 04:10:20
Subject: [Veritas-bu] db extention and schedules.
From: hampus.lind AT rps.police DOT se (Hampus Lind)
Date: Mon, 13 Jan 2003 10:10:20 +0100
This is a multi-part message in MIME format.

------=_NextPart_000_007B_01C2BAEB.FA7EF3A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all!

Can someone please help my to understand, what is what when preforming a =
db extention backup such as informix or oracle.
I `am starting to belive that our configurations are bad.=20
Can`t you configure several "application backups" with different =
retentions in the same policy?
Witch retention will be the correct one? The one configured in =
"automatic full backup" or the one in "application backup"?

We have a problem to get a schduleded backup to preform the right =
"application backup", for exampels:
full_daily sched, starts from the master, then the db client starts =
several other backups at ones. These backups starts with a different =
"application backup" (full_year_) instead of full_daily_. This one =
(full_year_) is the first listed in the policy.

Have anyone had this problem?? Or does anyone have some good pointers?

Regards Hampus.


------=_NextPart_000_007B_01C2BAEB.FA7EF3A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Can someone please help my to =
understand, what is=20
what when preforming a db extention backup such as informix or=20
oracle.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I `am starting to belive that our =
configurations=20
are bad. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Can`t you configure several =
"application backups"=20
with different retentions in the same policy?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Witch retention&nbsp;will be the =
correct=20
one?&nbsp;The one configured in "automatic full backup" or the one in=20
"application backup"?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We have a problem to get a schduleded =
backup to=20
preform the right "application backup", for exampels:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>full_daily sched, starts from the =
master, then the=20
db client starts several other backups at ones. These backups starts =
with a=20
different "application backup" (full_year_) instead of full_daily_. This =
one=20
(full_year_)&nbsp;is the first list</FONT><FONT face=3DArial size=3D2>ed =
in the=20
policy.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Have anyone had this problem?? Or does =
anyone have=20
some good pointers?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards Hampus.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_007B_01C2BAEB.FA7EF3A0--


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