What are the databases critical for CommServe disaster recovery?
The CommServ and DM2 databases are critical and hence required for CommServe disaster recovery. The CVCloud and WFEngine are also critical and required, if the Metrics Reporting and Workflow engines are installed in the CommServe. AppStudioDB is critical and required, if you plan to use AppStudio.
All other databases are non-critical and not required for CommServe disaster recovery. (The main purpose of having these as separate databases is to separate the non-critical data from the critical data, to ensure a quick and smooth CommServe failover.)
The following table provides a summary of critical and non-critical databases
|
Database Name |
Description |
Critical for CommServe Disaster Recovery? |
Additional Information |
|---|---|---|---|
|
CommServ |
Contains CommServe metadata. |
Yes |
|
|
CVCloud |
Contains metadata associated with Metrics Reporting Server. |
Yes, if Metrics Reporting Server is installed. |
|
|
DM2 |
Contains metadata associated with Web Server used for content indexing and search operation. |
Yes |
See Also: |
|
WFEngine |
Contains workflow related metadata. |
Yes, if Workflow Engine is installed. |
|
|
HistoryDB* |
Contains data related to running jobs and history data for completed jobs. Note that the history data is purely for troubleshooting purposes and does not contain useful information for audit or events. |
No |
The new history is automatically recorded in this database after the failover. If any old history is needed for troubleshooting purposes, it can be obtained from the DR backup. |
|
AppStudioDB* |
Contains metadata associated with the App Studio. |
Yes, if you use the App Studio. |
For more information about this feature, see App Studio. |
|
Audit DB*,CacheDB*,ResourceMgrDB*,TemplateDB*,Troubleshooting* |
Miscellaneous databases. |
Not needed for Disaster Recovery. |
These are non-critical databases that are not needed for disaster recovery. |
* Verify that all these databases are created in the standby CommServe host. Although these databases are created by default during CommServe installation, in some situations the databases may not be available. For example, when an existing CommServe is used as the standby CommServe host. In such situations perform a one-time backup of these databases from the production Commserve host and restore it in the standby CommServe host.