Re: OnBar and ADSM
Posted in 1999
Topics: Backup & Restore, Logging & Checkpoints
Daniel Ehrlich wrote:
>
> We use ADSM as the storage manager for onbar. I was wondering when, and if,
> the
> client ever deletes backups of log files or the databases? Does anyone more
> familiar with
> onbar than myself have any insight?
As Rick says, there is no way to expire your logical logs until version
9.20 (2000?). Your archives, if that's what you mean by databases, will
expire as soon as the next archive is taken. This is because the name of
the archive is the same. However, the problem with logical log backups
is that each log is given a unique name based on the log number, so it
never gets overwritten.
I believe, if you are desperate, that Informix Consulting in Germany did
write a utility for one of their clients. But it was not robust enough
to release as a utility.
Cheers,
--
Mark.
+----------------------------------------------------------+-----------+
| Mark D. Stock http://www.informix.com |//////// /|
| mailto:mdstock@mydas.freeserve.co.uk |///// / //|
| http://www.iiug.org +-----------------------------------+//// / ///|
| |What year 2000 bug? year 2000 bug? |/// / ////|
| |year 2000 bug? year 2000 bug? year |// / /////|
| |2000 bug? year 2000 bug? year 1900 |/ ////////|
+----------------------+-----------------------------------+-----------+
In article <7oufkm$rgg$1@news.xmission.com>,
"Mark D. Stock" <mdstock@mydas.freeserve.co.uk> wrote:
>
> Daniel Ehrlich wrote:
> >
> > We use ADSM as the storage manager for onbar. I was wondering
when,
and if,
> > the
> > client ever deletes backups of log files or the databases? Does
anyone more
> > familiar with
> > onbar than myself have any insight?
>
> As Rick says, there is no way to expire your logical logs until
version
> 9.20 (2000?). Your archives, if that's what you mean by databases,
will
> expire as soon as the next archive is taken. This is because the name
of
> the archive is the same. However, the problem with logical log
backups
> is that each log is given a unique name based on the log number, so
it
> never gets overwritten.
>
> I believe, if you are desperate, that Informix Consulting in Germany
did
> write a utility for one of their clients. But it was not robust
enough
> to release as a utility.
>
> Cheers,
> --
> Mark.
>
Mark,
As far as I know what happens with the database backups is that the
previous backups are marked "inactive", as you take a new backup. Adsm
can be set up to keep inactive backups for either a preset time, eg. 30
days, or you can specify the number of versions. Eg. with daily
level 0 backups, number of versions = 7, you'll always have seven
backups in adsm. The oldest ones are expired (meaning they get
deleted from adsm storage).
>
+----------------------------------------------------------+-----------+
> | Mark D. Stock http://www.informix.com |////////
/|
> | mailto:mdstock@mydas.freeserve.co.uk |///// /
//|
> | http://www.iiug.org +-----------------------------------+//// /
///|
> | |What year 2000 bug? year 2000 bug? |/// /
////|
> | |year 2000 bug? year 2000 bug? year |// /
/////|
> | |2000 bug? year 2000 bug? year 1900 |/
////////|
>
+----------------------+-----------------------------------+-----------+
>
>
--
Gabor Heppes
IBM Global Services
gaborh@au1.ibm.com
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Gabor Heppes <gaborh@au1.ibm.com> wrote in message
news:7ovnk0$upf$1@nnrp1.deja.com...
> In article <7oufkm$rgg$1@news.xmission.com>,
> "Mark D. Stock" <mdstock@mydas.freeserve.co.uk> wrote:
> >
> > Daniel Ehrlich wrote:
> > >
> > > We use ADSM as the storage manager for onbar. I was wondering
> when,
> and if,
> > > the
> > > client ever deletes backups of log files or the databases? Does
> anyone more
> > > familiar with
> > > onbar than myself have any insight?
> >
> > As Rick says, there is no way to expire your logical logs until
> version
> > 9.20 (2000?). Your archives, if that's what you mean by databases,
> will
> > expire as soon as the next archive is taken. This is because the name
> of
> > the archive is the same. However, the problem with logical log
> backups
> > is that each log is given a unique name based on the log number, so
> it
> > never gets overwritten.
> >
> > I believe, if you are desperate, that Informix Consulting in Germany
> did
> > write a utility for one of their clients. But it was not robust
> enough
> > to release as a utility.
> >
> > Cheers,
> > --
> > Mark.
> >
>
> Mark,
>
> As far as I know what happens with the database backups is that the
> previous backups are marked "inactive", as you take a new backup. Adsm
> can be set up to keep inactive backups for either a preset time, eg. 30
> days, or you can specify the number of versions. Eg. with daily
> level 0 backups, number of versions = 7, you'll always have seven
> backups in adsm. The oldest ones are expired (meaning they get
> deleted from adsm storage).
>
Hi All,
Dont forget about the sysutils database. The entries are not removed from
the
tables ever. The release notes give examples on how to clean up the tables.
They
recommend not to remove the log entries though. There is also the ixbar.#
file, in
INFORMIXDIR/etc. You will have to clean it up also, if you like to do house
cleaning:)
I also assume that you are talking about using onbar stand alone, and not
using a third party
utility such as Backtrack. It makes every backup(log or dbspace) unique.
Therefore, no
matter what you configure your management class to, it will NEVER expire ANY
backup.
They do supply(ftp from their website) a utility that will expire the
unwanted backups on the
ADSM server. You have to supply the backups though, to which you want
expired. I query
the ADSM database to retrieve this info, based on a date range, then feed it
into their utility.
> >
> +----------------------------------------------------------+-----------+
> > | Mark D. Stock http://www.informix.com |////////
> /|
> > | mailto:mdstock@mydas.freeserve.co.uk |///// /
> file://|
> > | http://www.iiug.org +-----------------------------------+//// /
> ///|
> > | |What year 2000 bug? year 2000 bug? |/// /
> ////|
> > | |year 2000 bug? year 2000 bug? year |// /
> /////|
> > | |2000 bug? year 2000 bug? year 1900 |/
> ////////|
> >
> +----------------------+-----------------------------------+-----------+
> >
> >
>
> --
> Gabor Heppes
> IBM Global Services
> gaborh@au1.ibm.com
>
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.