Skip to main content

seagate backup plus usb 3.0 ext drive

Thread needs solution

All,

I added a 4TB Seagate Ext. Backupplus drive? Acronis see the drive, created a directory, but will not back up to the drive. Suggestions?

0 Users found this helpful

What is the error you're receiving?  How was the backup configured?  Are you backing up in Windows or with the Acronis offline bootable recovery media? Screenshots of the backup configuration in Acronis and the exact error messages would surely help with finding a solution for your issue.

Also, what OS are you running (and is it 32 bit or 64 bit).  Does the entire 4TB drive show up in Windows?  Could you provide screenshots of the drive as listed in computer management and Windows file explorer as well?

I use the Seagate 8TB backup plus.  I use the WinPE version of Acronis and backup using the recovery disc.  No issues at all.  Create a WinPE recovery disk using either Windows 8.1 ADK or Windows 10 ADK and give it a try.

Thanks for the inputs Bob!  I would imagine that Acronis (Windows based and offline - Linux and/or WinPE) should see any standard SATA and/or USB hard drive. WinPE will certainly rule out driver compatibilty issues in the offline bootable recovery media if that is how the backups are being run.  This can be an issue on machines that don't have legacy USB enabled in the bios, or don't support USB 3.0 drives in the bios, but do in Windows (with proper drivers).  Some legacy/bios systems won't see drives larger than 2TB either until the drive has been formatted and extended correctly in Windows.  As this one is a USB drive, I doubt it's being used as "boot" drive anyway (since Windows won't allow it), but also wanted to point out that MBR systems are not capable of booting drives larger than 2TB.

That said, if Acronis can see it, there's no reason it shouldn't be able to write to it.  Unless, the permissions on the root of the drive are bad (say if they were setup on another system).  Might want to make sure that "administrator" or "all users" is the owner on the root of the drive and replicate it to all subdirectories.  Then ensure that the necessary user accounts have READ/WRITE (modify) access as well.  It's not very common to see these types of permission errors on external hard drives these days, but is still a possiblity, especially if it was originally setup and configured on another system with unique permssions that don't exist on the current system being used.