Veeam Agent for SQL Always ON - AD integration necessary?

[dbeerts]

Hi,

Following the KB (https://www.veeam.com/kb2463) you should use a Protection Group based on AD objects. I was wondering if this is necessary or just the most easy, flexible way to configure a Veeam Agent backup for a SQL Always On cluster. From what I read, the AD option is just something to make things easier, it doesn't add extra value over using IP?

In my use case we are using one VBR for multiple customer domains and I don't want to open network connections from the VBR to multiple customers DC's. Instead of using the AD objects I was thinking of using the IP address of the CNO (Cluster Name Object) instead, will this work the same as AD objects?

Last question, what are the benefits of using the Veeam agent over normal Image backups with T-Log backups? I know the Image + T-Log can't handle failovers between two job runs. It will complain that collected logs couldn't be matched with DB's, to solve you have to run a new backup cycle. Is the Agent backup smarter regarding to this?
Are there differences in speed?

Thanks!
Dries

[HannesK]

Hello,
it depends what you define as "extra value"

Working transaction log backups and proper failover handling would be enough for me to configure it in the way that is described in the KB article. A failover cluster job requires AD objects (IPs can only be used for standalone machines)

Agent based backups are also "image-based" per default. Transaction log backup after failover also requires image-based backup with agents. That's the same like for VM-based backup. Speed depends on the environment. But usually VM-based directly from storage is faster than agent-based via network.

Best regards,
Hannes