●
Estimated Required Time for Failover or Failback
The time it takes for a failover or a failback varies depending on the events that occurred, the OS used, and
the network environment or configuration.
The following table shows the estimated required time.
Table 81
Estimated Required Time for Failover or Failback
Event
Maximum required time (estimated)
When an error is detected in a NAS port or a path (*1)
Approx. 1 minute (*2)
•
When an error is detected in a controller or a NIC-CA
•
When a NIC-CA is replaced
•
When a preventive maintenance is performed for a controller
•
When components are replaced in a controller
•
When a memory expansion is performed for a controller
•
When a hot update of the controller firmware is performed
Approx. 3 minutes (*2)
*1:
The estimated time when an error is detected in a NAS port.
If errors occur in multiple ports, time is required to switch each port after errors are detected. The estimated time also depends on
the number of configured VLANs and the number of Bondings.
*2:
For NFS, part of the operations requires an additional 100 seconds added to the maximum required time in the above table due to
the lock reacquisition process.
Note
If an IPv6 address is used, detection of the access path switch is delayed in the client OS and the
access downtime may be longer than the estimated time described in
.
5. Connection Configuration
NAS Connection
224
Design Guide
Содержание ETERNUS DX S5 Series
Страница 335: ......
