Dell DL4000 Appliance Users Guide - Page 58

Managing events, Replication, Incoming Replication, Actions, Failback, Failback Warnings

Get Dell DL4000 PDF manuals and user guides View all Dell DL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 58 highlights

9. Import the archive you just created in Step 7. 10. Go back to the Core Console on the target core, and click the Replication tab. 11. Under Incoming Replication, select the failover agent and expand the details. 12. On the Actions menu, click Failback. 13. In the Failback Warnings dialog box, click Start Failback. 14. Shut down the machine that contains the exported agent that was created during failover. 15. Perform a bare metal restore (BMR) for the source core and agent. NOTE: When you launch the restore, you must use the recovery points that were imported from the target core to the agent on the virtual machine. 16. Wait for the BMR reboot and for the agent service to restart, and then view and record the network connection details of the machine. 17. Navigate to the Core Console on the source core, and, on the Machines tab, modify the machine protection settings to add the new network connection details. 18. Navigate to the Core Console on the target core, and delete the agent from the Replication tab. 19. In the Core Console of the source core, set up replication again between the source and target by clicking the Replication tab, and then adding the target core for replication. Managing events Managing core events assists with the monitoring of the health and usage of the Core. The core includes predefined sets of events, which can be used to notify administrators of critical issues on the Core or the backup jobs. From the Events tab, you can manage notification groups, e-mail SMTP settings, repetition reduction, and event retention. The Notification Groups option allows you to manage notification groups, from which you can: • Specify an event for which you want to generate an alert for the following: - Clusters - Attachability - Jobs - Licensing - Log Truncation - Archive - Core Service - Export - Protection - Replication - Rollback - SMTP Server Settings - Enabled Trace logs - Cloud Configuration • Specify the type of alert (error, warning, and informational). • Specify to whom and where the alerts are sent. Options include: - Email Address - Windows Events Logs 58

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
9.
Import the archive you just created in Step 7.
10.
Go back to the Core Console on the target core, and click the
Replication
tab.
11.
Under
Incoming Replication
, select the failover agent and expand the details.
12.
On the
Actions
menu, click
Failback
.
13.
In the
Failback Warnings
dialog box, click
Start Failback
.
14.
Shut down the machine that contains the exported agent that was created during failover.
15.
Perform a bare metal restore (BMR) for the source core and agent.
NOTE:
When you launch the restore, you must use the recovery points that were imported
from the target core to the agent on the virtual machine.
16.
Wait for the BMR reboot and for the agent service to restart, and then view and record the network
connection details of the machine.
17.
Navigate to the Core Console on the source core, and, on the
Machines
tab, modify the machine
protection settings to add the new network connection details.
18.
Navigate to the Core Console on the target core, and delete the agent from the
Replication
tab.
19.
In the Core Console of the source core, set up replication again between the source and target by
clicking the
Replication
tab, and then adding the target core for replication.
Managing events
Managing core events assists with the monitoring of the health and usage of the Core. The core includes
predefined sets of events, which can be used to notify administrators of critical issues on the Core or the
backup jobs.
From the
Events
tab, you can manage notification groups, e-mail SMTP settings, repetition reduction,
and event retention. The Notification Groups option allows you to manage notification groups, from
which you can:
•
Specify an event for which you want to generate an alert for the following:
–
Clusters
–
Attachability
–
Jobs
–
Licensing
–
Log Truncation
–
Archive
–
Core Service
–
Export
–
Protection
–
Replication
–
Rollback
–
SMTP Server Settings
–
Enabled Trace logs
–
Cloud Configuration
•
Specify the type of alert (error, warning, and informational).
•
Specify to whom and where the alerts are sent. Options include:
–
Email Address
–
Windows Events Logs
58