Complete the steps in this procedure to remove one or more protected machines from replication on the target Core.
- On the target Core, open the Rapid Recovery Core Console, and from the icon bar, click
![[Replication]](/ja-jp/technical-documents/image/0e623c19-5c6b-441f-a4c2-7363093e0210)
(Replication).
The Replication page appears. In the Incoming Replication pane, the summary table includes a row for each source Core with protected machines that this target Core replicates.
- Select the replicated machines to remove as follows:
- To delete all machines replicated from the source Core to your target Core, in the Incoming Replication pane, select the check box for that Core.
- To delete a smaller subset of machines from the same source Core, do the following:
- Click the
![[Expand]](/ja-jp/technical-documents/image/bc531b70-ceb3-4e04-8e98-e1ca1e4615f7)
arrow to the right of the source Core.
The view expands to show each of the machines from the selected source Core that are replicated on your target Core.
- Select the check box for each replicated machine that you want to remove.
- From the parent row of the selected source Core, click the
![[Settings]](/ja-jp/technical-documents/image/fe1363a2-7a8d-4400-9f19-e3a04edd8e8a)
(More) drop-down menu, and then select Delete.
The Remove Replication dialog box appears.
- In the Remove Replication dialog box, do one of the following:
- If you want to leave the replicated recovery points on the target Core, clear the option Delete existing recovery points.
- If you want to delete all replicated recovery points received from that machine as well as remove the source Core from replication, select Delete existing recovery points.
- Click Yes to confirm deletion.
|
|
Caution: If you select this option, all of the recovery points replicated to this Core will be deleted. |
The selected machines protected on the source Core are removed from replication on this target Core. Optionally, if you selected the option to delete recovery points, they are removed from the repository of this Core.
For more information, see the following related topics:
Day-to-day replication functionality is maintained on the source Core, while only the target Core is capable of completing the functions necessary for disaster recovery.
For disaster recovery, the target Core can use the replicated recovery points to recover the protected machines. You can perform the following recovery options from the target Core:
The Rapid Recovery Core includes predefined sets of events. These events can be used to notify administrators of critical issues on the Core or about issues with jobs pertaining to backups, virtual export, replication and so on.
This section describes how to view events displayed on the Rapid Recovery Core Console. You can also learn about event notification methods and configuration, including setting up email notifications. Finally, you can configure notifications to change the amount of time event logs are retained, and reduce repetitive event notification.
Topics include:
From the Core console, you can view events for the Core, and you can view events for a specific protected or replicated machine.
The Events pages on the Core Console display a log of all system events related to the Rapid Recovery Core. To access and view events for the Core, click ![[Events]](/ja-jp/technical-documents/image/61b1e5ac-7087-402c-a4a0-44545fc92f3c)
(Events).
The Events pages for a specific protected or replicated machine display a log of events related to that specific machine. To access and view events for a selected machine, click the machine name in the Protected Machines menu, and from the machine Summary page, click the Events menu.
Events pages (on the Core or a specified machine) are available in three views: Tasks, Alerts, and Journal.
All items shown in any category is an event. These views allow you to filter details about various subsets of events, as appropriate. The default view is to show tasks.
- A task is an event related to a job. A job is a process that the Rapid Recovery Core must perform. Each job has a current state, and a start and end time and date. Some tasks are initiated manually or scheduled by the user. Examples include forcing a snapshot, scheduling a backup, or performing a restore from a recovery point. Other tasks are automatic functions, such as running nightly jobs, or performing rollup using the default retention policy.
- An alert is a priority event, such as an error, warning, or important informational message. If you request notifications of any specific events, these notifications appear in the Alerts subset.
- The journal shows a complete list of all logged events (for the Core, or the selected machine, as appropriate). This list is more comprehensive, showing jobs, high priority events, and lower priority events. This category includes passive and non-job events (such as the Core starting successfully, or reporting status from the license portal).
Complete the steps in the following procedures to view tasks, alerts, or a journal of all events:
