Agent-based or agentless. That is the question. While this isn’t a mission-critical decision, it’s certainly an important one to weigh and determine which is your best fit. There are certain circumstances that call for agent-based backups versus agentless and vice versa. Here’s the rundown.

Agent-based backups

Agent-based backup products require the user to install a lightweight piece of software on each machine they want to protect. Agents live at the kernel level in a protected system so they can easily detect block level changes on the machine. They do not need to scan the file system to determine changes for incremental backups. As a result, agent-based can be more efficient than agentless.

On the other hand, agent-based backups rely on local compute resources to perform the backup and send it to the backup target. Because of this, the backup process can impact application performance if the protected server does not have the compute power necessary to perform backups alongside production workloads. Generally speaking, this isn’t a big issue as long as the server is right-sized to handle necessary tasks.

Agentless backups

Agentless backup, as the name implies, does not require users to install agents on protected servers, therefore making it slightly easier to deploy and monitor. This is particularly important in virtual environments with lots of changes. VMs can be spun up so easily it’s common for them to go unprotected when using agent-based backup because a backup agent is never installed. With agentless, this isn’t an issue.

Also, agentless backups can be less expensive than agent-based backups, because users do not need to pay licensing fees on a per-agent basis. Pricing models, of course, vary from vendor to vendor.

Many agentless backup products must inject temporary executable modules into systems before the backup can occur. For the most part, this isn’t an issue, especially if the application being backed up offers an API for the backup software to interface with. However, there is a chance that temporarily injected modules can create data integrity issues on protected machines.

With this information you’re in great shape to decide which is better for you. In addition, our new Product Information Sheet breaks down some common use cases to help you make the best choice.