Salta al contenuto principale

Warning Message in Backup

Thread needs solution

For the past week I have been getting the additional message regarding backups - see attached and partial copy below:
15 Acronis Test Program 1/31/2013 3:00:53 AM Failed to open backup E:\My backups\My_backup_2013-01-01_0700_inc_b1_s2_v1.tib. It may be inconsistent or corrupted.
16 Acronis Test Program 1/31/2013 3:00:53 AM
17 Acronis Test Program 1/31/2013 3:00:53 AM The specified file does not exist.
18 Acronis Test Program 1/31/2013 3:00:53 AM The system cannot find the file specified
19 Acronis Test Program 1/31/2013 3:10:53 AM Failed to open data stream. Try to remove the backup from the list, add it again by clicking

'Browse for backup' and recreate the backup settings.
20 Acronis Test Program 1/31/2013 3:10:53 AM Canceled.
21 Acronis Test Program 1/31/2013 3:10:53 AM Canceled.
22 Information 1/31/2013 3:10:53 AM Deleting backup file with path E:\My backups\My_backup_2013-01-01_0700_inc_b1_s2_v1.tib.
23 Information 1/31/2013 3:10:53 AM Deleting backup file with path E:\My backups\My_backup_2012-12-31_2216_full_b1_s1_v1.tib.

The file listed in #15 does not exist. How can I remove this from the backup? The backup completes successfully, however, the error message indicates an issue.

I also get this message as a separate email:

My backup Task is waiting for user interaction.
Description: Stage Description
Information: Failed to open backup E:\My backups\My_backup_2013-01-01_0700_inc_b1_s2_v1.tib. It may be inconsistent or corrupted.
Details: Click Retry to try to read from the same location. Otherwise, click Cancel to cancel the operation.

Since this backup operation kicks off at 11pm and ends around 3am, there is no way of doing a manual interaction.

Don

Allegato Dimensione
acronis_backup_log.txt 3.01 KB
0 Users found this helpful

My suggestion for a fix would be to stop using the old task and create a new task.

Your existing task involves consolidation. My suggestion would be use the example 11-Inc as listed in signature link #2 below.
Adjust the 6 and 4 examples to fit your needs. This example is a simple add and delete basis without any merging of data. The log message relates to merging of old files and these file names are lost with the program.

The option that I have found works best is to use the "keep x number of recent version chains". This option has worked better for me as compared to the option which is based on elapsed days or space consumed.

My experience has been that editing an exist task should be discouraged as the results are not always what you might expect.
Create a new task pointing to a new empty sub-folder.

http://forum.acronis.com/forum/39528

don_s wrote:
Thanks for the info. I will create a new task, however, that basically says that is the end of the previous task used for backups though I would assume the previous backups are still valid if needed.

When I setup backups in industry I typically used the differential mode because it would give me the quickest recovery time - the last full backup and the last differential after the last full backup restored. Is there an advantage of one over the other, other than what I mentioned?

Don

Validate the backup and if they pass validation, certainly keep them as long as they have any value.
If you are comparing the benefits of differential to incremental, yes, the diff is my preferred due to the risk factor of incremental type whereby if one bad inc spoiling all the later incs.