Renommage des fichiers tib/tibx
Bonjour,
Je possède deux licences : Acronis True Image 2016 (PC fixe - Windows 10 Professionnel version 20H2) et Acronis True Image 2021 (PC portable - Windows 10 Famille version 1909).
Je voudrais savoir s'il est possible de renommer (le nom, pas l'extension) les fichiers tib/tibx créés par une sauvegarde Personnalisée et Complète, donc des fichiers indépendants.
Dans l'affirmative, peut-on le faire manuellement via l'Explorateur de fichiers Windows ou faut-il obligatoirement le faire par une fonctionnalité d'Acronis True Image, si oui laquelle.
Merci d'avance pour la réponse.
Azin Wxon
Steve wrote:
Renaming .tibx backup files is not possible or recommended with ATI 2020 because of the new dependencies that exist along with the use of metadata.
Just for my own piece of mind -- If I only use the bootable environment (simple recovery media, etc.) to create .tibx partition images, and if I only do full backups in a non-scheduled, single-version scheme, is it safe to manipulate (rename, move, and/or delete) these .tibx files outside of ATI (e.g., in Windows cmd.exe or explorer.exe)? In case it makes a difference to the answer, ATI has been completely uninstalled from my Windows 10 OS.
In the linked forum thread from 2019, Enchantech recommends using a Custom Full Non-Scheduled scheme to minimize dependencies. Is this approach more robust than my practice of doing a Single-Version Full Non-Scheduled scheme?
J K, if you are only using the rescue media environment, then all your .tibx disk / partition files are independent by definition of that environment. There is no metadata involvement or database usage in the rescue environment, so you should be able to do whatever you wish while creating only full backup files.
The key issue with any backup scheme used with ATI running in Windows is that metadata is created when the scheme is run for a second or subsequent time if any existing file is present in the destination location. This doesn't need to be an issue providing you always keep the 12KB metadata file along with the other .tibx file(s) for the task together, but does present an issue if your intent is to rename those files!
For myself, when wanting to have fully independent full backup files, then I can do this by using a Post Command to rename the file extension from .tibx to .~tibx immediately after it is created, then I can do whatever I want with that .~tibx file. When I run the same task, it doesn't find any existing .tibx file so creates a new full backup again and my Post Command checks for and deletes any existing .~tibx files before renaming the new file extension. The Post Command could also rename the file itself, copy it, move it etc (after the extension is changed which stops Acronis Active Protection from intervening!). Note: the tool doing the extension rename needs to be added as an exclusion for AAP, so best to use a separate .exe tool rather than using the default Windows rename utility!
Je vous remercie Mr Smith pour toutes ces explications.