Skip to main content

Reduce size for archive TIB file size

Thread needs solution

Hi all,

existing our using is Acronis vmProtect 8.0 Agent (build 8.0.8184)
backup a windows 2008 standard server.

as archive TIB file size is too large 588GB, i need minimize the size.
In previous setting, we using GFS cleanup scheme,
Now, i changed it to simple cleanup scheme, keep around 14 recovery points.
In usage storage, it show used as below.
But why our hard disk usage still showing the TIB size is 588GB.
any methods or tools we can minimize the sizes.
Or we must delete the previous TIB file and create a new one?
Please kindly advise.

Used Storage:
98.873 GB
Total number/size
of recovery points:
14 point(s) / 90.858 GB

Rgds,
Sun

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Sun,

The behavior you noticed is caused originally by using "Always Incremental" archive format where archive physical size cannot be reduced if you later change the retention policy to keep less recovery points (see description of the format here: http://www.acronis.com/en-us/support/documentation/AVMP9/index.html#150… ).

The possible solution is to use the 2nd destination feature, i.e. edit your existing backup task and configure secondary backup location. The archive created in the secondary location will contain all recovery points from the primary archive (588GB), but it will be of the smallest possible size. After you run this backup task once and the secondary archive is created, you can remove your original 588GB archive and re-configure the backup task to save new recovery points into the archive created in the secondary location, thus effectively reducing the size of the backups.

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager

Hi Vasily,

when using the 2nd destination feature, can you explain how this feature works internally? I am interested in whether Acronis removes the snapshot after creating the 1st destination backup, and whether Acronis creates the 2nd destination backup solely using the data from the 1st destination backup. The other possibility would be that the snapshot is being kept open all the time, and the 2nd destination backup is being created with the help of the original source file.s

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi,

Technically 2nd destination feature is a process of backup where the source is represented as the backup archive in 1st destination (so the read source is not the original VM). The original VM backed up into 1st destination is not involved into this process, so the snapshot is not kept while the 2nd destination task is running. The copying is capable of retrieving the list of recovery points list to be copied and moving only this data from the primary archive. In other words it's not a simple copy of the original backup file, but it's a process of incremental update of the recovery points list in the 2nd destination archive.

Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager