Skip to main content

Used disk space of deduplicated depot

Thread needs solution

Hello!

I'm using Acronis Backup & Recovery 11.7.50073 on Windows Server 2012 R2 Servers with Hyper-V.

The Problem I have is the used space of my deduplicated Depot. In the Management console of the server the used space is shown with 2,009TB but the folder on my NAS uses 3,65 TB.

How can I cleanup the folder?

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Thomas,

The space in a deduplicated vault can be only cleaned up using the compacting task. Would you share a couple of screenshots from the vault\statistics of the Storage Node and from the directory where backups are stored, so that we can better understand the situation. 

Thank you!

Sorry for answering late.

I added two screenshots - but German version. There you see that the depot uses more than 4TB and it is shown using 1.9TB in the depot overview or dashboard. If I start the compacting task I can see a few traffic on the NIC connected to the NAS, but I will never shown as finished. Last thing I tried was to disconnect and reconnect the depot, but it doesn't helped.

Some weeks before after I restart of the server the used space of the storage was cleaned up. Because I installed ABR on my Hyper-V server I cant not restart it every week or day. And yesterday the server were restarted and nothing happened on the depot.

My last decision is delete the complete depot and all referring files and database and create a new one - but I don't wanna lose all my backups.

Yours sincerely,

Thomas

Attachment Size
440817-143024.JPG 30.21 KB
440817-143027.JPG 21.92 KB
440817-143029.JPG 15.96 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Thank you for posting details! From your description I'd suspect the machine with Acronis Storage Node (ASN) installed not being able to process large amount of deduplicated data. Apparently the restart helped to free up some resources for ASN to complete compacting. 

How long does your dedup-vault exist? If it had been created before build 43956 was published, then there is a chance it still uses the old deduplication algorithm. You can check this looking at the format of the dedup database. Here the examples of 

an old dedup db

OldDedup.PNG

and a new one

NEWdedup.PNG

If the database is of the old format, it's recommended to re-create it as described in the article How To Migrate to New Deduplication Algorithm

Next I'd make sure the server with ASN has enough resources as per Deduplication best practices.