Direkt zum Inhalt

6569 Backup to cloud always failed after 40% (20GB)

Thread needs solution

Hello,

the cloud backup starts normaly and stops after 40% with the message "not enough memory". 

I try to use the data storage in U.S. instead of Germany, but it makes no different.

0 Users found this helpful

Hello Wolf,

Please see post: 18623: How to get Technical Support: Tips, Tricks and Useful Information as you will probably need to contact Acronis Support directly to resolve issues with the Acronis Cloud.

Also please download a copy of the Log File Viewer app if you don't already have this and check for any messages in the log files that may shed more light on the 'not enough memory' error you are seeing.

See also post https://forum.acronis.com/forum/117524 for another user who has reported the same error message recently.

 

Thanks Steve for the information. I contacted the support and attached the log file.

Wolf, I had a similar issue, nothing, I did fixed it (reinstall Acronis, fresh install of Acronis after using cleantool and recreating the task, rename database folder, rename clouddatabase folder, etc), .  

Ultimately, it turned out to be a local Microsoft VSS issue on my machine.  All of my local backups worked fine, but on this machine, cloud backups would get to s a cedrtain percent (about the same place everytime).  What I found, for me, was disabling VSS for the cloud backup script allowed it to run past the sticking point.  Try disabling VSS for that backup task and see if it can complete then.

Ulltimately, I couldn't figure out the VSS issue so just left it off for that backup.   You may even want to create a new backup task (recommend it) to the cloud and disable VSS first for that script only.  Then run it and see how it goes.  

When I eventually rebuilt the machine with a fresh OS install, Acronis cloud put the task on the machine again and I configured the backup options again and it has been working ever since.  

How to disable VSS 3 different ways 

 

Bobbo_3C0X1, thank you very much.

I uninstalled and reinstalled the program. I did not use the cleaning tool, because I saw, that this tool remove ATI2015, my version is 2016.

What I want to add is, that DiscDirector 12 also is installed on my harddisk.

Now I set the entry in the .tis file "use_vss=true" to "false" and will see, if this will produce an other result.

 

Excellent - fingers crossed it will help out.

As for the clean tool, I don't think it will resolve the issue in this case (it might be worth a shot though) if the above suggestion doesn't help.  Even though it's listed for 2015 it does work for 2016 as well.  

Some other suggestions, if disabling VSS doesn't work and you want to hold off on the cleantool as the last try...

1) try renaming these 2 folders and let acronis recfreate them the next time the app is launched.  You'll need to first close out of Acronis GUI and then disable the running Acronis services before you can rename the folders.

control panel >>> administrative tools >>> Services (right click on services and "run as administrator".  Then stop the running Acronis services... there are usually for of them.  FYI, if you don't use non-stop backups, you can also disable the startup of that one as it's only needed for local nonstop configured backups). 

C:\ProgramData\Acronis\TrueImageHome\OnlineBackup          (rename to OnlineBackup.old or whatever you like)

C:\ProgramData\Acronis\TrueImageHome\Database                 (rename to Database.old or whatever you like)

If those don't help either, you can then redo the same, but also C:\ProgramData\Acronis\TrueImageHome\Scripts

When you start Acronis it will create then all again.  You can then copy and paste your local scripts from the old folder back in (while services are stopped). Acfronis should create the cloud ones automatically.  The downside is even though the scripts can be re-added this way, you have to check the configurations again and re-run them. Usually, it will start with a new backup as well so I usually then put the existing backups in a folder called "old" to hold onto for a bit and delete them later on when I'm confidennt I have enough backup history built up from this type of change.