Storage Node, the backup data is too big
Hello together,
i have configured that the storage node keeps only one backup from a machine. But every time when a backup is completed, the data on the storage node is going bigger an bigger, although the backup have only 127GB. What should to have to configure ?
Show the screenshots below.
greetings Y.Erol
Hello Ekaterina,
thanks for you answer. Here is a Screenshot from the .tibx File.
The problem is, the filesize from 471GB is going bigger and bigger although, it is configured to keep only one backup. And the first backup has only 117GB. Additionally I will backup this files on to RDX Media. And when the backup going bigger and bigger, and soon i didn´t have enough space on RDX Media. Can you understand my problem ?
Yavuz,
In the managed vault there are "sparce" files used for backup archives, which means that the free space is reclaimed within these files and is re-used for new backups. In your example: the size of the file is ~500GB, while physically it takes only 117GB on disk (that means that if your disk was 10TB, then the free space would be "10TB minus 117GB"). However if you copy this file "as is" via Windows explorer then it would still take 500GB on the destination (which doesn't support sparce files). It is highly NOT recommended to do manual manipulation with files in location managed by Acronis Storage Node. In order to export the backups somewhere from this location you need to use Plans->Backup Replication plans or 2nd destination option from the backup plan. In this case the extracted data will include only the real data size (117GB in your case).
To cover your scenario there are 2 ways:
1) Instead of manual copying the files to RDX, use Acronis Backup plans to replicate these backups
2) Do not use locations managed by Acronis Storage Node, and instead save backups on plain network shares (\\server\share\) which will then be capable for manual copying/movement. AND use Backup Options->Backup format->Version 11, which will produce backups in separate files (separate file for full and incremental backups).
Thank you.
Hello Vasily,
Now it is logical. I will configure it, like your suggestion. THX for you support.
Hello Vasily,
i´ve configured like your suggestion, and now, during the replication process, i have now this failure:
Any ideas ?
Hi,
Edit: The error states that the backup location on the target share \\bk02\ cannot be accessed from the agent and it cannot find archives on it. Since according to the screen shot you're performing replication by the same agent (it's BK02 machine), you can select local folder where your RDX drive is mounted as the target. If this doesn't help then please contact our support team for further assistance.
Thank you.
So,
i dropped out the storage node, i will do backups only on network share with the AMS. Every attempt to try, to work with storage node was with problems. For me, storage node is in version 12.5 to buggy, i hope it will be better in future. Thanks for your support Vasily.