Validate but not Mount on RMB?
I find Acronis 2019 very nice (backup cleanup seems like an excellent solution to some stuff I've been grumbling about for some time), but, why do RMB-ing on a backup sometimes give a Validate option, but not Mount? I never saw this behavior with 2018, and note that I can still rummage through such backups with Search Files, but mounting is still more convenient. Have other people noticed this, or understand what is going on?
Yes, thanks; RMB=right mouse button; your answer makes sense but can't be the whole story, since I have a backup made with ATI 2018 (or maybe earlier) that shows 'mount' under 2018 but only validate (on a different machine) with 2019. And believed I had seen this before. So this likes one for Support.
Avery, you are correct that ATI 2018 and earlier versions gave a RMB menu option to 'Mount' for any .tib file you clicked on, however, if you attempt to Mount a Files & Folders backup .tib file, then you would see the error shown in the screen image below (from ATI 2018):
Acronis have improved the Windows shell integration with ATI 2019 so that it does not offer you a Mount option for .tib files that cannot be mounted, so that users will no longer see the above error message panel with ATI 2019.
However there is still some kind of Acronis bug here, I think, because the backup in question is of a partition (a flash drive), and mounts correctly as such under 2018 (on the computer it was made on). Another instance of the problem has no mount option for an original full backup of a flash drive made in April 2018, but provides one for an incremental based on that full in May 2018, and also for a second incremental made in Dec with 2019. I first encountered this problem with a backup of an SSD rather than a flash drive, but can't reproduce it any more due to some system changes. Some other backups from April 2018 show the the mount option without issues (I almost always make disk or partition backups, or at least intend to), and test them by trying to mount some of the partitions,and have never seen the above error, so I guess I haven't made any file or folder backups by accident).
Perhaps there is some discrepancy between what ATI 2018 is writing about the nature of the backups and what the RMB facilities for ATI 2019 understands? Anyway, your responses will be very helpful in writing something sensible for support.
Avery,
I tried an experiment. I have a flash drive with 4 .tib backup files on it. I attached it to my PC, opened Explorer and selected the flash drive, right clicked on one of the backup files, an .inc file numbered b23_s2_v1, hovered over Acronis True Image in the menu that appeared, and got 2 options. Validate and Mount. I then moved to another backup file with my cursor to repeat the process and while doing so I suddenly saw a new file appear on the flash drive. This file was numbered b23_s3_v1 and was an inc. file. This file showed to have 0KB or empty. Hovering over this file and then ATI, I saw only one option, Validate, Mount was not available
I have no idea how that occurred. Even more weird is that after some time went by the file suddenly showed to have grown from 0KB to 1,171.255KB. Repeating the process to get the right click context menu I now had both options.
So can you tell us if the files that do not present both Mount and Validate options actualy contain any data?
Yes, the that had only a full backup had about 4G data, the one where the full wouldn't mount had about 30G. Strange!
Well, I would definitely open a support case on this. I intend to do so with my experience here.
I do know that there were some issues with flash drives and using them as a Survival Kit which is what I used here. That is probably a separate issue from yours but nonetheless, you should get Support involved here,
Just did so, mentioning this thread. The original problem arose with an SSD, not a USB, but for various reasons I couldn't do a proper set of tests to rule out the possibilities that Steve Smith brought up.
Glad you got a ticket started. I figured out what happen to me, my actions of attaching the thumb drive to the PC which again is a Survival Kit drive with the option set to run the associated backup task when the drive is attached triggered the backup task to run. So for me, expected behavior albeit a bit of a head scratchier. :)