Archive for the ‘dr’ Category
Live Coverage – GestaltIT Tech Field Day Veeam Presentation
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:
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!
Pre-existing Snapshot Could Cause Inconsistent Incrementals Using vSphere CBT
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.
The KB Article describes the exact scenario that causes the problem:
Determining VMware Data Recovery’s Use Case
With the recent news that VMware will be phasing out VMware Consolidated Backup and make the vStorage API for Data Recovery (VADR) the business continuity and full virtual machine backup enabler of the future, I want to better understand where VMware Data Recovery (vDR) fits in a virtual infrastructure today. This post outlines my notes as I explored both features and limitations of vDR in order to help explain how, where and when the product can be leveraged.
vSphere Editions needed for vDR
A great place to start is by understanding what licensed versions of vSphere 4 vDR can be used with. Using VMware’s vSphere edition comparison table you can clearly see that vDR is only available for use with the Essentials Plus, Advanced, Enterprise, and Enterprise Plus versions.
Although vDR is available in the Enterprise and Enterprise Plus editions, the limitations described in the next section present some design challenges for deploying vDR in larger environments.
Disclaimer: I am a systems engineer for Veeam Software.
Special Considerations For Using vDR
The following list of vDR limitations was taken from the VMware Data Recovery 1.1 Administration Guide:
Verify Recovery Of Full VM Backups With Future Version Of Veeam
Previously, all we knew about Veeam’s Surebackup was there was a public countdown in process. That countdown reached 0:00 early March 22, 2010 (this morning). Veeam sent emails to those who preregistered and then provided a press release shortly after. The countdown was for the introduction of a unique feature for verifying VM restores that will soon be introduced in the next version of Veeam Backup and Replication.
Here’s the information from my email for those that did not sign up to be notified:
Breakthrough Technology: Test and Verify the Recoverability of EVERY Backup
Veeam is enhancing the SureBackup™ capabilities in Veeam Backup & Replication™ with a breakthrough technology that overcomes the final obstacle of image-level backups. IT professionals will have the ability to verify the RECOVERABILITY of EVERY backup of EVERY virtual machine EVERY time. It’s never been possible before.
SureBackup introduces a new patent-pending technology that allows IT professionals to run a virtual machine directly from a compressed backup file.
By publishing the content of backup files directly to ESX hosts, you can:
- Eliminate the need to extract backup files
- Test and verify EVERY backup in a matter of minutes, without affecting backup windows
- Perform recoverability testing without additional hardware or staff
The same technology also allows for item-level restore for any virtualized application, on any OS (patent-pending).
This exciting new technology will be made available in version 5.0 of Veeam Backup & Replication, scheduled for release this summer.
Sound too good to be true? Join us for a free webinar on Wednesday, March 24 at 2:00pm EDT to find out more. Live Webinar – Register Now!
Can’t wait? Go to www.veeam.com/surebackup NOW!
I was actually invited to Veeam’s pre release blogger briefing over the weekend, and the rest of this post is my notes and thoughts about what I learned during briefing.
VMware VCB To Be Replaced by VADP. Does That Mean vDR Is The VMware Alternative?
I received an email today from VMware addressed to all customers about the end of availability for VMware Consolidated Backup (VCB). Quoting from the beginning of the communication but not the entire message, it reads:
“The purpose of this letter is to inform you of our vSphere backup product strategy, ongoing enhancements, and end of availability plans for VMware Consolidated Backup.
VMware Backup Product Strategy
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP).”[omited]
I’ll go out on a limb and say that most of the VMware community will
Simply Automating Virtual Machine IP Addressing For Disaster Recovery Sites (without scripting)
If you are looking at various options to automate virtual machine (VM) ip address reconfiguration when failing over virtual machines to a disaster recovery (DR) site, this post explains an option so simple it is beautiful. To give full credit, the Vizioncore vReplicator 2.5 Best Practices document enlightened me to the strategy of using a local only VMware vSwitch and an extra virtual NIC (vNIC) in each VM. It’s been a long time since I had a “ton of bricks” moment, but this concept crashed down on me with the realization of a configuration that works in any version of ESX, doesn’t require extra software or hardware, and better yet, doesn’t have to be scripted! Just configure some extra virtual networking and forget about it!
Here is a general outline for automating the DR ip addressing with this method:
At the Primary Site
- For these instructions assume the production vSwitch at the primary site has a Portgroup named VM Network
- Build a new vSwitch and do not attach any physical NICs (local only isolated switch). Create a Portgroup named DR Network
- For each VM you need to fail over to a DR site, add an extra vNIC and attach it to the DR Network Portgroup
At the DR Site
- Create your DR site production vSwitch, attach physical NICs and add a Portgroup named DR Network.
- Create another vSwitch and do not attach any physical NICs (local only isolated switch). Create a Portgroup named VM Network
All you have to do for this to work is
2 Free Tools Enhance VCB
VMware Consolidated Backup (VCB) is included with VMware Virtual Infrastructure 3.5 Enterprise Edition, but I’ve blogged before how VCB can be misunderstood as the complete solution for virtual machine (VM) backup. Furthermore, VCB’s scripting and command line interface can be a surprise for system administrators who are used to and expecting a GUI and scheduler. Mostly for these reasons, VCB is usually implemented integrated with traditional agent based backup solutions or virtualization third party VM backup products. However, for those that want to try a pure VCB solution in their virtual infrastructure there are a couple of free ecosystem developed tools that claim to provide GUI features and ease of use enhancements.
This post provides some basic information on 2 free VCB tools – VCB Wrangler and vbcMC Read the rest of this entry »











