Copying Current State from a Redundant Storage Manager

To copy current state from a redundant storage manager (SM), you must shut down the redundant SM and make a copy of its archive and journal directories. This method allows you to create the database copy with no interruption in service to your database. However, shutting down a storage manager decreases the number of failures that the database can tolerate. Consequently, the recommendation is to provision enough resources so that you can shut down a storage manager without dropping below the database's fault tolerance.

To have a redundant storage manager that can be shut down without dropping below the database's fault tolerance, you should be running a multi-host database on at least three machines. This ensures that at least two storage managers continue to run while a third SM is temporarily shut down.

If you are running a single host database, then you must change it to at least a minimally redundant database but it is preferable to change it to a multi-host database. To make these changes, you might need to add one or two hosts to your domain (see Creating the Domain and Adding Hosts). An example of updating a single host database to a minimally redundant database is described in Upgrading Your First Database to Be Minimally Redundant. When running a minimally redundant database, which has two SMs, when you use one SM to obtain a copy of current state, then you must shut down that SM to obtain the copy. Your database does not have redundancy during this time. This is why the recommendation is to change to a multi-host database and provision at least three hosts.

See the following topics:

Adding a Redundant Storage Manager

Shutting Down the Redundant Storage Manager

Copying the Archive and Journal of the Shutdown Storage Manager