Recover applications after hardware failure by switching over primary servers with pre-assigned spare servers.
This shortens and simplifies the recovery procedure.
Server switchover can be realized using one of the following methods.
Backup and restore method
Restore the system image that was backed up in the spare server beforehand and start it in the local boot environment.
HBA address rename method
In a SAN boot environment, using "I/O virtualization" enables the spare server to connect to and boot from the boot disk.
VIOM server profile switchover method
In a SAN boot or an iSCSI boot environment, using "I/O virtualization" in combination with ServerView Virtual-IO Manager enables the spare server to connect to and boot from the boot disk.
Storage affinity switchover method
This is the method used when the server is a Fujitsu M10/SPARC Enterprise. Server switchover can be realized by coordinating with ETERNUS SF Storage Cruiser storage management functions, and automatically modifying configurations in SAN environments.
Automatic Recovery of Failed Servers (PRIMERGY)
For PRIMERGY, N+1 cold standby which shares spare servers is provided.
The failed server environments are inherited, and automatically recovered.
By sharing spare servers, improved availability and reduced costs are both possible.
Figure 5.11 Automatic Recovery of Failed Servers (PRIMERGY)
Automatic Recovery of Failed Servers (Fujitsu M10/SPARC Enterprise)
This enables recovery of Fujitsu M10/SPARC Enterprise.
Through coordination with ETERNUS SF Storage Cruiser, the switch zoning settings configured in the fibre channel switches and the host affinity settings configured in the SAN storage can be switched over automatically.
Figure 5.12 Automatic Recovery of Failed Servers (Fujitsu M10/SPARC Enterprise)
