Ellen
For up to and including V 8.1 you must keep ALL logs files since the time
of the OLDEST backup image you will ever restore.
With V 8.1 FP2 we are enabling "rollforward recovery with log skipping"
which essentially means that we will only require the log files which
affect the tablespaces being rolled forward. If there are no log records
that affect the tablespace in a specific log file we will not replay or
recall that log file.
I would recommend that for such a large warehouse you use a storage manager
to manage your backups and log files, such as Tivoli's Storage Manager.
This will allow you to set up a policy for when the log files will be
automatically deleted.
Please note that we have yet to release support for rebuilding a database
from tablespace images, this will be coming soon. Thus you still need a
periodic full DB backup, especially if you adding new tablespaces. This
requirement is for disaster recovery where you have to rebuild your entire
system. For recovery from disk failures or application failure tablespace
back images will suffice. It really depends on what you are trying to
protect yourself from.
With V 8.1 FP2 we are also introducing backup compression which will
compress the data in the backup image before it is written out, and with a
6 TB DB you will need this.
Hope this helps.
_____________________________________________
Dale M. McInnis IBM Toronto Lab
Senior Technical Manager, DB2 UDB Backup, Data Protection and Recovery
Email: [EMAIL PROTECTED]
Phone: (905) 413-2397, Fax: (905) 413-4849, T/L: 969-2397
"Reys, Ellen"
<[EMAIL PROTECTED]
m> To
Sent by: [EMAIL PROTECTED]
owner-db2eug@Lugw cc
ash.org Dale McInnis/Toronto/IBM@IBMCA
Subject
[DB2EUG] ARCHIVE LOGS retention and
01/16/2003 04:21 its critically for RECOVERY? (DB2
PM UDB EEE 7.2 AIX 4.3)
Please respond to
"Reys, Ellen"
<[EMAIL PROTECTED]
m>
Hello,
We have a large warehouse in the above environment (over 6 TB). We take
weekly (Saturdays) backups of the most critical tablespaces and retain
archive logs. We use a native "userexit" to move logs from the active
directory to the archive directory. The backup images are going to three 1
TB file systems on disk simultaneously. One of these filesystems also holds
the archive logs. We keep two good versions of the backup images on disk
until Monday, then the previous version moves to tape and we remain one on
disk prior to next backup.
We do not remove the archive logs, and as a result we started experiencing
a
space problem. I understand that we can implement something where the
archive logs will be moved to another filesystem or tape, etc.
Given that we do not have full database backup, only isolated tablespaces
and the catalog space, and that we can re-build the rest of the tables, my
question is:
Can we remove archive logs older than a month? What is the archive logs
retention, if we have some spaces that have never been backed up? Is that
possible that some of the "old" logs may have something that will prevent
us
from doing successful recovery in case it is needed?
What is the impact on the recovery process of not having a backup of the
USERSPACE?
If we need to recover the database, what would be the best approach in our
scenario?
Thank you,
Ellen Klebaner-Reys
Data Management Services
Inovant - a Visa Solutions Company
[EMAIL PROTECTED]/650-432-1746 m/s: 3125-1D
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
