ADSM-L

Re: ADSM and hot oracle back up.

2000-03-08 19:59:55
Subject: Re: ADSM and hot oracle back up.
From: "Thomas A. La Porte" <tlaporte AT ANIM.DREAMWORKS DOT COM>
Date: Wed, 8 Mar 2000 16:59:55 -0800
I can't comment on EBU/RMAN/SQLBacktrack based solutions, as
we've only done script-based Oracle backups, however, the
process of restoring an Oracle database is almost always
dependent on the nature of the failure. How one goes about
restoring depends on what one lost.

The redbook on backing up databases (mentioned by several others)
is useful. For a much more thorough coverage of backup/recovery
for Oracle I highly recommend the Oracle Backup & Recovery
Handbook from Oracle Press, by Rama Velpuri. To me this book is
indispensable. In addition to several chapters that explain the
intricacies of the process(es) that Bernard mentions below, there
is a chapter that includes at least a dozen or more different
situations (lost datafile of SYSTEM tablespace, lost datafile of
non-SYSTEM tablespace, lost redo logs, etc., etc.) and the
recovery options available in each case.

To my mind, backup/recovery of the databases is *the* one thing
that a DBA absolutely must get right.

 -- Tom

Thomas A. La Porte
DreamWorks Feature Animation
tlaporte AT anim.dreamworks DOT com

On Wed, 8 Mar 2000, Kelly Lipp wrote:

>Can you provide further information regarding the restoration process: lay
>down the tablespaces, restore the redo logs, apply the redo logs, etc.?
>
>Thanks,
>
>Kelly J. Lipp
>Storage Solutions Specialists, Inc.
>PO Box 51313
>Colorado Springs CO 80919
>(719)531-5926
>Fax: (719)260-5991
>www.storsol.com
>lipp AT storsol DOT com
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Survoy, Bernard J
>Sent: Wednesday, March 08, 2000 1:33 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: ADSM and hot oracle back up.
>
>
>Oracle "hot" backups involve putting tablespace files into "backup" mode
>while the data is copied.  You can either place the entire database in this
>mode, or do this a tablespace file at a time, however you choose.  Note that
>during this process, the tablespace copies will be "fuzzy" since Oracle
>(from 7.3.2 up) updates them while you are backing them up, however, this is
>OK, because the archive/redo logs do special logging of tablespaces that are
>in backup mode and are aware of when they are placed in this mode and when
>they come out.  The database is fully available for use, the logs are the
>key to consistent recovery.  I'm not aware of actual locking being done in
>either case (table or row level).
>
>This is based on experience with Oracle database backups using user
>developed scripting and BACKINT with SAP.
>
>Thanks,
>Bernie Survoy
>MVS Systems Engineer
>216.615.9324 phone
>216.621.5920 fax
>StorageTek
>INFORMATION made POWERFUL
>
>
>
>-----Original Message-----
>From: Jason Thomas [mailto:syne7 AT YAHOO DOT COM]
>Sent: Wednesday, March 08, 2000 2:23 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: ADSM and hot oracle back up.
>
>
>        I am told that when Tivoli data protection backups up Oracle, it
>locks
>(quieses) the database at the table level.  I am also told that SQL Back
>trac will do the same thing but at the Row level.  Can anyone confirm this?
>If so the real question is are the Oracle DB's 100% available for use during
>back up?  Any help would be greatly appreciated.
>
>Regards,
>
>Jason
>
>
>__________________________________________________
>Do You Yahoo!?
>Talk to your friends online with Yahoo! Messenger.
>http://im.yahoo.com
>
<Prev in Thread] Current Thread [Next in Thread>