VM /ETC

Archive for the ‘dr’ Category

Recently a disgruntled vSphere administrator was able to delete 88 of his former employer’s virtual machines (VMs) remotely from a McDonald’s WiFi connection. We all know virtualization makes things a lot easier, and unfortunately, this is a scary example of the dark side of just that. I’ll argue it’s also a wake up call for IT departments to realize how virtualization changes the dynamics of data center security,  risk management, and overall data vulnerability, but I’ll leave that for the experts in those fields. What made me go “hmmmm” was the thought “what if I was on the team that had to investigate and recover from this incident?” I also wondered “What if the attack was less obvious?” What if only slight configuration changes were made to the virtual machines instead of  obvious deletions? For example adding limits and reservations to the vCPU and vRAM of the virtual guests or their resource pools thus making them sluggish, unresponsive, and unable to conduct business as usual.

How Long Would It Take To Troubleshoot And Recover?

Put yourself on the team that suddenly realized 88 VMs were gone! Where would you start? The storage  jumps out at me as a logical place to begin, but after your storage area network  is online, healthy, and normal then what? It’s time to try to crack open the VMware Black Box and scour event logs, alarms, permissions, and actions. Put that aside for a minute and think about how would you start the rebuild process and get the business reconnected!?

I don’t have an easy answer. My goal is asking you to think about this for yourself.

Warning! The Veeam Pitch

Since I work with Veeam products every day I’ll briefly suggest how they could help in this scenario. Decide for yourself what tools are best for your company. I’ll point out that Read the rest of this entry »

Because of the prevalence of virtual infrastructure these days, I’ll make the argument that virtual machine (VM) replication, both for business continuity (BC) and disaster recovery (DR) purposes, is the new P2V (physical to virtual migration) project. Not in the literal migration of physical to virtual, but in the same P2V concepts of infrastructure consolidation and capacity planning. I’m also talking similarity of process and in the frequency in which it is occurring. Simply put, IT shops that performed P2V migrations several years ago are now exploring how they can accomplish their DR site fail over or their BC needs with their virtual machines.

Let’s call these new generation of projects V4DR (virtualization for disaster recovery) or V4BC (virtualization for business continuity).

The comparison

If I rewind 3 to 5 years ago in my career, capacity planning for server consolidation was a weekly project and topic of discussion. Customers were either in the process of converting physical servers to virtual machines or they were exploring the possibility to do so. In both cases, capacity planning scenario spreadsheets and reports were frequent “ground zero documents” to almost every project plan I was involved in.

Just like P2V projects, VM replication today also requires some of the same considerations for job scalability and times to complete – i.e. using multiple hosts as targets and making sure the network can support getting the job done as quick as possible. Not to mention ip addressing, VLAN assignments, and application connectivity after the fact. Thank goodness we no longer have to deal with hardware drivers and other unneeded software a second time. Hopefully, VM alignment is a thing of the past too!

I’m not seeing the same “ground zero documents” for replication projects, however.

Use the same capacity planning tools?

So, I’ll ask the question:  Read the rest of this entry »

Most backup and VMware  admins already know that Veeam Backup and Replication  (VBR) can do File Level Restores (FLR) for any Virtual Machine running any Guest OS and File System that VMware supports. The default process to restore the files involves using the VBR GUI for auto assembling the VM’s .vmdk from the Veeam Backup Files (without moving data to any additional storage location or starting up the restored VM), and then using the pop-up file browser to “copy to” any location. But, did you know you could allow users to browse the restored VM file system and do their own file restores? From their own desktop or the desktop of the destination system? You won’t find this information in the VBR User Guide today, but it is very easily done.

disclaimer: I am a Systems Engineer for Veeam Software

Now, with VBR version 5 a FLR Appliance can be activated, auto registered, and configured for file level restores. Although the FLR appliance is only used when you select “Guest Files (other OS)” from the Restore options, the Linux based appliance VM can mount NTFS and most other non Windows file systems. By choosing to use this appliance you have the option to enable FTP access to the restored .vmdk thus making the recovered file system(s) easily available from any desktop. Therefore, end users or application owners can just open Windows Explorer, their favorite web browser, or a FTP client to browse, find, and download their recovered files themselves. No additional software needs to be purchased, and if you use the native OS web and file browsers nothing else even needs to be installed.

This means that the only time required by the VMware / Backup admin is the few minutes it takes to click through the Veeam restore wizard and verify the FLR appliance VM is running. Of course, a few extra seconds is required to click to close the FLR GUI when the user is done.

The rest of the post shows the many screen shots of using and configuring the Veeam FLR Appliance Restore option and a few simple, end user alternatives for accessing the restored files from the remote system. 

Read the rest of this entry »

Like everyone else, I have been reviewing the Release Notes for the latest Update 1 release of vSphere 4.1, but I decided to point out specific fixes that will make full image VM backups better for everyone. Note that I work for Veeam Software, but the fixes I am referring to are all VMware resolved issues that surface from time to no matter what backup solution you use. There are numerous other fixes and impovements in the U1 release, but, since most of my world is backup these days, these particular items “popped out” at me.

For a great overview of the entire U1 release check out Rick Vanover’s post vSphere 4.1 update 1 released from his Rickatron Blog and via his Servers and Storage Column/Blog at TechRepublic.

The rest of this post contains cut and pastes from the Release Notes and some commentary about them from me. I want to stress again that these are issues that have now been fixed!

Finally, I’ll point out the one huge VM backup issue (that I can think of right now) that still does not appear to be resolved.

Read the rest of this entry »

Figuring out whether you can replicate your VMs across your WAN to a DR site is never easy. There are many factors to consider, but luckily, one of my Veeam peers and a fellow VMware vExpert, Ricky El -Qasem has created a Replication Calculator to help figure it out.

From the post on the Virtualize Planet Blog: Replication Bandwidth Calculator | Virtualize Planet

ReplicaCalc

How many times do you get asked “how do I work out if VM Replication will work with my internet link” Well I wanted to demonstrate some way of providing a calculator without working it out in my head every time. So I made a Replication Calculation tool.  It is assumed that you provide it with 3 values:

1. Average Rate of Change.
2. The Link speed – this value should reflect the upload speed at the source site or the download speed at the target if this is less. So for example if the upload at the source is 6Mbs and 10Mbs download at the target then go for 6Mbs
3. Bandwidth % – which is the amount of bandwidth as % which achievable from the link speed specified.

Download and install ReplicaCalc from here > ReplicaCalc

Ricky describes the needed values in more detail in his post so be sure to read it all there. He also demonstrates how to use Veeam Backup and Replication to get the VM dynamic rate of change. The tool is useful whether using Veeam to replicate your VMs or not, however.

Thanks Ricky!

For more on this topic, I’ve blogged about using a bandwidth calculator to figure out whether your current WAN link is adequate or not for your replication jobs before.

I am in Seattle, WA for the third GestaltIT Tech Field Day (TFD). This time I am part of the presenting team for Veeam Software, and we are first up on the agenda. As with other recent events, I am using Cover It Live (CiL) to provide real time coverage and of our presentation and the reaction of the delegates (bloggers) attending. The best part about using Cover It Live is the event can be played back in the future, so check it out even if you missed it live.

I’m automatically pulling in the tweets of all involved, so I should have a good stream of both bloggers and sponsors represented here.

I’m using the following twitter lists:

• @TechFieldDay/tfd3-sponsors
• @TechFieldDay/tfd3-delegates

Look for my occasional commentary as well, but I’m not sure how much time I’ll actually have to participate. I’ll end the coverage when our time is up, which should be roughly 3 to 4 hours.

Click through the page break for the CiL widget and tune into the fun!

By the way, we are providing the first ever public demo of Veeam Backup and Replication 5.0 SureBackup!

Read the rest of this entry »

Tom Howarth, VMware Communities Moderator and blogger at PlanetVM.net, posted this week how he was informed by a developer of a virtualization backup vendor about a scenario involving reverting to an ESX snapshot that results in corrupted incremental backups when using vSphere’s Change Block Tracking (CBT). Howarth’s post Major issue with Change Block Tracking recounts his conversation and exploration of the problem with the developer. In summary, Howarth reported “there is a major issue with the way VMware handles the indexing of the ChangeID.”

Almost a week later and after a flurry of comments from most of the vendors leveraging CBT for virtual machine backups, VMware has published a KB article on the subject.

VMware KB: Reverting to a pre-existing snapshot under specific conditions can cause incremental backups based on CBT (Changed Block Tracking) to become inconsistent

The KB Article describes the exact scenario that causes the problem:

Read the rest of this entry »