As failover progresses the service set status changes to Unknown.
On completion the service sets information shows Service Set 1 and Service Set 2 both running
on the same Current Node; the failed node has moved to the failover node without any user
intervention and both service sets are now running correctly.
IMPORTANT: It is very important to fix the hardware problem that caused the node to fail as
soon as possible. Although all services are running correctly, performance may be slower (depending
upon NAS, VTL and replication configuration and volume of data). If the second node has a
hardware failure before the first node is repaired, the couplet will fail.
Running failback
Once the issue has been resolved and the failed node is available again, it must be brought back
into the cluster configuration. This must be invoked manuallyFrom the Failback this server button
on the appropriate Hardware page of the GUI.
NOTE: You can also use the CLI command hardware failback nodeX where X is the node
identifier. See the HP B6000 CLI Reference Guide for more detail.
Failover with CIFS Server in AD authentication
The failover process works in the same way as described above. However, there are some best
practices to follow to ensure failover and failback work correctly.
Best practices
• Assign Group permission to configured shares, e.g. BackupUserGroup
• Use the B6200 VIF IPs to mount the shares into backup application or Windows.
• For each node, join the AD domain and ensure it is connected.
• Use the closest name server (DNS server) and domain controller to the HP B6000 Backup
System.
138 Troubleshooting
To Next Page
Loading...
Need help?
General