* Need help on Backup *

[Anantha]

Hi All,
We are haveing 4 DB's in our company, and presently we used to take
offline backup on once in a week, we knew we cant recover last-in-time
data. But we would like to shift to some new technique which saves
time, sapce & last-in-time recover. we heard about the online backups
and incremental backups, what are they actually, what is the
differences. Here the main requirements is recovering the with- miniual
loss and 24x7 availability is needed.
I will be greatfull if someone could help me on this issue asap.

Thanks
Anantha
(sm**********@g mail.com)

[Mark Yudkin]

Your best source of information is the section entitled "Recovering Data"
under "Tasks" - "Administer ing database systems" in the DB2 documentation.

"Anantha" <sm**********@g mail.com> wrote in message
news:11******** **************@ z14g2000cwz.goo glegroups.com.. .

Hi All,
We are haveing 4 DB's in our company, and presently we used to take
offline backup on once in a week, we knew we cant recover last-in-time
data. But we would like to shift to some new technique which saves
time, sapce & last-in-time recover. we heard about the online backups
and incremental backups, what are they actually, what is the
differences. Here the main requirements is recovering the with- miniual
loss and 24x7 availability is needed.
I will be greatfull if someone could help me on this issue asap.

Thanks
Anantha
(sm**********@g mail.com)

[Bernd Giegerich]

Hi,

and/or the "Data Recovery and High Availability Guide and Reference"
(http://www-306.ibm.com/software/data...anualsv8.html).

8.2 (8.1.7) has some very nice features addressing high availability
needs and eases the whole log management, but you need a proper strategy
(24x7 needs more than only a good backup plan).

Regards,
Bernd

[Pierre Saint-Jacques]

DB2 V8.2 offers the following support for recovery. Define your DB's with
the logretain parameter set to RECOVERY.
You can then do:
1) Full Database or Tablespace backups. Offline or Online.
2) Full Database Restore (Always offline)
3) Selective Tablespace Restore, offline or online.

Moreover, there are a series of parms. in your DB CFG that allow you to
define how thearchiving of your logs will be handled.
I would suggest some reading of the DB2 UDB Administration Guide which tyou
can access on line.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Anantha" <sm**********@g mail.com> a écrit dans le message de news:
11************* *********@z14g2 00...legr oups.com...

Hi All,
We are haveing 4 DB's in our company, and presently we used to take
offline backup on once in a week, we knew we cant recover last-in-time
data. But we would like to shift to some new technique which saves
time, sapce & last-in-time recover. we heard about the online backups
and incremental backups, what are they actually, what is the
differences. Here the main requirements is recovering the with- miniual
loss and 24x7 availability is needed.
I will be greatfull if someone could help me on this issue asap.

Thanks
Anantha
(sm**********@g mail.com)

[Anantha]

Thanks for the support, I have been starting looking the guide.

[UDBDBA]

Hi Anantha:
I am not sure what version of DB2 you are running, but if it's 8.2 and
you need 24x7, here is a few things you can get started:

1. Save space - Use compression. In my shop, i get 66% compression.

2. Speed - Backup to disk and let the disk be backed up to TSM at a
later time. Straight backups to TSM / any storage device are time
consuming and can't beat the speed you get with disks.

3. I am not sure about the size of DB, but 8.2 self tunes the backup
performance. We usually backup a 44 gig DB into a 12 gig comperssed
image to disk in 20 minutes.

4. Use mirror logpath, just incase logs disappaer from active path

5. If you don't have multiple hardware resource to do logshipping/HADR,
TrueCopy (HITACHI Term for bit-to-bit copy), udb replication to
maintain a warm standby, then device a plan to take full, incremental
and delta backups to keep the recovery time as short as possible. In
my shop, we have 5 copies of DB on two different DR sites and we only
take daily full backups and retain 3 day old images on TSM.

HTH

Vijay

[Jay Lal via DBMonster.com]

Anantha

Could you please specify following-
your db size :
Available space :
Recovery time objective:
(How much time is available if you have to recover)
Recovery point objective:
(How much data lose is acceptable )

Based on above requirement I can help you to come up with your BR strategy.
--
Jay
IBM DB2 Engineer
NetApp Inc.

[Anantha]

Hi Jay & All,
The size of the DB is 5GB and, Recovery time objective is not an
constraint, but last point-in-time data recover. I would like to know
steps to do this, and wat are the tools and how should run these
process.

Thanks & Regs
Anantha

[Mark Yudkin]

The database is small enough that you only need to use log retention, online
backup proceudres and the user exit to move log files to the backup media.
See the DB2 documentation for the details.

"Anantha" <sm**********@g mail.com> wrote in message
news:11******** **************@ g47g2000cwa.goo glegroups.com.. .

Hi Jay & All,
The size of the DB is 5GB and, Recovery time objective is not an
constraint, but last point-in-time data recover. I would like to know
steps to do this, and wat are the tools and how should run these
process.

Thanks & Regs
Anantha