Top
ETERNUS SF Storage Cruiser V16.8 / AdvancedCopy Manager V16.8 Operation Guide for VMware vSphere Virtual Volumes
FUJITSU Storage

2.1.1 Initial Design of System Configuration

This section describes the system configuration required to install and operate this product.

See

This document describes the VMware vSphere Virtual Volumes environment. Refer to "Operation Design" in the Storage Cruiser Operation Guide for details on the operational design of the entire system.

System Configuration

Figure 2.1 Example System Configuration

Management Server

Management Servers are required to configure the operational environment of VMware vSphere Virtual Volumes. ETERNUS SF Manager and ETERNUS VASA Provider must be installed on the Management Server.

Virtual Machine

The virtual machine is to be connected to the created Virtual Volume. Additionally, this is the virtual machine to be backed up with the backup function. VMware Tools must be installed in the virtual machine.

VMware ESX Host (VM Host)

This server provides virtual machines an execution environment.

VMware vCenter Server

This server manages and operates virtual machines.

Point

Multiple ETERNUS VASA Providers can be managed by a single VMware vCenter Server.
In addition, multiple VMware vCenter Servers can manage a single ETERNUS VASA Provider.

Note

  • Ensure the Management Server, VMware vCenter Server, and VM host can mutually confirm FQDN with DNS service.

  • Synchronize the timestamps for the Management Server, VMware vCenter Server, VM host, and ETERNUS Disk storage system using an NTP service.

  • To manage a single ETERNUS VASA Provider with multiple VMware vCenter Servers, ETERNUS VASA Provider that supports Multi vCenter Server is required. Refer to the ETERNUS VASA Provider manual for details about Multi vCenter Server.

  • In a configuration that manages a single ETERNUS VASA Provider with multiple VMware vCenter Servers, do not register the same VVOL datastore in the multiple VMware vCenter Servers.

  • The host name of the Management Server must be a name that can be specified as the FQDN name in ETERNUS VASA Provider. For details about the available FQDN names for ETERNUS VASA Provider, refer to the ETERNUS VASA Provider manuals.

Operational Management Environment Redundancy

In the VMware vSphere Virtual Volumes environment, the following operations are affected if a failure occurs in the operational management environment. Therefore, it is recommended that the operations management environment is made redundant.

Point

Even if a failure occurs in an operational environment, the currently operating virtual machine can continue to be used.

VMware vCenter Server Redundancy

Refer to the VMware vCenter Server manuals.

Management Server Redundancy

Redundancy is achieved by VMware vSphere High Availability (vSphere HA).

Figure 2.2 Example of vSphere HA Configuration

In vSphere HA, achieve redundancy by configuring the Management Server on the virtual machine. The business VMware environment and operational management VMware environment can be managed by one VMware vCenter Server.
In the above example, we use four VM hosts and divide these into VM hosts for the Management Server and VM hosts for the business server. It is possible to configure this with just two VM hosts and share the Management Server and the business server.

Point

If a failover occurs at the same time on both the Management Server and the business server, the business server may not be able to start normally. If the Management Server and the business server are configured on the same VM host, the risk of both servers performing a failover simultaneously increases. Therefore, it is recommended that you configure the Management Server and the business server on separate VM hosts as shown in "Figure 2.2 Example of vSphere HA Configuration".

See

Refer to the VMware vSphere manuals for information on how to configure the vSphere HA environment.

Network Redundancy

It is recommended to make business LAN and management LAN redundant.

The Management Server and the business server are made redundant using NIC teaming. In the ETERNUS Disk storage system, as there is a management LAN in CM, the management LAN can be made redundant through redundancy of CM.

See

  • Refer to the VMware vSphere manuals for NIC teaming configuration method as to the VM host.

  • Refer to the ETERNUS Disk storage system manuals for configuration method to make the management LAN connected the ETERNUS Disk storage system redundant.