Running jobs via TrueImageLauncher
I have two disks in my system (Windows10 and Users) each with separate jobs to backup to my NAS and Acronis Cloud. I also have a simple file-based backup job for testing which backs up a small number of files on the same disk. I am executing the following commands in an elevated command prompt:
pushd %ProgramFiles(x86)%\Acronis\TrueImageHome TrueImageLauncher.exe /script:xxxx
Specifying the id of my simple job causes it to run as expected. However, when I specify any of the other ids the job doesn't run and the following message pops up very briefly:
I have tried changing the default directory to the scripts' location with the same result. The next option will be to recreate one of the disk backup jobs to see whether that has any effect. I just wondered whether anyone has seen anything like this? I remember that a previous version (2016?) let you create shortcuts to jobs, but can't really see what the connection is with this message.
Thanks for that Steve, will take a look. I had seen another post about killing active processes before running jobs in the background, but wasn't sure if that was an unusual case. Curiously my simple job seems to run just fine in the background even with the TI console open - I can see the job status changing and the Activity page being updated. I then created a task for one of my disk backup jobs in Task Scheduler, but when I ran it, nothing happened. That's when I resorted to the command line approach which produced the weird pop-up message.
While on my PC last night I noticed that the first of the backups was running, having been started by Task Scheduler. I waited until each of the others should have run, but none of them did. After checking everything I remembered that I had done a manual "back up now" on one of them the previous night - the same one that was now running. I did the same with the others, and when I checked this evening all of them had been run successfully by Task Scheduler.
It looks like disabling the schedules in TI put them in a strange state (producing that odd "shortcut" message when trying to run them via the launcher) but manually running them somehow fixed that.
Alastair, you will need to decide which method you are using for running your backups. I do not have any scheduled tasks in the ATI GUI but am able to use Back up now when needed, while running my tasks via the Windows Task Scheduler using my PowerShell script, but not both at the same time. I added an extra step in my script to check for an already active task to avoid trying to walk over it.
Write-Host "Wait for any running tasks to complete"
wait-process TrueImageHomeNotify, TrueImageHomeService -ErrorAction SilentlyContinue
I decided changed from the TI scheduler to Task Scheduler as it has more features including the option to ignore a missed run. I created a task for each job to run TrueImageLauncher with the relevant script and disabled all of the schedules in TI. That's when I found that the jobs weren't getting run by Task Scheduler - the only way to make them "runnable" was to manually run them once from the TI GUI console. Since doing that Task Scheduler has been running all of them okay.
Alastair, I haven't seen any issues where I needed to run any tasks manually in the GUI in order to get them to run correctly from the Task Scheduler. I don't have any tasks scheduled in the GUI and have been using Task Scheduler for a long time now because of the added flexibility it gives to me when using my own PowerShell scripts to launch the backups based on various conditions being satisfied, i.e. am on my local network for access to my Synology NAS drive, the Acronis Cloud servers are available.