Scenarios: Remote journal management and recovery
These scenarios describe the possible ways that JKL Toy Company can use remote journal management. JKL Toy Company uses the server JKLINT as their web server.
They need 24x7 availability for the critical data on this server, and they accomplish that by having a second server, JKLINT2, that shadows JKLINT. They use a high availability replication solution to copy the data from JKLINT to JKLINT2. Then, if JKLINT goes down, they can switch to JKLINT2.
The following scenarios describe two possible environments in which they can use remote journaling. The first scenario describes how JKL Toy Company can set up a data replication environment. The second scenario describes how they set up a hot-backup environment. The third scenario describes recovery steps if one of the servers fails.
Scenario: Journal management contains a complete description of JKL Toy Company's network and their overall strategy for journaling.
- Scenario: Data replication environment for remote journals
In this scenario, JKLINT and JKLINT2 use remote journaling for data replication purposes only.- Scenario: Hot-backup environment
In this scenario, the remote journaling environment uses a hot-backup application that causes JKLINT2 to replace JKLINT in the case that JKLINT has a failure.- Scenario: Recovery for remote journaling
This scenario describes a hot-backup environment in which the local system, JKLINT fails. It is necessary to restore the local system, and synchronize it with the remote system, JKLINT2.- Details: Recovery for remote journaling scenario
This topic describes the details of the recovery process for remote journaling.
Parent topic:
Remote journal managementRelated concepts
JKLINTRelated information
Scenario: Journal management