Scheduled Backup not working

Gery, have you checked the Advanced settings for your scheduled task, and in particular, the option to run missed tasks at system start with a delay of ?? minutes?

If you manually run the missed task, does the schedule pick up again at the next time it is due to run?

Do any of your tasks show as being in 'queued' status?

Hi Steve, Thanks for your answer.

Delay is 2 minutes and the box is checked. But in my version, it doesn't say "Missed Backup", just "Run at system startup with delay". Ok, maybe because I got the German version!?

If this option is just for missed backups, I anyway would uncheck it. I want missed backups just to be missed and TI has to backup the next scheduled task.  

No, it doesn't run by itself anymore. Also if I create a new backup beside the existing one, the new one shows the same behavior. I would have to delete all the backups and create a new one to make it run again. But I don’t want to do that, every time a backup is missed, because the PC was off.

There is no queue.

Gery, the other option here is to clean out all the scheduled task data which you can do by using the Acronis Scheduler Manager tool (link in my signature).

Run the tool as Administrator which will open a black command prompt type window, then in this window issue the command task zap  which will remove all the scheduled task entries.

After doing the above, you will then need to reschedule any of your tasks as needed.

Thanks so far, but..

I didn’t post my issue to get a one time fix and it's no option for me to go through this after every time the PC was off and a backup is missing.

I want a solution. My question: Is it possible to configure TI the way that if the PC is off and a backup can't be made, it just goes ahead with the next scheduled task? If yes, how?

Gery, this is a user forum / I am just another user offering help here.

ATI works correctly for me with regards to how my own scheduled backups work, i.e. depending on the settings used, they either run the missed backup when the computer is turned on later (with delay time), or else just skips the missed schedule and runs on the next scheduled time.

The key difference here is that I am not using ATI 2016 and haven't used it for some years.  My computers are running ATI 2018, 2019 or 2020 versions.

I am also running on Windows 10 64-bit systems with the exception of one older Win 7 32-bit box.

Ref ATI 2016, you should be using the final build 6595 version.

Don't get me wrong, I appreciate your help.

To buy an update would only make sense for me, if this would be a bug which is eliminated in the newer versions.
Another reason to buy it would be, if the import/export of backup-chains would be easier.

For now I once again will delete all the backup-tasks and created them new. I will see how long it works this time.  If I have some more information to narrow the problem, I will come back.   

Thank you.

Gery, not sure what you mean by the import/export of backup chains but if you mean the backup task configuration, then this is definitely improved in the later versions of ATI by the provision of a new option on the main Settings page in the ATI GUI where you can export all your backup configuration settings to a zip file, then later import them back from the zip file if needed.

Hi Gery, Hi Steve :-)

I have the same problem (or a similar problem ...)

In my case, Acronis Scheduler2 does not work because there is a problem during startup.

Gery, since you don't shutdown your PC, there is no chance that Acronis Scheduler will restart. The problem is therefore repeated.

Check if the Accronis Scheduler service is running when you encounter the problem (and before starting Acronis GUI)

I have "fixed" this with a .bat and a Windows task, to be sure that Acronis Scheduler is running when the backup should start.

Here is the .bat (save it on the desktop):

@ Echo off

net start AcrSch2Svc

Then :

Creation of a shortcut (shortcut) to the .bat

Advanced properties: run as Administrator.

Hide the .bat and the shortcut.

Here are the entries (Windows / System) (translation from french) :

"The timeout (45000 milliseconds) was reached while waiting for the connection of the AcrSch2Svc service."

Then:

"The AcrSch2Svc service could not start due to the error: The service did not respond quickly enough to the launch or control request."

But there is another problem, which I have not solved, and for which I need help.

Even if Acronis Scheduler is running, the task does not start.

In the Acronis GUI, the only change is the date of the next backup. The backup does not start, only the date changes.

Entries in Windows / Application) (translation from french) :

"Acronis Scheduler:" The scheduler cannot execute the task with the GUID '3A329907-BE50-48D6-A091-4D3230E51826' because of error 5 (Access is denied .). "

It is not every time, but often enough.

It is not specific to Acronis 2016 (Acronis 2019 to).

Thank you for your help. .

Stéphane

Bonjour Stéphane, all versions of ATI are intended to be run from an Administrator account and should have been installed from the same in order that all the correct authorities, permissions & privileges have been given.

If you are running from a user account, then first ATI must be installed correctly per above, and then the program should be launched with 'run as Administrator'.

Hi Steve.

ATI was installed from an administrator account.

But some days there is a problem.

I have already tried to delete / create a backup task, but it is not enough, the problem recurs for some time.

It's not on all PCs.
Some never experience a problem.

Best regards.

Stéphane

Acronis Scheduler:" The scheduler cannot execute the task with the GUID '3A329907-BE50-48D6-A091-4D3230E51826' because of error 5 (Access is denied .

Did you try checking in  C:\ProgramData\Acronis\TrueImageHome\Scripts folder for a file with the above long name 3A329907-BE50-48D6-A091-4D3230E51826.tib.tis ?

If there is such a file, then open it in Notepad and see what the name of the task is (shown inside the <display>.... </display> brackets).

<?xml version="1.0" encoding="UTF-8" ?>
<batch>
    <version>1.0</version>
    <uuid>A46C9D16-6E12-400E-B28E-58B1E49AE5F8</uuid>
    <display>Win 10 SSD Diff&#32;E</display>
    <priority>low</priority>

Hi again Steve :-)

This is what is written in the 3A329907-BE50-48D6-A091-4D3230E51826.tib.tis file :

<?xml version="1.0" encoding="UTF-8" ?>
<batch>
    <version>1.0</version>
    <uuid>3A329907-BE50-48D6-A091-4D3230E51826</uuid>
    <display>Sauvegarde clé&#32;Z</display>
    <priority>low</priority>

And in the 5F478A8F-5B2C-416B-ACDC-737DBD479313.tib.tis file

<?xml version="1.0" encoding="UTF-8" ?>
<batch>
    <version>1.0</version>
    <uuid>5F478A8F-5B2C-416B-ACDC-737DBD479313</uuid>
    <display>Sauvegarde bidon</display>
    <priority>low</priority>

Any idea ?

For information, at 7 PM, Acronis Scheduler is not running :

And in Windows / System, just after the PC starts :

Le dépassement de délai (45000 millisecondes) a été atteint lors de l’attente de la connexion du service AcrSch2Svc.

and

Le service AcrSch2Svc n’a pas pu démarrer en raison de l’erreur :
Le service n’a pas répondu assez vite à la demande de lancement ou de contrôle.

Stéphane

Stéphane, try setting the Schedul2 service to 'Automatic (delayed)' [Automatique (retardé)].

Are you able to get the service to start if you select to do this from the services panel?

You may need to do a Repair Install (using run as Administrator or using an Admin account).

Hi Steve.

Thank you for your suggestions.

I'll try this and tell you the result.

Merry Christmas and Happy New Year.

Stéphane

Meanwhile I did a lot of testing, but still have the problem. After a missed backup, it won't backup anymore.

I also uninstalled ATI with Cleanup Utility (https://kb.acronis.com/content/48668  and installed ATI 2020. So, the "old version" is no excuse anymore.

Backup worked fine from standby. After PC was off and the backup was missed, there is no action (option "Run missed operations at the system startup…" is not set). From there on the next scheduled backup brings the error: "The latest backup has failed. Edit connection settings". The settings are correct. I can test it or connect it without problems.

I can start the backup manually, but the next scheduled backup brings the same error again (doesn't matter if PC is on or in standby mode).

I guess the key question to fix that is: What is the difference between starting a backup manually and scheduled?  

Gery, sorry to hear that this issue continues after doing a clean install of ATI 2020.

Please can you define how your backup task is setup here?

What is the Destination for the backup task here?

What version of Windows is involved?

Does it matter what type of backup is being performed here?
Example: does the same issue occur if making a simple Files & Folders backup of a few files?

What I am trying to understand here is whether I would be able to try to recreate this problem on one of my own computer systems, assuming that I can setup the same variables as are involved in your scenario?

Perhaps you can setup a test on your computer of a very simple backup scenario and document this / capture screen images of the configuration?  This would prove very useful in testing if this is limited only to your computer, or can be replicated by other users, and if the latter, can then be proven to Acronis support as an issue that needs to be fixed!

I am always using Windows 10/64 Pro and always go trough the same process (fullbackup manually > inc backup scheduled, missed backup (PC off) > inc backup scheduled > error).
I've tested all kind of tasks (NAS, HD, testfolder, user account), but couldn’t reproduce it reliable. Sometimes the error occurred, sometimes not. The only difference between testing and real backup is that I changed the scheduled time during testing.

I will now make a final test without changing the time (just as real) with just a small testfolder. This will take a few days.

Meantime I have one questions:

After the error occurres, I can backup manually and the error is away (or at least it says "The backup has successfully completed"). But once the error occurred before, the scheduled task won't work anymore (error: "The latest backup has failed. Edit connection settings."). What very exactly changes in the software during this process? If I can observe this, I maybe can find the problem.
And again: What very exactly is the difference between starting a task manually and starting it scheduled (PC on, not standby).

Gery, the only time I have seen any reference to 'Edit connection settings' has been when a backup has been to a network location - never to an internal or external drive!

The inner workings of the Acronis Scheduler are not documented and isn't using the Windows Task Scheduler, so difficult to say why there should be an issue with the scheduled task if a manual backup has run correctly.

The only other thought I can offer here, with this new twist to the story about connection settings, is that something has got corrupted in the Acronis database that stores information about backup tasks!  The best way to resolve any such database issues is to force the database to be rebuilt.

KB 60915: Acronis True Image: repairing program settings - covers how to rebuild the database by renaming or deleting the old files.

Uninstalled ATI again completely. Created a task with just one folder with one textfile in it and the destination is a NAS. Options I changed from default: Checkt Exclude files matching the folloging criteria and Performance operation priority high. 

Started fullbackup manually. After that I created a missed backup situation (PC off). After that I scheduled the task -> error.

I can start as many times I want manually, but as soon as I want to start it scheduled, the error comes.

For the path to the destination I used \\IP-Adress and \\Hostname. It both makes no difference for the result.

The problem is the connection, not the backup task itself and once again, there must be a difference between establish a connection manually and scheduled. And that’s where the error point is.
 

Has the destination always been your NAS for this issue?

Are you also mapping a drive letter to the NAS from within Windows?

The error also comes if the destination is a USB drive and no I didn't try the version to map the NAS to a drive letter.

But today I contacted the support. Result is that the problem seems to be if the backup is encrypted (no encryption -> no error; encryption -> error).  Support gives this issue to the developers.

Not to encrypt is no option for me, but for the moment I have a workaround. If all the Acronis processes are going to be stopped, scheduled backups start again afterwards. This is no solution for very long but for a while and I will see if Acronis is willing to fix that issue.

I will be back with the feedback of the developers. Thanks a lot.

Ok, thanks for the update and good luck with the developers!

Hi Steve and Gery.

Just to inform you that Acronis Scheduler now starts correctly.

Perhaps because there is no longer a problem.

Perhaps because 'Automatic (delayed)' setting is a good solution.

But I still have problems with backups, I will open a new discussion about it.

Best Regards.

Stéphane