Yellow Bricks

by Duncan Epping

BC-DR

vCenter Site Recovery Manager 1.0 Update 1

· ·

VMware just released vCenter Site Recovery Manager 1.0 Update 1. Scott already dropped the news that it doesn’t contain NFS support, and that has always kept me away from NFS and iSCSI for that matter. But with 10GB ethernet becoming more mainstream this focus might change.

Anyway, the following features have been added:

  • New Permission Required to Run a Recovery Plan
    SRM now distinguishes between permission to test a recovery plan and permission to run a recovery plan. After an SRM server is updated to this release, existing users of that server who had permission to run a recovery plan no longer have that permission. You must grant Run permission to these users after the update is complete. Until you do, no user can run a recovery plan. (Permission to test a recovery plan is unaffected by the update.)
  • Full Support for RDM devices
    SRM now provides full support for virtual machines that use raw disk mapping (RDM) devices. This enables support of several new configurations, including Microsoft Cluster Server. (Virtual machine templates cannot use RDM devices.)
  • Batch IP Property Customization
    This release of SRM includes a tool that allows you to specify IP properties (network settings) for any or all of the virtual machines in a recovery plan by editing a comma-separated-value (csv) file that the tool generates.
  • Limits Checking and Enforcement
    A single SRM server can support up to 500 protected virtual machines and 150 protection groups. This release of SRM prevents you from exceeding those limits when you create a new protection group. If a configuration created in an earlier release of SRM exceeds these limits, SRM displays a warning, but allows the configuration to operate.
  • Improved Support for Virtual Machines that Span Multiple Datastores.
    This release provides improved support for virtual machines whose disks reside on multiple datastores.
  • Single Action to Reconfigure Protection for Multiple Virtual Machines
    This release introduces a Configure All button that applies existing inventory mappings to all virtual machines that have a status of Not Configured.
  • Simplified Log Collection
    This release introduces new utilities that retrieve log and configuration files from the server and collect them in a compressed (zipped) folder on your desktop.
  • Improved Acceptance of Non-ASCII Characters
    non-ASCII characters are now allowed in many fields during installation and operation.

Be sure to read the “known issues” section before you start implementing.

Leave powered on…

· ·

On Friday I got a question about the “Leave powered on” setting for HA. This setting is used for the Isolation Response. In other words, what does HA needs to do when a network isolation is detected. The question was pretty straight forward:”What happens when a host is isolated from the network or a host dies completely?”.

This question was asked because the default setting changed in ESX 3.5 / VirtualCenter 2.5 from “Power off vm” to “Leave powered on”. The old value was simple, what ever happens the VM will be powered off and restarted on a different host. [Read more…] about Leave powered on…

What’s in a name…

· ·

This will probably take me a couple of weeks and maybe months to get fully adjusted to the new names VMware is going to use for their products.

Most of the name changes were already announced during VMworld. And there are three major ones in the actual list:

  1. VirtualCenter → VMware vCenter
  2. VDI → VMware View
  3. VMFS → VMware vStorage VMFS

So most related products also had a revamp, Lifecycle Manager became VMware vCenter Lifecycle Manager and so on. Makes sense to me with the Virtual Datacenter OS coming up.

So learn this list by heart and we will do a test tomorrow 😉

Backup your ESXi vm’s

· ·

On the VMTN forum there’s a great topic on backing up your ESXi VM’s with a free solution. After a couple of pages of discussion and several solutions VMTN user lamw created a community document called “ghettoVCBni.sh – Free alternative for backing up VM’s for ESX 3.5+ and ESXi”.

This document contains a script and a list file. The list file should contain all the VM’s that need to be backed up. You can hook your ESXi box up to an NFS share and backup your VM’s to the NFS share. (NFS share could be a Windows Server for instance) You can set several variables to adjust the script to your needs:

  • Backup location
  • Sparse files(2GB chunks)
  • Backup Rotation
  • Directory naming scheme
  • NFS mount options

I haven’t personally tested the script but looking at the feedback it should work great. I think this is definitely worth checking out. So if you need a backup solution for your ESXi host and don’t want to spend money on 3rd party tools, check this one.

SRM, it’s just too easy

· ·

You’ve probably also noticed a whole bunch of Site Recovery Manager(SRM) related articles popping up with people installing and configuring it in their home lab:

I love these articles because they are prove of the fact that SRM is really easy to set-up. But, and this actually scares me, it might seem a bit too easy. I said “too easy” because implementing a Disaster Recovery solution isn’t about the tools you are using. The tools, which will make your life a lot easier, are not the most important piece of the puzzle. Indeed PUZZLE.

There a whole bunch of SRM projects going on globally where VMware PSO, the department I work for, is assisting. These projects typically have a duration of 3 to 9 months, while it seems that with the ease of VMware Site Recovery Manager this should be a matter of days.

People tend to forget that the most important thing about Distaster Recovery / Business Continuity is the business. You need to know the organisation and IT environment very well before you can even start:

  • SLA’s? –> RPO / RTO?
  • Which services are most important to the business?
  • Which servers are part of the service?
  • In which order need these be started?
  • Which service have the highest priority?
  • Are there any dependencies between services?
  • What about the desktops?

And these are just a couple of questions one should normally have to answer before even going down the SRM road. The fact that SRM is so easy to setup makes it really hard to actually explain to a customer why a BCDR project will take much longer then he expected. And remember that although SRM is a great tool you would still need to create a Disaster Recovery Plan, SRM will be part of the plan but it needs to be in place!

I’m not saying that you should not go down the BCDR / SRM road, but be sure to be prepared. (read this e-book, it’s good and it’s free) Get to know your “business”, and be prepared for a long engagement… cause my experience is that normally people have a hard time answering really obvious questions.

You will talk to a lot of people who don’t have a clue of what the core business services / applications actually are. And the same goes for the sys admins, dependencies? Why would you want to know about that and how would I know?

Do you know which questions to ask, do you know how to get the right answers… This is why BCDR subject matter experts are needed for SRM engagements, so before you start give VMware a call, or your local VAC partner for that matter and make sure you get the best out of the SRM product.