Table of Contents
Advertisement
If the backup TeraStation has not received a packet from the main TeraStation within a specified time, the backup
TeraStation considers the main TeraStation to have failed. By default, it will try 5 times and wait 60 seconds. If this
is triggered by accident, reconfigure failover from the main TeraStation.
• Errors
Failover will occur if any of the following errors occur:
E12 (cooling failure), E14 (cannot mount RAID array), E16
(drive failure)
*When the drive is configured in JBOD.
Notes:
• Only use identical model and capacity TeraStations for failover. If the capacity of the main TeraStation is larger
than that of the backup TeraStation, an I33 replication error will occur.
• All drive bays of a TeraStation should be occupied if it will be used for failover. Failover will not work if a drive is
missing from any bay.
Before Configuring Failover
Use the same LAN ports for transferring data and configure both TeraStations with static IP addresses for the
purposes of failover. It is recommended to use a 10GbE port for failover. This section explains using an example with
LAN ports 1 and 3.
Using the Same LAN Port for Both Failover and Connecting to the Network
Using this setup, if the main TeraStation fails, the backup TeraStation will replace it completely. The backup
TeraStation will be updated over normal network traffic.
Using Different LAN Ports for Connecting to the Network and Failover
With this setup, the backup TeraStation and main TeraStation are connected by a second Ethernet cable connecting
their LAN 3 ports. Updating is done over this dedicated network path, so updates are quicker and don't interfere
with normal network traffic.
(drive not found), E22
*
LAN port 3
(Static IP)
Network
LAN port 3
(Static IP)
98
(cannot mount drive), E30
*
Main
Backup
*
Advertisement
Table of Contents
