Memory leak in Acronis Backup & Recover 10

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

Hello,

we're using Acronis Backup & Recovery 10 Update 4 (Build 10.0.13544) on a virtiualized (kvm) windows 2008 r2 fileserver.

We observe that just opening the task definition of an existing backup task (100 GB data, 2 mio files, 70000 dirs) consumes up to 1 GB of memory which are not released again through closing the management console. We don't find any process in taskmanger that consumes this amount of memory.

The only way to free up memory again ist to reboot the machine. Did anyone observe such a behavior?

Thanks in advance,

Joerg

ven 27/04/2012 - 13:47
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Contributions: 1
Commentaires: 70

No, but why aren't you using the latest build (http://kb.acronis.com/content/14177)?

In general for large volumes, where most of the contents should be backed up, i'd definitely recommend doing a partition instead of file backup.
This will take less resources for the backup process - and you may still exclude folders (http://kb.acronis.com/content/2849) + restore on file/folder level (see http://kb.acronis.com/content/10645 + http://kb.acronis.com/content/10645).

dim 29/04/2012 - 10:31
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

Thank you Stefan for your reply and the links you provided.

Yesterday I managed to update acronis to the last build 10.0.13762 but this update didn't change the behavior: opening a file based task with lots of files to be saved still consumes memory which isn't released after closing the management console.

But: running a nightly backup task cleans up / releases the memory. So, as far as the server is not running completely out of memory, we can ignore that memory consumption an wait for the next backup.

Just one more question to what you've replied:
Is it a kind of best practice to avoid file-based backups if the number of files is high? If yes: What is a high number of files?

Joerg

mar 08/05/2012 - 15:08