2016 Deleting backups and backup versions you no longer need...
I decided to start from scratch : I formatted my external HD and start a all new backup with your recommended settings. I'll keep U posted on the situation. Thanks again for your help Steve
I tried several times to delete a specific backup version using the above approach of booting from the Acronis boot disk. Everything works until I get to step 4. Nothing happens after I right click and select remove. The manual says not to delete files using windows file management. As additional information, the backup files for three machines all running ATI 2017 are stored on a Drobo 5N. I could use some help here.
Steve,
I ran the all new backup (it took 38H !) everything seem OK, I wait for the next schedule backup to see if it's working. Thanks
All,
I'm a ATI 2016 user for over a year. Last week (28 Aug) I accepted an upgrade to Win 10 to Build 1703 (Creator's Edition). This put a lot of data on my eternal drive for keeping incremental disk backups. This pushed me to the capacity limits on the external drive. So, I wanted to delete just the oldest B/U version (of 2 versions) since I need to keep the backup data from the night before I upgraded to WIN10 Build 1703 (the reasons are arcane and not needed for this discussion).
PROBLEM STATEMENT: Following the procedure in the ATI 2016 manual, section 4.4.6, "To delete a specific backup version" (pg #63) cannot be followed.
DETAILS: Step 4 of this section tells the user to right-click the backup version to be deleted. However, when this done nothing happens. The work-around appears to be to highlight the version to be deleted an press Delete on the keyboard. This takes the user to the next screen where a list of backups are expected to be displayed as stated in step 4. In my case none are shown. Then following step 5 by clicking Delete results in the whole PC being locked. The only way to recover is to power-off the computer. No deletions are made.
My concern is that this problem is somehow related to the WIN10 upgrade and that no one will take ownership of this issue.
Request any suggestions as to how to proceed.
Thanking you in advance, USN1Guy
USN1Guy, welcome to these User forums.
I suspect that you are referring to the ATIH 2016 User Guide section:
Deleting backups and backup versions
where a little lower down the page, it states:
To delete a specific backup version:
- Start your computer by using bootable media. Refer to Arranging boot order in BIOS for details.
- In the Recovery section, click Refresh backups. This will update the backup list. If you cannot find the target backup in the list, or the backup is located on removable media, click Browse for backup, and provide the path to the backup.
- Depending on type of the backup, go to the Disk backups or File backups tab.
- Right-click the backup version that you want to delete, and then click Remove. The opened window displays the list of backup versions that will be deleted. See below why this list may contain more than one backup version.
- To confirm the deletion, click Delete.
To be absolutely honest, I have never booted from the bootable media in order to delete any backup files, and doing it in this way does not address the issue of the information stored in the Acronis Database files used by the Windows version of the Acronis application, which will give error messages for each deleted file.
I am sure that this topic has already discussed this topic in some depth and detail, so would request that you read through from the beginning rather than repeating a lot of the same advice.
The key point here is that you can delete backup version chains (i.e. all files sharing the same _Bx_ number in the file names) using Windows Explorer provided that you then run a Validation for the backup task that created those deleted files in order to reconcile the Acronis Database information - taking the Ignore option for each deleted file giving an error popup.
Steve,
After 4 backups OK, the last attempt finished with "Backup failed" Write error !
I don't understand, my DD is 21 months old and I ran a check disk on all my DD in june, everything was fine, no error.
Thanks for your help
Alain
Alain, what was the context of the error message? A write error could mean different things? That the drive was full or that a bad sector was encountered etc?
What is shown in the backup log for when this error was given? Download the MVP Log Viewer from the Community Tools link in my signature if you don't already have it for accessing the logs.
Here is the log:
log uuid=1175526E-19D8-4365-A257-34C78120C767; product=True Image; version=19.0; build=6595; task=F32081AD-A3AE-4CFB-8987-E1D79C47FE4A; task_name=(1)Entire PC (BOSS2010WIN10)
Start= 24/09/2017 22:35:01
id=1; date/time=24/09/2017 22:35:01; message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2; date/time=24/09/2017 22:35:02; message=Operation (1)Entire PC (BOSS2010WIN10) started by schedule.
id=3; date/time=24/09/2017 22:35:06; message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=4; date/time=24/09/2017 22:35:06; message=Operation: Backup
id=5; date/time=24/09/2017 22:35:06; message=Priority changed to Low.
id=6; date/time=24/09/2017 22:35:06; message=Create Backup Archive From: To file: M:\(1)Entire PC (BOSS2010WIN10).tib Compression: Normal
id=7; date/time=24/09/2017 22:35:06; message=Pending operation 172 started: 'Creating partition image'.
id=8; date/time=24/09/2017 22:36:53; message=Writing full version to file: (1)Entire PC (BOSS2010WIN10)_full_b2_s1_v1.tib
id=9; date/time=25/09/2017 01:20:47; message=The quotas are violated.; line_tag=0x1D8EAB676A3F6AEC
Error_Code=AR0ABADsaj9qZ6uOHVRoZSBxdW90YXMgYXJlIHZpb2xhdGVkLgBQYXRoAFdNOlwoMSlFbnRpcmUgUEMgKEJPU1MyMDEwV0lOMTApX2Z1bGxfYjJfczFfdjEudGliACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfbWVzc2FnZV9jYWxsYmFjay5jcHAAJGZ1bmMAQVRydWVJbWFnZTo6QXJjaGl2ZTo6QXJjaGl2ZU1zZ1dyaXRlQ2FsbGJhY2tQcm9jZXNzb3I6OlByb2Nlc3NXcml0ZUNhbGxiYWNrACRsaW5lAE7DBAAAAAAAAAAdAAQAy+Vd+ZYz2QZUaGUgcXVvdGFzIGFyZSB2aW9sYXRlZC4AJG1vZHVsZQBBdGlfZGVtb25fdnNfNjU5NQAkZmlsZQBBazpcNjU5NVxiYWNrdXBcZmlsZV93cml0ZXIuY3BwACRmdW5jAEFgYW5vbnltb3VzLW5hbWVzcGFjZSc6OkZyZWVTcGFjZUNoZWNrZXI6OkNoZWNrRnJlZVNwYWNlACRsaW5lAE5vAAAAAAAAAAA=
id=10; date/time=25/09/2017 01:20:47; message=The quotas are violated.; line_tag=0x6D93396F95DE5CB; hide=1
id=11; date/time=25/09/2017 01:20:49; message=Write error; line_tag=0x65B5EB7011094700
Error_Code=AfYBAQAARwkRcOu1ZVdyaXRlIGVycm9yACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvY2Vzc29yXGRpc2thZG1cZGFfY29tbWl0LmNwcAAkZnVuYwBBRGFQcm9jZXNzb3I6OkNvbW1pdEltcGw6Ok9uRGFFcnJvcgAkbGluZQBOWQEAAAAAAAAABAAHANjEy4jw4S2dV3JpdGUgZXJyb3IAJG1vZHVsZQBBdGlfZGVtb25fdnNfNjU5NQAkZmlsZQBBazpcNjU5NVxyZXNpemVyXGJhY2t1cFxzdHJlYW1fd3JhcHBlcnMuY3BwACRmdW5jAEFyZXNpemVyOjpTdHJlYW1XcmFwcGVyOjpXcml0ZQAkbGluZQBOQAAAAAAAAAAAHQAEAOxqP2pnq44dVGhlIHF1b3RhcyBhcmUgdmlvbGF0ZWQuAFBhdGgAV006XCgxKUVudGlyZSBQQyAoQk9TUzIwMTBXSU4xMClfZnVsbF9iMl9zMV92MS50aWIAJG1vZHVsZQBBdGlfZGVtb25fdnNfNjU5NQAkZmlsZQBBazpcNjU5NVxwcm9kdWN0c1xpbWFnZXJcYXJjaGl2ZVxpbXBsXG9wZXJhdGlvbnNcYXJjaGl2ZV9tZXNzYWdlX2NhbGxiYWNrLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpBcmNoaXZlTXNnV3JpdGVDYWxsYmFja1Byb2Nlc3Nvcjo6UHJvY2Vzc1dyaXRlQ2FsbGJhY2sAJGxpbmUATsMEAAAAAAAAAB0ABADL5V35ljPZBlRoZSBxdW90YXMgYXJlIHZpb2xhdGVkLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XGJhY2t1cFxmaWxlX3dyaXRlci5jcHAAJGZ1bmMAQWBhbm9ueW1vdXMtbmFtZXNwYWNlJzo6RnJlZVNwYWNlQ2hlY2tlcjo6Q2hlY2tGcmVlU3BhY2UAJGxpbmUATm8AAAAAAAAAAA==
id=12; date/time=25/09/2017 01:20:49; message=Write error; line_tag=0x9D2DE1F088CBC4D8; hide=1
id=13; date/time=25/09/2017 01:20:49; message=The quotas are violated.; line_tag=0x1D8EAB676A3F6AEC; hide=1
id=14; date/time=25/09/2017 01:20:49; message=The quotas are violated.; line_tag=0x6D93396F95DE5CB; hide=1
id=15; date/time=25/09/2017 01:20:49; message=Write error; line_tag=0x91BD40306B6C5083
Error_Code=AQQABwCDUGxrMEC9kVdyaXRlIGVycm9yACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVcaW1wbFxvcGVyYXRpb25zXGFyY2hpdmVfb3BlcmF0aW9uLmNwcAAkZnVuYwBBVHJ1ZUltYWdlOjpBcmNoaXZlOjpBcmNoaXZlT3BlcmF0aW9uOjpFeGVjdXRlACRsaW5lAE5tAAAAAAAAAAAEAAcA2MTLiPDhLZ1Xcml0ZSBlcnJvcgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHJlc2l6ZXJcYmFja3VwXHN0cmVhbV93cmFwcGVycy5jcHAAJGZ1bmMAQXJlc2l6ZXI6OlN0cmVhbVdyYXBwZXI6OldyaXRlACRsaW5lAE5AAAAAAAAAAAAdAAQA7Go/amerjh1UaGUgcXVvdGFzIGFyZSB2aW9sYXRlZC4AUGF0aABXTTpcKDEpRW50aXJlIFBDIChCT1NTMjAxMFdJTjEwKV9mdWxsX2IyX3MxX3YxLnRpYgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHByb2R1Y3RzXGltYWdlclxhcmNoaXZlXGltcGxcb3BlcmF0aW9uc1xhcmNoaXZlX21lc3NhZ2VfY2FsbGJhY2suY3BwACRmdW5jAEFUcnVlSW1hZ2U6OkFyY2hpdmU6OkFyY2hpdmVNc2dXcml0ZUNhbGxiYWNrUHJvY2Vzc29yOjpQcm9jZXNzV3JpdGVDYWxsYmFjawAkbGluZQBOwwQAAAAAAAAAHQAEAMvlXfmWM9kGVGhlIHF1b3RhcyBhcmUgdmlvbGF0ZWQuACRtb2R1bGUAQXRpX2RlbW9uX3ZzXzY1OTUAJGZpbGUAQWs6XDY1OTVcYmFja3VwXGZpbGVfd3JpdGVyLmNwcAAkZnVuYwBBYGFub255bW91cy1uYW1lc3BhY2UnOjpGcmVlU3BhY2VDaGVja2VyOjpDaGVja0ZyZWVTcGFjZQAkbGluZQBObwAAAAAAAAAA
id=16; date/time=25/09/2017 01:20:49; message=Write error; line_tag=0x9D2DE1F088CBC4D8; hide=1
id=17; date/time=25/09/2017 01:20:49; message=The quotas are violated.; line_tag=0x1D8EAB676A3F6AEC; hide=1
id=18; date/time=25/09/2017 01:20:49; message=The quotas are violated.; line_tag=0x6D93396F95DE5CB; hide=1
id=19; date/time=25/09/2017 01:20:50; message=Operation has completed with errors.; line_tag=0x9F2C53C72E8BCE7B
Error_Code=AQUAPAF7zosux1Msn09wZXJhdGlvbiBoYXMgY29tcGxldGVkIHdpdGggZXJyb3JzLgAkbW9kdWxlAEF0aV9kZW1vbl92c182NTk1ACRmaWxlAEFrOlw2NTk1XHByb2R1Y3RzXGltYWdlclxkZW1vblxtYWluLmNwcAAkZnVuYwBBbWFpbgAkbGluZQBOhQIAAAAAAAAA
Start= 24/09/2017 22:35:01
Finish= 25/09/2017 01:20:50
Total Time= 02:45:49
Thanks for your help,
Alain
Alain, the key message showing in the log is "The quotas are violated" which is normally an indication that there is insufficient free space on the target drive, hence the backup file cannot be written to the drive.
See forum topics:
Steve,
a month ago, I used your advice to choose your settings, I started a complete new backup from scratch on my formatted 4Tb DD, and now it runs out of space AGAIN ! In that past month I did not save any new picture, document, file, so I can't understand why ATI, stops backup with 800GB of free space on my DD.
Do we need a Phd to use ATI?
Alain, no-one should need a Phd to use this or any similar software - I certainly don't have one!
I guess that we may be going round the same ground again if we are repeating history here with this 4TB drive.
Your log shows that you are doing an Entire PC backup and one of your earlier posts said this took around 38 hours to complete, which suggests a significant size for the backup image.
Returning to basics, exactly what Backup Scheme settings are you using? How many full / incremental images are being kept before automatic cleanup is intended to run?
What are the actual file sizes of your backups on the 4TB drive?
Steve, I changed the settings according to your recommendations. I would like to save only my main DD splitted in 2 (C: and F:) not my entire PC which has 3 DD. May be I just don't know how to do it. There is 820GB free out of 3,6TB on my external DD. Which settings to choose to do a weekly incremental backup only, with no fuss? Thanks
Alain, OK, if you are only wanting to save just 1 drive on a multi-drive system, i.e. C: and F: for drive 1, then in your Backup task, Source selection panel, instead of choosing 'Entire PC' which is the default (and which will include your other 2 drives too), you need to click on the Source panel to reveal further options below this, one of which is for Disks & Partitions.
Click on Disks & Partitions, then choose only the 1 drive that has your two partitions (C: & F:) plus include the required hidden system partitions on that drive, but clicking on the drive should do this automatically for you.
Once you have selected just the 1 drive, not the Entire PC with 3 drives, then this should make your backup image file a whole lot smaller.
See the PDF document I shared in the MVP User Tools and Tutorials web pages which was written to show how to make a new backup using ATIH 2016.
Steve,
Thank you, I followed your tutorial and save only my main DD (C:, F:)
I hope that now I'll be OK with my incremental backup.
Thanks for your precious help and expertise
What kind of effing insane STUPIDITY to NOT ALLOW removing old backups without BOOTING FROM A SPECIAL DISK???? How dumb could this possibly be? Here am wasting a few hours, manually deleting and trying to follow the workarounds. I was very happy with the newest Acronis.... until this insanity. HOW COULD YOU POSSIBLY NOT ALLOW OLD BACKUPS TO BE REMOVED IN A SIMPLE FASHION. Utterly ridiculous. Am I getting my point across? ACRONIS, will you please answer? Why can't you include a simple, "REMOVE OLD BACKUP/TIB FILES"??? Unless this gets fixed in the next few months, I will switch to some other... ANY other.... backup system. What a totally crap problem... and so easily fixed.
kw, welcome to these User Forums.
I have never needed to boot from the Acronis Rescue Media (CD/DVD or USB stick) in order to remove / delete old backup .tib files, so this is most definitely not the only method of doing so.
There is nothing to fix here but if you want Acronis to fix something, then you need to open a Support Case directly with them as it is most unlikely that 'shouting' here in these user forums will achieve any such action. This will also depend on whether you are using a currently supported version of Acronis True Image such as 2017 or 2018, as these are the only 2 product versions where support will accept such issues and consider producing fixes. All older versions are no longer supported for fixes.
To get back to the core issue raised by your post above.
You can delete any Acronis .tib files using Windows Explorer provided that you understand the consequences of doing so!
If you have ATI 2018 or 2017 New Generation with Acronis Active Protection active, then you need to disable this before attempting to delete .tib files as these are protected by AAP and such actions would be considered to be malware attempts.
If you are deleting .tib files that are associated with current backup tasks shown in the main ATI GUI, then you will need to run a Validation for the tasks after deleting files via Explorer. Validation will produce an error popup message for each deleted / missing .tib file that you will need to take the Ignore option for. This is because ATI tracks all of these files in an internal Database and this will need to be reconciled with the actual status of those files still present.
An alternative approach would be to use the 'Clone settings' option for the backup task in the GUI, then remove the original task you cloned from, which would remove all information from the Database for the task & its files, which would allow you to do what you want with the .tib files. You could then rename the cloned task back to the same name and start afresh with a new full backup image.
Finally, the recommended method of managing backup .tib files is to use the 'Automatic cleanup' options on the Backup Scheme options page for your backup task, where this will automatically delete older files according to the rules that you configure.
Steve,
With your advices, my backup is running now just fine. Hope it stays that way!
Thanks for your wise help.
Hi Steve Smith,
Thank you for your level-headed reply to my obviously very frustrated complaint and cry for help!
First things first... it does seem obvious that I'm not the only one suffering from this issue, as the thread has dozens of similar angry comments.. ranging from mildly frustrated to full blown anger.
Perhaps the problem is with Acronis' documentation. It would be great if the docs popped up YOUR reply, instead of the standard one in Acronis that does not adequately address the issue of removing old backups. I do hope that someone from Acronis is scanning this blog.
Also, in response to your question, I do have a valid version of Acronis... True Image 2017. I'll leave it to others with more time to make suggestions directly to Acronis via the change request route.
But in any case, thanks again for your considered reply. I'm going to implement right now.
Best,
KW
In reply to Hi Steve Smith,… by truwrikodrorow…
As an addendum to my reply to Steve Smith,
Again, thanks for your reply and suggestion.
However... if anyone from Acronis is reading this... why not just have a feature that allows for the simple removal of old backups? The "Validate" method that Steve mentions is extremely time consuming. I'm now waiting for a 2-hour validation because I manually removed a few old TIB files. The older versions of Acronis allowed deleting old TIB files. Why was the feature removed? Was there a reason to remove it? It's easy enough to add new TIBs by starting a new backup.
I do not understand the reasoning.
KW
KW, first thank you for your further comments on this issue.
I understand some of your frustration with how the product works but at the heart of this issue is the way in which Acronis have changed the design of the application and use the Database to manage and track backup file versions - something that we are unlikely to change in the short term without registering a lot of user feedback about this to Acronis.
One of the other issues here perhaps is that you are reading the documentation - something that is a little unusual if I am honest! Many users have never opened the help documentation and get into all sorts of problems because of not doing so. Others only refer to it when they can't figure things out themselves due to a lack of intuitive design etc.
On the validation topic - one thing that you can do, once all the pop-up error messages have been issued for any missing / deleted files, is simply to cancel the validation at that point, as it has done what was needed in reconciling the database information about files. The remainder of the process is all about recalculating the checksum for all the backup files to compare this with the values stored within those files - this to confirm the files are unchanged from when they were first created.
In reply to KW, first thank you for your… by truwrikodrorow…
Thanks Steve.
Your recommended manual steps really so spell out a method that Acronis could automate:
1) Delete TIB files that are no longer needed (using a user interface similar to previous versions).
2) Update metadata in the DB to reflect the fact that certain backups are gone.
3) No need to perform check-sums on remaining backups, since they have not been touched.
I'm very curious.... what's your opinion on why Acronis hasn't made this procedure available? It's just so simple. Maybe there's a reason, I just can't figure it out. Sure, the metadata is stored in a DB. But certainly the program has access to the database and the fields are apparently easy to update... that's why your "work around" works.
Maybe they'll change it. I appreciate programs that don't require work-arounds, especially backup programs!
Thanks, KW
Hi Steve,
first Happy New year!
I come back again for your help: since 10/03/2017 everything was working fine with your recommandations, then on 12/17/2017 "backup failed, disk is full"! remember it's a 4To HD external for a backup of a 2To HD! Pls find attached my options screen shot, I don't know what to do now, I thougth the problem was solve for good. Thanks.
Dallas75, a Happy New Year to you too!
Your backup settings image show that you are keeping the following:
The original, first backup version - 1 x Full backup plus 3 x Incrementals
Two further backup versions - 2 x Full backups plus 6 x Incrementals
One more Full backup as required before the oldest (not first) backup version chain is deleted to keep with your automatic cleanup rules of "Store no more than 3 recent version chains".
So, the next question here is to ask, what are the sizes of the above files? You may need to adjust your cleanup settings to reduce what you keep from 3 to 2 plus also consider if you really need to "Keep the first version of the backup", i.e. keeping the oldest backup and deleting the more recent oldest instead?
You need to set the options to match what it is possible to fit on your 4TB destination drive.
Thanks, Steve,
Do you think my new settings (attached pic) will keep me safe for some times to come?
The changed settings should help but difficult to be certain without knowing what your actual backup version file sizes are. I suspect that you could keep to the number of incrementals that you had previously or even increase that to say 5 if only storing the one version chain, so that you are not having to create a new full backup as often as after just 2 incremental backups.
Thanks, I'll try it and keep you posted
Hi Steve,
I feel very unsecure with my Acronis backup, here the last problem which occured last night. Aconis was running alone, during the night... no space pb on the external DD: 2.5GB free!
1 True Image 28/01/2018 23:06:12 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 True Image 28/01/2018 23:06:12 Operation BOSS C,F started manually.
3 True Image 28/01/2018 23:06:15 Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
4 True Image 28/01/2018 23:06:15 Operation: Backup
5 True Image 28/01/2018 23:06:15 Priority changed to Low.
6 True Image 28/01/2018 23:06:15 Cannot access the path: M:\BOSS C,F_full_b5_s1_v1.tib
7 True Image 28/01/2018 23:06:15 The initial full backup version is not accessible at the moment.
8 True Image 28/01/2018 23:06:15 The specified file path does not exist.
9 True Image 28/01/2018 23:06:15 The system cannot find the path specified
10 True Image 28/01/2018 23:06:15 Create Backup Archive From: Disk 1 To file: "N:\BOSS C,F.tib" Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\alain\AppData\Local\Temp, C:\Users\Administrator.BOSS2010WIN10\AppData\Local\Temp, C:\Users\alain\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Administrator.BOSS2010WIN10\AppData\Local\Microsoft\Windows\INetCache, C:\Users\alain\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\alain\AppData\Local\Opera Software, C:\Users\alain\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\alain\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\alain\AppData\Local\Opera Software, C:\Users\alain\AppData\Local\Mozilla\Firefox\Profiles, C:\WINDOWS\CSC
11 True Image 28/01/2018 23:06:15 Pending operation 172 started: 'Creating partition image'.
12 True Image 28/01/2018 23:06:50 Writing full version to file: BOSS C,F_full_b5_s1_v1-2.tib
13 True Image 28/01/2018 23:06:50 Writing full version to file: BOSS C,F_full_b5_s1_v1-2.tib
14 True Image 28/01/2018 23:06:52 Pending operation 172 started: 'Creating partition image'.
15 True Image 29/01/2018 00:29:20 Pending operation 172 started: 'Creating partition image'.
16 True Image 29/01/2018 00:30:11 Pending operation 172 started: 'Creating partition image'.
17 True Image 29/01/2018 02:03:56 Pending operation 172 started: 'Creating partition image'.
18 True Image 29/01/2018 02:03:56 The following backups have been successfully created: "N:\BOSS C,F_full_b5_s1_v1-2.tib"
19 True Image 29/01/2018 02:03:57 Consolidate Backup Archive Location: "N:\BOSS C,F_full_b5_s1_v1-2.tib" Destination: "N:\BOSS C,F_full_b5_s1_v1-2_89D7CBCD-08EC-4CCE-BC7A-42C013F12669.tib"
20 True Image 29/01/2018 02:03:57 Consolidate Backup Archive Location: "N:\BOSS C,F_full_b5_s1_v1-2.tib" Destination: "N:\BOSS C,F_full_b5_s1_v1-2_89D7CBCD-08EC-4CCE-BC7A-42C013F12669.tib"
21 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
22 True Image 29/01/2018 02:03:57 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.
23 True Image 29/01/2018 02:03:57
24 True Image 29/01/2018 02:03:57 The operation is not supported.
25 True Image 29/01/2018 02:03:57 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.
26 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
27 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
28 True Image 29/01/2018 02:03:57 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.
29 True Image 29/01/2018 02:03:57
30 True Image 29/01/2018 02:03:57 The operation is not supported.
31 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
32 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
33 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
34 True Image 29/01/2018 02:03:57 Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications.
35 True Image 29/01/2018 02:03:57 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.
36 True Image 29/01/2018 02:03:57
37 True Image 29/01/2018 02:03:57 The operation is not supported.
38 True Image 29/01/2018 02:03:57 Operation has completed with errors.
Thanks for your help
Alain
Alain, the task log is showing a change of drive letter has occurred at some point here:
6 True Image 28/01/2018 23:06:15 Cannot access the path: M:\BOSS C,F_full_b5_s1_v1.tib
7 True Image 28/01/2018 23:06:15 The initial full backup version is not accessible at the moment.
8 True Image 28/01/2018 23:06:15 The specified file path does not exist.
9 True Image 28/01/2018 23:06:15 The system cannot find the path specified
10 True Image 28/01/2018 23:06:15 Create Backup Archive From: Disk 1 To file: "N:\BOSS C,F.tib"
This change of drive letter from M: to N: (or reverse) then led to the further errors being reported in the log.
Steve,
I did not change my USB port's letter, I just saw that it was attempting to backup on M (which was wrong, it fails) then I change the setting to come back to my physical backup DD which was changed to N, then I restart my backup, then it's sending me this new problem. The physical DD on which reside the backup is the same, it should see the previous backup files. Why is it talking about " Failed to exclusively access a backup file during consolidation. Make sure the file is not opened in other applications." it doesn't recognize its own backup files? The physical DD did not move, it stayed on the same USB port, for an unknown reason the system changed the port letter, which I adjusted in order for Acronis to find the right DD... This software is a nightmare, I'm doing manual backups to sleep at night!!
Alain, drive letter changes can occur for a number of reasons, including having a USB stick plugged in which takes the normal letter used etc.
ATI records drive letters in its internal database, so at some time a backup was done when this drive was using M: hence the initial error.
The best way around this is to use Windows Disk Management and allocate another unused drive letter from lower down the alphabet, i.e. drive S: etc.
Then use the 'Clone settings' option for your backup task to create a duplicate task - this will have the same name prefixed by (1). Remove the original backup settings (not the files).
The edit the duplicate task, remove the (1) prefix and select the new destination drive letter (S:).
At this point the new task will clash with the existing backup files because it will want to start again from _b1_ so you should either name the task to be slightly different in name, or else point it to a new folder on the destination drive. It will start with a new Full backup.
The point about using a lower drive letter is that this should not be changed accidentally again unless you have got a bucket full of USB ports and sticks to plug in!