Salta al contenuto principale

Need a pre-command script to delete password proteced .tibx files before adding the new version chain.

Thread needs solution

Due to limited storage space on a local hard drive, it will return an 'insufficant space' error on the next version cycle when the drive is filled even though cleanup is set to clean before filling up drive space.  

This is because the current Acronis automatic clean-up process FIRST ADDS a new full backup THEN DELETES all old versions. I need this process reversed to FIRST DELETE the old THEN ADD the new.

The only way I can do that is by a pre-command using a batch (.bat) file. The Acronis technical support team refuses to assist creating one for unknown reasons.

The script may require Acronis specific commands. Since the backup is both password protected and encrypted, the scrip must first insert the password before proceeding or it will be blocked. 

I need assistance writing a batch (.bat) script for a pre-command to: (1) FIRST DELETE PASSWORD PROTECTED .tibx files in a local drive folder, (2) THEN ADD the new version chain on the next cycle. 

Anyone having experience wrinting pre/post command scrips, please respond.

0 Users found this helpful

Charc, how many backup version chains are you creating here?

If you are creating more than one version chain, then deleting older chains will break all future backup chains because of the way the chains are linked by metadata.

If you are creating only one backup version chain, then the next question is:  what type of version chain is it?  Is it an incremental chain where all the increments are stored within the one .tibx file, or is it a differential chain where the differential files are stored separately in their own files?

The approach that you can use is to use a Pre Command to rename the existing file(s) by changing the extension from .tibx to something like .~tibx, after which you can simply delete the .~tibx files.

If you have Acronis Active Protection enabled, you will need to whitelist the rename tool that you use so that it is not blocked from changing the file extension by AAP.

In terms of the files being password protected, that is not relevant as the password is only used to open the file and access the contents, so is not needed when renaming or deleting the file.

As far as new version chains go, this is why you can only do this with a single version chain, either renaming the .tibx files or deleting them will cause ATI to assume that no backup chain has been created and will then start a new Full backup for a new version chain.