Re: Backing Up Rollback Tablespaces

In article <CH9zoH.12H_at_butch.lmsc.lockheed.com> stroup_at_aspen.ops.lmsc.lockheed.com () writes:
>
>O.K. Now you've got me worried!
>
>We are currently using Hot Backups as our primary method of backup. I've
>got a separate tablespace just for my rollback segments...Do I need to
>include this tablespace in my hotbacks? And what are my risks if I don't?
>
> judie

Judie,

If you do not backup ALL the database files, (including RB, SYSTEM, LOG FILES , CONTROL FILES, etc...) then you can only perform partial recovery. For example if you have failure of several disks and you loose control files and system tablespace, you might need to do a full database recovery. This can be achieved through a full cold backup and rolling transactions forward using the offline redo logs manually, or using hot backups if you have designed the backup scenarios carefully. In some cases, I have seen people just backing up vital data files (data tablespaces) and forget about system, control files, log files, etc. Data synchronization is something you should look at carefully. Unfortunately this e-mail medium is not too appropriate to delineate all the backup/recovery options available to every client's specific case.

I tend to look at the worst case scenario when I design backup policies but that need not necessarily be the case. (I've been burnt once too many times)

Regards,
S. Tedjarati
Unisys Hong Kong and China Limited Received on Tue Nov 30 1993 - 04:37:00 CET