Difference between revisions of "VMWare"

Revision as of 14:15, 27 March 2012

VMWare was the second step of virtualization infraestructure in Maretec (after Xen).

Physical Machines

Installation Phase

Migrating Existing VM in Xen

Existing VM in Xen server were duplicated in VMWare environment in RAID machine (the future backup machine). Before installation in definite place (CISCO server, ESXi1) the original ones should be replaced by the news to ensure the system works.

Creating a new FTPServer

A VM was added to vShere and installed Windows Server 2008 and configured as the existing Xen FTPServer. See Creating a FTPServer in VMWare for details.

Creating a new WebServer

A VM was added to vShere and installed Windows Server 2008 R2 and configured (Web sites that were inside FTPServer). See Creating a WebServer in VMWare for details.

Creating a new OpenDAPServer

A VM was added to vShere and installed Fedora and configured as the existing Xen OpenDAPServer.

See Creating an OpenDAPServer in VMWare for the first attempt with LVM defaults from Fedora. After PVextend machine crashed.

See Creating an OpenDAPServer in VMWare2 for the second attempt with user defined LVM and till now the best creation.

Creating a new VM Domain Controller

A VM DC, VM-DC2, was added to CISCO server, ESXi1, and installed Windows Server 2008 R2. See Creating a Domain Controller in VMWare for details.

Creating a new Physical Domain Controller

A physical DC, DC1, was installed with Windows Server 2008 R2. It was similar install as the VM-DC2 but drivers for LAN, sound, video, etc had to be installed.

Creating a VM Backup Server

Creating a BackupServer in VMWare

Production Phase

Changing the bridging between the LAN and the DMZ

Opendap

eth0 - LAN

eth1 - DMZ

The steps are for changing from DMZ to LAN and (from LAN to DMZ)

• Need to add in vSphere the new interface to the VM (by default the DMZ machines should not have the two interfaces on because that would create a security issue since anyone that had control to the machines could connect the LAN and access it) - see the steps in the creation of the machines.
• Enter the VM through console access as user

• Just use network icon in rigt up corner, disconnect eth1(eth0) and connect eth0(eth1)

• It is done if change is temporary! Do not forget to remove the LAN adapter in vSphere after not needed because it creates a security issue.

• However if connection is to maintain after reboots it is better to take eth0(eth1) down definitely in network restart

Other--> Network Connections 
Select to not connect eth1(eth0) automatically but connect automatically eth0(eth1)    'or eth1(eth0) it would give fail in network restart after taking it down below)
Save.

> ifconfig ethx down                 'x is 1 in case of wanting to go LAN at restart, is 0 otherwise
> service network status
> su
> service network restart
> ifconfig

• Do not forget to remove the LAN adapter in vSphere after not needed because it creates a security issue.

FTPServer

• Need to add in vSphere the new interface to the VM (by default the DMZ machines should not have the two interfaces on because that would create a security issue since anyone that had control to the machines could connect the LAN and access it) - see the steps in the creation of the machines.

• Enter the VM in console and just go to connections and disable one and enable the other.

• Do not forget to remove the LAN adapter in vSphere after not needed because it creates a security issue.

Increase /opendap size

First, do a snapshot, backup the files.

• Add a virtual disk to the VM vSphere Client from the same physical disk(default)or select other datastore.

IMPORTANT: do not add size to the existing virtual disk or the space will not be usable. Add one new disk.

• Check the name of the new disk in the VMMachine Disk Utility (Accesories). It was /dev/sdb

• Create a new partition of appropriate size using fdisk

>fdisk /dev/sdb
>n             (create new partition, select start and end cylinders (default), all free space is selected by default)
>w             (save partition table and exit)
>fdisk -l      (check the new partition, /dev/sdb1 was created ~10G in size)

• Create an ext3 filesystem in the partition (this step is optional, just a quick test that all is well)

>mkfs.ext4 /dev/sdb1

• Initialise the partition for use as a physical volume in lvm and add it to vg_opendap2

>pvcreate /dev/sdb1
>vgextend vg_opendap2 /dev/sdb1

• Extend LogVol00 (use 'df /' to check that / is mounted on LogVol00) as required (by 10G here)

>lvextend -L +10G /dev/vg_opendap2/lv_opendap

• If you receive errors about not enough physical extents, then reduce the size of the extension a little until it fits.

• Finally, resize the filesystem (this part normally would require unmounting /, but for ext4 it works while the partition is mounted)

>resize2fs /dev/vg_opendap2/opendap

• Type 'df -h /', to check it worked, there should be an extra 10G available

(you can use vgdisplay, pvdisplay and lvdisplay (as root) to see detailed info, pvscan for a summary)

Backup VM

The backup strategy

1. One Replication for each VM from 192.168.20.80 to 192.168.20.81 (FTPServer and WebServer in disk 1 and OpenDAPServer, DC2 in disk 2 (4 restore points done weekly (saturday morning)).
2. One reverse incremental backup of all initial VM to Davinci 192.168.20.45 and then one backup of all machines (above + BackupServer) (2 restore points done monthly (last sunday in the morning)).

Virtual Machines Backup and Replication Scheme

Restore VM

Links

Go Back to Virtualization

Xen