September 14, 2016
Christophe Bertrand

100% agentless backup is a lie – buyer beware!

It’s undeniable: agentless backup offers a lot of big benefits to IT departments. But the question is, can you really go 100% agentless?

The answer: no.

 

Agent-based backup and the virtualization explosion

Since the beginning of backup times (almost), backing up specific platforms has typically required an agent optimized for the environment in question. Typically, you’d get one agent installed on each server, and the agent would interact with the backup engine/server and do its thing.

This became very cumbersome when virtualization exploded, of course. Then, adding a virtual server could be easily done with a single phone call to your favorite IT admin. And, not just one, but dozens…or hundreds. And, it meant installing one agent on each virtual machine; a task which quickly became cumbersome and, operationally, created data protection gaps and issues.

 

The welcome arrival of agentless backup

Along came agentless backup, and it significantly reduced the difficulty associated with backing up virtual machines. With this approach, IT admins can capture all of the VMs with a proxy server without having to install an agent in each virtual machine.

Less IT administration. Less data loss exposure. What else could be better? It certainly made agent backup look old and clunky.

But, not so fast. As is often the case, there’s more here than meets the eye.

 

You can’t just go 100% agentless

And, here’s why.

With VMware, any virtual machine that does not use native VMFS cannot be properly protected “agentless-ly,” leveraging the native VMware API’s. Raw Device Maps (RDM’S) and SQL Cluster disks are both examples where a different File System to VMFS is used.

Our competitor, Company V, offers agentless technology, for example, and it can’t protect these systems.

In contrast, Arcserve can quite easily through the installation of an agent. In a recent conversation with our field, we confirmed that we often see customers who use RDM’s being told by Company V that they have to convert them to ‘normal’ virtual machines.

That’s a dirty little secret, and something that many customers just won’t deal with.

By the way, this company’s recent announcement around agent deserves serious inspection – a glorified desktop agent is not the same thing as a full-featured server agent.

To quote one of our field leads:

“Our physical server support through the UDP agent install is a significant advantage over virtual-only agentless solutions. The ability to protect and recover physical machines as bare metal, as virtual machines, or at an object and file level is obvious, but it also allows us to protect virtual machines that are not supported by the native tools and API’s. There are also circumstances where it may be preferable to install an agent inside the virtual machine – for example if the virtual machine is very large or has a very high change rate, or if the VM Tools are perhaps not properly configured or up to date.”

Furthermore, with our High Availability module, which provides continuous data protection, fail over, fail back, and more — supporting the replication and backup of an MSCS cluster running on Windows 2008 R2 in VMware with physical RDM is easy. It is, however, a big issue with our competitors, Company V and Company Z. In addition, remember that Arcserve offers great deduplication, that’s global across nodes. Not everyone does that!

Net net: Beware of 100% agentless backup solutions – they just don’t cut it in many cases!