# CommServe Recovery

CommServe provides centralized management and administration for the entire CommCell environment. A failure in the CommServe system can result in the entire CommCell environment becoming non-functional. Therefore, it is essential to plan and implement a disaster recovery process to protect your CommServe system that includes database and host.

## CommServe Recovery Solutions

Based on the Recovery Point Objective (RPO) of the organization, you can protect your CommServe system using one of the following methods:

### Disaster Recovery (DR) Backups

By default, the Commvault software runs Disaster Recovery (DR) backup jobs to protect the CommServe database. DR backups include the CommServe database, MongoDB persistent data (from the Web Server), and other databases (if installed with the Commvault software).

In this method, the databases are backed up to disk media and can be periodically moved (if configured) to a network share, Commvault Cloud, cloud library, or tape media. In the event of a disaster, you can use these backed-up database dumps from the remote media to recover the CommServe database on the same or a new host.

Because no standby CommServe exists, the recovery time objective (RTO) is typically longer.

For more information, see CommServe Recovery Using Disaster Recovery (DR) Backups.

### CommServe LiveSync

You can configure one or more dedicated computers as standby or passive CommServe hosts. Install the Commvault software and stage the CommServe database for faster activation.

The databases and logs on the active (production) CommServe host are automatically replicated to the standby host at regular intervals. When the active CommServe host goes offline, you can quickly fail over CommServe system and resume CommCell operations on the standby host.

Because this method uses a standby CommServe host, the recovery time objective (RTO) is shorter.

For more information, see CommServe LiveSync For High Availability Disaster Recovery.

×

Loading...