Agentless Backups Do Not See All Attached Volumes

Follow

Scope

This article describes troubleshooting steps to take when agentless backups do not recognize all attached disk volumes.

Agentless backups are unable to recognize Bitlocker-encrypted volumes, and will skip them. Make sure that you do not have Bitlocker encryption active on any agentless volumes you intend to protect with the Datto appliance.

Issue Symptoms

When adding a server to a Datto device, only the C volume is recognized by the Add Agent Wizard. Volumes contained on other virtual disks and partitions are not recognized by the wizard.

Conditions

Diskpart shows the disks set to online. There are no volumes set to hidden. Secondary volumes are attached to the VM using the same method as the C volume. All .vmdks have the same naming convention.

Resolution

Datto appliances can fail to recognize agentless disk volumes when all disks use the same naming convention. This is because all agentless metadata for the protected system will appear to point to the same image file. To correct this issue, Datto recommends that you identify each .vmdk's datastore in its name - for example, the name CCRFS01-P.vmdk indicates datastore CCR for FS01's P volume. Assigning unique names to each volume will help the Datto appliance differentiate between VMDKs.


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!