The best way to verify backup data integrity is to routinely perform restores from this backup data. For a variety of reasons, the majority of administrators do not verify backups using this method very often (if ever). Wouldn’t it be great if a backup and recovery solution provided the option to do this automatically on a regular schedule? Wouldn’t it be even better if the solution reported the results of the verification exercise? I am happy to report that is one of the new features of vSphere Data Protection (VDP) Advanced 5.5! Keep reading for more information and to download a short white paper on the topic that includes best practices…
Category Archives: Uptime
One of the new 5.5 features in vSphere Replication is the ability to retain historical replications as point-in-time snapshots on the recovered virtual machines.
Using this feature is quite handy in order to recover from systems that have corrupted data or viruses or even to do auditing of system changes and the like. While VMs protected with vSphere Replication can be recovered manually, and one by one, the full automation of recovery is of course offered by Site Recovery Manager.
In this post I’ll look at how we configure these multiple points in time (MPIT) during replication, and how we interact with them after failover by SRM.
VMware vSphere Data Protection (VDP) Advanced 5.5 was announced at VMworld in Barcelona. I am happy to announce that it is now available for download. Even though this looks like a “dot release”, VDP Advanced 5.5 represents a significant update to this backup and recovery solution for VMware, from VMware. These features are among the highlights of what is new with VDP Advanced 5.5:
- Replication of backup data between VDP Advanced appliances
- Support for app-level backup and recovery of Microsoft SharePoint
- Mailbox recovery for Microsoft Exchange
- Support for using EMC Data Domain as a backup data destination
- Automated backup verification
In Part 1 I covered how to upgrade vCenter Heartbeat to version 6.6 which is required for vCenter 5.5.
Once the Primary and Secondary nodes are upgraded to vCenter Heartbeat 6.6 we can begin upgrading to vCenter 5.5 and any optional components (such as VUM or AutoDeploy) that may be installed also.
The first decision before we move on is if Single Sign-on (SSO) will be installed locally to the vCenter (recommended for most customers) or if SSO will be deployed in a centralized fashion (recommended for customers with 8 or more vCenters in a single site). Continue reading
I have heard a few rumors around misconceptions on what storage platforms vSphere Data Protection (VDP) and VDP Advanced will work with. Perhaps these rumors stemmed from the announcements of new features in VDP 5.5 and VDP Advanced 5.5. For example, it is true that VDP 5.5 can replicate backup data only to EMC Avamar. By the way, VDP Advanced 5.5 will be able to replicate backup data to EMC Avamar and other VDP Advanced 5.5 virtual appliances. It is true that VDP Advanced 5.5 can leverage EMC Data Domain as a backup data target, but that is an option (not a requirement). I have heard that VDP and VDP Advanced can only be used with EMC storage which is FALSE.
VDP and VDP Advanced virtual appliances can be deployed to one or more VMFS or NFS datastores on any storage that is supported by vSphere. In other words, I can deploy VDP and VDP Advanced virtual appliances to EMC, NetApp, HDS, IBM, HP, Dell, etc. I can even deploy a VDP or VDP Advanced appliance to a VMFS datastore on direct attached storage (DAS) in a vSphere host.
Glad we cleared that up. :)
One of the most popular feature requests for vSphere Data Protection (VDP) 5.1 and vSphere Data Protection Advanced (VDP Advanced) 5.1 was the ability to restore a virtual machine (VM) directly to a vSphere host when vCenter Server and/or vSphere Web Client were offline. VDP 5.5 was announced at VMworld in San Francisco and, as you may already know, this feature was introduced. It is called Emergency Restore. VDP Advanced 5.5 was recently announced at VMworld in Barcelona. VDP Advanced 5.5 is not available for download yet, but as you would expect, Emergency Restore will be a feature of VDP Advanced 5.5. This article takes a closer look at Emergency Restore and discusses a few use cases.
A common question that comes up when a new vCenter Server version is released is “How do I upgrade if I’m using vCenter HeartBeat?”.
The first thing we need to check is whether the version of vCenter HeartBeat we’re running is compatible with the version of vCenter we want to upgrade to. You can check this by visiting the VMware Product Interoperability Matrixes.
We periodically survey our customers to try to understand how you use our products and to help us when developing new features. We are currently surveying SRM customers and would appreciate it if you could take approximately 10-15 minutes to share your feedback and thoughts about SRM.
This is part three of a set of blogs about the fantastic performance improvements found in vSphere Replication 5.5. Take a look at the prior two posts to understand what has changed and why it such a change by reading:
But now I do have a few warnings about all this improved vSphere Replication performance. Why is this not unequivocally a great thing? Because you may run the risk of overloading certain systems with this.
Let’s look at the technical issues at hand Continue reading
A few days ago I did a post on why VR is much quicker with version 5.5 than it had been in the past.
Now let’s take a look at what the result of those changes is.