HiperLogic

Virtualization, High Performance Computing, Healthcare IT, Enterprise Computing

VMware

You are currently browsing articles tagged VMware.

I was asked today how to perform an application consistent backup of MySQL in a Linux Virtual Machine on VMware for a customer evaluating Veeam Backup.

On Windows, Veeam can do application consistent backups through the Veeam Microsoft Volume Shadow Copy Services (VSS) integration for VSS aware applications. Unfortunately Linux does not have a system like Microsoft Volume Shadow Copy Services (VSS) that allows applications to be made application consistent by backup applications like VMware vDR or Veeam Backup.

A simple workaround is to leverage VMware tools ability to call custom freeze/thaw scripts during a quiesced snapshot to enable customers to do the required application quiescence.

The example below is for MySQL, for other applications you need to know the application specific command to quiesce the application and modify the scripts below appropriately.

Step 1. Make sure VMware Tools are installed in the Linux VM
VMware Tools MUST be installed and should be up to date in your Linux Virtual Machine.
Step 2. Determine how to quiesce the application
To quiesce MySQL we will do a mysqldump to create a transactionally consistent backup of mysql without downtime.

Note the disadvantage of this method is that it takes more space since it creates a copy of the database. Alternatively, If you can stop/start mysql during an off hour backup that is a simple way to quiesce ( no transactions can occur if the database is stopped ) as well. You would stop mysql in the pre-freeze, and start mysql in the post-thaw in that case.

Step 3. Create /usr/sbin/pre-freeze-script
Below are the commands to type at the Linux command shell to create the pre-freeze script which will create a transactionally consistent backup of MYSQL and store the resulting statements in /var/mysqlbackup.todaysdate.sql

The resulting .sql file produced by mysqldump contains a set of SQL INSERT statements that can be used to reload the dumped tables at a later time

cat <<EOF > /usr/sbin/pre-freeze-script
mysqldump --single-transaction --all-databases > /var/mysqlbackup.\`date +"%m%d%y"\`.sql
EOF

Check the above command worked properly by examining the created script.

cat /usr/sbin/pre-freeze-script

The result of the cat command above should look like below

mysqldump --single-transaction --all-databases > /var/mysqlbackup.`date +"%m%d%y"`.sql

Make the script executable

chmod 755 /usr/sbin/pre-freeze-script

Step 4. Create the /usr/sbin/post-thaw-script
In this case we don’t have to call anything in the post-thaw so create an empty script :

  touch /usr/sbin/post-thaw-script
  chmod 755 /usr/sbin/post-thaw-script

Step 5. Enable VMware Tools Quiescence
Now check “Use VMware Tools Quiescence” in Veeam Backup, and Veeam will ask VMware tools to quiesce the VM, and VMware Tools will call /usr/sbin/pre-freeze-script and /usr/sbin/post-thaw-script to create the application consistent snapshot.

After the Veeam backup, login to the VM and validate the backup file with the date of the backup exists:

root@vCentos ~# ls -la /var/mysqlbackup.032411.sql
-rw-r--r-- 1 root root 422120 Mar 24 11:59 /var/mysqlbackup.032411.sql
root@vCentos ~#

You can customize the above procedure for any Linux application that provides a method to quiesce itself.

Tags: , , , ,

VMware announced today a new product called vCenter Operations. The one takeaway about this new solution is that it enables the VMware admin to quickly find out what is abnormal in the environment through self-learning technology.

For example, an application owner will come to the VMware team and say “something is not normal with my application, it is slower than normal, what is going on?”.

The VMware admin now has to determine what “normal” is for the application is, determine if the problem is the application or the infrastructure, and package all of this information up to report back to the application owner.

With vCenter Operations a skilled VMware admin can quickly understand what is abnormal to narrow the scope of the issue, quickly identify what the problem and remediate the issue.

vCenter Operations has a very different UI than you may be accustomed to. In the screenshot below, vCenter Operations is reporting on three metrics: Workload, Health, and Capacity:

  1. workload score (0-100) – The amount of resources the objects wants to use compared to the resources the object has.
  2. health score (0-100). How normal is the object behaving based on past historical behavior of the object.
  3. capacity score (0-100). How much capacity do you have on a object, less than 30 days capacity left would be red.

Note I use the word “object”, and object can be many things like a virtual machine etc.

vCenter Operations

Another detail view:

vCenter Operations Detail

vCenter Operations Detail

vCenter Operations is packaged as a virtual appliance and comes in three editions, see below for some the basic differences. For the standard edition pricing starts at $50 per VM (Less than 500 VMs). With standard edition you don’t get access to 3rd party integration, customized dashboards, or AD integration.

vCenter Operations Edition Comparison

Note vCenter Operations still requires the VMware admin to interpret the abnormal metrics and create a plan of action, it does not offer a prescriptive recommendation (yet).

Tags: ,

There was a recent discussion online on the merits of using VMware High Availability (HA) and Fault Tolerance (FT) to protect an application that had HA and FT baked in. I believe this discussion will start popping up more and more in the near future, many new “cloud scale” applications are coded in such a way to be highly available, scalable, and fault tolerant which alleviates the need for features like Hypervisor level HA and FT.

For example, Google uses a software stack that has allowed them to withstand 1,600 server failures in a 1,800-unit cluster with uninterrupted service. This same distributed model that assumes failure of the underlying resource is how cloud applications are commonly developed today. VMware with their investment in Spring Source has recognized the importance of supporting the next generation of applications that will not be depend on keeping a single OS instance up and running at all costs. The future is going to revolve around applications built and designed to run on unreliable, cheap, expendable resources.

Tags:

I recommend the following reading list for Java on VMware vSphere:

Enterprise Java Applications on VMware – Best Practices Guide [PDF]

Java in Virtual Machines on VMware [PDF].

Check out this blogger on Java and VMware as well who also wrote a whitepaper on the topic.

Tags: ,

VMware has extended the deadline for VCP3 holders to qualify for VCP4 certification without having to attend an official vSphere training course, you now have until January 31st 2010.

The free 2nd chance re-take exam offer is also extended until the end of the month, note that January 22nd 2010 would be the last day for 1st attempt at VCP4 exam if the free re-take is required since there is a cooling off period before you can take the 2nd exam. See this VMware Blog for information on how to register for the free re-take.

Tags: ,

During a recent customer VMware healthcheck, we noted a customer did perform the VMware NFS timeout tunings as recommended by NetApp TR-3749. However none of the guests had the correct guest level timeout tuning.

TR-3749 doesn’t explicitely spell out that you should make sure and update your guest level disk timeouts to match the NFS timeout tunings.

Also note that these disk timeout settings if done once in the guest, may be reset through a VMware Tools upgrade. (See http://communities.vmware.com/thread/212235) so watch out.

See NetApp article kb41511 “VMware ESX Guest OS I/O Timeout Settings for NetApp Storage Systems”  for more details.

Tags: ,

We frequently get questions from customers with NetApp if they should store the swap with the VM or on a separate datastore, and how big should they make their swap datastore.

NetApp recommends in NetApp TR-3749 to use a separate datastore, as to avoid storing “transient” data like swap when using array based snapshots or disk-to-disk replication with SnapMirror and/or SnapVault. (Also See TR-3428).

For sizing, you can thin provision and use autogrow on the NetApp side to avoid having to worry about an “exact” space figure as this space is dynamic in nature depending on the number of VM’s, the memory in those VM’s, and memory reservations, and is used only when there is memory pressure.

If you want an absolute worse case add up all the VM’s you would create with the memory you anticipate allocating to them, and use that result if you need an absolute worse case number.

Tags: ,

© 2006-2010 HiperLogic, LLC.  |  Serving the Ann Arbor, Southeast Michigan, and Ohio region  |  (888)-268-3930  |