The Hunger Site

Friday, May 16, 2008

RMAN and Enterprise Manager

One of the best uses of Enterprise Manager Grid Control is to set up and
schedule daily maintainance tasks, such as RMAN backups. RMAN is
one of the best utilities from Oracle to back up your databases, and it
amazes me that there are some people out there still doing cold backups.
This is one of the oldest techniques of backup, when it was not possible
to do any online (hot) backups, people were forced to do offline (cold)
backups. But when Oracle created online backups (with the alter
tablespace ... backup command), when Oracle created the RMAN
backup utility, then who would still use offline backups?

In any case, coming back to the point, RMAN backups can be set up
very easily using Grid Control. In the past, we used to write unix scripts
to call RMAN, then these scripts had to be installed on each new database
server with modifications, then tested. This normally took about 4 hours
or so for each new database server. But when the same is done using
Grid Control, all we need is the Enterprise Manager Agent on each
server, then we can easily configure and set up and schedule the
RMAN backup for the databases on that server. It would take no
more than 10 minutes or so to do so, which is a big saving in time,
besides the fact that no unix scripts or cron jobs at the unix level
are involved. Grid Control generates the scripts and schedules
the scripts at the times you want, and all logs are accessible
at the Grid Control level.

More on this later. Right now I want to mention my OTN article
"Technical Note: Using Oracle Grid Control with Filer Snapshotting"
which you can read at ,
this explains how you can use Grid Control with Netapps
Filer snapshots to backup the database.



No comments:


Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive