Skip to main content

Backup failure with only 1 minute remaining

Thread needs solution

My backup has started giving me an error with only a minute remaining of the backup process.
When I click "retry", I get the same error message.
I don't know if my backup is good or not, I don't even know how to delete the current backup and start another one.
I can't get anyone to reply on "chat" and I can't locate an email for tech support.
I'm stuck - like Chuck.

Attachment Size
error.jpg 359.06 KB
0 Users found this helpful

You need to provide detail, otherwise we're just guessing. for example (just examples of info. you should provide - you should provide more detail than just these examples):

- where are K: and L:?
- if they are external drives, how are they connected?
- has this backup task worked previously?
- if yes, what changed since then?
- does the backup task include validation?
- is this an Incremental backup task? I think it is, as naming includes "s114" which would be the 114th incremental in the chain.
- try validating other backups made with that task
- etc.

Internal drives
Yes, worked previously
What changed? I use the computer every day, I can't pinpoint any changes.
As for validation, incremental, and other stuff... I don't know.
I just go to the main menu and click "backup now".
Maybe this program is too complicated for someone like me. I don't want to read hundreds of pages of instructions.
I just want to make an image of my hard drive in case my computer crashes.
Is there any way to just wipe everything and start over and make a simple image of my HD?

Check out the many user guides and tutorials in the left margin of this forum, particularly Getting Started and Grover's True Image Guides which are illustrated with step-by-step screenshots.
In particular, 29618: Grover's new backup and restore guides http://forum.acronis.com/forum/29618

I advise you to follow Grover's guide to create a brand new backup task, backing up to a new folder. Myself, I prefer full backups (not incremental nor differential) because each one stands alone and depends on no earlier backups. If you don't have space for that, use incremental nor differential but do not allow an incremental chain to become so long. 114 incremental backups in a single chain is outrageously risky.

FYI:

A task for Incremental or Differential will always begin with a full backup. That is necessary, as that becomes the baseline.

For an Incremental task, after the first full backup, subsequent backups will be incremental, each one based on changes since the previous Incremental backup, all the way back to the second backup being incremental based on changes since the full backup. As such, you need all links in the chain, all incremental backups right back to and including the first full backup, in order to Restore.

For a Differential task, after the first full backup, subsequent backups will be differential, each one based on changes since the first full backup. To restore, you would need just any Differential and the Full backup on which it is based.

You should not allow an incremental chain to become too long. An incremental restore depends upon every incremental in the chain being valid, including the original full. It's better to limit each chain to just a few incrementals, followed by a fresh full backup to start a new chain.

You should validate backups periodically. That would alert you much if the full backup were missing or unreadable.