Skip to main content

Scheduled backup to network drive fails continually

Repeated attempts to run a backup of files and settings to network drive fails with error "The last backup has failed.  The backup cannot be started. Ensure that [path to network drive (a W10 64 pro pc) ] is accessible."  

When I run the same program instead of scheduling it, I receive notification of a 'connection error'.  When I test the connection error and connection is always established, and I then attempt to run the backup, the backup completes successfully.  It will not work if scheduled.  

Repeated attempts to solve this problem including months' long work with escalated TS have yielded no results.  I even went through the age old TS professed solution of reinstalling the OS and starting over WITH A CLEAN INSTALLATION! 

I have been using Acronis for several years, upgrading faithfully but the last move from 2017 did not solve the problem and I am done with the TS methodology of screen saves and log files.  I won't move to 2019 unless I get this solved.  (I also struggled with the OneDrive issue which I eventually solved through the forums after escalated TS could do nothing but request another log file.)

I'd appreciate any thoughts before I begin looking for new backup software.

0 Users found this helpful

Daniel, welcome to these public User Forums.

Sorry to hear of a long running saga with your backup to a network location but there is insufficient information provided to help us understand how best to try advise you on this?

Please provide us with details of how exactly your backup task is configured - screen images of the settings is fine, else pertinent information of the main configuration settings.

How exactly are you specifying the path to the network drive when selecting the Destination location for the backup?

If you don't already have it, please download the MVP Log Viewer tool (link below) and provide the backup task logs showing the error, and the scheduler logs.  An Acronis System Report would include these if the size would be under the forum 2 MB limit for file attachments.

There is nothing fancy about the backup;  the source files are documents and settings for the admin user on the host pc; nothing fancy about the network path;  the pc that functions as a backup server is a W10 pro installation as stated earlier;  the backup drive and folder were all recognized when the backup scheme was created, and after it fails due to an Acronis "connection error," it will work fine if I subsequently manually test and confirm the connection and then initiate the process manually   

 

Backups ran fine for several years until a Windows update this last summer.  The Acronis software failed after that update.  My expectation as a customer is that, within a reasonable period, Acronis will stay current with changes in the OS that is currently in production for consumer and commercial pc installations -in this case Windows 10.  Having been a longtime Windows user I understand that this is a challenge for software companies, but this is why I buy the Acronis product rather than turn to freeware and complain that it does not work correctly.

 

I upgraded to ATI 2018 hoping that would fix the problem, but it didn't. I've sent many screenshots and logs, but there is always another log or diagnostic file requested by TS with no solution in sight.  I've posted on this forum to see if it offers any better strategies, but none so far.

It seems to me that users who do not want to pay for cloud backup or prefer to have data saved locally, are not served well by this product.  While I do differential disk backups of my c and d drives 3/week to e and f drives on my local pc, I prefer to backup data and settings daily to my networked pc so I always have access to those files on a second device.  Acronis used to do this consistently as well as seem to keep up with Windows, but for me it just has not passed that test as these failures of scheduled daily backups still occur consistently on a new, pristine installation of W 10 pro.

Daniel, sorry but still no real information here for us to work with.  I have multiple different network backups that work just fine either as scheduled or on demand.  The only key difference is that my backups are going to my Synology NAS on the local network, not to another PC operating as a network server.

Daniel, does any helpful error message appear in ATI TI_demon log?  (Using the MVP log viewer utility is the best way of viewing it.  Steve's posts have a link to the Tools page.)  Sometimes there are some very unusual and unexpected problems writing to NAS drives.  Perhaps those problems also can happen when writing to a networked Win10 PC.

On your "remote" system are you accessing a shared drive owned by a Windows user or is access via something running under IIS?  I won't be able to help you regardless of your answer, but it might steer a more knowledgeable reader in the proper direction.

Thanks for responding.  I haven't seen anything that steers me to a solution.  Although I created the  Windows 10 PC that I use for backups with a separate username, I have Administrator account authority for both users.  I indicated that I have backed up to this pc's 'backup drives' without incident for several years, using Acronis until the Windows update this last summer.  Oddly, my wife's pc, which I also built and maintain, continues to backup daily to the same remote pc without incident.  I had hoped that a clean installation would have removed something on my pc that was causing the problem, but no luck.  It happens only on scheduled files backups, and the first differential of a manual files backup.  It is a connection error with a box to test the connection, which if done, enables the backup to proceed.  All pcs are W10 64 pro intel pcs, all licensed for Acronis, and I have user account authority on the other two pcs.