Are you in fact doing archive logging or circular logging? If you are
invoking the userexit, simply write the archive logs to a different file
system or directory. For example: if your logpath is
/dblogs/db2inst1/dbname/activelogs, have your archive log path
dblogs/db2inst1/dbname/archivelogs. Once the logs are sent to the archive
directory, you can send them to tape and either leave them there (if space
is not an issue), or purge them. After your backup, you can issue the
"archive log ..." command and that send the backup and the log(s) that are
archived off to tape as well. That is what you need to restore to that
particular point in time.
As far as how often to backup and what types you need, it really depends on
how quickly you need to recover and how available the database needs to be.
For some of our regions, we do circular logging (no archive logging) because
restore to the previous night backup is acceptable for some of the test and
development regions. On the other hand, some of our production environments
require more availability. We take full offline backups Sunday, and online
incrementals the rest of the time. We send everything to tape at the end of
the backup script, so our archive logs are vulnerable for 24 hours --
however, we are using Raid 5 technology, so it would take quite a bit for us
to lose them.
We have also implemented flash copy technology where we suspend our database
and flash the SAN/Shark to another set of disk, bring the database up on a
different server and backup it up there, as well as all the other archive
logs. We can basically flash several hundred GB of data in a couple of
minutes, and then spend a couple of hours doing offline backups without
effecting production, both performance wise and availability.
Backup strategy is based on several things, the most important being
application availability and recovery time requirements.
-----Original Message-----
From: ighiurea
[Email address protected]
Sent: Wednesday, May 19, 2004 5:17 PM
To: LazyDBA Discussion
Subject: Re: DB2 v8.1 backup logs on tapes
Hi DBA gurus,
I need some sugestions , plans how you implemented online backups for a big
size db? how often you
backup the db, and copy the archoved logs to tapes, how about active logs to
tapes..etc?
Are other files I need also for restore db ?
Isabella
ighiurea wrote:
> Hello DB2 backup experts,
>
> I have a question also in regards to logs on DB2 UDB ver 8.
>
> I'm using DB2 userxit program to archive the logs to disk to diferit path
from active logs .The
> active logs are on mirror disks ( for redundacy , is it enough?), here
are my questions:
>
> -which logs should I backup daily since I'm running my full online
backup db every 2 weeks ?
> -when can I rewrite this tapes for logs?
>
> Thank you
>
> oliver_mefford wrote:
>
> > are you using the IBM supplied 'userexit' program?
> >
> > Oliver Mefford
> > Senior DBA, Corporate Database Services (CDS)
> > PeopleSoft, Inc. Data Center Facility
> > 5840 Owens Drive, Pleasanton, CA. 94588
> > Office - 925/694-9011
> > Cell - 925/895-6384
> >
> > |---------+--------------------------------------------------------->
> > | | "Joe Philip " |
> > | | [Email address protected]
> > | | azydba.com> |
> > | | |
> > | | 05/18/2004 12:29 PM |
> > | | |
> > |---------+--------------------------------------------------------->
> >
>---------------------------------------------------------------------------
----------------|
> > |
|
> > | To: "LazyDBA Discussion" [Email address protected]
|
> > | cc: (bcc: Oliver Mefford/PeopleSoft)
|
> > | Subject: moving the log files from the regular log path
|
> >
>---------------------------------------------------------------------------
----------------|
> >
> > We have archive logging on for our DB2 UDB 8.1 databases. Our log
directory
> > is getting filled up very often. Can I move the old log files (log files
> > which have 10 day's earlier timestamp) and that do not have the active
> > status? Is there anything else I should aware of before putting a script
to
> > move the old logs to archive log storage location.
> >
> > ---------------------------------------------------------------------
> > PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> > website: http://www.LazyDBA.com
> > To unsubscribe, e-mail: [Email address protected]
> > For additional commands, e-mail: [Email address protected]
> >
> > ---------------------------------------------------------------------
> > PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> > website: http://www.LazyDBA.com
> > To unsubscribe, e-mail: [Email address protected]
> > For additional commands, e-mail: [Email address protected]
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe, e-mail: [Email address protected]
> For additional commands, e-mail: [Email address protected]
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe, e-mail: [Email address protected]
For additional commands, e-mail: [Email address protected]
*************************************************************
This message, including any attachments, may contain
confidential information intended for a specific individual
and purpose, and may be protected by law. If you are not
the intended recipient, please notify the sender by e-mail
or telephone immediately, and then immediately delete this
message. Any disclosure, copying or distribution of this
message, or the taking of any action based on it, by any
unintended recipient is strictly prohibited.
DB2 & UDB email list listserv db2-l LazyDBA home page