Aller au contenu principal

Backing Up Image

Thread solved

I have setup Acronis to run back ups on my colleagues with a full back up every month and increments in-between but this months full back up is now a .tibx file type instead of the usual .tib. Looked at the logs and it says its done a full back up.

0 Users found this helpful

Peter, if these are new Disks & Partitions backups created with ATI 2020 then these will always result in creating backup files using the new .tibx file format.

ATI 2020 will only create .tib backup files for Files & Folders backups, or else if continuing a backup that was created by ATI 2019 which used this file type.

See the following KB documents published by Acronis with regards to .tibx files.

KB 63518: Acronis True Image 2020: do not delete first tibx file

KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image

KB 63498: Acronis True Image 2020: new tibx backup format FAQ

KB 63425: Acronis True Image 2020: Limitations of tibx backups

KB 63516: Acronis True Image 2020: Incremental backups do not create separate files when using new backup format

KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format

KB 63444: Acronis True Image 2020: tibx backups in local destinations

KB 63613: Acronis True Image: local backups are not available for recovery if "metadata" file appears in the backup destination - if you see metadata file(s).

 I just find it strange that we have been using 2020 for a while now the other back ups on the pc are .TIB and then it suddenly decides  to do a .tibx file type back up out of the blue.

Please check that you do not have a metadata type file present in your backup location as per the final KB document referenced above?

Peter,

I believe this is expected behavior.  You are performing full disk backups.  The application is designed to use the new tibx format on full disk level backups by default.

Your tasks having reached the end of the backup chain scheme reached the point of cleanup and create a new full backup version.  Therefore, the app, starting a new full backup by default creates a backup file in the new tibx format.

Enchantech wrote:

Peter,

I believe this is expected behavior.  You are performing full disk backups.  The application is designed to use the new tibx format on full disk level backups by default.

Your tasks having reached the end of the backup chain scheme reached the point of cleanup and create a new full backup version.  Therefore, the app, starting a new full backup by default creates a backup file in the new tibx format.

Bob, that is no my own experience with a task created by ATI 2019 and run on 2020 where the new chains continue to use .tib files, even after all the lost backup settings fiasco resulting in a new b1 chain being created.

 

Steve,

I trust your results.  Possibly the users task was modified or reconfigured to cause the change.  Unfortunately I no longer have any backups using the .tib format to back test with.

The documentation does suggest that the default behavior of using the tibx format for full disk image backups would be the norm.  

I believe the backup scheme used may also be a factor here.  If a Custom scheme is used and auto cleanup occurs which deletes the initial full file version then the next full written might assume the new format.  I say this because the Custom scheme does not have as rigid parameters as that of Inc or Diff schemes.

Hi guys thanks for the reply, it was the metadata issue. So ill try the fix for that.

 

Ah, glad to hear.  :)

Just one quick question, where is the page for checking if you can upgrade to 2020 from 2019 serial number check. I saw  it yesterday when it was looking for a solution to the above issue, but for cant remember what page it was on and trying googling it and came up blank.

Peter, please see KB 63219: How to upgrade to Acronis True Image 2020 - which should answer your questions.