Direkt zum Inhalt

Dedup vault compaction issue.

Thread needs solution

I tested a bit Acronis Backup 11.5:
- Created centralized dedup vault
- Made a backup to this vault. Vault contains now 15 Gb of data
- Deleted this newly create backup. Vault is empty, but it is still 15GB in size.
- Tried to compact storage node. The the compaction task starts and stops immidiately after the start.
- Played with threasholds in Group policies, but still no luck :(

Is there something I do wrong?

0 Users found this helpful

Hello,

The backup data is stored in both the vault location and the dedupe DB. If you delete the archive from the vault it will still reside in the dedupe DB until compacting is done. Compacting only clears out the DB but the DB will stay the same size. To reduce the size of the DB you will need to vacuum it.

First start Compacting on the vault

1. Find sqlite3.exe
2. After compacting finishes stop the Storage Node service.
3. Copy your deduplication database somewhere (just in case of any problem)
3. Open CMD as administrator and execute "sqlite3.exe PATH_TO_DEDUP_DB".
4. It will open sqlite shell. Execute "vacuum;" (without quotes)
5. It will defragment the database and reduce its size.

I got this from Acronis Dev but have not tried it yet. They did say it will take a long time to run depending on the server and the size of the data.

Let me know how it goes.

Kurt