Skip to main content

Consolidating Backups Error

Thread needs solution

Hi all,

I have an issue with using multiple backup destinations in True Home 2014. When a hard drive is swapped, we receive an email with the error:
"Backup Task is waiting for user interaction.
Description: Stage Description
Information: Error occurred while creating the file.
Details:
To specify another location, click Browse."

I check the hard drive and the backup file is in there and full. I decided to run a manual backup and the backup process completes without issues until it says "Consolidating Backup" and an error comes up saying it cannot find the backup file. The file name is looking for is the latest backup which is stored on the other hard drive and since we use two external hard drives, it has been unplugged.

What do I do?

Thanks in Advanced.

0 Users found this helpful

The app cannot complete an action without access to the backup file needed to complete that action. This unplugged drive must be attached to the machine for the action to complete.

Is there no way around this? I want to use multiple drives and have one drive offsite. I understand I can create 2 backup jobs (1 for each drive) but this doesn't help me when I'm away or can't change the drives.

Well, making sure a copy of the latest backup is available on both drives I suppose would be one way, cloud backup would be another.

Well, another way would be to write a batch file to check which storage disk is attached and then have the batch file run the correct backup task for the specific disk which is attached.

When the task is first created, TrueImage stores information about the source and target. The backup will only succeed when that specific storage disk is attached; so you need a separate backup task for each storage disk. The tasks can be scheduled or manually envoked.

I can provide an overview but frankly, I would recommend that you make other changes as well so you might have no need or less need for the special batch file.

1. I would stop using Consolidation. This would eliminate your error message. Consolidation is like a 1000 (or more) piece puzzle and all the pieces look alike but each piece can only fit in one place. Consolidation is time consuming and vulnerable to problems.
My suggestion would be to use the custom backup scheme with automatic cleanup instead of consolidation. See links.
Which backup scheme are you using?
Full only
Full plus X incementals
Full plus X differentials.

GH11. Create Custom Full Backup Scheme.Keep 4 versions (chains).
GH12. Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains.
GH13. Create Custom Differential Backup Scheme. 2 Diff, Keep 2 chains.

Each of my examples work with automatic cleanup which means you designate how many chains you want to keep and once the program reaches that user set goal of keep x chains, then each new full backup will cause the oldest chain to be deleted automatically. Thus you have a revolving set of backup chains--much like an escalator--the new is added and the old is removed--automatically. No consolidation as the old backups deleted automatically when its replacement has been created.

You need a backup task for each storage disk. The tasks could be run manually or could be scheduled but one task would need to be de-scheduled during the time that storage disk is not in use and not attached. Later, when the times arrives for the other disk to be attached, the scheduler roll of the tasks would be reversed so each task matched to its own disk.

------------------------------------------
If the above scheduling were to be refined, you cold have a batch file check to see which disk is attached and then the batch could run the appropriate task. This is not a primer on batch file creation--just the concept.

For example: Each backup task is capable of creating a desktop shortcut to run the backup task from either a shortcut or via Windows Scheduler.
GH7. How to create a desktop backup shortcut from an existing backup task.

Lets assume that disk 1 is called the blue disk and is run from the blue task and can be run via the blue shortcut. An empty blue.txt file is added to the root directory of the blue disk.
Lets assume that disk 2 is called the red disk and is run from the red task. and can be run via the red shortcut An empty red.txt file is added to the root director of the red disk.

The control batch file would be run via the Windows Scheduler (not the Acronis scheduler).
This batch file would use the Dos Dir command and check the provided path to each disk. As only one disk would be attached, the batch file would only find the one color . If it finds the colored text file, it then runs the shortcut script for that task. Blue disk such as
IF EXIST X:\RED.TXT GOTO RUN-RED
IF EXIST X:\BLUE.TXT GOTO RUN-BLUE
:
:
:RUN-RED
"C:\Program Files\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:DA68328F-C5F2-4ADE-8B96-CDC550E28076
:
:
:RUN-BLUE
"C:\Program Files\Acronis\TrueImageHome\TrueImageLauncher.exe" /script:DA68328F-C5F2-4ADE-8B96-CDC550E28999

This would give you a general concept of one method on how to approach.
The batch file could be as simple or as elaborate as you wish to design it.

Ok I understand. Thanks for your detailed response.

If I turn off consolidation, do I still need to use scripts? Or will turning it off fix my issue.

Currently these backup jobs are custom with full backups keeping last 7 versions. I cannot find the location to turn off consolidated backups. When I click the gear icon > more, there is no consolidate option. Any ideas?

Post a screen capture of your backup scheme so I can see more details.

On your backup scheme page, If you are using a setting which is based on elapsed days or size limits. these settings involve consoldation. The "store no more than X" does not involved consoldiation.

Whenever changes needed, I create a new task and never make changes to an existing task.

In order to use multiple storage disk, you need a different task for each disk.
In order to have the correct disk in place and to use the correct task needs to be done either manually using one of my custom backup scheme examples; or, automated via a custom batch file.

I had this issue as well with my portable hard drive, which was mounted under different letter. Support recommended me to alter windows to set sticky drive letter name for this disk. Sorry I do not remember the procedure. Then I started new backup from scratch and it works.