Designing server configuration
This server manages and operates all virtual machines.
It installs AdvancedCopy Manager CCM and acts as a backup server.
This server provides a virtual machine execution environment.
Designing Volume Configuration
Design a volume (LU) configuration that meets the following requirements.
The transaction volume, backup volume, and restore volume are placed on the same ETERNUS Disk storage system.
The transaction volume and backup volume are an Open Volume of the same size.
The restore volume is a Snap Data Volume, and is of the same size (logical capacity) as the transaction volume.
The transaction volume and restore volume are connected to the ESXi Server.
The backup volume is not connected to the ESXi Server.
The formula for estimating the transaction volume size is as follows. If the capacity that is bigger than the estimated size can be allocated, bigger capacity is recommended to be allocated.
[System Area size : for 20GB or higher] transaction volume size = System Area size (size of virtual disk for guest OS) * 2 [System Area size : less than 20GB] transaction volume size = System Area size (size of virtual disk for guest OS) + 20GB
Notes when virtual machine is constructed
The following notes apply when building a virtual machine (VM) on the ESXi Server.
Virtual machines to be backed up/restored using these scripts are those created on a VMFS-5 datastore. Always select a VMFS-5 datastore when building a virtual machine.
Only the System Area on the transaction volume will be backed up/restored using these scripts.
You may create multiple virtual machines on a single transaction volume.
Create a virtual disk (hereinafter called "Data Area") where the data of a virtual machine is stored for other volumes different from the transaction volume. In that case, select "Independent (Persistent)" as the mode of a virtual disk.
Connect all virtual disks including the System Area of a virtual machine with SCSI.
The following guest OS are supported:
Windows Server 2008 R2
Windows Server 2012
Red Hat Enterprise Linux 6.2 (for Intel64)
Red Hat Enterprise Linux 6.3 (for Intel64)
In this script, the virtual machine snapshot is acquired in the snapshot name called "ETERNUS_Backup". Do not acquire the snapshot of the same name to avoid the repetition of the snapshot name.
Figure E.3 Configuration image of volumes backed up/restored using these scripts