Just like any other application
or database deployment, we should also devise a backup and recovery policy for
the OEM deployments. Here I would discuss how we devise a backup policy to back
up our OEM 13c (and also previous versions) deployment. Following are the major
components that should be considered for the backup. Official documentation explains this in more detail
Backup Management Repository
Since Management Repository is an Oracle database, any backup procedure can be adopted for backing up Management Repository, for example configuring an RMAN backup. To recovery the repository in case of disaster, just perform the recovery using RMAN backup.
Since Management Repository is an Oracle database, any backup procedure can be adopted for backing up Management Repository, for example configuring an RMAN backup. To recovery the repository in case of disaster, just perform the recovery using RMAN backup.
Backup OMS
This includes backing up Software Library, Middleware Home, Instance Home, Administration Server. For my OEM 13c Installation available here, I have following directories.
This includes backing up Software Library, Middleware Home, Instance Home, Administration Server. For my OEM 13c Installation available here, I have following directories.
[oracle@salman11]$ cd /u01/software/em/
[oracle@salman11]$ ls -l
total 8
drwxr-x---.
4 oracle oinstall 46 May 25
13:29 agent
drwxr-x---.
4 oracle oinstall 35 May 25
12:44 gc_inst
drwxr-x---. 58 oracle oinstall 4096 Jun 24 14:19
middleware
drwxr-x---. 75 oracle oinstall 4096 Jun 26 06:35
swlib
|
agent directory contains agent installation, gc_inst is Instance Home
(contains configuration files for Weblogic Server, OMS and webtier), middleware
contains Middleware installation, and swlib contains software library.
Oracle recommends taking a filesystem backup of all directories; along with Oracle Inventory so that everything could be restored back in case of any disaster.
Along with above directories backup, OMS configuration backup should also be taken using following command
Oracle recommends taking a filesystem backup of all directories; along with Oracle Inventory so that everything could be restored back in case of any disaster.
Along with above directories backup, OMS configuration backup should also be taken using following command
$OMS_HOME/emctl exporconfig oms –sysman_pwd
<sysman_password> -dir <backup directory>
Example
[oracle@salman11]$ $OMS_HOME/bin/emctl
exportconfig oms -sysman_pwd salman77 -dir /u01/oms_backup/
Oracle Enterprise Manager Cloud Control 13c
Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
ExportConfig started...
Backup directory is /u01
Machine is Admin Server host. Performing Admin
Server backup...
Exporting emoms properties...
Exporting secure properties...
Export has determined that the OMS is not fronted
by an SLB. The local hostname was NOT exported.
The exported data can be imported on any host but
resecure of all agents will be required. Please
see the EM Advanced Configuration Guide for more
details.
Exporting configuration for pluggable modules...
Preparing archive file...
Backup has been written to file: /u01/oms_backup/opf_ADMIN_20160627_145626.bka
The export file contains sensitive data.
You must
keep it secure.
ExportConfig completed successfully!
|
Backup Agent
Agents are not usually
backed up. A new installation (usually from cloud control), is done in case we lose
the agent software.
No comments:
Post a Comment