Acronis 2020 misplaced my backup?
OK.. this is a Bizarre one... my Acronis backup has just "randomly" decided to put its backup of my C drive... on the C drive!!!! Which is clearly a very stupid thing to do (and would normally block you from doing that?)
Looking at settings it is still showing the correct destination (my NAS drive)
And if I look at "activity tab.. it shows
So note.. the update on 17th Jan was a full.... so the update on 24th should have been an incremental.. but for some reason it did a full one.. and put it on the C drive.
You can tell it was not moved to the C drive after.. as the backup time was just 7 mins... when you can see.. a full backup to the NAS (on 17th Jan) takes about 36 mins.
I THINK the NAS would have been online all the time.. (not aware of any disruption, its on 24/7) and even if it had a blip... True image should not have done what it did? should have failed and alerted me (via the app is sys tray?)
The log file shows nothing untoward!!!
So anyone have any ideas WTH happend here?
Thanks in advance for any insight
Cheers :)

- Log in to post comments

Yoji, the log viewer tool you are using does not show all the new logs found in ATI 2020 or 2021 so you are not seeing log information that may tell a fuller story here!
There is a new MVP Assistant log viewer tool that has now been made available by Acronis via the Community Tools page..
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backup using same) then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
- Log in to post comments

HHmmm.. going to need some help here..
Attached are the "Backup worker" files... there are 4, identifying by date they are
17th Jan... the sucessful backup from 17th Jan .. shows no errors
24th Jan... the problem backup .. it shows errors trying to open the tibx on the NAS... but later in log seems have no problems
30th Jan at 0:33... shows it identifying and accessing/deleting all the old backups on NAS with no problems
30th Jan at 0:41 .... shows it completing the new backup... it seems to again report issues reading the tibx file (which is correct.. as it was brand new.. so no existing tibx file) and went on to create everything fine on the NAS.
The log of 24th does seem to say the initial error was as it trying to find the tibx on the C drive (which would correctly be an error... as the tibx would be on the NAS.. but why look for it on C drive?).. but then reports error as it tries to find it on the NAS (which it should have been able to do)..
Perhaps someone can review and enlighten me/us?
Attachment | Size |
---|---|
567361-211658.zip | 10.45 KB |
- Log in to post comments

Yoji, thanks for the Backup Worker logs, these do not tell us why ATI decided to write the backup file on your C: drive other than the single line reference on the 24th Jan.
24/01/2021 02:00:07:595 PM opening archive path="\\?\UNC\READYNAS\Backup\Justin\Justin C Drive\/\Justin C drive.tibx" in readonly mode;
24/01/2021 02:00:07:610 PM failed to open '\\?\C:\Justin C drive.tibx' (win_err=-2);
24/01/2021 02:00:07:610 PM failed to open "\\?\UNC\READYNAS\Backup\Justin\Justin C Drive\/\Justin C drive.tibx" (pcs_err=-8);
24/01/2021 02:00:07:610 PM failed to open archive path="\\?\UNC\READYNAS\Backup\Justin\Justin C Drive\/\Justin C drive.tibx" err=-5022 (File not found);
24/01/2021 02:00:07:610 PM message=unable to open archive file (err -5022);
The only guess I can make is that your drive mapping to the ReadyNas had broken down in some way on this occasion leading to the unwanted effect of the file being created on C:\
- Log in to post comments

Exactly.. the first line you show shows it trying to open the correct file in the correct location on the NAS... but then reports that it cant open it on my C drive!!!!
Thats a bit strange...
But basically... if it cant find the backup where it thinks it should be (i.e. where its configuration tell it where it should be) ..or if it fails to get access to the location it configured to put it... it should not really just failover to putting it on the C drive and not report it as an error...
On the face of it... What it has done here is bad behaviour..
Thanks for your reply.. lets see if anyone else can add anything (or has questions.. I will try and answer)
Cheers :)
- Log in to post comments

Just a quick post to say that it has done it again!!!
I just noticed that Sundays weekly backup was again "Randomly" put in the root of my C drive. Same as before... no warnings or anything.. reports just say backup completed sucessfully... and if I go to the backup section and tell it to open backup location, it again opens up the correct location on my NAS drive.
Same story as before... I NEVER have issues accessing the NAS.. and yet its the C drive again (when I have 2 other backups going to the NAS.. and neither of those have ever experienced this behaviour)
In exasperation I just nuked the old backup in its entireity and recreated it from scratch...
If it happens again, I will have to do a deep dive and open a support ticket... though it on TI 2020.. so I guess they will not be very interested.
Anyway - just wanted to record it again in this thread.,... no-one else seem to have jumped on this with a "me to", so what the hell is happening to make Just me suffer? :(
Cheers
- Log in to post comments

I have the same problem as described by Yoji and I am impressed that it happened almost at the same date...
The log files show the same situation as posted above:
12.07.2021 09:28:41:864 +02:00 23216 I00000000: >>> --id=10001 --action=browse --agent="Acronis True Image 2020 24.7.1.38530 Win" --archive="smb://NAS_NAME/backups/FOLDER/\\PC_NAMEx.tibx" --archive-password=* --ar-loc-username="USERNAME" --ar-loc-password=*
12.07.2021 09:28:42:255 +02:00 10468 I00000000: type=log; level=inf; message=ar#1: opening archive path="\\?\UNC\NAS_NAME\backups\FOLDERNAME\/\PC_NAMEx.tibx" in readonly mode;
12.07.2021 09:28:42:427 +02:00 10468 I00000000: type=log; level=err; message=io: failed to open '\\?\C:\PC_NAMEx.tibx' (win_err=-2);
12.07.2021 09:28:42:427 +02:00 10468 I00000000: type=log; level=err; message=io#1: failed to open "\\?\UNC\NAS_NAME\backups\FOLDER\/\PC_NAMEx.tibx" (pcs_err=-8);
12.07.2021 09:28:42:427 +02:00 10468 I00000000: type=log; level=err; message=ar#1: failed to open archive path="\\?\UNC\NAS_NAME\backups\FOLDER\/\PC_NAMEx.tibx" mode=readonly uuid=00000000000000000000000000000000, err=-5022 (File not found);
12.07.2021 09:28:42:427 +02:00 10468 I00000000: type=log; level=err; message=unable to open archive file (err -5022);
At 12.07.2021 09:28:42:255 the "normal" backup-file is accessed in readonly mode as usual. No error is mentioned
At 12.07.2021 09:28:42:427 it fails to open the backup-file on C:\ which fails since it hasn't been created yet. I looked at previous log-files and at no point in the past has the folder C:\ been mentioned. It comes completey out of the blue.
At around 10:00 Acronis True Image shows a succesfull backup which now is located at C:\PC_NAMEx.tibx. I have started further backups an hour later and from now on every changes are written to C:\PC_NAMEx.tibx.
Since there is no warning whatsoever, this is a big problem. Does anybody know how to handle the problem
Thanks very much
PS: I tried to contact the support team but when I try to enter the serial number it says that the number has already been activated. But it doesn't show in my account which I am also logged in in the Acronis True Image software on my pc. Is there a way to re-activate the serial number in order to contact the support team?
- Log in to post comments

Peter, with the support request, are you logging in to your Acronis Account and does it show a version of ATI. Even it it does not, click on the Support icon bottom left, then select the appropriate category - in the case Technical Assistance.
One gotcha - if you are using ATI 2020 (you have posted in ATI 2020 forum) it is out of support. If you have ATI 2021 it will be OK.
Ian
- Log in to post comments

Thanks, Ian, for the comment. Then, it seems to be irrelevant whether I can activate the code or not. Beside the end of the support for ATI 2020, there should be an interest for Acronis to address an error which compromises a backup strategy without notifying the user. I don't know if staff members read the threads but I hope so. Anyways, maybe there is someone who has an idea as to why this error occurs. I would be very grateful for that.
- Log in to post comments

Thanks very much
- Log in to post comments

You can use the in app feedback to notify Acronis of the problem.
- Log in to post comments