How to create a Disk backup as .tib (not .tibx)


- Se connecter pour poster des commentaires

Rob,
I understand you frustration. However, one more test would be very telling. Attach the disk to a different computer and try again.
- Se connecter pour poster des commentaires

Paul, being a devil's advocate, would that really be the same given this is an NVMe M.2 disk connected to the internal position, unless Rob has another computer where he could make the same connection method?
- Se connecter pour poster des commentaires

A successful backup of the disk (even if connected by a different method) would suggest that the problem was related to the computer and not related to a program bug. If the same failure happens with a different computer, that would point to a possible program bug. I realize none of this testing would prove anything beyond a doubt, but it would help narrow down the cause.
- Se connecter pour poster des commentaires

I concur with Paul here. Thus far we have only seen this issue on one machine, Robs. If he can reproduce on another than I would think application bug. As it is now I am lead to a hardware issue. I know it gets frustrating to chase down issues like this however, to me if I were in Rob's place I would always wonder if this drive were going to be reliable or not.
I think I might even test a different installer\version of ATI 2019 on it to see if that made any difference.
- Se connecter pour poster des commentaires

I don't have another machine for that test (need something else with a PCIe boot capability). Looking into that, but i don't expect the outcome to change either. Eventually we will verify though.
To reiterate: I can backup this hard drive just fine, just not with 2020 WinPE/WinRE rescue media where 2019 is installed on the OS that resides on this drive.
That's the one kicker.
This same hard drive backs up fine with all other tools and passes all integrity checks I've thrown at it. It backs up fine with 2019 WinPE/WinRE rescue media with 2019 installed on the OS housed on this drive.
I can back it up with 2020 WinPE/WinRE rescue media if 2019 is upgraded to 2020 or I can back it up with 2020 WinPE/WinRE rescue media if 2019 is completely uninstalled from the OS, but as soon as I install 2019 on the OS housedo that drive, the 2020 WinPE/WinRE rescue media says the disk is corrupt, and it's not.
This isn't a hardware issue, it's repeatable simply by changing the version of the application that is meant to be backing up the computer, and responsible for the one version of the rescue media (2020 WinPE/WinRE) meant to do the same thing offline.
I will try moving the drive as soon as I get my hands on another computer, but expect the exact same behavior if my theory is correct.
- Se connecter pour poster des commentaires

Rob, I just encountered a problem with ATI 2019 rescue media in failing to properly backup a disk because of something in the System Volume Information folder on the drive being backed up (posted on ATI 2019 forum).
Just curious... are you backing up System Volume Information? If so, is there any change if you exclude it?
- Se connecter pour poster des commentaires

Bruno,
Interesting post and I think you're on to something here. The System Volume Information folder contains information used by the content indexing service databases that speed up your file searches, the Volume Shadow Copy service for backups, and the Distributed Link Tracking Service databases used to repair shortcuts and links. It may also contain IndexerVolumeGuid and WPSettings.dat files.
The IndexerVolumeGuid file assigns a unique identifier to this drive. The Windows Indexing Service examines the files on the drive and indexes them. When you connect the drive to the computer in the future, Windows checks the identifier and knows which search database to associate with the drive. You can then use Windows Search features, such as the search box in the Start menu, Cortana on Windows 10, or the search box in the File Explorer or Windows Explorer, to quickly search for files on the drive.
Not sure what WPSettings.dat is for so cannot elaborate on that.
This may well be where the reference to Shadow Copy or VSS state comes from in the error files Rob posted.
Rob, if you have System Protection enabled on that drive I would suggest disabling it and select Delete to remove all restore points. After that test the 2020 backup WinPE/RE again. If this is the problem then case solved.
- Se connecter pour poster des commentaires

Enchantech wrote:Rob, if you have System Protection enabled on that drive I would suggest disabling it and select Delete to remove all restore points. After that test the 2020 backup WinPE/RE again. If this is the problem then case solved.
Before doing what is suggested here, try a backup with the folder excluded. I'd be interested to know if that works better. If it does, then see what happens by removing the restore points. One step at a time.
- Se connecter pour poster des commentaires

phred wrote:Will following your method to change from .tibx to .tib then create filenames such as what .tib used before? For exampleSusan_full_b2_s1_v1.tib and Susan_inc_b2_s2_v1.tib
It's so much easier to know what's taking place with my backups using this naming scheme. The .tibx really tells me nothing unless I check the file date and happen to remember what yesterday's file size was. Per bobbo's (Rob?) suggestion in another thread, I have submitted feedback via the app on this request.
Can anyone who has used Steve's method for changing .tibx to .tib answer this question?
Thanks
- Se connecter pour poster des commentaires

Fred, this method of changing back to .tib files (for Disk backup tasks) will only work for new backup tasks - you cannot use it to change any existing .tibx backups or backup tasks to .tib.
- Se connecter pour poster des commentaires

phred wrote:It's so much easier to know what's taking place with my backups using this naming scheme. The .tibx really tells me nothing unless I check the file date and happen to remember what yesterday's file size was. Per bobbo's (Rob?) suggestion in another thread, I have submitted feedback via the app on this request.
During beta testing, a request was made to use the Windows Explorer preview capability to provide visibility into the backup .tibx contents. On June 18th, Ekaterina posted:
And here the related change request - TI-170296 Shell integrated "preview" in Explorer with a detailed list showing all archive slices with date and backup type
Let's hope this one can get implemented before too long.
- Se connecter pour poster des commentaires

phred wrote:@Steve-
Will following your method to change from .tibx to .tib then create filenames such as what .tib used before? For example
Susan_full_b2_s1_v1.tib and Susan_inc_b2_s2_v1.tib
It's so much easier to know what's taking place with my backups using this naming scheme. The .tibx really tells me nothing unless I check the file date and happen to remember what yesterday's file size was. Per bobbo's (Rob?) suggestion in another thread, I have submitted feedback via the app on this request.
Can anyone who has tried Steve's method for using .tib instead of .tibx answer my question?
Thanks.
- Se connecter pour poster des commentaires

phred, I believe the answer is yes. Since it only works for a new task, you could give it a try.
- Se connecter pour poster des commentaires

Will someone who has used Steven's method of using .tib instead of .tibx please take a look at my question in reply #49 and provide an answer? I have posted it twice as a quoted post yesterday and both times it was deleted. So perhaps with the quote I'll get an answer.
Thanks.
- Se connecter pour poster des commentaires

Will following your method to change from .tibx to .tib then create filenames such as what .tib used before? For example
Susan_full_b2_s1_v1.tib and Susan_inc_b2_s2_v1.tib
Fred, we have answered this question several times - the answer is yes, it will create file names as for previous ATI .tib versions.
- Se connecter pour poster des commentaires

I thought system volume information was excluded by default - maybe not in rescue media. I'll try to test and see. It's definitely excluded in Windows backups by default so might explain some of the difference. It doesn't explain why 2020 WinPE Rescue media is the only one to fail though (not 2020 Linux, not any version of 2019, not any version of Macrium, Aomei or EaseUS and not Windows backup)
I don't have system protection enabled - I have had it off a couple of years now. The reason being (and I think this goes back to a 2016 or 2017 thread), is that when I do go into check system protection (just to view it based on the old threads), even though it is off, I still see that the capacity slider has been moved to 100% and fixed there. I see this on every computer I run True Image on at one point or another.
Matter of fact, I just checked and sure enough, my secondary EVO 970 (data only) i scratch that, it is the OS drive (NVME1) is exactly as mentioned. The drive I'm trying to backup though, was not.
When you run a VSS backup, if you monitor this, you'll see that the slider does move to 100%, and normally it will go back to the limit that you set it on. Mine was doing this correctly (uninstalled ATI, cleanup, reinstall, run Acronis VSS doctor, etc. to make sure it was working correct), but every now and then, when I check on it, sure enough it would be pegged at 100% again, and that is after sliding it back, turning system protection on and back off and deleting any snapshots.
- Se connecter pour poster des commentaires

Steve Smith wrote:Fred, we have answered this question several times - the answer is yes, it will create file names as for previous ATI .tib versions.
I'm sorry Steve. I must've missed the replies. Apologies to all who answered.
[Is there any way for me to delete the repetitious posts I made?]
- Se connecter pour poster des commentaires

Steve Smith wrote:Fred, this method of changing back to .tib files (for Disk backup tasks) will only work for new backup tasks - you cannot use it to change any existing .tibx backups or backup tasks to .tib.
Understood Steve. That's exactly what I'd like to do. IOW, give it a fresh start with .tib. Thanks.
- Se connecter pour poster des commentaires

phred wrote:[Is there any way for me to delete the repetitious posts I made?]
Don't worry about the repeated posts, only the forum moderator can remove these.
- Se connecter pour poster des commentaires

Steve / Bob,
The plot thickens. So, After turning the slider back to 10% (even though it was disabled), and then turning system protection on and back off again and clicking the option to delete snapshots (which there weren't any), I did a 2020 backup test and..... it worked! However, I'm not convinced it will remain working so will need to keep an eye out for the 100% slider issue again. And if this is/was a choking point for 2020, why if there is no disk or file system corruption since this is a bit/block backup... plus 2020 has never felt compelled to need to revert to sector-by-sector and again, all of these other backup products, including all versions of 2019 rescue media and Linux 2020 rescue media are good too?
BTW: here were some forums and other links about this to:
https://forum.avast.com/index.php?topic=162041.0
And the plot thickens more too....
I did a 2019 test backup again and although it does result in a successful prompt, when I look at the log, there are actually some errors. They may have always been there, but never bothered to look at the log since it was always reported as successful in the rescue media and there are not error reported when backing up with 2019 in Windows either.
The log with the 2020 successful completion had no information - just 2 lines, backup started and backup completed on this successful attempt.
The 2019 rescue media log errors seem bogus - volume 8 and 9 are the external usb drive used to launch the rescue media and store the backup - they are not being backed up. volume 11 is an empty SD card slot from the internal 19-1 card reader and is not associated with Disk #2 or the physical drive we are backing up - which is the E: volume (the OS drive being backed up here is being assigned E in the rescue media). The only volumes in play for the backup are not listed in the log with any errors.
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 3 Recovery NTFS Partition 529 MB Healthy Hidden
Volume 4 E NVME1_500GB NTFS Partition 465 GB Healthy
Volume 5 FAT32 Partition 100 MB Healthy Hidden
Fichier attaché | Taille |
---|---|
515798-173299.txt | 4.61 Ko |
515798-173302.txt | 2.07 Ko |
- Se connecter pour poster des commentaires

Rob, the ATI 2019 offline log does show issues with System Volume Information data / folders.
See the 'cleaned up' version of the log file below:
Version: 1.0 encoding= UTF-8
Build: 17750
Product: Acronis True Image
Task: My Disk Drives Backup
UUID: 09AD25FD-2058-442D-80D1-4213F46D8A29
Version: 23.5
Operation My Disk Drives Backup started. Time = 10/04/2019 20:30:43
Create Backup Archive
From: Disk 3
To file: I:\_OFFLINE_BACKUPS\ACRONIS\TEST01C\MyBackup.tib Compression: Normal Time = 10/04/2019 20:30:43
Pending operation 173 started: 'Creating partition image'. Time = 10/04/2019 20:30:43
Volume Tracker has failed to open session '\Device\HarddiskVolume8' for volume '\\?\Volume{415c881e-8d8f-43bf-803b-785ae59a33fe}\'. Time = 10/04/2019 20:30:43
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Time = 10/04/2019 20:30:43
path type= TIdentifier volume_tracker_driver_api.dll
$module type= TIdentifier trueimg_home_pe_vsa64_17750
The specified module could not be found Time = 10/04/2019 20:30:43
code type= TULong64 2147942526
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Writing full version To file: MyBackup_full_b1_s1_v1.tib Time = 10/04/2019 20:30:43
Pending operation 173 started: 'Creating partition image'. Time = 10/04/2019 20:30:51
Volume Tracker has failed to open session '\Device\HarddiskVolume9' for volume '\\?\Volume{5319aa1d-91de-4f9a-a686-cbb185e6c6fb}\'. Time = 10/04/2019 20:30:51
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Time = 10/04/2019 20:30:51
path type= TIdentifier volume_tracker_driver_api.dll
$module type= TIdentifier trueimg_home_pe_vsa64_17750
The specified module could not be found Time = 10/04/2019 20:30:51
code type= TULong64 2147942526
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Pending operation 173 started: 'Creating partition image'. Time = 10/04/2019 20:30:51
Volume Tracker has failed to open session '\Device\HarddiskVolume11' for volume 'E:'. Time = 10/04/2019 20:30:51
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Time = 10/04/2019 20:30:51
path type= TIdentifier volume_tracker_driver_api.dll
$module type= TIdentifier trueimg_home_pe_vsa64_17750
The specified module could not be found Time = 10/04/2019 20:30:51
code type= TULong64 2147942526
$module type= TIdentifier trueimg_home_pe_vsa64_17750
Pending operation 173 started: 'Creating partition image'. Time = 10/04/2019 20:48:17
The following backups have been successfully created: I:\_OFFLINE_BACKUPS\ACRONIS\TEST01C\MyBackup_full_b1_s1_v1.tib
Time = 10/04/2019 20:48:17
Backup operation succeeded. Time = 10/04/2019 20:48:17
I do not understand why the volume tracker code is being involved in backups created using the rescue media?
- Se connecter pour poster des commentaires

Steve Smith wrote:There are no guarantees for how long this workaround method of forcing .tib usage will continue to work, so you may be better to 'bite the bullet' and adopt a more descriptive backup name, i.e. Susan_Inc.tibx or Susan_Diff.tibx and control this yourself.
Point noted.
- Se connecter pour poster des commentaires

Steve, I noted those errors. Those are from 2019 WinPE rescue media with a "successful backup".
2020 WinPE also had a successful backup and no errors after looking at system protection in the Live Windows OS and nothing the 100% usage, even though it is disabled. This is the 2020 log after seeing the 100% system protection (even though it is disabled) as reported way back in 2016...., after I manually set it back to a smaller amount. Why that would even matter, makes no sense. If WinPE is not running VSS (confirmed by Mustang's notes and test), then the Source backup disk with the OS should not have an issue backing up if there are no disk integrity issues at the sector, bit, block levels.
<?xml version="1.0" encoding="UTF-8" ?>
<log build="21400" product="Acronis True Image" task_name="My Disk Drives Backup" uuid="F53A526F-7973-43D5-B3CF-DA46EC699345" version="24.4">
<event code="0" id="1" level="2" message="Operation "My Disk Drives Backup" started." module="100" time="1570226868" />
<event code="252" id="2" level="2" message="Backup operation succeeded." module="100" time="1570227655" />
</log>
I've submitted a ticket - with all of the logs, screenshots and system reports from each offline and online test. Laying it to rest and sticking with 2019 unless Acronis can provide some insight on what is happening.
- Se connecter pour poster des commentaires

Rob, I can only say that your issue is 'very strange!!' so hope that Acronis get to grips with it for your support ticket.
- Se connecter pour poster des commentaires

Rob, have you run a validation against either the 2019 or 2020 versions of the backups created under rescue media? I've encountered a validation problem in backups from ATI 2019 rescue media that only shows up when System Volume Information is included in the backup (see ATI 2019 forum). I don't believe it to be related to VSS but there is a lot more in that folder.
From what I've seen and you've seen, the SVI folder does seem to come into play in the backups made from rescue media, and not just on ATI 2020.
- Se connecter pour poster des commentaires

Rob,
Snapshot error messages in the WinPE backups are not referring to VSS errors. Acronis' WinPE rescue media uses Acronis' snapman.sys to create snapshots. How it works and where it stores the snapshots has never been explained. I do know Acronis' snapman service is much less trouble prone that VSS. That was what drew me to True Image years ago. It's only been in the last 3-4 years that True Image has used VSS in the Windows versions.
- Se connecter pour poster des commentaires

Rob,
Glad you got 2020 to work even though you still think it is flawed.
Steve,
The error "Volume Tracker has failed to open session" has some association with Acronis Backup Cloud and Acronis Backup 12.5 Apparently Volume Tracker is responsible for tracking changes on disk. It is necessary for CBT (changed block technology) to run which accelerates backup. There is also some association between these and Shadow Copy service. You might find the link below of interest.
https://kb.acronis.com/content/60700
https://kb.acronis.com/content/62649
https://www.acronis.com/en-us/support/documentation/AcronisBackup_12.5/#36340.html
Although these are not identical errors to yours or Rob's they do raise questions. I did a registry search on one of my machines and found an entry for Acronis Volume Tracker at:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\volume_tracker
It shows that the Volume Tracker is located in the System32 folder. I found it to be in C:\Windows\System32\drivers folder.
I wonder if you or Rob are missing this registry entry and/or driver which would indicate that the service is unable to run. I do recognize that this is specific to Windows however, if these components are found in WinPE/RE and are applied when the TI module is installed then possibly TI does use the Shadow Copy service in the media after all and in Robs case if these components are present and the database this service keeps did not agree with the check run on the source drive resulted in the error.
- Se connecter pour poster des commentaires

I had a few extra minutes today so decided I would have a look at Ti 2020 Recovery Media (WinPE built with the Media Builder tool in TI) to see if in fact this volume tracker exists. I can confirm that it does. Shows up in the registry in the same key. Shows in System32 as volume-tracker-driver-api.dll. I also see in System32 vss.api, as well as snapapi.dll, snapapint.dll, and snapapint64.dll.
Given the fact that i can use the Recovery Media to backup the OS disk on my PC in less than 2 minutes I believe it is obvious that TI uses volume tracker in WinPE to accelerate the backup process in WinPE. Given that, I also believe that in Rob's case the application was finding different data (leftovers) from a snapshot in the System Restore area of the source disk that was not in the snapshot taken for the backup task. This caused the error.
In the case of TI 2019 Recovery Media showing the volume-tracker error, I believe that if you see this error in the WinPE log you might find that volume tracker is not installed in your media for some reason.
As for other backup applications it seems to me that they do not perform as deep of a scan of a source drive to discover such differences. As a consequence they are more than happy to run a backup task on the disk as do previous version of ATI. Will such differences cause the backup to be flawed to a degree of being unable to restore properly and boot. I would think not but then again it might possibly do so.
I like the idea of 2020 performing deep scans and comparisons on disks to look for trouble spots. I think that we as users must become accustomed to this behavior and learn to work with it. I believe that overall, reliability of 2020 is far better than previous versions because of this. I also believe that the enhancements to the Cyber security components of the app are a big yet seldom seen benefit of TI 2020.
- Se connecter pour poster des commentaires

I've been away, but am back. I'm working with a support engineer now so hopefully there will be some finding to this in the end. In the mean time, 2020 offline backups are working now since "fixing" the Online version of my installed Windows 10 System Protection (which was disabled by me years ago, going back to the bug noted in 2016 listed above) from being stuck at 100% at some point in time.
Since then, I've also gone to town on my own system... reinstalling Windows 10 over-the-top of itself, just in case, moved the main drive to one of the PCIe add-on adapters and the other drives onto the mainboard m.2 slot where the original was - just to see.
Now, I'll have to wait and see if, at some point, system protection usage moves to 100% and stays there again and if so, if the problem returns. Until then, maybe they'll find something.
Interesting look at the volume-tracker info, Enchantech. I really am not sure how I feel about this. I just want the backup to backup the disk "exactly" as it is - at the bit, byte, block level. Reading content on disk, regardless of the feature, seems to be having a negative approach towards success in backups and cloning (at least to some extent).
Acronis says it will make an exact copy of the source, and that appears to possibly not really the case anymore? But that's exactly what I need, want and expect from an offline backup - an exact copy, for better or for worse.
- Se connecter pour poster des commentaires

Rob,
I'm trying to understand your statement " Acronis says it will make an exact copy of the source, and that appears to possibly not really the case anymore?" Can you explain a bit?
- Se connecter pour poster des commentaires

Tested the steps in the initial post again today using ATI 2020 build 22510 and the process still works as expected to create a Disk backup using the older .tib file format & naming.
- Se connecter pour poster des commentaires

Powershell script attached that will modify a select .tib.tis XML script file to change it from tibx to tib. This should only be used for a new Disk backup task that has NOT been run to create any files!
To run the script I prefer to use the Powershell ISE (run as Administrator) but the default security settings for most users will prevent any unsigned scripts from being run unless you have created a Powershell profile and set a different execution policy to allow scripts to run.
For Powershell ISE the profile document is stored at:
$env:HOMEPATH\Documents\WindowsPowerShell
in document: Microsoft.PowerShellISE_profile.ps1
The contents of this profile document need to include the following line at a minimum:
Set-executionpolicy -executionpolicy RemoteSigned process
When the script runs, it will open the C:\ProgramData\Acronis\TrueImageHome\Scripts folder to show all available .tib.tis files. If you have just created a new Disk backup task in the main GUI, then you should select the most recently created file from those shown.
Do NOT select other files for any active backup with files created!
The lower window panel will show a confirmation prompt that you want to proceed, and if answered Yes, the script will turn off AAP then change the file before turning AAP on again. The last action is to open Notepad to show the changed file.
Fichier attaché | Taille |
---|---|
527173-178662.zip | 1.43 Ko |
- Se connecter pour poster des commentaires

Thanks again for that tutorial Steve!
I found a little mistake in step 7:
07. Find & Replace all occurrences of .tibx with .tib then Save the file.
Note: Ignore the .tibx entry in the Exclusions listing (*.tibx)
If one really does only replace occurences of .tibx to .tib it will not work. You will have to replace all occurences of tibx to tib (except the one in exclusions list). Otherwise you will miss to replace tibx in that 2 lines because in that tags it is written without a leading dot and it won't switch to old format with 1 file per day:
<archive_options check_network_timeout="false" computer_id="XXX" format="tibx" id="0" network_timeout="0" split_archive="false">
<stream_options allow_silent_media="false" cache_network_write="false" compression_level="maximum" encryption_algorithm="none" format="tibx" freespace="0" ignore_bad_sectors="false" reattempt_count="5" reattempt_on="true" reattempt_pausesec="30" silent_asz_cleanup="true" silent_mode="false" type="disk" ver="1">
- Se connecter pour poster des commentaires

Jurgen, thanks for spotting the omission in the original initial post for this topic - I have added some updates to the text for this. The PowerShell script (ForceTib.ps1) in the previous post to yours does handle all the places where tibx needed to be replaced by tib using the following lines of code script.
function ProcessLogData
{
((Get-Content -path $SelectedFile -Raw) -replace 'format="tibx"','format="tib"') | Set-Content -Path $SelectedFile
((Get-Content -path $SelectedFile -Raw) -replace '.tibx" volume','.tib" volume') | Set-Content -Path $SelectedFile
}
- Se connecter pour poster des commentaires

Just a word of thanks to the original poster Steve.
tibx files were driving me nuts with their lack of obvious info and they were wrecking my wifi disk mirroring of my NAS backup server to my offsite server (ultra cautious!)
Acronis could not help, told me it could not be done, then I found this thread.
Mirror task took sixteen hours last tibx run, once the new tib full backups had propagated then today's incremental mirror took five minutes!
Cheers!
- Se connecter pour poster des commentaires

Chris, welcome to these public User Forums. Thanks for your comments, glad the information has helped your situation.
- Se connecter pour poster des commentaires

Actually been a member for seven years! though no posts on here. I guess there was an earlier forum.
Acronis reply for interest
Ans: Changing the script is not recommended, however, if the tib files are accessible for recovery then you can continue as that is the only option available for your approach.
I have taken a copy of the script file in case I accidentally change any options. Feature request done
- Se connecter pour poster des commentaires

Modified the Powershell script 'ForceNewTib.ps1' to remove the functions that tried to Stop and Start Acronis Active Protection so will work with both ATI 2020 and 2021 Beta by prompting the user to turn off or pause protection (2021) if found to be running.
Tested the script with ATI 2021 Beta #29610 to successfully create a Disks & Partitions .tib backup image file.
Fichier attaché | Taille |
---|---|
547999-195131.zip | 1.35 Ko |
- Se connecter pour poster des commentaires

I am using True image 2021 on a newly purchased Windows 10 PC. The account that I'm performing the following on is marked as an "Administrator".
When I attempted this process I first tried to save a copy of the latest .tib.tis file using "copy/paste" and got an "access denied" error, but the paste still created 3 copies that are all 0 bytes. Now I find that I can't delete these empty files. I then copied the file to my desktop for safekeeping and edited the original file in the Scripts folder. After making the specified changes, I attempted to save it and received a write error. Sigh.
Please advise as to how to proceed. I'm going to re-enable the Active Protection and revert to the original backup scheme for now until I hear back from you.
Thank you for your attention to this matter,
Scott Lindley
- Se connecter pour poster des commentaires

Scott, thanks for your post on this topic. I hadn't tested this process again on ATI 2021 since when using the Beta build version and it seems that Acronis have made changes to Active Protection such that it continues to protect the .tib.tis files even when it is supposedly Turned off permanently!
The way around this is as follows:
Turn off Protection in the ATI GUI - I would recommend using the Turn off Pemanently option regardless of the intention to turn it back on again later!
Open the Windows Services control panel and set the Startup for Active Protection to be 'Disabled'.
Restart the computer so that Active Protection is shown as 'Stopped' in the Services panel.
Make the changes to the .tib.tis file of a new backup task that has never been run or created any .tibx files.
Once the .tib.tis file has been saved, you can reset the Active Protection service back to Automatic startup and start that service, plus Turn on Protection again in the ATI GUI.
Note: Take the option to Backup LATER
Restart the computer after making this change!
- Se connecter pour poster des commentaires

The forced switch to the tibx format was a horrible move by Acronis in my situation. We have been using ATI since 2014 and recently replaced a couple of laptops and decided to move from 2019 to 2020 with the new laptop installs. Over a period of about two months we noticed tripled costs for bandwidth and storage from our ISP (they have data caps) and our offsite storage provider. For 8 months we could not figure out what was causing it and finally tracked it down last week to the way the tibx format works. Since we installed 2020 clean it defaulted to tibx which apparently appends incrementals to the original full backup file instead of writing separate incremental files. Since we ship the backup files to our offsite storage provider this meant the file changed at every incremental backup and triggered a re-upload to the offsite location. Since it was the same file, our daily uploads went from 3 to 4GB to an extreme every night. For example, the original full might be 60GB and that file gets uploaded, then the incremental runs and might be 3 to 4 GB which gets appended to the original 60 GB file each time. So the 60 GB goes from 60GB to 88 GB within a week and the entire file gets shipped offsite every night. This caused us to hit our bandwidth caps and because the offsite system is file-level and not byte/block level the file gets deleted then uploaded again which means we got hit with early delete charges. Needless to say this was infuriating... Acronis needs to make tib or tibx an option in the UI so that we have a choice and the fact that the software now seems to want to be an AV solution as well has caused me to pause on our 2021 purchase and will likely result in looking for a new product. I have a solid AV solution and dont need two running on my machines. I need a quality backup solution but ATI questionable for me at this point.
- Se connecter pour poster des commentaires

Hi Dedrick and welcome.
If you look back to my earlier posts you will see my situation was exactly the same as yours. Following Steve's excellent solution has solved my problem to be able to revert to discrete tib files, which I have used in restorations without problems.
- Se connecter pour poster des commentaires

Part of the explanation of the increased usage could be that file compression is broken for *.tibx files. Not sure what compression is applied but I suspect it is not max compression.
Ian
- Se connecter pour poster des commentaires

Looks like the script is working for me on ATI 2020 25700, despite the error displayed when it attempts to change the state of whatever the security garbage is called. I just had to pop in here and thank you, so THANK YOU. In fact when I wind up on these forums, I see your face nearly every time I find succes. So thanks again. If I can buy you a cup of coffee, please share a link. I ll see what I can find around your profile. Cheers-
OT: I've been using Acronis since 2007, professionally, and personally. I've turned truly countless friends, family, and clients on to it over the years. It has saved my hide, provided true peace of mind, served as a crutch when that crutch was all we had, and has really maintained a key roll in so so many of my professional, and personal computer endeavors, simple and effective. Sad what has become of it (True Image.) Ill use my older versions as long as I can, and Ill look into Acronis' other offerings to see if something is a better fit, as in, without security functions I do not need or want, and is stable/non beta, etc. It's unfortunate existing users' needs have no role in the direction of development.
- Se connecter pour poster des commentaires

Santiago, welcome to these public User Forums.
Thank you for your kind words - glad that the work-around is help you.
I can only recommend that you and all other users who feel the same way about the recent changes made by Acronis submit Feedback to them to make them aware directly of your disappointment and also tell them why you want to have the continued option to still create backups using the older .tib file format. Example: users who mirror their backup files to either a NAS or third-party cloud where using .tibx files massively increases the data being transferred due to consolidation of incremental backups into the main .tibx file.
- Se connecter pour poster des commentaires

Update: Test this process on ATI 2021 build #39184 and found that AAP remains active regardless of turning it off in the Protection settings!!
Tested modified version of Powershell script which forces AAP to stop before changing the script .tib.tis XML file which does still work! 20th March 2021.
New file attached in file ForceNewTIB-2.zip
Fichier attaché | Taille |
---|---|
572502-216954.zip | 1.61 Ko |
- Se connecter pour poster des commentaires

I want to thank you for this information.
I needed a license for my daughter's new laptop (she previously had only a desktop), and decided that instead of using my last 2017 one, a new computer deserved a new version. Well, I wish I'd not simply relied on my experience with a previously stellar product when choosing True Image 2021, but I did. At least I got in under the wire for a perpetual license.
But I thought I was stuck with the .tibx format. According to 63441: Acronis True Image 2020: tib and tibx backup format usage, the user cannot choose the tib format manually. OK, I'd say that was silly, but it is clearly a diabolical part of Acronis' new "maximize profit, screw the users" business model. I need the incremental backups to be the small files they used to be so that transfer to a backup system doesn't take forever. Most backup solutions will see the updated .tibx as a whole new file and transfer it all, also affecting snapshot space (where applicable) for the old ones. I'm sure Acronis' own cloud solution gets around that, thus the diabolical nature of the change, pushing users to their cloud solution.
But that article also says a backup converted from 2019 or earlier would retain the .tib format, so they could have allowed that selection, and chose not to. I was thinking I had to uninstall 2021, install 2017, create a backup, and then re-installed 2021. But you have obviously determined how that process works, and it is working great for me, greatly simplifying the process. I did it manually, just because I want to know what's going on, so can't comment on the script.
I did find I had to disable more than just the protection process. I just disabled them all, so I'm not sure which other one(s) needed it. And for anyone doing it manually, your editor must also be run as administrator because of Windows restrictions on the folder. An easy way is to type notepad in the search bar and select run as administrator, then you can open the file from that instance of Notepad,. make the modifications, and save it in the proper place.
- Se connecter pour poster des commentaires

Steve Smith wrote:Update: Test this process on ATI 2021 build #39184 and found that AAP remains active regardless of turning it off in the Protection settings!!
Tested modified version of Powershell script which forces AAP to stop before changing the script .tib.tis XML file which does still work! 20th March 2021.
New file attached in file ForceNewTIB-2.zip
I couldn't get your script to work with the current build 39216 of ATI 2021.
Specifically, it gets an error trying to stop the AcronisActiveProtectionService.
AcronisActiveProtectionService status is Running
Stopping AcronisActiveProtectionService service & anti_ransomware_service process
Stop-Process : Cannot stop process "anti_ransomware_service (6152)" because of the following error: Access is denied
At D:\Downloads\ForceNewTIB-2.ps1:62 char:5
+ Stop-Process -Name $process -Force -Confirm:$false
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (System.Diagnost...omware_service):Process) [Stop-Process], ProcessCommandEx
ception
+ FullyQualifiedErrorId : CouldNotStopProcess,Microsoft.PowerShell.Commands.StopProcessCommand
AcronisActiveProtectionService status is Running
And yes, I was running it as administrator.
- Se connecter pour poster des commentaires

Julien, Acronis have continually tried to harden their Cyber Protect components in the latest builds of ATI 2021 and ACPHO to prevent them from being 'tampered' with!
The only method to circumvent this and try to force use of .tib files for disk backups is as follows:
Open the Windows Services control panel (services.msc) then sort the name column by clicking on the heading so that you can see all the Acronis services first.
Select the Acronis Active Protection service and open its Properties then set the automatic start to Disabled. Do the same with Acronis Cyber Protection Service, then do a Windows restart.
When restarted, both services should not be running (unless you have any Acronis tasks set to run on startup or open the ATI GUI). You should then be able to change the script .tib.tis file / use the Powershell script to do the same.
Once done, you can reverse the changes to set the services back to Automatic start.
All of the above shouldn't be necessary if Acronis respected the user settings for Protection when turning off Acronis Active Protection!
- Se connecter pour poster des commentaires