Incremental backup useless for low bandwidth and capped clients
Hmm, the idea of incremental backups in True Image Home 2020 is all well and good to just have one large file all the time but this is useless for some of my clients who are thinking of upgrading to TI2020 as they have low bandwidth broadband (some are even capped) and when the nightly or weekly backups are created (in a Dropbox folder) it would be totally impractical to upload one large file every time!
I can't see a way of performing an incremental backup that uses the previous method (like in TI2019) where smaller individual incremental backups are created after the main initial backup.
Come on Acronis - this is poor planning.
Oh that's easy then - well done Acronis for making things really simple.....not!!!
That is a workaround which users should not have to "workaround"
Geeez why are there so many apologetics in software forums. What with this and not being able to mount .tbx images as drives!!....
Acronis - always two steps forward, one step back....
Dave Pozner wrote:Oh that's easy then - well done Acronis for making things really simple.....not!!!
That is a workaround which users should not have to "workaround"
Geeez why are there so many apologetics in software forums.
What you see as "apologetics", I see as users trying to help other users when we have no control over what Acronis does. We can't change the way the software works; we can only help people use the tools available. That's what this forum is about. Perhaps you should submit a Feedback to let Acronis know how you feel about the need for this workaround.
Dave Pozner wrote:... not being able to mount .tbx images as drives!!....
No apologies needed here. Acronis simply eliminated an unneeded function. You can open the backup file in File Explorer and have access to everything you had in the mounted image. Yes, traversing the directory structure can be very slow and tedious if the directory structure is large and deep,but in that case the old mounting scheme took a very long time, too.
If you actually have a need for a mounted backup, please describe the need here (so we can understand that need) and submit Feedback to the ATI developers can understand why the function is needed. And in the mean time, you can copy everything from the backup into a directory on some drive and then mount that directory - map a drive letter to the directory.
Patrick O'Keefe wrote:Dave Pozner wrote:... not being able to mount .tbx images as drives!!....No apologies needed here. Acronis simply eliminated an unneeded function. You can open the backup file in File Explorer and have access to everything you had in the mounted image. Yes, traversing the directory structure can be very slow and tedious if the directory structure is large and deep,but in that case the old mounting scheme took a very long time, too.
If you actually have a need for a mounted backup, please describe the need here (so we can understand that need) and submit Feedback to the ATI developers can understand why the function is needed. And in the mean time, you can copy everything from the backup into a directory on some drive and then mount that directory - map a drive letter to the directory.
One thing that you don't seem to get when opening a backup file in Explorer which can be available through the Mount function is to see file sizes and dates.
Bruno,
In Explorer having a backup file opened, click on View from the window menu and select Details. This will show sizes and dates.
Getting back to the main point. The code allows for the continued use of previously created *.tib backups, and I would think that it wold be easy to retain the ability to create new *.tib backup tasks. While they may not be as reliable as *.tibx users should be able to opt to use them provided they understand the risks.
Ian
IanL-S wrote:Getting back to the main point. The code allows for the continued use of previously created *.tib backups, and I would think that it wold be easy to retain the ability to create new *.tib backup tasks. While they may not be as reliable as *.tibx users should be able to opt to use them provided they understand the risks.
Ian
This ^
Especially until all of the new features and functionality of 2020 are fully mature. Default to .tibx for any new backup scheme, but allow the user to decide whether or not to use the new method or stick with the previous .tib method before running the backup. Then, lock down the setting, just like has been done with other settings such as the encryption password of backups if it can only be one or the other for that backup job.
IanL-S wrote:... it wold be easy to retain the ability to create new *.tib backup tasks. While they may not be as reliable as *.tibx users should be able to opt to use them provided they understand the risks.
I'm pretty sure we suggested this during the Beta test, but maybe it's time that we all request it again via Feedback.
Yes we did suggest this during beta testing - cannot remember the response (if any) we got from Acronis.
There is a "workaround" get a subscription version of ATI, although doing so depends on a cost benefit analysis by individual users.
I suspect the response by Acronis will be that they do not support cloud backup to third part cloud.
Ian
See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 GUI.
Enchantech wrote:Bruno,
In Explorer having a backup file opened, click on View from the window menu and select Details. This will show sizes and dates.
Thanks, Enchantech. I missed that. I was bamboozled because right clicking on a file only gives the Open and Copy options. And with the ribbon gone I hadn't even spotted the menu.