It is important to remember that the
installations in an Oracle Collaboration Suite environment are interdependent
in that they contain configuration information, applications, and data that
are kept in sync. For example, when you perform a configuration change, you
might update configuration files in the middle-tier installation and Infrastructure;
when you deploy an application, you might deploy it to all middle-tier installations;
and when you perform an administrative change on a middle-tier installation,
you might update data in the Metadata Repository.
It is, therefore,
important to consider your entire Oracle Collaboration Suite environment when
performing backup and recovery. For example, you should not back up your middle-tier
installation on Monday and your Infrastructure on Tuesday. If you lost files
in your middle-tier installation, you could restore it to Monday’s state.
However, your Infrastructure would be in its current state—out of sync
with the middle tier. And, because you backed up the Infrastructure on Tuesday,
you would have no means of restoring it to a state in sync with Monday’s
middle-tier installation. You would not be able to restore your environment
to a consistent state.
Instead, you should
back up your entire Oracle Collaboration Suite environment at once. Then, if
a loss occurs, you can restore your entire environment to a consistent state.
Roadmap for Backup and Recovery
Implement a backup and recovery
for Oracle Collaboration Suite by performing the following steps:
Learn
about database backup and recovery, because the OracleAS Repository, Oracle
Internet Directory, and the Information Stores are Oracle databases.
Learn about
operating system or your third-party tool backup and recovery, so that you
can back up the files on the operating system.
Learn
about Oracle Calendar backup and recovery: Oracle Calendar uses its own
data store and has its own backup and recovery utilities.
To
prevent loss of application data, place all Collaboration Suite databases
in ARCHIVELOG mode. This includes the OracleAS Metadata Repository, the
Oracle Internet Directory, and the information stores.
Test
the strategy: Ensure that both backup and recovery procedures work.
Implement
the backup strategy: Following a standard backup strategy ensures that you
will be able to plan for recovery operations and avoids confusion and delay
in recovery after a failure. Perform recovery as necessary.
For the purposes of backup and recovery, you can divide your
Oracle Collaboration Suite into different types of files:
Oracle
software files are static files, such as binaries and libraries, that
reside in the Oracle home directories of your Infrastructure, Information
Store, and middle-tiers hosts. Because configuration files are also stored
in the Oracle home directory, Oracle software files backups include configuration
files..
Configuration
files contain configuration information. They reside in the Oracle home
directories of your Infrastructure, Information Store, and middle-tiers
hosts. The configuration files can be for an application or the database.
Examples of database configuration files includes tnsnames.ora, listener.ora,
sqlnet.ora, orapwd, and the spfile/pfile. Although configuration files are
updated during the normal operation of your suite, they are less dynamic
then database files.
Database
files are the data files, redo logs, and control files that make up
your Metadata Repository, Oracle Internet Directory, and Information Storage
databases. They reside on your Infrastructure and Information Store hosts
and are updated during the normal operation of your suite. You can create
these files in any directory. For example, you might store database files
outside of the Oracle home directory to distribute the files over several
disk drives to improve I/O performance..
Oracle
Files BFILEs contain archived files. They can exist in any directory
on the Information Store host and are updated during the normal operation
of your suite..
Calendar
database and configuration files are the files that contain the Oracle
Calendar data and configuration. Like the database files, they do not need
to reside under the Oracle home directory of the hosts where Calendar is
installed. These files are updated during the normal operation of your suite..
Oracle
system files include the /var/opt/oracle
or /etc directory, and the
oraInventory directory. They
exist on each host in your Oracle Collaboration Suite environment. They
usually reside outside of your Oracle Collaboration Suite installations,
although the oraInventory directory may be in an installation home directory.
They are created and updated by Oracle Universal Installer at installation
time and contain information about your installations.
There are a number of different ways of implementing your
backup procedures. A complete Oracle Collaboration Suite environment backup
is a complete backup of every file type on every host in the suite. This is
typically performed just after an Oracle Collaboration Suite installation or
some major administration change (i.e.., a new patch, OS change, topological
change, etc.).
A complete backup (hot or cold) is a full backup of every
Oracle file type on a particular node. You can perform a complete backup while
the system is up (hot) or down (cold). As an alternative to a complete Oracle
backup, if your host is dedicated to Oracle, you can perform a complete system
backup. Although this backup uses more space, it has the advantage of restore
the entire host to a previous state. During recovery, this simplifies the process
of restoring the host.
The example shown in this module performs a complete Oracle
Collaboration Suite environment backup. The first backup you perform should
be a complete Oracle Collaboration Suite environment backup, which includes
all of the files in your environment (each step is covered in detail later in
the module). Before you backup for the first time, perform the following steps:
1.
Create
a record of your environment. In the event you need to reconstruct your
environment, you can refer to this record
2.
Place all Oracle database into ARCHIVELOG
mode and configure them for complete recovery.
3.
Shut down your Oracle Collaboration Suite environment.
4.
Back
up the Infrastructure.
5.
Back
up the middle-tier installations.
6.
Back
up the information store installations.
7.
Start
your Oracle Collaboration Suite environment.
On a regular basis, especially after
every administrative change, perform an online backup of your Oracle Collaboration
Suite environment. It contains the following steps:
You should maintain an up-to-date record of your Oracle Collaboration
Suite environment in hard copy and in electronic form. You need this information
in the event you must restore and recover your Oracle Collaboration Suite environment
on a new disk or host. The electronic form should be stored on a host or e-mail
system that is completely separate from your Oracle Collaboration Suite environment.
Your Oracle Collaboration Suite hardware and software configuration record should
include:
1.
For
each host in your environment. The host name, virtual host name (if
any), domain name, IP address, hardware platform, and operating system
release level and patch information. Also, list the /etc/hosts file.
2.
For
each Oracle Collaboration Suite installation in your environment. The
installation type (for example: Infrastructure, Information Store, or
Middle Tier), host on which the installation resides, username, user ID
number, group name, group ID number, environment profile, and type of
shell for the operating system user that owns the Oracle home (/etc/passwd
and /etc/group entries), directory structure, mount points, and full path
for Oracle home, and port numbers used by the installation.
3.
For each database. Include database information
(for example, the database version, patch level, base language, character
set, global database name, and SID).
To enable ARCHIVELOG
mode for an Oracle Database, perform the following steps:
1.
Set
the ORACLE_HOME and ORACLE_SID
environment variables (this example is using the Infrastructure database).
2.
Shutdown
the database.
sqlplus "
/ as sysdba"
shutdown immediate
exit
3.
Edit
the init.ora file and incorporate
the following parameters:
log_archive_start
= true
log_archive_dest=<full path of your archive location>
log_archive_format=arch%s.arc
4.
Start the database in mount state (NOT open) and enable
ARCHIVELOG mode.
sqlplus "
/ as sysdba"
startup mount
alter database ARCHIVELOG;
5.
Verify the archive log mode of the database:
SQL> archive
log list;
6.
Finish starting the instance.
SQL> ALTER
DATABASE OPEN;
SQL> exit
Because your OCS
implementation may exist on several hosts, in most cases, you want to bring
the recovered host to the same state as the other hosts in the suite, by recovering
to the point of failure. See the DBA courses for more information on database
recovery options.
Shutdown your Oracle Collaboration Suite
Environment
To
completely backup the Infrastructure, begin with the following:
1.
Perform
cold database backups. This backup gives you a starting point for
database recoveries of your Metadata Repository and OID.
2.
Perform
a complete backup of all files in the Infrastructure home directory.
As user root, and using your preferred operating system command, perform
the backup so that file owners, groups, permissions, and timestamps are
preserved. For example,
tar -cvf
ihonfrmebak.tar $HOME/infra
This backup includes your configuration files.
3.
Perform
a complete backup of your Oracle System files. As user root, and using
your preferred operating system command, perform a backup of all your
Oracle system files. Consult your OS-specific documentation to determine
which directory contains your Oracle system files.
For
each middle-tier installation in your environment, perform the following steps:
1.
Backup
the home directory, including the configuration files. Use your preferred
operating system command to backup the middle-tier home directory.
2.
Backup
the Oracle Calendar Files. For example, to backup all of the Calendar
server nodes on the host to the directory /backups/cserver/jan.7.04,
use the following command:
unidbbackup
-d /backups/cserver/jan.7.04
3.
Perform
a complete backup of your Oracle System files. As user root, and using
your preferred operating system command, perform a backup of all your
Oracle system files. Consult your OS-specific documentation to determine
which directory contains your Oracle system files.
As
with the other backups, use your preferred operating system command to backup
the Oracle homes, Oracle system files, and Oracle Files BFILEs. For each information
store installation, perform the following steps:
1.
Backup
the home directory, including the configuration files. Use your preferred
operating system command to backup the information store home directory.
2.
Backup
the database files.
3.
Backup
the Oracle System files. As user root, and using your preferred operating
system command, perform a backup of all your Oracle system files. Consult
your OS-specific documentation to determine which directory contains your
Oracle system files.
Bookmark
