Missed backup operations not caught up

Just guessing but the error condition probably stopped the tasks, so they aren't "missed", they actually ran, just unsuccessfully. The daily task gets a new initiation everyday, since it's a daily task. so even if it misses a day, it's run again the next, other things being eequal.

Thank you for your hint, Scott. IMO, such behaviour would contradict to the manual, section 6 "Scheduling":

"If you schedule a backup to a USB flash drive or validation of a backup that is located on a USB flash drive, one more check box appears: Run when the current device is attached. Selecting the check box will let you perform a missed operation when the USB flash drive is attached if it was disconnected at the scheduled time."

In the current settings, that check box was selected. IMO, the behaviour described in the manual is highly desireable since missed backups shall be caught up ASAP, regardless of the reason why they were missed.

Is there any chance there was a drive letter change assigned to the usb drive? An insertion of a flashdrive, etc could consume the drive letter normally assigned to the backup storage. Just a possibility. I assign a specific drive letter to my external drives such a x or y or z.

Thank you for attention, GroverH.
Unfortunately the answer is "no". I already fell into that trap months ago. Thanks to Acronis support, they advised me to assign a fixed drive letter (in this case: X) to the external drive. That works fine; i had tested the possible combinations with different flash drives and the external hard drive. The external hard drive always gets letter X.

This "fixed" assignment will work so long as no other device has been assigned the letter. E.g., if you assign "D" to a usb drive and it is unplugged, it will shouw up as "D" when you plug it back in except if some other device is recognized before you plug the USB drive back in and Windows assigns, on the fly, "D" to that other device -- in that case, Windows will assign "E" to the USB drive when ou plug it in.

So it's a good idea to assign a drive letter that is several letters down from whatever in use is farthest down the alpha.

Scott, that's what i tried to describe in my first posting today. Again: There is definitely no confusion with drive letters.

Alexander,
As the task appears to be quite old for the weekly and monthly backups, would you simulate editing the task and confirm the settings are as you believe them to be. My reason for asking is that there have been reports of settings not being retained during certain types of save procedures when creating a task.

You might also consider utilizing "DriveNotify" written by MVP contributor MudCrab. This is a reminder program that opens a window on the desktop advising to insert a specific external drive--specific to that task. More details in my signature below.

GroverH,

thank you for your hints.

From my experience with ATIH 2010/2011 (since midst of 2010) i can confirm that backup task settings sometimes are not stored/saved. I've seen this several times but to my regrets have not discovered the exact circumstances yet - or even found a solution. As a workaround, after changing+saving/closing a backup task i reopen it to verify that ATIH really saved the settings. However, according to your hint i deleted the old backup tasks for weekly and monthly backups, created new tasks from scratch, saved them (and reopened them to verify the settings). Some days later i checked the status again. As before, the daily baskup task was caught up (as expected) but the weekly task was not.

Yes, i considered "DriveNotify" (last year) but did not use it yet because IMO this utility can call the customer's attention to the need of connecting the backup medium (external USB hard drive) -  but it can not prevent a backup from being missed (if the customer does not "obey" the advice given by "DriveNotify"). And if a backup has been missed,  i suspect interference with the Scheduling Options i'm using (because they seem to fit the customer habits best):

• Advanced Settings, check box "Run at system startup": selected
• Advanced Settings, check box "Run when the current device is attached.": selected

I don't know the program logic and operating sequences of ATIH and it's scheduler and i unfortunately did not find a description yet. I just supppose that the above options will prevent a missed backup task from being started as long the backup medium is not available. If this is true(?), the pre-command will not be executed and "DriveNotify" will not be started, right?

What I have found that works for me is to always exit the task (new or edited) from the backup scheme section. Look at this attachment and note the comments at the top in red and on the bottom regarding how I save my tasks. That example also shows one example of a successful task execution.

http://forum.acronis.com/forum/20993

There was a new task scheduler update release a short time ago. I have been using it without any ill effects. You might want download and try it. This is not part of the 6696 release. Check item 8-AO inside my yellow signature index below.

I don't know of what can prevent a backup from being missed. In order for Drive Notify to be of assistance, the task must be started either by TrueImage or by Windows Task Scheduler to start TrueImage. Once the task is started, the pre/post starts Drive Notify which displays an open window advising user to insert Disk X. The task will remain open on the screen until the user either minimizes the window or cancels the window or attaches the matching disk and is recognized by Drive Notify before the Window will close. If user cancels the info windows, the tasks fails and the log file (if examined) identifies it as a failed pre/post execution.

Is this something that a reminder program could assist or a Windows Task scheduler message at a specific time and date, etc.

GroverH,

thank you for your HowTo (successfully save backup tasks) and the update pointer (to task scheduler 464). I'll give it a try upon my next site visit.

Re pre-commands & DriveNotify I'm sorry for my (apparently) unclear question. To say it in other words:

Will ATIH start a task (and hence execute the pre-command)

a) for the 1st time

b) for an n-th time (n > 1; i.e. at least the 1st backup was missed)

even if the backup medium (external hard drive) is not available/connected and the Advanced Scheduling Settings "Run at system startup" + "Run when the current device is attached" are both selected?

Re: Drive Notify
Its only purpose is to place a Window on the screen telling the user to attach drive x. It has no scheduling capabilities. If it is placed in a pre/post task, Drive Notify will run every time TrueImage begins that particular task--no matter when the task runs.

I have not tested your last question. My guess is that you would not need the "Run when device is attached as the task would be run by the scheduler or the "Run at startup" option.

Is the system up and running when the backup is forgotten? If yes, then having Drive Notify putting a message window on the screen should the a solution to get the drive attached so a backup can be completed.

No, due to low usage frequency, in many cases the system is unfortunately not up when (according to the backup schema set up in ATIH) a backup should take place. In other words: In many cases, the backup is missed because the system is not up. That's why i chose to select the options "Run at system startup" + "Run when the current device is attached". As far as i understand, a backup missed during system downtime will not be caught up if these options are not selected. Right?

So if the answer to both my above (2011-04-25) questions a) and b) would be yes(?), DriveNotify would help even in cases when a backup was missed due to downtime and the backup medium is not connected upon next startup. Otherwise, DriveNotifyjust would help just in cases when a backup is about to be missed due to unconnected backup medium while the system is running.

Before I respond, I want to do a little testing. Will try to respond Thursday night.

In your post #1, is each task directed to its own folder so that the 3 tasks are using 3 different folders?

Referring to the tasks which failed to run. when the task was first created, did you run the tasks to make sure they perform and validate the backups?

GroverH,

thank you for your efforts!

Yes, each backup task uses a different destination folder:

• daily for a selection of user folders (subset of files from data partition): X:\Backup_Acer_TravelMate_5730\Users\Andrea\
• weekly for the data partition: X:\Backup_Acer_TravelMate_5730\Partition_D\
• monthly for the system partition: X:\Backup_Acer_TravelMate_5730\Partition_C\

where X is the fixed drive letter of the backup medium (external USB hard drive).

Re verification of the backup tasks I'm not sure because of the long-lasting background and the many attempts to fix the problem. I'm sure that in most cases i verified (by manually starting) the daily backup (because that does not take much time) which (as the only backup task) works fine automatically. I'm not sure whether or not I've already verified the weekly backup task i recreated recently during this thread (posting #8).

Alexander,
I did not get my testing completed. Will respond tomorrow. My apologies for the delay.

Alexander,

Re: Advanced Scheduling Options for a USB backup storage disk

   If Missed: "Run at startup"
   If Missed: "Run when current drive is attached"

Recommendation:
After a whole bunch of testing of various option settings my advise would be for you to use the single option "Run at startup" and to use the accessory Drive Notify in the pre/post pre command option.

Drive Notify is started by TrueImage and runs before the backup is initiated. The sole function of DriveNotify is to place a good sized information window on the destkop advising the user to attach the specific external disk associated with that task. It pauses the intended backup until the external disk is attached, Drive Notify checks to confirm the correct disk has been attached and then exits. The free version requires the operator to close the info window whereas, the paid version will auto close the window once the correct drive is recognized. The backup begins as per its task options.

My reasoning:
1. If computer operational at time of schedule backup, TrueImage will start and launch Drive Notify. Who will in turn, prompts the user to attach a specific external disk. Once correct disk is recognized, DriveNotify exits and the backup begins under the control of TrueImage.

2. If computer is off and a backup has been missed, the "If missed: Run at startup" option will initiate the backup upon startup and the procedure will repeat as listed in item 1 with the info window, etc. Drive Notify becomes your reminder that a backup has been missed and a reminder to check the log files for additional entries.

------------------------------------------------------------------
Results-1: If the "If Missed: "Run when current drive is attached" option is used, it assumes control and is total control. If computer is active and the drive is attached when scheduled time arrives, a backup is created. If a backup has been missed, upon bootup, no backup will be run until the external disk is attached. No prompting and no errors. TI simply will not start until the disk is attached. The "Run at startup" is superseded by TI waiting for a prior backup to be run and makes no difference whether the "Run at Startup" is checked or unchecked as the program won't do any backup (for that particular task) until the disk is attached.
----------------------------------------------------------

Results-2: If both "If missed" options are not used and computer is active, the backup will run if the disk is attached. If not attach, an error windows will appear "Error occurred when trying to create the file." You may have a retry option or the computer may hang awaiting a response and the only response accepted may be an cancel of backup until the next scheduled time.
---------------------------------------------------

Results-3: If the single "If missed: run at Startup: is checked. If computer active, the schedule backup will run if disk attached.

If computer not active and a backup is missed, upon bootup, the Startup command will attempt to run the backup. If the disk is attached,the backup will run. If disk not attached, the backup will attempt to run and immediately go into an error condition as in Results 2.
-----------------------------------------
So for me, the bottom line is that the only thing which most solves the problem of a missed backup is my Recommendation as above.

-------------------------------------------------
Task Suggestions:
1. The frequencey or type of backups should not matter as to whether functional.
2. When creating new task, when finished, prove that the task is works. Execute "Run task Now" option.
3. The folder names you are using should not be an issue. Each task to its own folder and its own unique file name.
4. As for the backup file name, Avoid using spaces or numbers or periods or parenthesis as part of the backup file name. I use two underscores as the last two characters of the actual backup file name. Avoid lengthy names.

5. I do not edit my tasks but I always try click the "OK" button from the "backup schemes" subsection. I do NOT click the OK button from any of the sub-sections (advanced or notiifcations,etc) but return to "backup scheme" for clicking "OK." before the final save function.
6. If you have not checked your disk for errors within the past few months, it would be wise to do so as TrueImage will function better in an error free environment.

------------------------------------------------------
You mention that one of your backups is a partition backup. Be reminded that Windows 7 may have it own boot partition so a backup of the single drive C may NOT be adequate to create a new replacement disk. A full disk backup (all partitions) is your best insurance to insure a bootable replacement disk. Or, having backup of all partitions can also be adequate for a replacement disk but disk option backup is preferred because it enables the user to recover the "Disk signature" if a new disk is needed. Windows Disk Management offers a good view of all the partitions in your disk and will also display any non-lettered partitions which do not appear in Windows Explorer.
--------------------------------------------------------

GroverH,

thank you very much for all your testing, in-depth analysis and documentation! May it help many other users, as well.

I studied your posting yesterday, will now setup the backup tasks again (from scratch) considering your recommendations and report the results. (Due to other liabilities, this may last until next week.)

Re your reminder on Windows 7 boot partition: As the customer's computer came with a preinstalled Windows 7 and a recovery tool from Acer, there are 4 partitions on the disk:

• PQSERVICE: recovery partition
• Acer (C:): primary partition; start partition, swap file, post mortem dump
• DATA (D:): primary partition
• SYSTEM RESERVED: primary partition; system, active

In ATIH, when I create a new backup task and select the "volume mode", I see all 4 partitions and can select each of them. The current backup plan is to make

• weekly "data partition backup" inluding "DATA (D:)" and
• monthly "system partition backup" including "PQSERVICE" + "Acer (C:)" + "SYSTEM RESERVED".

Would you anyway recommend not to split these and instead to make a disk backup? (I am sorry, haven't understood the importance of the disk signature yet.)

Some software vendors utilize the Disk Signature for identification purposes and base some of their preference settings on that information and to help prevent unauthorized installation.

When and what to backup is often a matter of personal preferences but you should always have at least one disk option backup that includes all partitions so the entire disk contents is within the backup. This type backup much more easily restored to a new disk if and when needed.

As in the prior post, I suggest that you look at the disk via the Windows Disk Management graphical view. It is highly probable that the sequence of partitions will differ from what you have reported in your last post. The sequence that you see in the graphical view is what must be duplicated should you ever need to create and restore all the partitions--one at a time.

There will probably be none to few changes in the PQService and System Reserved partitions but C and D will change every day the computer is powered up. It's your choice but my suggestion would be that you setup one task (weekly) to do a disk option backup (all partitions). The first week would be a full backup and the remaining 2nd, 3rd, 4th week weekly backups, would be either differential (preferred) or incremental type backups.

For redundancy, you might consider setting up an additional monthly full backup by itself.

The attached shows some sample backup settings for a weekly type backup.

Note that OEM versions of Windows preinstalled on new PCs often have a rstricted license that does not allow transferring to a diff PC so you need to restore incuding the disk signature. Also, they do not come with an install disk but rely on a special partition instead. Plus Windows uses a special partition for some system files. So if you need to reinstall, you might need the Manufacturer's partitions as well as the main and Windows sysem partiton. I'd recommend doing a full disk backup and keeping this, at the very least, as a last resort backup regardless of whatever other kinds of backups you decide to do.

GroverH and Scott,

thank you for your recommendations and background information! I have changed the backup strategy to

• daily file backup for a selection of user folders (subset of files from data partition)
• weekly volume backup for the data partition ("DATA (D:)")
• monthly disk backup for the entire hard disk (including partitions "PQSERVICE", "SYSTEM RESERVED:", "Acer (C:):", "DATA (D:):").

Re the scheduling issues, i cleaned up, set up new backup tasks and user-defined pre-commands (considering your hints). Triggered manually, each of the backup tasks ran successfully one time. I will continue tests with automatic (scheduled) start next week.

Thank you for the update. Keep us posted on the results--good or bad.

If and when you have some time, also investigate the possibility of using Chain2Gen as listed in my signature.