backup when logged off

Teotech,

I could be confusing TI with ABR here, but I think it should run scheduled tasks if not logged on, BUT, when you installed TI did you select All Users or just for your logon?

Do you use a password to logon to Windows?

I don't have TI 2013 installed on my W8 at the moment, but it is possible that in W8 it behaves differently to XP->W7.

Colin,

I am seeing this problem on two W8 machines, with different hardware. Both have multiple users with passwords. TI is set up for all users.

If the user remains logged on, but the PC is in sleep mode, it wakes up at the expected time and backup proceeds normally. But if I log out and the PC goes into sleep mode, the backup doesn't occur until the next morning after logging on. I have not yet tried disabling sleep before logging out.

If you turned off the TrueImage Scheduler and created a Windows Scheduler Task, I believe you could accomplish your goal. A new backup task is not needed--just change the TI task to to "do not schedule".

Click on link #3 below and review item #10 (also look at item 9) which discusses the use of the Windows scheduler.
In particular, the Figure 14 picture provides the option to run if not logged in and be sure and also select the wake up option (figure 18). Rewiew all screens for any options which might be pertinent to your situation.

I have never used the "not logged in" opton but it should work.

You may also have an interest in item 9 as well if you have any sleep issues with the backup.

Thank you, that looks like exactly what I need! I hadn't noticed the Create Shortcut option, and there is nothing in the help or manual about running scripts.

I will try it tonight and let you know what happens.

Backups run now when logged off. I just need to take care of the PC going to sleep before the backup is finished, I will do that in separate scripts so that my sleep settings don't change if a backup is run manually from the TI interface (my logon/logoff scripts change to 3 min sleep when logged off, 1 1/2 hours when logged on).

Thanks again.

Yes, item #9 in post #3 above can help you.
My solution uses the Acronis pre/post pre command to turn on (no sleep) while the backup is being created.
After backup created, the pre/post post command returns the computer back to normal or whatever was set prior to the backup. My settings change the computer power configuration only during the backup creation time.

I was unable to get this to work when logged off. The Windows task scheduler showed that the backup tasks started when expected, but the backup including the pre/post commands for the power scheme would not start until I logged in the next morning. All task scheduler and TI settings were OK.

I found an old post from Acronis Support that showed how to make a batch file to run a backup. It used "C:\Program Files\Common Files\Acronis\TrueImageHome\TrueImageHomeService.exe" instead of "C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageLauncher.exe". Tried using TrueImageHomeService, and now backups run when logged off!

This may have something to do with increased security in Win 8. I have some Autohotkey scripts that ran OK under Win 7, but could not start some programs from the scheduler under Win 8 until those programs were moved to a new folder.

posted in wrong thread

I believe you will find that whenever the homeservice exe is used, the program control will NOT completely function as expected. The number and type of backups will become out of whack. The execution of the program needs to be the Laucher.

You might double check the Windows task scheduler for these options should be enabled.
General tab:
..Run whether user logged in or not.
..Configure for you specific OS

Conditions tab:
..Wake the computer to run the task.

Settings tab:
..Allow task to be run on demand.
..Run task as soon as possible, if missed
..Run with hightest priveleges.

Since I do not have Window 8, I cannot run any actual tests.

If I am understanding correctly, since the TrueImage Scheduler is disabled, the Windows task did kick of at the correct time but TrueImage did not start and prepost did not start until after the login.

Grover,

Homeservice did cause some issues, a full backup was created when it should have made an incremental.

All of the task scheduler options are set properly. The power scheme for backups is set to never sleep or turn off the hard disks.

Last night I tried putting a copy of the launcher program in a folder outside of Program Files and referenced this copy in the task scheduler. I have two backups scheduled. The smaller one for the system disk ran and completed successfully in about 6 minutes. The other one created an 211MB incremental for 3 drives; it ran for many hours - the log says it started at 1:54 AM and completed at 4:51 AM, but when I logged on about 8:00 it was still running and took another 40 min. or so to complete.

At least the backups are starting OK now, but something is still not right.

We have discussed a lot. Would you mind confirming for me--just to make sure I am understanding correctly.
1. When is the task schedued to run?
2. When the backup is completed, what is supposed to happen next. A shutdown or a sleep, etc.
2. Is the system supposed to shut down the computer when done. If yes, what is it you are using to issue the shutdown command?

Do check the power setting from inside the device manager on the usb root controller.
Option ot allow computer to power down the usb disks shouldl e unchecked.

1. I have two backups, the first one is only the Windows 8 and System Reserved partitions, and is scheduled to run at 1:03AM. The other is larger, containing data files from three drives, scheduled to run at 1:54AM. They are backed up to an internal SATA drive.

2. When the backup completes, the post batch file, which I also use as a logoff script, changes the power mode to one that makes the system sleep after 5 minutes.

3. I sometimes manually copy some backups to an external USB drive, USB is not an issue for the automatic backups.

Using a copy of the launcher program in a different location was just a test to see what would happen, last night I got quite different results from the previous night. This time when I logged on, the first backup was only half done, it completed in a short time. The second backup showed "queued" in the TI interface and started when the first one completed.

Also, for at least the last week, when I log on new folders are created on the backup drive with the same names as the real backup folders, but with "-" added to the folder name, "=System 8" and "-Data disks". These new folders remain empty. If I delete them they are recreated the next day.

The most recent backup logs are attached.

General comments as to what you can expect
1. Two backups will not run at the same time. The later scheduled one will always be delayed until after the first one has been completed. A second scheduled backup should be scheduled later so the first one has time to complete.

2. A backup initiated via desktop shortcut (or Windows scheduler using a shortcut) should product the same type backup type (inc or full, etc & same elapsed time as the same backup would if the backup was initiated via the program scheduler or using the "backup now" option. In other words, the shortcut should produce the same results as the normal scheduled or manual job.

3. A backup which is validated as part of the task will task at least twice as long as without validation and maybe even longer--depending upon the number of incrementals being validated.

If you have any static files which are being redundantly included in many backups, perhaps you can use the exclusion feature and exclude them from the backup to improve performance time.

4. The issue with empty backup folders being created across several drives is a known issue "hopefully" will be fixed in some future version.

5. The Windows scheduler (if optioned to do so) should wake the computer to run the backup task--even if not logged in. If the Windows task is not waking the computer, we may have to try an alternative of using the Windows Schedule to run a pseudo bat file--just prior to the scheduled backup time--just to incur somne computer activity to cause a wakeup.

6. Here is a link which I have just created. This link has nothing to do with your question but it may be of interest.
http://forum.acronis.com/forum/42887

6. Let me know what issues are still pending and I will attempt to help.

Edit:
A. If your bat comands are using an actual bat extension, you would get better resulsts using a cmd extension.
B. Would you a screen capture of your backup scheme for the system backup. Thank you.
C. Do you have any other hidden or non-lettered partitions which are NOT being included within the backup?
D. For my own preferences, I prefer the full disk mode image which is illustrated in link #2 below.

Grover,

Thanks for continuing to help with this.

I am not trying to run two backups at the same time, the first one normally takes about 20-25 minutes when making a full backup, much less for incrementals. This one is backing up from an SSD to a newer quick SATA drive. The only unlettered partition is System Reserved, it is included in the backup. The SSD also has a Win 7 partition that rarely used, so it is not included in the backup.

The computer is waking up at the expected times. I can see that in the logs, and If I haoppen to get up in the middle of the night, I see/hear the PC running :)

The problem is getting everything to run when logged off. If do not log off when done for the day, but just put the PC in sleep mode, then the backups run OK at the scheduled times. They are both complete the next morning when I wake the PC.

1. Should you need to restore your SSD, you many need to have a backup of the Win7 partition in order to get your SSD or its replacment to boot. If the SSD is now bootable, it may be inter-dependent upon the Win7 partition.

2. As I am unserstanding, the backups run via Windows Scheduler work when you are logged in but do not work the same when you are logged out.

3. You have 3 files which I would check or change the security on.
The two cmd files which are your pre & post command files.
and the Windows task scheduler task file.

In Windows browse to where the two cmd fies are stored.
Right click on each and choose properties
Click on the Security Tab

Make sure all user names or groups listed all have the "allow" checked for each permission.

The Windows task is stored in
Windows/system32/tasks/ maybe a sub folder--all depending on where you saved the Windows Task when created.

Repeat the security checks on that the same as the cmd files.
On my Windows task, I had to Edit and change the System Permission so the "allow" was checked on all.

Whether this will help, I have no clue.

If that does not help, do you have the pre/post commands set on both tasks. If yes, remove from the task which runs first and only leave the commands listed on the long task.

At this point, I am only trying to find something that will work for you in case the issue is not Acronis.

I believefinally got it work for me but with these changes.

Open notepad using the "Run as Administrator" option.
Place the shortcut information inside the command file
@echo off
"C:\Program Files\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:097A3AE1-A4B1-4DA0-82B4-38F4CD1828AC
exit

Save as xxxxxx.cmd

and change the Windows task scheduler to run the xxxxxx.cmd file above.

Let me know.

PS: Note inside the Windows task scheduler there is a history tab which can be very informative when it fails.

Later edit:
To clarify. What I am saying is that I was able to successfully get the Windows 7 Scheduler to initiate a successful backup with NO user being logged in.
Some of the options checked were
"run whether user is logged in or not"
"run with highest privileges."

Having the TI shortcut be part of the scheduler command did not work but having the TI shortcut contained inside a separate cmd file and having the scheduler run the cmd file was successful.

Just as a precaution, I would verify security on these files that all the users groups listed all have full "allow" rights plus

Shortcut command file.
TrueImage.exe
TrueImageLauncher.exe

The shortcut cmd file was created with "run as administrator" rights.

All set up to run tonight, I will let you know what happens.

I am not clear on making the cmd file run as an administrator. That option is available for lnk shortcuts, but not cmd or other file types (except in the right-click menu when running manually). Will the Run with highest privileges scheduler option take care of this?

Probably.
The method I use is to
start/program/accessories
RIGHT click on Notepad
Click the option to "run as administ rator"
paste the contents into notepad
save the file

Two nights ago according to the log, the first backup saved and validated an incremental in a few munutes, but the final "operation has succeeded" entry happened the next morning after logging on, and a "succeeded" popup message was shown. The other backup started after that.

This morning the first backup was creating a full backup as it is configured to do after 3 incrementals. It began at the scheduled time, but did not continue until I logged on. It looks like the PC went into sleep mode enen though the 'pre' batch file should have prevented that. The batch files and containing folder all have security set to full control for System and all user groups. Some files in the TI program directory also have full permissions set for ALL APPLICATION PACKAGES, maybe I should do that for the batch files?

Something got scrambled in the records of which .tib files belong to which backups. File restore shows entries in the timeline for both the System 8 and Data Files backups. Also, when I try to browse those backups on the backup drive with Explorer a file dialog is shown to locate volumes that aren't there. Older backups that are not scheduled are OK.

I may just go back to just staying logged on and manually invoking sleep mode, and use the scheduling in TI. That seemed to be much more reliable here.

Sadly, I read your update. Not having Wn8, I cannot test further.
One last thing, I do want to confirm that all your "batch" files have a .CMD extension and not a "bat" extension.
Additionally, you might want to try a different command within the cmd file to achieve the same effect just to see if that helps.

If the files are mixed up, then you may have to start over.
Any tib files you are concerned about should be validated as a separate action.

Keep me posted if the results change.
If and when another build or version of Acronis comes out, maybe you can recheck.

Grover,

The batch files are all .cmd.

I am going to uninstall TI and the Plus Pack, run the cleanup tool, and then reinstall, just in case some settings in ProgramData or elsewhere are messed up. It only takes a few minutes, been through it several times when working with tech support on another problem. I will then recreate the two troublesome backups and schedule them from within TI. And stay logged in :)