Best Practices for Disaster Recovery Version 9.2.00

In the event of data loss, for whatever reason, it is critical that you have a backup of the APTARE StorageConsole system. This section lists the key files and data associated with APTARE StorageConsole that you need to protect. These should be backed up regularly to mitigate risk of data loss.

At a high level, your backup and recovery strategy will consist of:

Each of these is discussed in detail in subsequent sections.

See Restoring the StorageConsole System for steps to recover data that has been backed up.

This should be done about once a month. A cold backup is required of the Oracle data file directories; by default, /data01, /data02, /data03, /data04, /data05, and /data06 for Linux and \oradata for Windows. Cold backups require Oracle to be shut down, thereby disrupting the Portal’s availability. Perform a cold backup, then back up (export) the database tables on a more regular basis (nightly is recommended). In addition to monthly cold backups, a cold backup is recommended after a significant software upgrade to capture the updated database schema. See Perform a Cold Backup of the Database.

The reporting database should be exported nightly. Exports do not require Oracle to be shut down. See Backing Up the Oracle Reporting Database.

Filesystem backups are required to protect the APTARE StorageConsole application directories, files, and OS-specific settings, such as the registry and services for Windows. The filesystem backup should also capture the nightly database export, which resides in the filesystem.

APTARE recommends that you utilize your company’s backup method of choice to perform the filesystem-level backup. While we recommend a full system backup, we have identified below the key files created or modified by APTARE StorageConsole.

• The file paths are shown with Linux usage. For the Windows path names, preface the path with C:, use backslashes instead of forward slashes (for example, C:\opt).

• Typically, you’ll have the reporting database located on the Portal server. If you are operating in a split architecture—that is, your database is on a server that is different from the Portal server—there may be some files from both servers that need to be backed up. If you have a split-architecture environment, see the comments in the following tables; however, we recommend that you contact the APTARE Global Support Services to verify that you have the necessary backup coverage for the files that reside on the Portal server and on the Database server.

File	Comments
.bash_profile for tomcat and users
/etc/init.d/aptare
/etc/rc3.d/aptare
/etc/rc5.d/aptare
/data0?	DB server (Linux) Contains the Oracle database files; must be backed up using a Cold Backup. See Perform a Cold Backup of the Database.
\oradata	DB server (Windows) Contains the Oracle database files; must be backed up using a Cold Backup. See Perform a Cold Backup of the Database.
/opt/openldap, /opt/apache, /opt/aptare, /opt/tomcat

NOTE: When backing up the above directories, follow the symbolic links to back up the source directory.
For example: /user/java is typically a symbolic link to /usr/java_versions/jdk<version>

These symbolic links may vary in your environment. Check the APTARE StorageConsole Certified Configurations Guide for the latest third-party and open source versions.

File	Comments
/etc/hosts	both Portal & DB servers
/etc/oratab	DB server
/proc/sys/kernel/shmmax	DB server

File	Comments
/usr/java
/etc/profile.d/java.sh