Can't save backup file location - "Specified file does not exist" event code 0x0040011+0x0000FF0+0x80070002
Hi,
Anyone have a problem saving a destination when setting up a disk backup?
I go to set the destination to a particular disk and folder, set the filename to to something like "@date@_backup.tib" and save.
I get an error "The specified file does not exist"
...well yes, it doesn't exist, it is supposed to be created when the backup runs.
What is causing this? I tried deleting the whole backup task and re-creating it and that didn't help. I have other backup tasks setup the same way that are fine.
I have Home 2011 - Build 6696 - Update 1
Any ideas?
- Se connecter pour poster des commentaires
Hi Sandy/Grover...
Yes, I have the very same error that you do.
I don't on the other hand, have issues with a daily incremental backup using default options.
My stats are:
Windows 7 Home Premium, 64bit SP1
Acronis True Image Home 2011, Update 1, build 6696
I too need an answer to this as I can't backup my C:\drive until this is resolved.
Thanks..
Simon
- Se connecter pour poster des commentaires
Anyone?
Seems I have to pay more money to Acronis to open a ticket or move to another product.
Not happy or impressed.
:(
- Se connecter pour poster des commentaires
You can get this error if ATI cannot access the particular folder where you wan to save the backup.
Try another folder, maybe even on another disk to verify this is the case or not.
If it is not, try to move any existing TIB to another folder, then delete your backup task. ATI will complain it couldn't delete all the files, insist until the backup is deleted or ATI crashes (it will, but it is not an issue).
Then recreate your task from scratch.
BTW, try to avoid using the @date@ and @time@ tags. They can create problems when you edit backup tasks, or when you use the Acronis Secure Zone, or when you move your backup, etc.
I also recommend not to change the task name to a name different from the file name. So choose a simple TIB file name like "FullDisk_Backup", and keep "FullDisk_Backup" for the task name.
All these precautions reduce the risk of database corruption.
- Se connecter pour poster des commentaires
Using ATIH 2011 vs 6696
Win 7 64/32
OS Name Microsoft Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601
System Manufacturer Alienware
System Model M17x
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz, 1730 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Alienware A05, 23/04/2010
SMBIOS Version 2.6
Hardware Abstraction Layer Version = "6.1.7601.17514"
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.99 GB
Available Physical Memory 3.68 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 12.0 GB
Page File Space 7.99 GB
Page File C:\pagefile.sys
I got the same error message for the first time today when I tried to create a new back up.
I chose to ignor the message and try to back up my system anyway. It is in the process of doing so as I type so I do not know yet if that worked or not. It does appear to be going to the correct location.
However, the reason I was creating a new back up task is because for some reason I have started to have problems backing up. After a couple of hours, the system back up cancels itself out (time delay on my responding to error) saying there is not enough room (running out of space)
I am backing up to a WD external HD. There is more than 2x the amount of space (930 gb) required for my back up files. There is nothing else on this HD.
My backup is approx 410 gb.
Not only that, I do have the option to "delete oldest backup if not enough space" option chosen which never seemed to work even when I was doing incremental backups. Hence, the reason I have chosen to do full back ups deleting the previous one all the time.
I have had to start manually deleting the old backup before starting the new back up (which makes me nervous).
Would appreciate any help I can get to resolve this issue.
- Se connecter pour poster des commentaires
Hi Kathy...
You now have the exact same issue as me down to the same machine etc.
Thanks for submitting all the details.
Simon
- Se connecter pour poster des commentaires
Hi Pat...
ATI can access the folder as I am able to browse to the backup location and see/choose previous backup files.
As Kathy stated, the backup starts and runs with no issues for a couple of hours before stopping with the error. I am sure that ATI is writing to the disk up until this time.
I created my backups as per your instructions using simple names and avoiding the @date@ and @time@ tags to no avail.
I will delete everything and start from scratch to test your other suggestion.
Thanks
Simon
- Se connecter pour poster des commentaires
Hi Simon
Thank you for your reply.
Had a few more "oops" before i was finally able to save a system backup. I don't know if I will run into the same problem again or not :(
Oh and BTW... I agree with you, the files were being backed up because I could see it happening and in the right folder....then Phoof! gone :)
This is what I did: (according to instructions found earlier on this string)
Deleted the old backup task. Had to keep right clicking and repeat the delete until the task was finally gone and program crashed.
Started right from scratch with wizard doing system back up....left all the names etc as is.
wooooowhooooo....success !!! for now anyway.
I do hope ATI is working on a solution to these issues.....not impressed with the program anymore and will not renew unless the problems are corrected.
Best of luck to you
- Se connecter pour poster des commentaires
Thanks Kathy...
Hi Pat/all...
I deleted the job as suggested and have performed one successful backup just moments ago. Nearly four hours to complete but my external disk is only connected at USB 2.0 so my data throughput is low.
I will let you know how the next backup goes (Friday April 29) to see if this has resolved the issue.
Cheers.
Simon
- Se connecter pour poster des commentaires
Hi...
I should have noted that yesterdays successful backup time of 4 hours included validation of the backup, so that is reasonable.
Cheers
Simon
- Se connecter pour poster des commentaires