Recovery Management Suite

My last few posts have been about backups and DR and I have intensively covered PHD Virtual’s products and their capabilities. I have covered PHD Virtual backup, CloudHook (my review) and  just recently I also covered ReliableDR (my review). Just recently PHD virtual has released their Recovery Management Suite (RMS) that ties all these products together and delivers an extremely powerful solution that ranges from simple backups to a whole site failure (without making it an extremely complex undertaking).



So why is this such a big deal. There are various products out there with similar capabilities. And that is true. However I cant think of a single product that does all that RMS offers and still manages to keep it simple. For example lets take a look at SRM (not trying to talk trash but simply using it for comparison). The business centric view of ReliableDR, DR automation and the ease of use in a multi tenant environment for cloud providers sets this product in a league of its own. Now if we throw the other two products into the mix (Virtual backup and CloudHook), PHD Virtual starts to sound like a real complete solution. And it truly is. Did I point out that PHD virtual has its own replication mechanism that can be used to replicate date between sites?

I really like SRM too. However being a technologist I like to compare products and see where one serves a better purpose. Lets put SRM in the back seat for now and lets call on Veeam for change and see how some of its features stand against RMS. I am a big fan of Veeam backup and replication also. However there is some real planning that goes into setting up Veeam’s backup manager, proxies and repositories. In the case of PHDVB things are pretty simple. And once you tie in cloud storage things get even better. And just like Veeam PHDVB also offers support for multiple hypervisor, but the ReliableDR portion is what puts PHD Virtual’s products miles ahead of Veeam in my opinion.

For the first time, companies of all sizes have a unified, affordable solution that automates and assures recovery processes in order to reduce risk, decrease recovery times, and help sustain the business throughout any issues that might occur. PHD Virtual RMS is the only solution to offer comprehensive, integrated recovery that addresses the entire recovery continuum. IT provides unified data protection and disaster recovery capabilities delivered through integrated backup, replication, recovery and DR orchestration that is powerful, scalable, easy to use, and delivers immediate value “out-of-the-box”


Obviously nothing is life is perfect and so is the case with RMS and its components. There is room for improvement and I am more than certain that the improvement will come before you know it. I am saying this from experience. PHD Virtual has made tremendous amounts of changes and enhancements to their products over the last few years that could only compare to a handful of organizations. What may seem like the next logical step actually does happen at PHD Virtual. And I hope they maintain that trend. As a matter of fact, some of what I thought should have been included in the future releases of the products also made it. For example I wondered why all the PHD products weren’t being offered as a single solution that worked together like one.. tadaaaaa! So there, an organization that can keep a character like myself pretty satisfied has a lot to offer in years to come.

Some of the latest enhancements coming in the upcoming versions of RMS are as follow:

  • Automates the replication of backup data from a source Backup Data Store (BDS) to a remote BDS (including cloud storage).
  • Only changed data is moved from source BDS to archive BDS (bandwidth saver and more importantly data the cloud will not move from production, it will likely move from your primary BDS, hence not even touching your production load).
  • The archive BDS can have different retention policies than the source (I complained about this).
  • You can configure individual VMs to be replicated, or synch the entire BDS with the archive location.
  • You can configure multiple source BDS locations to be archived to a single archive BDS location.
  • The archive BDS supports global deduplication across all source BDS data
  • Configure a generic S3 backup target to leverage additional object storage platforms, other than Amazon, Rackspace, and Google (Yoooohooo! more options)
  • Certified Replica – Automating the testing of virtualized applications that have been replicated using PHD Virtual Backup
    • A new CertifiedReplica job exists in ReliableDR for configuration of recovery jobs against PHD VM replicas
    • These jobs can be used to automate complex recovery specifications for failover and testing of PHD VM replicas. What kinds of complex jobs? For example:
      • Boot orders
      • Network mapping for test and failover
      • Re-IP for Windows AND Linux (Unlike Veeam here you can re-IP linux machines :))
      • Application testing and other recovery tasks
    • Verification can be scheduled at intervals as frequently as every 4 hours
    • Hypervisor snapshots are used for CertifiedReplica recovery points and other testing/failover tasks, making the entire process storage agnostic

And lastly some rumors. I have heard that ‘Certified Backups’ are also in the works. Yes machines are taking over! Look at what certified backups have to offer if it makes it through.

  • Automating the testing of VMware virtualized applications directly from backups using Instant Recovery from PHD Virtual Backup
    • A new CertifiedBackup job that initiates Instant Recovery jobs within PHD Virtual Backup and automates boot orders, network reconfiguration, and other recovery tasks
    • These jobs can be used to automate VM recovery specifications for testing of PHD backups
    • When testing is complete, Instant Recovery sessions are terminated automatically
    • Verification can be scheduled at intervals as frequently as every 4 hours

When you look at all the capabilities tied into a single product, you have no choice but to give it a go. Like I mentioned earlier I like other products too but if you are looking for a single solution that addresses your backup and DR needs, you have to give RMS a go. It will be silly to overlook it. I hope VMware Veeam and other vendors try and come up with their versions of RMS as well (though it will be interesting to see VMware come up with a solution that supports other hypervisors also).

I have been asked a couple of times in the past if ReliableDR supports vCloud Director and the answer is YES, it does. Try RMS for free today.

PHD giveaway

I have been keeping my eye on PHD Virtual for sometime now as their tools tend to make me feel smarter than I really am. It turns out they are having a free give away where you could potentially win a 1 year free license for either their VMware/Citrix backup solution or even their Reliable DR product that I reviewed just a few weeks ago.

So what do you have to do to win? Simply download their Virtual backup tool for VMware/Citrix or their Reliable DR product, from there on you are automatically entered to win. Here is the post that may have more information. Good luck!

CloudHook will hook you up – PHD Virtual 6.2

A few months ago I reviewed the backup tool from PHD Virtual for VMware. Yes, I specifically mentioned VMware because they have one for Citrix also. The company is on the verge of releasing their next major update 6.2 and I got an opportunity to do a sneak peak.

Last year I was completely new to PHD Virtual and had figure out all the moving parts, which weren’t many to be honest. The post from my last review is here. The one thing I loved about the product was its simplicity where I really didn’t have to sit down and figure out what was needed in order for it to work. I just followed the screen instruction and taadaaa!.. it worked.  So, I have huge expectations this year and won’t be going into the details of how to setup and install.


The overall procedure to do the install is still pretty much the same. You are working with two pieces here.

  1. VBA (appliance)
  2. Console (windows installer)

In order to get the backup tool going, you will install the console on a windows machine and deploy the VBA appliance. From that point some initial configurations are needed and you are all set to go. Configuration like the IP address for the VBA, storage to be used for backup, email notification, retention polices, write space etc.. What is write space? Good question, hold your horses.

You will also create your backup jobs here and kick off a manual or schedule a backup job.  All of this is pretty basic and I don’t plan on going into the details of how to complete these tasks. Once you have the VBA deployed, you will realize you don’t need anyone to blog about the how to steps. And if you really need that, click on the “question mark” on the top right of the console window and you will have access to all the help you will ever need. 


The documentation is embedded within the console and its pretty good and detailed. Read the rest of this entry »

PHD Virtual – Backup review

I have been sold on the idea of virtualization for a long long time now, for all the reasons that is common knowledge today. We all know them. Virtualization has opened up doors for all different types of development/enhancements in the last few years. One of the most important among all these is how we backup our all important data.

Not too long ago I got an opportunity to test drive PHD virtual’s Backup tool for vSphere version 5.4.2. They also have one for Citrix that I will not be discussing as I have not had a chance to look at that. To simply summarize what I think about the backup utility that PHD virtual makes for vSphere, I will say its a very good product and will help you sleep better at nights. However keep in mind that it only does virtual. So if you are looking for all in one solution that lets you backup both physical and VMs, you may want to look elsewhere. But wait, I would say you should still take a look at this for what it has to offer.

What is PHD Virtual backup?

PHD virtual backup is really a virtual appliance that runs in your pre-existing ESX/i cluster and helps you backup your environment. It is configured with 1GB or memory and single vCPU. It doesn’t stop there, it also helps you replicate the backup to another site or whatever your preference is. I wish I could say a few complicated things here and there but it’s really that simple. One thing I would like to point out is that PHD virtual has been evolving their backup tool for sometime now, at least since 2006. Bottom line – they are not new, but they are good.

The virtual appliance runs linux and is called the virtual backup appliance (VBA). This setup is designed with scalability in mind and allows you to have multiple VBAs running within the same vCenter. Now the backups rely on snapshots to work and we wont go into the details of that here. But just so that we don’t go on a freaked out state here, like most other good backup tools, the VBA will also delete the snapshot of the VMs. We obviously don’t want snapshots lying around. Once the snapshot has been taken, the data can be stored on a locally attached disk (locally attached to the appliance – a vmdk), a NFS or CIFS location. So there is that flexibility of where to store the data. Read the rest of this entry »