Skip to main content

The specified file does not exist...

Thread needs solution

This one is driving me crazy.

Log of a failure below if that helps.

First we ran out of space, so I deleted older files.  This is apparently a no-no.  After getting more drives in, I recreated the backup (which oddly enough is not called "Entire PC (BILLING)" - even though it's looking for a file with the old job's name".

How do I reset this and start over?  "Cancel", "Retry", "Ignore" options don't seem to accomplish this.

Also is there a simple way to copy settings from an existing profile?  

Thanks,

Charles

1    Information    11/9/2015 6:03:46 PM    Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
2    Information    11/9/2015 6:03:46 PM    Operation Auto Incremental (BILLING) started by schedule.
3    Information    11/9/2015 6:03:46 PM    Operation description: billing network backup incremental.
4        11/9/2015 6:03:46 PM    AcronisLRPCConnect::BEGIN id=5,248
5        11/9/2015 6:03:46 PM    AcronisLRPCConnect::BEGIN id=6,192
6        11/9/2015 6:03:46 PM    Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
7        11/9/2015 6:03:46 PM    Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
8        11/9/2015 6:03:46 PM    Refreshing Drivers...
9        11/9/2015 6:03:46 PM    Enter to process disks in Mbr Driver (id = 7)
10        11/9/2015 6:03:46 PM    Exit from process disks in Mbr Driver (id = 7)
11        11/9/2015 6:03:46 PM    Enter to process disks in Gpt Driver (id = 8)
12        11/9/2015 6:03:46 PM    Exit from process disks in Gpt Driver (id = 8)
13        11/9/2015 6:03:46 PM    LDM: New ProcessDisks(rawLayer, headLayer)
14        11/9/2015 6:03:46 PM    ProcessDisks: One more disk to check
15        11/9/2015 6:03:46 PM    Mark All groups as Root Like Dgs
16        11/9/2015 6:03:46 PM    ------ Volumes Objects ------
17        11/9/2015 6:03:46 PM    LDM initialization complete
18        11/9/2015 6:03:46 PM    Analyzing partition '0-0'...
19        11/9/2015 6:03:47 PM    Analyzing partition '1-1'...
20        11/9/2015 6:03:47 PM    Analyzing partition 'C:'...
21        11/9/2015 6:03:47 PM    Analyzing partition 'Q:'...
22    Information    11/9/2015 6:03:47 PM    Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
23        11/9/2015 6:03:47 PM    Error while opening configuration file .
24        11/9/2015 6:03:47 PM    Error occurred while creating the file.
25    Information    11/9/2015 6:03:47 PM    Operation: backup
26    Information    11/9/2015 6:03:47 PM    Priority changed to Low.
27    True Image    11/9/2015 6:03:47 PM    The specified file does not exist.
28    True Image    11/9/2015 6:03:47 PM    The system cannot find the file specified
29    True Image    11/9/2015 6:13:47 PM    The specified file does not exist: \\10.77.66.50\billing\Entire PC (BILLING)_inc_b14_s21_v1.tib.
30    True Image    11/9/2015 6:13:47 PM    Check whether the source and destination partitions exist.
31    True Image    11/9/2015 6:13:47 PM    Canceled.
32    True Image    11/9/2015 6:13:47 PM    The specified file does not exist.
33    True Image    11/9/2015 6:13:47 PM    The system cannot find the file specified
34        11/9/2015 6:13:47 PM    ServerLRPC::_CloseConnection id=5,248
35        11/9/2015 6:13:47 PM    ServerLRPC::_CloseConnection id=6,192
36        11/9/2015 6:13:47 PM    ServerLRPC::_CloseConnection id=5,248
37        11/9/2015 6:13:47 PM    ServerLRPC::_CloseConnection id=6,192
38    True Image    11/9/2015 6:13:47 PM    Operation has completed with errors.
0 Users found this helpful

1. Each incremental backup contains its own changed data. There is no backup dupliation elsewhere. The data containined in the deleted incrmental  is lost from the backup. The FULL BACKUP _FULL_S1_V1.TIB should still be usable but you may need to manually validated the chain clicking ignore on each error prompt until the validation succeeds.

2. Each task has an option to "Clone settings". You can clone the settings of that task to a new task. After cloning but before use, you will need to

a.  If a task  name correction is needed, then rename the task to a new name. The same task name as befoer SHOULD NOT BE USED. New name should be unique or differ from prior task names. The name of the new tib backup file will be whatever name you create as the new task name for the cloned task.

b.  The new storage target should also be changed such as to a new sub-folder inside the orignal folder.

c.  The backup scheme settings should be changed so that the backup scheme name is "custom", plus the automatic cleanup settings should be enabled to prevent a re-occurrence of the full disk error.  It is not a safe practice to have so many incrementals based on one old full backup. For example, if you wanted to restore the most recent incremental, the program would need to restore each and every preceding incremental before restoring the most recent, so all preceding incrementals must be present (nor deleted) and be disk readable withiout disk errors, in order to have a successful restore.   My preferrred cleanup option is the "Store no more than (n) recent version chains, where (n) is the number of CHAINS (not # of backups) you wish to keep.

3. The bottom line is that you will need to create new backup tasks and start your backup routine again.

4. If you wish to post a screen capture of your storage folder, we might be able to determine what is usable from what is left. At this point, we do not really know what was deleted and what remains.

5. Additional references below.

------------------------------------------------
Custom Backup Scheme Discussion--extract
http://forum.acronis.com/forum/100416

-----------------------------------------------------------
Depending upon the type of backup scheme you wish to create, here is an example of each type.  These can be set up for Disk image, or Partition, or Files-folders backups.  These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.

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.

GH11. Create Custom Full Backup Scheme w/auto cleanup.
...Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..

GH12. Create Custom Incremental Backup Scheme w/auto cleanup.
...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

GH13. Create Custom Differential Backup Scheme w/auto cleanup.
...Keep Full plus 2 Diff per chain. Store/Keep 2 chains. Use whatever number best fits your needs.

GH25. Understanding differences between Incremental and Differential backups for data recovery.

GH64. 71342: 2015 How to save a non-scheduled task.

GH63. 64640: Hints to help prevent issues with your TIB backup files creation.

GH63. 75086: A discussion on how to configure backup schemes.

Later Edit: Display Corrected.

This is all great information, thanks so much!

I wasn't able to use the "clone" operation, since I need encryption (is adding encryption after creating a backup supported in the 2016 version?) so I started anew.  I had a chain limitation previously, but I was misunderstanding what constituted a chain. :)

Another great tip is to keep everything in subdirectories, that helps keep things straight (especially when on a network share).

For my old versions from this broken backup, I'm just keeping fulls, which is what I'm really interested in.  I assume a full is always 100% restorable regardless of naming, existence of a current matching backup profile, etc.

Display links corrected.  I would manually validate each full retained and respond ignore to each error prompt.