backup

Veeam Backup & Replication v5 Preview – Instant Indexing

There’s now an FAQ section in the Veeam Forums for Veeam Backup & Replication v5.

The screen shots below were created with a pre-release build of Veeam Backup & Replication v5 featuring vPower, many dialog boxes and text will change with the final release of Veeam Backup & Replication v5.

Another new feature in Veeam Backup & Replication v5 is the ability to create a catalog (or index) of the files contained within the Windows image backup. Cataloging is only available for Windows file systems with version 5 but we do have plans to extend this to other file systems as well as applications in future releases.

Indexing is now an option that appears on the VSS “Backup Consistency” screen on backup jobs. Creating the file system catalog is extremely fast and it is stored with the backup image. The full text indexing is actually handled by utilizing Microsoft Search Server so it does not affect the backup window when selecting the option to build the guest file index.

Once the backup is complete, the catalog file is passed off to the Microsoft Search Server. Simply connect Veeam’s Enterprise Manager to the Search Server through the configuration settings and you can now search across all Veeam Backups for any file on your Windows VM’s. Since Enterprise Manager supports multiple Veeam Backup & Replication Servers, you can search for files no matter what server was used to back them up.

The default search option is to only look at the most recent backups. This can easily be changed by utilizing the Advance Search feature.

Select a time period to search through all backups created during that period:

The search results are now very different as you see the results for all backups.

Clicking the link for the file brings up a window that tells you exactly where that version of the file is. You can print this information as well

Now that you know what version of the file you want to recover, simply run the Recovery Wizard for Windows Guest Files and choose the proper backup to recover from

With version 5 we’ve also included a “reason” box for all restore activities, this helps to track why a particular restore has been done.

Once you’ve completed the wizard, simply browse to the location of the file and recover it.

Another option for finding files that does not require Microsoft Search Server is to utilize the “Browse” functionality on the Files tab in Enterprise Manager. The browse feature displays the catalog of files for the chosen VM and restore point:

Veeam Backup & Replication v5 Preview – SureBackup, U-AIR and Instant VM Recovery

UPDATE: There’s now an FAQ section in the Veeam Forums for Veeam Backup & Replication v5:

The following screen shots are taken from an early “Alpha” build of Veeam Backup & Replication v5 featuring our patent pending vPower technology. While the functionality is there, some of the dialog boxes and text will change before the official release of Veeam Backup & Replication v5. The screen shots and wizards are very self-explanatory, I have provided additional text where needed.

SureBackup: Recovery Verification

This is just a quick preview of Recovery Verification, you can check out a more in-depth video preview for more information.

Step 1, Create an application Group and set options

Create a verification job using the application group. This can be scheduled to run or run manually:

Real-Time statistics of the Verification Job

U-AIR: Active Directory Restore Wizard

Create an AD restore lab request

Once the request is created, the work-flow engine starts. Lab requests can either be approved or denied.

Approving the Lab Request

With Veeam’s Advanced VSS integration, when the domain controller starts in the virtual lab, it is first started in “Safe Mode” for directory services restore, and then automatically rebooted into normal mode. This is done to ensure the consistency of Active Directory when recovering from a VSS aware snapshot.

As the lab is starting, the administrator can track progress and will be notified once the lab is ready.

The AD restore wizard connects to both the production domain controller as well as the domain controller in the virtual lab.

In this example there are no differences between what’s in the backup and what’s in production for the selected user:

InstantRecovery: Instant VM Recovery

The process of Instant VM Recovery is wizard driven and takes just a few minutes to complete. Once finished, the VM is live on the production network but running from the Veeam Backup Server’s datastore. You can easily Storage vMotion the VM to a production datastore or use Veeam Backup & Replication to replicate the VM to a production datastore.

To Virtualize or Not to Virtualize: A SMB Debate

I was recently reading an Information Week B-Mighty article on SMB Virtualization, where the author mentions that VMware believes SMB customers (defined here as sub-10 physical server) are either jumping in full force, or not virtualizing at all. He also spoke with Dell GM for SMB, Erik Dithmer, who mentioned that customers would save little or no money at all on virtualization. Dithmer must be basing his math on the process of shared storage in a virtualized environment vs. individual server storage on the non-virtualized path. I would actually present an alternate solution to the problem for a user with less than 10 physical servers in their company today.

Physical

On Dell.com today, I can purchase a R710 for $999 at street price. This will be my baseline for a physical server solution. Multiply this by 10, and we have a $10k price tag. To build a proper disaster recovery scenario in a physical world, you need to both backup and replicate your data from one physical location to another. The least expensive backup option I can select is Commvault, at $549 per server. The least expensive replication scenario I can find is a 5-pack of Double-take for $2499. So, at a very minimum, a physical server disaster recovery scenario is going to run you $10k +$5500 +$5000 = $20,500.

Virtual with SAN

Best practice for a disaster recovery scenario including shared storage is for there to be 2 equal SAN arrays on either side of your disaster recovery location. At a minimum, it is required to have 2 servers in your primary location for failover activities, and a single machine in the disaster facility for run-time operations. Once again, I went out to Dell.com to prove out Erik Dithmer’s hypothesis.

Although Dell markets a Virtualization in a Box config listed at $12,999, that configuration contains 3 R710 servers which only have a single socket, rendering most of the features VMware offers like Virtual SMP and CPU affinity fairly useless. So lets config this the old fashioned way. Dell offers the R805 online ($4500) as the “Virtualization” ready choice, so the standard configuration has dual quad-core Opterons and 8GB of memory, when coupled with VMware’s Memory overallocation capabilities, gives it the same performance as 16GB of RAM in physical systems. The shared storage component of this equation brings in the big question mark. Do I go with the MD3000i, iSCSI SAN on both sides for about $5000 each and add the $3500 per ESX server Commvault and $2500 per 5-VM Doubletake ($25,500 total) or do I go with two Dell Equallogic arrays, which have free replication software but would still need the Commvault (well over $25k).

So with the two scenarios side by side, Dithmer is correct that virtualization can in fact be more expensive than business as usual based on some assumptions.

The Third OptionVeeam Backup and Replication

Virtualization is the right option for so many reasons, a few of them including encapsulation, isolation, and portability. The ability to get a VM back up in running in minutes versus hours to rebuild a physical box is definitely the soft dollar value that most people know it is. But how do you accomplish these SLAs without requiring the large capital investment in shared storage? Or how do you leverage something like the Dell MD3000i, which comes in at roughly $5000 a piece in a proper DR strategy? The answer for me is Veeam Backup and Replication 4.1 with its virtualization capabilities. At a retail price point of $599 per physical ESX socket for unlimited VM backup and replication, you have the opportunity to get your disaster recovery scenario under control immediately. Veeam has the capability of backing up local storage, VMFS datastores on iSCSI and deliver those backups to pretty much any data storage site you can see. Veeam’s replication includes the capability of replicating ESXi to ESXi systems as well, so the security of ESXi can also be covered. So in the above scenarios, you can configure your hardware any which way you like for a DR scenario and still get accurate backups and replications.

Let’s take a look at the minimum virtualization configuration capable of accomplishing the DR strategy. Let’s use 3 virtualization capable systems with the R805 ($4500) plus 6 total sockets of Veeam Backup and Replication 4.1 ($3600). The primary location will have two R805’s, each configured to backup to each other’s local storage. The primary systems would also replicate to the DR location in case of site failure, and your data would be contained in two places. Mission accomplished, 10 VMs backed up and replicated for under $14,100. That is roughly $6,000 less than the 10 physical servers in a customers environment. It also takes no consideration for the reduction in energy usage, number of parts that might break, or any of the other environmentals of a data center.

In summary, Veeam Backup and Replication can save your SMB business significant costs when implementing virtualization.

Veeam Backup & Replication 4

A few weeks ago Veeam released Veeam Backup & Replication 4.0. I should have written a post the week it was released but I’ve been pretty busy and I also wanted to wait and get some of our customer’s reactions before writing about it. Our 4.0 release is a major milestone for us since it provides full support for the vStorage APIs for Data Protection. There appears to be a bit of confusion with some on what the vStorage APIs for Data Protection really do, especially when compared with VMware Consolidated Backup (VCB). As VMware states on the vStorage page, the vStorage APIs for Data Protection are the next generation of VCB. For a good explanation on the differences, check out my friend @Gostev’s blog over at vNotion “What is VMware vStorage API?

So why do we still have support for VCB? The simple answer is that we have a number of current customers that are using VCB and have not switched over to vSphere yet. We could have dropped support for VCB but then that would require us to maintain both 3.x and 4.x releases. Since 4.0 is an built upon 3.x and not a complete re-write of the software, we left VCB support in for our customers. The benefit is that our customers have a choice of how to process their backups: vStorage APIs, VCB or Veeam’s Service Console or Network modes. Of course I do recommend that customers use the vStorage API methods, it gives you the best performance and is also built specifically for vSphere.

Up to 10x Faster

Yes, it’s really true and our customers have posted as much on our forums. We’ve consolidated this feedback into a handy PDF document INSANE BACKUP SPEED, it’s not us saying this, it’s real people using our 4.0 product.

How is it so fast? One of the biggest reasons is Changed Block Tracking (CBT) which is included in the Virtual Disk Development Kit (VDDK). With CBT enabled for VM’s running on ESX or ESXi 4.x, VMware actually tracks the block level changes made to the VMDK. This way, when software like Veeam Backup & Replication takes a Snapshot, VMware returns a list of what blocks have changed. This significantly increases backup speed as we no longer have to try and determine the changes ourselves, VMware tells us in a matter of seconds.

The Critics

Of course anytime a vendor releases software that’s cutting edge and ahead of the rest of the field, others will try and knock it down. This recently happened on a blog sponsored by one of our competitors, claiming Veeam Backup & Replication was corrupting data. Of course when I first saw this I was a bit alarmed, but since they included a link to our forum where a user was reporting the problem, I followed the link and realized they were just sensationalizing something for their own apparent gain. Since this particular blog decides to heavily moderate comments, I thought I would post the facts here, lest any other competitors decide they want to sensationalize this non-issue.

The Facts

Taken from the Veeam Forum post:

  1. Backups are NOT corrupted.
  2. You can only run into this issue with NON-DEFAULT restore mode, in 1 restore mode of 3 existing modes.
  3. Despite what competition may be claiming, there is no actual user data loss or corruption – VM will still boot and work.

The only real issue is OS and file system check tools complaining about unexpected content of the unused disk blocks. Linux ext3 file system and disk test tools merely suspect a problem seeing unused blocks being non-zeroed, and warn about this. This is specific to certain file systems only, for example, Windows NTFS considers this situation absolutely normal.

Of course every software has bugs, the example above is a bug in our software when using 1 particular recovery method and we have a fix available and it will be included in our next release. The important piece of information is that NO DATA WAS EVER CORRUPTED, just an issue on recovery and zero byte blocks. We are very thankful to our active forum  community and for bringing this to our attention. Veeam’s motto after all is “Listening to You, Building the Tools You Need”, it’s on the back of all of our business cards. I’d like to point out the below points about our user forum:

  • Our forum is one of our greatest resources where people share their experience, best practices and getting support from Veeam and the community
  • We understand that our competitors are so desperate that they will continue using our own forum to try and fool the community
  • We will continue to be honest and direct with our customers in our forum vs. ending all the threads with ‘please contact our support’
  • User feedback: The quality and effectiveness of this Forum alone would be enough to justify switching to Veeam, even if the product wasn’t superior to its competition (as it is at the moment). It seems just too good to be true… I hope it will continue this way!

Conclusion

Sorry to waste so much space on this post answering the competition. If they would allow comments on their own blog I would have written it there. In closing I just want to say that we encourage everyone to evaluate our software and make decisions for themselves. Put us in the lab and you will see, others promise, Veeam delivers!

Long Distance vMotion?

While I generally reserve this blog for all things Veeam related, I saw something today that I just had to write about. There’s a software solution called HyperIP from NetEx that makes vMotion of VM’s possible over WAN connections. “Too good to be true” you say? Well, I’ve seen it and we’ve also done testing ourselves and with some of our partners and not only is vMotion possible, but if you’re using Veeam Backup & Replication you can get a significant performance increase in copying data over slow or high-latency connections. If you’re considering “the cloud” you really should check out HyperIP combined with Veeam Backup & Replication.

Check out NetEx’s press release here and also check out their YouTube video below. You can download a 10 day free trial of HyperIP and also a free trial of Veeam Backup & Replication to test it out on your own.

You can follow both @HyperIP and @Veeam on Twitter.

New Veeam Essentials Bundle

While there’s been a lot of talk this past week on Free ESXi (more on that later) I wanted to take some time and explain the new Veeam Essentials bundle and our reasons behind it. We view our Veeam Essentials bundle as a great entry bundle for the small business just getting into virtualization using VMware vSphere. As you may know, VMware has introduced a very attractively priced vSphere bundle called VMware vSphere Essentials, this gives you vCenter and up to 6 sockets (3 hosts) for just shy of US $1,000. If you think about it, that’s a lot of power for not a lot of clams. Think how many physical servers you can virtualize on 3 ESX(i) hosts…way more than 3. For more information, check out VMware vSphere Pricing.

So, for just shy of 1K you get fully licensed vSphere. This is great but it still leaves you without an efficient backup and recovery tool, single pane of glass monitoring or detailed reporting…enter Veeam Essentials bundle…offering Veeam Backup & Replication, Veeam Monitor and Veeam Reporter for around US $2,000 (Americas pricing). The Veeam Essentials bundle is fully functional licensed versions of those 3 products for 6 sockets (3 hosts).

Of course Veeam is placing some limits on this bundle…

  • Must be purchased with VMware vSphere Essentials (or proof of VMware vSphere Essentials must be given)
  • Each bundle will only support 6 sockets. This means that even if you purchase multiple bundles, each Veeam product will only work on 6 sockets, you’ll need to install other instances with the other license(s) to manage the other VMware vSphere Essentials vCenters.
  • Each bundle is 6 sockets, no less (sorry folks, you can’t get it cheaper for only 4 sockets)

What does all this mean? For just under US $3,000 (hardware not included) you get 6 sockets of VMware vSphere, 6 sockets of Veeam Backup & Replication, 6 sockets of Veeam Monitor and 6 sockets of Veeam Reporter. That’s 3 servers with up to 8 cores (2×4) and 256GB RAM each running VMware ESX(i). Couple that with a free iSCSI solution such as Starwind and now you’re talking 2 TB of shared data for free (hardware and Windows licensing not included).

I did not include Support and Subscription (SnS) above because for VMware vSphere Essentials it’s optional (it’s not optional on VMware vSphere Essentials Plus). Veeam’s Essentials bundle includes 1 year of support and upgrades in the list price.

Now, let’s discuss a few things about the Free Version of ESXi. We’ve gotten a number of questions on this since we released the “news” and the Essentials bundle on the same day. Below is a simple table explaining what is and isn’t supported:

Table of compatibility:

ESX Version

Current Customers As of June 3, 2009

Future Customers

ESX/ESXi 3.x licensed

+

+

ESX/ESXi 4.x licensed

+

+

ESXi 3.5 free

+

-

ESXi 4.0 free

-

-

+ = supported/usable
-  = not supported

Now please note that Veeam will not be supporting ESXi Free 4.0 at all. If you’re a current customer using Veeam Backup & Replication for ESXi Free 3.x, please contact your Veeam ProPartner or sales person for vSphere options.

While I don’t endorse or condone any of the following, I thought I would be doing an injustice if I did not include links to the community’s reaction to our announcement regarding dropping ESXi Free support. The list below is just some of the reaction, be sure to read the comments in each as well.

Rick Vanover at Virtualization Review

Rich Brambley at VMETC

Eric Scholten at VMGURU.NL

Gabes Virtual World

Search Server Virtualization’s Alex Barrett

Rich Brambley at VMETC again after Alex Barrett’s post

Search Server Virtualization’s Eric Siebert

Edward L Haletky’s The “soon to be launched” Virtualization Practice

The comments to my post on the original announcement

Update: June 12, 2009 – New Links

Bridget Bothelo over at Virtualization Pro

Discussion over at ars technica (I noticed this in my referral stats)

Update: June 15, 2009 – New Links

Search Server Virtualization’s weekly Podcast: VMware cuts free ESXi hypervisor support, fuels battle vs. Hyper-V

Update: June 26, 2009 – New Link

Mike Stokes over at eGroup

Update: July 3, 2009 – New Link

Tom Howarth over at PlanetVM

Mike Laverick from RTFM

Veeam and Free ESXi – it's official now

Figured I would blog this…These are not my words, I just copied from Veeam’s official release. Let me know in the comments what you think…

As a longtime Premier Technology Alliance Partner and supporter of VMware’s product strategy, Veeam Software takes great pride in creating innovative software products that enhance the customer value of VMware ESX, ESXi, and ESXi Free.  One such example is support for the free edition of VMware ESXi in Veeam Backup and Replication.

Recently, VMware requested that Veeam Software discontinue support for ESXi Free in Veeam Backup and Replication in order to comply with VMware’s updated licensing policy.  In light of VMware’s request, and our close technical partnership, Veeam Backup and Replication will no longer support ESXi Free. We will still continue to offer support for ESXi Free to existing Veeam customers who purchased Backup & Replication prior to version 3.1.

For small or branch office environments, Veeam advises its new customers to buy VMware vSphere Essentials and the Veeam Essentials bundle (announced today).  This combination costs exactly the same amount of money as purchasing 6 sockets of Veeam Backup at regular list price for use with free ESXi, but it is actually better, because with Veeam Essentials at its special discounted price, customers also get Veeam Monitor and Veeam Reporter.

What a Difference a Year Makes

This interesting little tidbit was just brought to my attention by one of my very alert Systems Engineers. It would seem that when customers do case studies, you should follow-up with those customers to make sure the case study is still valid because a lot can change in one year.

February 2008 – Customer does a case study

March 2009 – Same customer does another case study, this time for Veeam

If you read the one from 2008, then the one from 2009 (for Veeam) can you draw a link as to who the “competitor” is referenced in the 2009 Veeam case study?

We all know this virtualization market is highly competitive and many people have asked how Veeam can claim that we’re #1 for VMware backup. I think the example above speaks for itself. Let me know what you think in the comments!

VSS and VMware ESX: What your VMware backup vendor isn’t telling you

Since the recent release of ESX 3.5 Update 2 and Veeam Backup 2.0, both featuring Microsoft Volume Shadow Copy Service (VSS) support, we’ve been getting many questions from our customers asking why this feature is needed.

It’s true that the whole VSS support issue around VMware disaster recovery solutions created a lot of confusion due to each vendor having different opinions about the usefulness of this feature, as well as different implementation approaches, with some of them being quite questionable. So I decided to perform some testing on real applications to investigate whether VSS support is really required for a disaster recovery solution, and what VSS support implementation approaches are the most correct at this moment.

For my testing, I used one of the most common mission-critical applications, an Active Directory domain controller. To make a long story short, here’s the summary table for my testing results:


For the testing, I used my test lab containing a few clean domain controllers. I’ve chosen one domain controller (DC1) to perform all the testing on, and performed its backup of a live domain controller with the different VMware disaster recovery solutions listed in the table above. For all the solutions supporting VSS integration, I performed the backup with that option enabled.

As soon as I finished creating the backups, I switched to my test DC, created a few test users there to simulate post-backup activity, verified that the test users were replicated over to the other DC successfully, and crashed my test DC. Here’s a short video for this step.


At this point, I shut down the remaining domain controller, and created a copy of the whole lab so that I could test recovery for all solutions in similar conditions. After testing recovery with each solution, I rolled the whole lab backup to this state.

Recovery testing showed that in the case of Veeam Backup 2.0, and the latest VMware Consolidated Backup, the recovered DC was fully functional.

One thing I noted, however, is that with VCB, the domain controller did not start up in the recovery mode during the first boot, as it did with Veeam Backup 2.0. According to Microsoft documentation however, when performing a VSS-integrated domain controller restore, the system must be rebooted in Directory Services Restore mode when Active Directory is running on the server (which is exactly our case). To my understanding, booting in this mode is required so that the NTDS.DIT file is not locked with Active Directory services, antivirus or other applications when the shadow copy restore is performed. So I don’t know whether or not this domain controller restore approach is supported by Microsoft.

This video demonstrates the DC recovery process using the most correct VSS-integrated recovery implementation, as provided by Veeam Backup 2.0.


With all the other solutions I have tested (including vRanger Pro, which was originally the first to claim having VSS support), the recovered DC was not functional and was put into the condition known as an update sequence number rollback, or USN rollback. The only way to recover a DC from rollback is to forcibly demote the domain controller, and reinstall it. Luckily, I had my lab fully preserved, so instead I could simply rollback the entire Active Directory.

This video demonstrates the DC recovery using a solution not featuring correctly implemented VSS support.


As you can see, some applications cannot be restored correctly by simply starting up the VM image, even when VSS is leveraged to perform the backup. Some applications, especially those featuring replication, require a certain sequence of actions to be restored from a backup made by leveraging VSS. Similar to the domain controller that I used to perform my testing, Microsoft Exchange Server is another example of a mission-critical application that must be restored using an application-specific restore technique (refer to the following support KB article for more information about VSS-integrated backup and restore of Microsoft Exchange server).

If you ask me why I am the first one to bring this issue up – I don’t know. Could it be simply because no one ever tried to actually restore VMs to the production environment from their backups? I can understand how this type of issue could be overlooked in a small test lab setting, where typically only one DC is installed. But before you put your VMware backup solution into production – give some serious thought to the recoverability of the backups it produces.

For more detailed information on correctly using VSS in VMware environments, please read the “VMware and VSS: Application Backup and Recovery” white paper available at Veeam Backup product page.

Veeam is #1 for VMware backup