asked on

Need some guidance with backup/restore strategy

I have a database I want to be able to recover to a time when failure has occurred. The database in NOARCHIVELOG mode and planning on using incremental differential backups, running level 0 backup on Friday at 11PM and level 1 backups daily.

This is the script to create level 0 backup:

run {
      SHUTDOWN IMMEDIATE;
      STARTUP NOMOUNT;
      BACKUP LEVEL 0 WITH TAG 'inc_lvl0' DATABASE;
      ALTER DATABASE OPEN;
}

and for level 1:

run {
      SHUTDOWN IMMEDIATE;
      STARTUP NOMOUNT;
      BACKUP LEVEL 1 WITH TAG 'inc_lvl1' DATABASE;
      ALTER DATABASE OPEN;
}

Then the recovery script is as follows:

run {
      SHUTDOWN IMMEDIATE;
      STARTUP NOMOUNT;
      RESTORE CONTROLFILE;
      ALTER DATABASE MOUNT;
      set until time "TO_DATE('29-JAN-2013 10:51:00','DD-MON-YYYY HH24:MI:SS')";
      RESTORE DATABASE;
      RECOVER DATABASE;
      ALTER DATABASE OPEN RESETLOGS;
}

Can someone tell me what can I do to improve my backup/recovery strategy and also see if anything I am doing is wrong?
I'd appreciate your recommendations.

P.S. I am not sure if I need to restore a control file.. Do I?

slightwv (䄆 Netminder)

>>recover to a time when failure has occurred

May not be possible in no archive mode. You may only be able to restore to the point of the last backup if the current online redo logs have been overwritten but are necessary for the recovery.

Any particular reason you don't want to run in archive log mode? Typically if a database is important enough to need a recovery plan, it is important enough to need archive log mode.

I'll have to defer to the 'correctness' of your strategy to the RMAN other Experts on the site. From your previous questions, I know the basics and prettry much what I needed to use for my specific databases.

I'm not fully versed on ALL RMAN workings.

I would suggest running in archive log mode, enable block change tracking and cumulative incrementals (rolls the last lvl1 into the current lvl0). This is what I do.

You still have an outstnading issue to address:
backup retention. how long to keep backups on disk, how to ensure you have access to a backup when you need it, etc...

YZlat

ASKER

a few questions:

1) so UNTIL TIME will not work with a database in NOARCHIVELOG mode?

2) how do i eneble block change tracking and cumulative incrementals ans what will it give me?

ASKER CERTIFIED SOLUTION

slightwv (䄆 Netminder)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial