As the title. Drive in question is a USB 3 drive. Drive detects fine in Storage Manager, can be formatted as NTFS and have files on it and so forth so I know the drive is physically detected.
When I run a : wbadmin enable backup -addtarget:{00000} (With a real drive ID from wbadmin get disks) I get the error "The specified file path does not exist or is not on a locally attached disk."
Up until a week ago backups were triggering daily at 9pm just fine and I've added additional target drives this way around for a while. I get the same error if I add a new target from the 'update backup' wizard.
Thoughts?
The backup includes Hyper-V folders, Exchange and SQL, and is set as 'VSS-Full backup'. It includes a bunch of random file shares too, as well as system drive and system state foo for bare metal.