Drive C Empty in TIB (Part 2)
There are two other, older posts, but do not want to clutter them with my specific situation. Hopefully Steve Smith or others can help. I installed Acronis 2019 v14690 two days ago on my new Dell XPS. I set up two separate jobs and ran them back-to-back.
One for C:, a 500gb M.2 SSD, single instance backup. All other settings were untouched. This one worked, and I can see the files in Explorer.
One for E, a SATA 4TB (yes 4TB) Samsung SSD. Again, single instance, no other setting changes . This shows files are empty.
Both have the what would be expected for a file size, so the data is there.
Per another topic thread, I tried to clear cache at %userprofile%\appdata\Local\VirtualStore\ProgramData\Acronis\TrueImageHome\Database, but the only folder below VirtualStore was "Windows", so nothing available to clear.
I've attached what the Files look like in Explorer. (1)
In Acronis Recovery, the C: Backup shows normal tree structure. (2)
In Acronis Recovery, the E: Backup shows no tree structure. (3).
I would appreciate help, as I am vulnerable if I need to recover even in Acronis, much less access via Explorer. Help!
[Moved the topic to Acronis True Image 2019 forum]
I've attached what the Files look like in Explorer. (1)
In Acronis Recovery, the C: Backup shows normal tree structure. (2)
In Acronis Recovery, the E: Backup shows no tree structure. (3).
Bruce, sorry but no images / files found for this topic per your update above.
I've added the images.
Also, I have already run the repair cycle/operation.
Bruce, thanks for posting the images - this does seem strange!
Just to confirm, the E Data backup has only been run the once to create the Full backup file shown in your first image?
The only time I have seen this type of issue has been where there has been no data to show for the selected Recovery point, i.e. 'Yesterday at 8:17 PM' shown in image 3.
Have you checked the Recovery point drop-down to see if any other times are shown? My reason for asking is seeing the difference in times shown in image 1 (5:20 AM) and image 3 (8:17 PM) which makes me wonder if a subsequent incremental or differential backup has run but not found any changes?
The times shown for your C backup file & Recovery panel point are much closer (1:40 PM and 1:21 PM on 08/03/2019).
What happens if you double click the .tib file and try to navigate the content in Windows file explorer?
What happens if you turn on show hidden files and folders in windows explorer and then try this in Acronis or by double clicking the .tib file in explorer?
What is the partition type of this other drive? NTFS, FAT32, extfat or something else?
Some of these answers are repeats from previous entries. I've added two more attachments ((3) and (4))
Double clicking Explorer yields Attachment (4) for C drive backup., Attachment (5) for E drive backup.
The Acronis views are Attachment (2) and (3)
The f: drive is where the acronis backups reside
All to-date work has the hidden files *and* system drive folders/files allowed.
All three drives are NTFS.
I'd definitely open a support case. Never seen this behavior before. Only thing that comes to mind is encryption active on the disk when backed up, but really doesn't seem likely, especially if the original drive data is accessible for n Windows file explorer.
If you have an extra disk, I'd recommend attempting a disk recovery to it to see what the results end up being - at least to see if that is a success or not. Of course, even if it is, we would want this behavior identified and if need be, fixed. But, if it receivers as is, at least you know the backup is actually good.
All:
Thanks for your ideas. If you have any other ideas, please post. I'm going to try a few more wrinkles with other drives, etc. In the meantime, I'll submit a ticket. I think referencing this Posting # would be most efficient, but I'll probably cut and paste the thread and attachments just to bundle it up for Support all in one place. If a fix or solution is found, I'll post it to this discussion.
Again, Thanks!!
Best of luck, Bruce. If there is an answer to this strange behavior, looking forward to finding out the cause and hopefully a fix too!