Problem solve Get help with specific problems with your technologies, process and projects.

Patching, backing up and troubleshooting virtual machines : Necessary evils

Your virtualization environment needs constant maintenance. Here's how to stay up to date on patching and updates for virtual machines, how to back up VMs and troubleshoot problems.

A virtualization deployment needs constant care and attention to run smoothly and has different requirements than do physical machines. You must avoid security problems, back up your data regularly and monitor the environment.

The first three parts of this series have covered planning, building and securing a virtual environment. In this final part of the series, we cover how to patch, back up and troubleshoot your virtual machines (VMs) and virtualization environment.

Patching and updating virtual machines
Ignore patching and updates at your own peril. Software patches and upgrades are necessary to resolve bugs and security vulnerabilities and to update software with new features. With virtual hosts, it is even more important to apply patches in a timely manner because a bug or vulnerability can affect many virtual machines on that host. Each virtualization vendor has a different patch schedule, so be aware of them, and sign up for alerts when new patches are released. Pay special attention to security patches, and apply them as quickly as possible. You should establish a regular patch routine, and after patches and updates have been released, don't delay in applying them in your environment.

In addition, virtual environments offer some advantages, such as the snapshot feature that can provide an easy recovery point for any patches that cause problems on virtual machines. So you should look for patching systems that are designed to work with virtual hosts and virtual machines.

Backing up your virtual environment
Good backups are a must for any environment, physical or virtual. Traditional backup methods for physical environments can still be used in virtual environments, but there are alternatives that can back up your virtual machines more efficiently and quickly. Virtual environments allow for different approaches to backups because of their snapshot abilities and unique architecture. Taking a snapshot of a VM's virtual disk suspends writes to it and allows for backups to occur without the possibility of files being modified during the backup. Further, many third-party products are specifically developed to back up virtual machines. They are worth considering for even better integration, efficiency and backup speed.

For more on launching a virtual deployment:
Virtualization deployment: The assessment and planning phases

Building and configuring in a virtualization deployment project

Virtualization infrastructure monitoring: Eating your veggies

You should also plan your backup strategy around your current or future disaster recovery strategy, since good backups are the foundation for any business continuity plan. You should look for a backup strategy that supports your requirements for recovering from an event. In addition, you may look into some of the products that can replicate your VMs from your production environment to a DR environment. Test the restore ability so that when you try to restore data later on you don't encounter surprises.

Troubleshooting your virtual environment
Trouble is a given in even the best-designed environments: Hardware can fail, bugs will strike, and unintended outcomes happen. Troubleshooting virtual environments can be more complicated than physical ones because of the architectural differences between them. When a problem occurs in your virtualization environment, there are more components to check, and trying to look for a problem's cause can be more difficult. Troubleshooting can often be frustrating, and knowing where to look and what to do is the key to quickly finding and resolving problems. Familiarize yourself with the many different locations in which log files are located, and know which log files to check for specific problems.

In virtual environments, small changes can have large effects, and a seemingly innocent configuration tweak can cause huge problems for your hosts and VMs. It is critical to have a change management process in which changes are reviewed and documented before they are implemented. You may not notice the effects of a change right away; it could take days or weeks before a problem becomes apparent. Often, when a problem occurs with a system that was previously working, the first question is, "What changed?"' The ability to correlate a change that was made to the cause of the problem can help you quickly resolve it. Third-party applications can document changes in the configuration of your virtual environment and correlate them with events and performance data.

Eric Siebert, is a 25-year IT veteran who specializes in Windows and VMware system administration. He is a guru-status moderator on the VMware community VMTN forums and maintains VMware-land.com, a VI3 information site. He is also the author of the upcoming book VI3 Implementation and Administration, which is due out in June 2009 from Pearson Publishing. Siebert is also a regular on VMware's weekly VMTN Roundtable podcast.

Dig Deeper on Virtualization security and patch management

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchVMware

SearchWindowsServer

SearchCloudComputing

SearchVirtualDesktop

SearchDataCenter

Close