Agent-based backup pros and cons

Agent-based backup pros and cons

What are the pros and cons of agent-based backup software like TSM or Netvault compared to an agentless backup solution like Asigra? Which would be better for a SMB environment?

    Requires Free Membership to View

    Login

    When you register for SearchDataBackup.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Because your job never seems to get any easier, it’s our goal to keep you up-to-date on the latest backup tips, trends and technologies that will help you get the job done.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchDataBackup.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataBackup.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The advantage to an agent-based architecture is that it can provide its own authentication mechanisms. The agent is always running as a service/daemon, and the server authenticates itself using a proprietary mechanism that doesn't usually involve the creation of a username and password on the client. (There are some agent-based architectures that still require the root/administrator password of the machine to be backed up. That's just lazy programming, IMNSHO.) The disadvantage to an agent-based architecture is that you have to manage an agent installed on potentially hundreds or even thousands of client machines.

An agentless architecture doesn't require the management of agent software; however, it must rely on established communication protocols (e.g. FTP, CIFS/SMB, TELNET, SSH) to communicate with the client. Therefore, the backup server must communicate with each client using a pre-arranged username and password, usually a privileged one. (It must be privileged enough to access all data that must be backed up.)

I think either architecture would work just fine in an SMB environment. It's the enterprise that would have the strongest opinions about the values or merits of an agent-based or agentless architecture. While a company with 1000 systems to back up would see a great benefit from not having to manage an agent on each machine, they might also object to storing the username and password of a privileged account on the backup server (even if it's encrypted).

Do you know…

How to choose a backup reporting tool

How to optimize your backups?

This was first published in April 2006