You can run various operations on the scenarios.
Follow these steps:
All the scenario groups in the control service are listed in the center pane.
The <scenario group>:<scenario> page is displayed.
After you create a scenario, you need to run it to start the replication process. Normally, before data changes on the Master can be replicated on the Replica, the Master and the Replica must be synchronized. Therefore, the first step in initiating replication is synchronizing the Master and Replica servers. After the servers have been synchronized, online replication starts automatically, continuously updating the Replica with all of the changes that occur on the Master.
The assessment mode enables you to assess the accurate bandwidth usage and compression ratio benchmarking that is needed for replication, without actually replicating data. When you run this command, no replication occurs but statistics are gathered. A report is provided once the assessment process is stopped.
You stop a running scenario to set or change properties. You could stop the scenarios in running state or assessment mode.
Synchronization is a process to make data consistent in the Master and Replica. Activate the synchronization process (whether replication is running or not).
A Difference Report compares the differences between the Master and the Replica at a certain point in time. The comparison is performed using the same algorithms that are used in the synchronization process, but no data is transferred. A Difference Report is generated for each Replica and sent to the Manager at the end of the process. This report can be produced at any time.
Switchover (or failover) is the process of changing roles between the Master and Replica. This means, making the Master server the standby server, and the Replica server the active server.
When the switchover process did not complete properly, you could manually select the server that acts as the active server through a process called Recover Active Server.
Suspend the Is Alive check that verifies that the active server is operational. You can manually suspend/resume Is Alive checking for a running HA scenario.
The Assured Recovery option enables you to perform a full transparent test of the recoverability of your data on the Replica server. The Replica server that is tested is the one that would take over the production server if it is down. The Assured Recovery option is a true test of the actual server, applications and actions that will be required in the event the Replica server will have to switch, become the Active server, and carry out its functions.
Use this operation to start or stop a virtual machine from its latest system status or from a bookmark. You can start or stop a virtual machine after you create a scenario and synchronize the master and replica. Use this feature when the scenario is not running. This feature is available for Full System DR and HA scenarios. The Start/Stop is a toggle menu item.
Suspend replication updates on the Replica host in order to perform system maintenance or some other form of processing that does not modify the replicated data there. Changes continue to be recorded for update on the suspended Replica, but are not actually transferred until replication is resumed. You cannot suspend replication during synchronization.
When you run a full system scenario, some temporary resources are created such as disk files, snapshots, and other files. This operation lets you delete these resources and is available when the scenario is not running.
Recover lost or corrupted Master data from any Replica by activating a synchronization process in the reverse direction.
A bookmark is a checkpoint that is manually set to mark a state back to which you can revert. This manual setting is called setting rewind bookmark. We recommend that you set a bookmark just before any activity that can cause data to become unstable. Bookmarks are set in real-time, and not for past events.
The selected operation is performed.
|
Copyright © 2016
|
|