In the last post in this series (way back in 2014!) we discussed whether Hyper-V replica should be used as an alternative to backup? The answer was that there were a number of drawbacks to using Hyper-V replica instead of backup – and in particular Unitrends backup. We left that post posing the question as to whether Hyper-V replicas should be used with backup.

Using Hyper-V replicas with Unitrends enables you to do the following:

  • Typical use case for Hyper-V replicas with Unitrends backup is using backup at the local site with replication using Hyper-V replica.
  • Unitrends backup at the local site with replication at the second site or at Azure via ASM. This means you’re backing up at the source; not the target.
  • File and item granular restore can be used at the source.
  • Flexible schedules and unlimited restore points can be performed at the local site.
  • Restore point compression and deduplication can be performed at the local site.
  • You have retention with Unitrends backup.

Another important feature that you get with Unitrends backup is the ability to support granular RPOs (Recovery Point Objectives) and RTOs (Recovery Time Objectives) using Deep Virtualization. As your VMs get larger and you get more serious about using virtualization to protect tier 1 and tier 2 applications, this gets increasingly more important. The technique we call “shallow virtualization” – in other words virtualization data protection only at the hypervisor level without the ability to protect more granularity – tends to be limited in this scenario.

How do you virtualize?