Synology SA3200D Synology High Availability SHA User Guide for DSM 7.0 - Page 17

Tests and simulations, Before you start, Manual switchover and automatic failover

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

Page 17 highlights

Chapter 3: Set Up and Configure an SHA Cluster 3.3 Tests and simulations SHA's failover mechanism is the key to minimizing service interruption resulted from system malfunctions. To ensure your disaster recovery plan is robust and tested, you can simulate disaster scenarios to assess your SHA setup. Before you start • Make sure you have backed up any important data. Your devices may get disconnected while running tests, which could result in data loss. • Sign in to DSM using the cluster IP address. We do not recommend using the active server IP address to sign in, and the passive server IP address is unavailable. • If a problem occurs during the testing process that causes the cluster or a server to be removed, you can sign in to DSM again using the active server's IP address. Manual switchover and automatic failover A switchover can be manually triggered for system maintenance with little service interruption. An auto-failover can be triggered by various events. When certain errors occur (such as network unavailability, software error, hard disk damage, RAID damage, etc.), the system can automatically initiate a failover of services from the active to the passive server to maximize availability. To trigger a switchover: On the Cluster page, confirm that the status of the cluster is Healthy, and then click Manage > Switchover. The servers in the cluster should exchange roles: the original active server will assume the role of the passive server, while the original passive server will take over the provision of services to become the active server. To trigger an auto-failover: On the Cluster page, confirm that the status of the cluster is Healthy, and then recreate one of the following events to induce an error and trigger auto-failover: • Remove the power source from the active server to simulate a power outage. • Disconnect the active server from the Cluster connection to simulate network failure. Do not disconnect the Heartbeat connection. Refer to this article for step-by-step instructions on how to manually initiate a switchover, trigger an auto-failover, or simulate connection problems. 15

  • 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
15
Chapter 3: Set Up and Configure an SHA Cluster
3.3 Tests and simulations
SHA's
failover
mechanism is the key to minimizing service interruption resulted from system
malfunctions. To ensure your disaster recovery plan is robust and tested, you can simulate
disaster scenarios to assess your SHA setup.
Before you start
• Make sure you have backed up any important data. Your devices may get disconnected while
running tests, which could result in data loss.
• Sign in to DSM using the
cluster
IP address. We do not recommend using the active server IP
address to sign in, and the passive server IP address is unavailable.
• If a problem occurs during the testing process that causes the cluster or a server to be
removed, you can sign in to DSM again using the
active server’s IP address
.
Manual switchover and automatic failover
A
switchover
can be manually triggered for system maintenance with little service
interruption. An
auto-failover
can be triggered by various events. When certain errors occur
(such as network unavailability, software error, hard disk damage, RAID damage, etc.), the
system can automatically initiate a failover of services from the active to the passive server to
maximize availability.
To trigger a switchover:
On the
Cluster
page, confirm that the status of the cluster is
Healthy
, and then click
Manage
>
Switchover
. The servers in the cluster should exchange roles: the original active server
will assume the role of the passive server, while the original passive server will take over the
provision of services to become the active server.
To trigger an auto-failover:
On the
Cluster
page, confirm that the status of the cluster is
Healthy
, and then recreate one
of the following events to induce an error and trigger auto-failover:
• Remove the power source from the active server to simulate a power outage.
• Disconnect the active server from the
Cluster connection
to simulate network failure.
Do
not
disconnect the Heartbeat connection.
Refer to
this article
for step-by-step instructions on how to manually initiate a switchover,
trigger an auto-failover, or simulate connection problems.