Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Scheduling backups in Oracle Enterprise Manager Database Control 1

Status
Not open for further replies.

holdahl

IS-IT--Management
Apr 4, 2006
213
NO
I'm trying to set up backup of some Oracle Database Servers using the Oracle Enterprise Manager 10g Database Control.

I have managed to schedule some backups, but where do I find the schedules that I have created?
Is there some way to list them?
How do you backup the redo log?


-holdahl
 


You can find the schedules under the "Jobs" tab.

how do you backup the redo log?

You don't, redo logs are "archived" automatically.
When you create (schedule) backups with EM, there is an option to backup (and remove) the archive logs.
[3eyes]





----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb
 
Does the database need to be in ARCHIVELOG mode for redo logs to be automatically backed up.?
I don't see an option for doing backup of redo logs when creating a backup.


-holdahl
 

REPEAT:

You don't backup redo logs, redo logs are "archived" automatically. DB must be in archive log mode.

When you create (schedule) backups with EM, there is an option to backup (and remove) the archive logs.
[nosmiley]





----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb
 
That's right. Redo logs are never backed up explicitly, which is why you don't see any option to do so. That doesn't mean that they don't get backed up at all. To see what is happening "behind the scenes", please take a look at selected output of one of my backup jobs, which does a level 0 database backup followed by an archive log backup.

After connecting to the database and recovery catalog, the first thing that happens is the level 0 backup. According to the job log, the command being executed is

rman job log said:
RMAN> backup incremental level 0 cumulative device type disk tag 'LEVEL0_BACKUP_OP03_070409090024' database;

There follows various log messages about allocating i/o channels and which database files are included in which backup sets. Eventually the database backup finishes with the message

rman job log said:
channel ORA_DISK_2: backup set complete, elapsed time: 01:31:47
Finished backup at 04-JUL-09

Rman then does an autobackup of the control file and spfile, after which it is ready to start the archive log backup. The command for this is

rman job log said:
RMAN> backup device type disk tag 'LEVEL0_BACKUP_OP03_070409090024' archivelog all not backed up delete all input;

At this point rman has to deal with the fact that there is a partially full redo log that is in danger of not getting backed up. Rman is smart enough to know that this needs to be done as part of its "backup...archivelog all" command, even though you haven't explicitly asked for it to be done. So, the very first thing in the job log after the backup archivelog command is

rman job log said:
Starting backup at 04-JUL-09
current log archived

Rman has just forced a log switch, so the contents of the redo log is written to archive, ready and waiting to be backed up along with all the other archive log files.

So you can stop looking for an option in Database Control to back up the redo log. Oracle already knows what has to be done and includes it as part of its normal backup procedures.
 
Hi,
A star to karluk - that is the way to answer a question - if you have the time and knowledge to do so - it not only provides the answer but shows how it was derived...



[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Thanks for great answers.


Let's say I run a full backup every sunday at 6pm.
If I want to delete those files before running the job next time, is that set in the policy setting 'Keep this backup for the specific number of Days'?

I did try to set up an incremental backup job, but the file created was bigger than the file created in the full backup.
Something to do with backup settings?

-holdahl
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top