Skip to main content

Version 15: Backup ultra fast and tibx ultra small

Thread needs solution

Hi all,

we installed Cyber Protect 15 Virtual Host for backup up a Windows 2019 Hyper-V Host.

We did backup a Windows Server 2019 Virtual Machine comtaining almost 4TB of actually used data (no dynamically-expanding VHDX, it's real used data). The corresponding VHDX on the host is of 3.6 TB in size. The resulting .tibx File(s) is of 1.4 TB in size (as default it is split up to 200GB single files which is ok to me). I have to mention that the inital backup from scratch took 8 hours writing the backup (1,4 TB of data) over gigabit network. Acronis Console is fine and status is "successfully completed". I can restore single files form that backuo, full system recovery not tested.

I am aware of compression and network speed, but I'd like to ask here, shall this be the normal behaviour? Also the following incremental backup the next day is running 120 Seconds, status "successfully".

I find this too fast and resulting .tibx too small.

Any experiance on this around here?

Thank you

Attachment Size
hc_3526 - Kopie_2.png 156.52 KB
1 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Flo Feller,

thank you for posting on Acronis forums!

 The corresponding VHDX on the host is of 3.6 TB in size. The resulting .tibx File(s) is of 1.4 TB in size

The data type stored on your VM influences the backup size. Thus, text and logs could be compressed and deduplicated with a higher ratio rather than media files.

A backup size can also be reduced if you store it on a Storage node with enabled deduplication.

 I can restore single files form that backuo, full system recovery not tested.

If you still doubt a backup consistency you can either validate it or convert it to a VM.

I am aware of compression and network speed, but I'd like to ask here, shall this be the normal behaviour? Also the following incremental backup the next day is running 120 Seconds, status "successfully".

An incremental backup only contains changes to the data from the previous backup.