Skip to main content

[CRITICAL ISSUE] Mounted TIB files / only in write-protected mode

Thread needs solution
Forum Star
Posts: 381
Comments: 1590

ATIH 2016 It is still not possible to mount tib files with write permissions, this makes it impossible to alter NTFS settings and so prevents the user access vital parts of an archive if he is now trying to browse the backup using the TIB mounting service when being on a foreign computer or freshly installed computer with changed NTFS UUIDs. Ironically the TIB explorer grants access without checking any NTFS permissions legacy thread about this problem: https://forum.acronis.com/de/node/93186

0 Users found this helpful
Forum Star
Posts: 381
Comments: 1590

#1

oh sorry just got aware about an older thread for the same topic.

https://forum.acronis.com/de/node/99129#comment-301086

Thank you for your response there, Anna.

Forum Star
Posts: 381
Comments: 1590

#2

ATIH 2016 b6027

This one is still valid. Funnily the problem with NTFS permission will only affect mounted TIBs while in TIB Explorer files and folders do not have any NTFS restrictions.

Beginner
Posts: 0
Comments: 3

#3

I do not understand why thier has not been more complaints about the removal of this feature. It should be re-instated asap. I used to use it all the time to view\modify data in my user folders.

Now I cannot even access them via a mounted image. What is the point of being able to mount the image if you cannot access protected folders that need to have write permission changes to the folder to access, bnut with no write ability the data cannot be explored???? 

Forum Hero
Posts: 68
Comments: 8204

#4

I'll play devil's advocate since the product is designed to protect files (backup as is at the point in time taken).  With write access available in a "BACKUP" file, you no longer have a backup as it was taken and can purposefully or accidentally modify the content within it.  There are users who accidentlly copy (or cut) and paste contents to the wrong location without even knowing it because of the sensitivity of their laptop touchpad.  Or, perhaps someone less techy accidentally replaces the content in the backup with the wrong/bad file instead of restoring it to the current location.   To me, a backup should be just that - a backup as this is a home user product and a simpler version than what you'd find capable with Backup 11.7.  Of course, people will debate this back and forth but I'm assuming the 80/20 rule comes into play with these types of features.  If Acronis could allow a more advanced mode that specifically had to be turned on to allow this back, that might make more sense though.  I would suggest submitting feedback to Acronis through the app and reference this thread.

That said, you should always be able to access the content of the full tib using the Acronis bootable media (Linux) since the NTFS permissions won't apply in Linux.  I realize this is not as convenient, but it is possible and keeps the backup data "safe" in Windows from non-techy or unkowing users who might accidentally corrupt their own data if the backup was mounted in Write mode.

 

Forum Star
Posts: 381
Comments: 1590

#5

You have made good points Bobbo. If we are concerned about users to accidently delete their files from a tib file, it would be a feasible solution to have them write protected by default, and allow to toggle this in the options of the tib mounter.
Afaik this was possible in the past. For current I use the tib explorer as I do not face the NTFS restrictions either.

 

Regular Poster
Posts: 3
Comments: 413

#6

https://kb.acronis.com/content/13327

In earlier versions of True Image when you mount a backup archive in read/write mode an incremental file was created to store the changes.  The contents of the original backup file were not modified in any way.

Attachment Size
362194-129727.png 437.3 KB
362194-129730.png 349.9 KB
362194-129733.png 372.81 KB
362194-129736.png 267.64 KB
Forum Hero
Posts: 68
Comments: 8204

#7

Thanks Joey.  I had never known it was possible in earlier versions.  The change log shows it was removed in 2015, but not idea why.  I couldn't find any forum posts that explain why it was removed either.  Not sure why it was remvoed in 2015 - I can only speculate as to issues with the write mode in newer version of Windows or too many problems with it.  Or, it was because VSS is now being used as the default snapshot creator, but still don't know why that would limit this feature.  If it was READ only by default, and could be enabled for write mode with a new inc being created as a result, that could indeed be useful. 

https://kb.acronis.com/content/48662

Regular Poster
Posts: 3
Comments: 413

#8

My guess is that it created too many issues with the database files.

Frequent Poster
Posts: 4
Comments: 560

#9

Hello All,

Thank you for the feedback.

Write mode for mounting backups was indeed removed due to a number of issues found with that feature. Statistics showed that writing mode was very rarely used and it was decided to remove it starting from 2015 version of the software.

Although there is a change request to bring it back to the program, that is unlikely to happen in 2017 version.

Regards,

Slava

Beginner
Posts: 0
Comments: 1

#10

Are you saying this the solution,  well please refund me my money.  This was the reason why I contiued my subscription for this product and now to remove this function because you beleive it is rarely used!!!  That that is some shotty business practices.

 

 

 

Slava wrote:

Hello All,

Thank you for the feedback.

Write mode for mounting backups was indeed removed due to a number of issues found with that feature. Statistics showed that writing mode was very rarely used and it was decided to remove it starting from 2015 version of the software.

Although there is a change request to bring it back to the program, that is unlikely to happen in 2017 version.

Regards,

Slava

Beginner
Posts: 1
Comments: 1

#11

I hate writing on forums, but feel that in this instance it's warranted. The removal of the read/write feature was very stupid. It makes it difficult to access data due to NTFS permissions. This make the use of your own product harder and reduces the user experience. In the above it says that the statistics showed the feature wasn't used often. I dare say that your statistics are not an accurate reflection of the real world.

Legend
Posts: 81
Comments: 18158

#12

Travis, welcome to these user forums.

If you feel so strongly about this missing feature (Read/Write access to .TIB files) then please submit Feedback directly to Acronis using the tool in the main GUI.

To be honest, in all the years that I have been using ATI, I have never used the read/write option (when it was available upto the 2014 version), and the lack of it has not caused any issues for me.  As for NTFS permissions, these would only really apply if accessing the .TIB data from within the Windows ATI application GUI - you can always boot from the Acronis Rescue media which would not impose the same permissions.