Scaling Out the Oracle Business Intelligence System 6-19
the different addresses communicating with the Administration Server and other servers. See
Chapter 7, Setting Up Node Manager for further details. The procedures
in that chapter must be performed twice using the information provided in Table 6–2
.
6.10 Configuring Server Migration for the Managed Servers
Server Migration is required for proper failover of the Oracle BI Publisher components in the event of failure in any of the APPHOST1 and APPHOST2 nodes. See
Chapter 8, Configuring Server Migration
for further details.
6.11 Backing Up the Installation
After you have verified that the scaled out domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of
problems in the further steps. The backup destination is the local disk. This backup can be discarded after the enterprise deployment setup is complete. At that point, the
regular deployment-specific backup and recovery process can be initiated. Oracle Fusion Middleware Administrators Guide provides further details. For information on
describing the Oracle HTTP Server data that must be backed up and restored, refer to the Backup and Recovery Recommendations for Oracle HTTP Server section in that
guide. For information on how to recover components, see the Recovering Components and Recovering After Loss of Component Host sections in the guide.
For recommendations specific to recovering from the loss of a host, see the Recovering Oracle HTTP Server to a Different Host section in the guide. Also refer to
Oracle Database Backup and Recovery User’s Guide for information on database backup.
Perform these steps to back up the installation at this point:
1. Back up the Web tier:
a. Shut down the instance using opmnctl:
WEBHOSTn ORACLE_BASEadmininstance_namebinopmnctl stopall
b. Back up the Middleware home on the Web tier using the following command
as root: WEBHOSTn tar -cvpf BACKUP_LOCATIONweb.tar MW_HOME
c.
Back up the Oracle instance on the Web tier using the following command: WEBHOSTn tar -cvpf BACKUP_LOCATIONweb_instance_name.tar ORACLE_INSTANCE
Repeat this step for WEBHOST2.
d.
Start the instance using opmnctl: WEBHOSTn cd ORACLE_BASEadmininstance_namebin
WEBHOSTn opmnctl startall
2.
Back up the database. This is a full database backup either hot or cold using Oracle Recovery Manager recommended or operating system tools such as tar
for cold backups if possible.
Table 6–2 Details for Host Name Verification for Node Manager and Servers
Run Host Name HOST
Server Name WLS_SERVER
Run1: APPHOST1
bi_server1 Run2:
APPHOST2 bi_server2
6-20 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
3.
Back up the BI Instance in the application tier, as follows:
a.
Shut down the instance using opmnctl: APPHOST1 ORACLE_INSTANCEbinopmnctl stopall
b.
Back up the Middleware home on the application tier using the following command as root:
APPHOST1 tar -cvpf BACKUP_LOCATIONbi.tar MW_HOME
c.
Back up the Oracle instance on the application tier using the following command:
APPHOST1 tar -cvpf BACKUP_LOCATIONbi_instance_name.tar ORACLE_INSTANCE
d.
Start the instance using opmnctl: APPHOST1 ORACLE_INSTANCEbinopmnctl startall
4.
Back up the Administration Server and Managed Server domain directories to save your domain configuration. The configuration files all exist in the ORACLE_
BASEadmin domain_name directory. Run the following command to create the backup:
APPHOST1 tar -cvpf edgdomainback.tar ORACLE_BASEadmindomain_name
Note: Create backups on all computers in the application tier by following the
steps shown in this section.
7
Setting Up Node Manager 7-1
7
Setting Up Node Manager
This chapter describes how to configure Node Manager in accordance with the EDG recommendations.
This chapter contains the following topics:
■
Section 7.1, About Setting Up Node Manager
