Bug or Feature? Checkmark for computer shutdown not retained // Häkchen für Herunterfahren des Computers bleibt nicht gesetzt
| English | Deutsch |
|---|---|
| When one clicks on Status of a running backup in the Windows notification area, the main program window appears and the user may select Shutdown computer after completion. If the main window is closed and re-opened, the checkmark is no longer there. Result: 1) The true current status of the setting is unclear; 2) Once activated and the main window closed and re-opened, a deactivation of the setting is perhaps not possible. | Die Aktivierung (Häkchen) beim "Computer nach Fertigstellung herunterfahren" bleibt nicht gesetzt, nachdem das Hauptfenster während eines Backups geschlossen und wieder neu aufgemacht wird (z.B. über "Status"-Abfrage eines laufenden Backup-Tasks. Folgen: 1) Den tatsächlich aktuellen Stand der Einstellung ist unklar; 2) Eine spätere Deaktivierung der Einstellung ist evtl. nicht möglich. |
Hello Alfred,
Thank you for taking time to contact us.
We were able to reproduce the issue in our test lab.
I have submitted a new case, here is the case number: ATIHIIOXII-6044
Thank you.
Hi Oleg
You may also want to check what happens if you have multiple backups queued and check the last one you queued to shut the system down.
You should see that it may work sometimes and not others, the reason for this is that the scheduler runs backups in a random order NOT the order in which the user queued them.
This is also a BUG and needs to be resolved.
Hello Ray,
Thank you for your report.
Unfortunately, I was unable to reproduce the issue. Here is what I have done exactly:
I mixed disk, file and e-mail backups (1st backup - disk backup, 2nd (queued) backup - file backup, 3rd (queued) backup - mail backup, 4th (queued) backup - disk backup, etc). I created 4 "chains" of disk-file-mail backups. All of them started in accordance with the order I have queued them.
After that I repeated the steps I mentioned above and marked the box "Shut down the computer after completion" for the task located in the middle of the chains. The computer was turned off after the last backup task completion only, i.e. the program executed all the tasks and only then the system was turned off.
What was done wrong? Could you please provide me with the exact sequence of your actions so that I can reproduce the issue?
Thank you.
Hi Oleg,
Have you tried this more than once - it is entirely possible that the GUID of the script that is generated randomly just happened to cause all the tasks to be executed in the right order. I have seen this happen several times and I am pretty sure if you try it a few times you will see the effect. Please ensure you watch the order of execution as this will also affect what is backed up as the ATIH Database - I always TRY to make the system disk the last backup but this - in my experience rarely succeeds. I have to run that backup after all the others have run or started to ensure it is last which means sitting in front of the system until the correct situation is reached and the last task can be queued.
As an addendum to this - when I can get the sync's to run under a non admin account I would also like to ensure that the sync's of the backup just taken are completed to my NAS device before the system is closed
English Deutsch When one clicks on Status of a running backup in the Windows notification area, the main program window appears and the user may select Shutdown computer after completion. If the main window is closed and re-opened, the checkmark is no longer there. Result: 1) The true current status of the setting is unclear; 2) Once activated and the main window closed and re-opened, a deactivation of the setting is perhaps not possible. Die Aktivierung (Häkchen) beim "Computer nach Fertigstellung herunterfahren" bleibt nicht gesetzt, nachdem das Hauptfenster während eines Backups geschlossen und wieder neu aufgemacht wird (z.B. über "Status"-Abfrage eines laufenden Backup-Tasks. Folgen: 1) Den tatsächlich aktuellen Stand der Einstellung ist unklar; 2) Eine spätere Deaktivierung der Einstellung ist evtl. nicht möglich.
Hello,
I have the same issue like Alfred.
I tried it yesterday. It's exactly the same.
Hello all,
Thank you for your responses.
The issue ATIHIIOXII-6044 has been fixed. The fix will be available in the next released build.
The exact date of the next build release is unknown.
Ray,
I failed to reproduce the issue. Could you please try to restart Acronis scheduler and see if the issue remains?
Actually, I tried to reproduce it several times.
Thank you.
Hi Oleg,
The scheduler is restarted every day as I turn my system off overnight. I have just tried it again and the same thing tasks executed out of order.
Is there a log I can look at that shows what is being asked for if not I will add that as another issue to the lonh liust of issues I have with logging in ATIH. (all versions)
I need to be able to prove to you (and myself) that what I am saying is in fact what happens.