Salta al contenuto principale

Trouble with "failed" backups

Thread needs solution

I am trying to figure out what is wrong with this backup log.
I have C: in the laptop, and an external drive which also get backed up. The user tells me that the external drive which gets backed up is turned on and plugged in. Any thoughts?

1 Information 21/10/2015 3:46:57 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 Information 21/10/2015 3:46:57 PM Operation Goldstein-Full started by schedule.
3 Information 21/10/2015 3:46:57 PM Operation description: Stage Description.
4 21/10/2015 3:46:57 PM AcronisLRPCConnect::BEGIN id=3,768
5 21/10/2015 3:46:57 PM AcronisLRPCConnect::BEGIN id=6,512
6 21/10/2015 3:46:58 PM Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
7 21/10/2015 3:46:58 PM Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
8 21/10/2015 3:46:58 PM Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0
9 21/10/2015 3:46:58 PM Refreshing Drivers...
10 21/10/2015 3:46:58 PM Enter to process disks in Mbr Driver (id = 9)
11 21/10/2015 3:46:58 PM Exit from process disks in Mbr Driver (id = 9)
12 21/10/2015 3:46:58 PM Enter to process disks in Gpt Driver (id = 10)
13 21/10/2015 3:46:58 PM Exit from process disks in Gpt Driver (id = 10)
14 21/10/2015 3:46:58 PM LDM: New ProcessDisks(rawLayer, headLayer)
15 21/10/2015 3:46:58 PM ProcessDisks: One more disk to check
16 21/10/2015 3:46:58 PM ProcessDisks: One more disk to check
17 21/10/2015 3:46:58 PM Mark All groups as Root Like Dgs
18 21/10/2015 3:46:58 PM ------ Volumes Objects ------
19 21/10/2015 3:46:58 PM LDM initialization complete
20 21/10/2015 3:46:58 PM Analyzing partition '0-0'...
21 21/10/2015 3:46:58 PM Analyzing partition '1-1'...
22 21/10/2015 3:46:58 PM Analyzing partition 'C:'...
23 21/10/2015 3:46:58 PM Analyzing partition 'Q:'...
24 21/10/2015 3:46:58 PM Analyzing partition '0-0'...
25 21/10/2015 3:46:59 PM Analyzing partition 'E:'...
26 Information 21/10/2015 3:46:59 PM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
27 21/10/2015 3:46:59 PM Error while opening configuration file .
28 21/10/2015 3:46:59 PM Error occurred while creating the file.
29 Information 21/10/2015 3:46:59 PM Operation: backup
30 Warning 21/10/2015 3:46:59 PM The specified file does not exist: E:\Acronis Backups\Goldstein-Full_full_b3_s1_v1.tib.
31 Warning 21/10/2015 3:46:59 PM The initial full backup version is not accessible at the moment.
32 Warning 21/10/2015 3:46:59 PM The specified file does not exist.
33 Warning 21/10/2015 3:46:59 PM The system cannot find the file specified
34 True Image 21/10/2015 3:46:59 PM The specified file does not exist.
35 True Image 21/10/2015 3:46:59 PM The system cannot find the file specified
36 True Image 21/10/2015 3:56:59 PM The specified file does not exist: E:\Acronis Backups\Goldstein-Full_full_b3_s1_v1.tib.
37 True Image 21/10/2015 3:56:59 PM Check whether the source and destination partitions exist.
38 True Image 21/10/2015 3:56:59 PM Canceled.
39 True Image 21/10/2015 3:56:59 PM The specified file does not exist.
40 True Image 21/10/2015 3:56:59 PM The system cannot find the file specified
41 21/10/2015 3:56:59 PM ServerLRPC::_CloseConnection id=6,512
42 21/10/2015 3:56:59 PM ServerLRPC::_CloseConnection id=3,768
43 21/10/2015 3:56:59 PM ServerLRPC::_CloseConnection id=6,512
44 21/10/2015 3:56:59 PM ServerLRPC::_CloseConnection id=3,768
45 True Image 21/10/2015 3:56:59 PM Operation has completed with errors.

0 Users found this helpful

Line 30-36 indicate E:\Acronis Backups\Goldstein-Full_full_b3_s1_v1.tib. does not exist.

What is drive E? Is it connected and is it CURRENTLY assigned as drive E. Windows often assigns different drive letters when other disks are attached. Perhaps the disk is attached by as another drive letter.

Or, maybe the missing tib file was deleted.

More investigation needed to confirm what actually is missing. Is it the file or is it drive E not there as drive E.

I will be onsite later today to confirm. E: should be the external hard drive that Acronis is backing up to. Maybe I should force the drive letter to Z: and adjust the backup to point there instead?

That would be better but you may have to create a  new backup task in order to make sure the change works.

So, If I delete any backup job, change the drive letter, format the external drive, and create a new weekly full backup to the new drive letter, everything should work out. I will test this later this afternoon.

A  reformat of the destination drive shouold not be necessaryi.

Here are two examples of how to set up a backup scheme with automatic cleanup so manual deletion is not needed.

GH11. <a href="/system/files/10-1full--custom_keep4.jpg"><strong>Create Custom Full Backup Scheme w/auto cleanup.<br />...Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..</strong></a><br />

GH12. <a href="/system/files/10-2inc-custom_keep64.jpg"><strong>Create Custom  Incremental Backup Scheme w/auto cleanup. <br />...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.</strong></a><br />

 

Editing an existing task is not recommended.  Rarely does an edited task perform to user expectations. It is usually  better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.