How do I stop it from starting an index task after every back up ?

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 8

I'm doing a full backup of about 10 virtual machines every night. This is scheduled via Backup Policies. Unfortunately Acronis starts an Indexing task over the Vault after the first machine, this dramatically slows down the subsequent backups and causes them to often continue through the following day. We're only talking about 500gb total per night, so it's not a log of data to be expecting to be able to back up.

How can I stop automatic indexing tasks and run them on a schedule of my choosing ?

Tue, 06/15/2010 - 15:47
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Paul,

Thank you for your question. I will definitely help you with it.

At the moment, the indexing task starts automatically after a backup has been performed. There is no way to schedule it unfortunately, but I would like to thank you for your suggestion. I will create a Customer Listening Ticket for this and forward it to our Development team for consideration.

In the meantime, can I suggest the following workaround?
Pick a number of your computers that have the bulk of your data. Schedule a few full backups over the week-end, after the backups get created the indexing task will run and sort out all the relevant data. After that, all consecutive indexing tasks will work faster.

Please let me know if you have any other questions or require additional assistance and I will be very happy to help you.

Thank you.

Wed, 06/16/2010 - 18:46
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 8

Anton,

Thanks for the suggestion. The problem is I am backing up a total of over 10Tb. I have split this into 3 vaults 'windows, 'linux', 'vmware'.

For the Windows vault I did a few backups ( a few Tb worth ) and let the index task run ... it took several days. I then backed up another path and the index task has been running for 23 hours and is only at 21%.

It's ridiculous for the indexing task to be taking this long as it interrupts or at least slows all my other backups down to a crawl.

My backup solution is basically looking to be unworkable with Acronis now ... With the linux stuff broken, and the indexing task causing so much headache I can barely reliably backup a few hundred gb overnight. When I have tens of tb to deal with it's impossible.

Thu, 06/17/2010 - 16:23
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 88
Comments: 4769

Hello Paul,

Thank you for replying.

May I suggest this workaround, I am confident this will speed up the process.

You can try creating 1 vault per machine and backup no more then 500 GB per day.

Alternatively, this I think will work better, you can use 1 Acronis Storage Node per machine.

I will create a Customer Listening Case for this and forward it to our Management team, I am very sorry for the inconvenience.

Please let me know if there is anything else I can do for you.

Thank you.

Thu, 06/17/2010 - 17:23
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 8

Wow really? That seems like a large amount of management overhead to overcome shortcomings in software I paid good money for.

Wouldn't creating a different vault/storage node for each system cut down on my deduplication savings as it wouldn't offer deduplication across multiple server's data ?

Fri, 06/18/2010 - 14:26
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 8

So I tried your idea. I backed up a single volume to it's own Vault ... It was just over 1Tb and was compressed/deduped down to show an Occupied space of '745.7 GB'. The Indexing task has been running for 2 days and 3 hours and is only at 34%. Does this not seem a little crazy ?

Mon, 06/21/2010 - 14:03
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Dear Paul!

Thank you for your reply and for keeping us posted. I sincerely regret that you;ve been through all these difficulties and will be glad to help you.

First of all I would like to apologise for the inconvenience we've caused you. it is highly recommended to have 1 deduplication vailt on 1 ASN, so I would appreciate if you could kindly correct it. I'm sorry for we have confused you by the information provided in the previous post - it's not absolutely correct, and Experts team advises you to use just 1 deduplication vault on one ASN.

Please also check in addition the vailt and the database to be on separate disks: having them both on one disk will slow down the indexing significantly.

I'd like to offer you several suggestion which should speed up the process of deduplication and help to use this tool efficiently:

Setting up a machine for Acronis Storage Node

  • Prepare a dedicated machine for Acronis Storage Node hosting deduplication vaults. Server operating system is preferred;
  • Multi-core machines are highly recommended;
  • Acronis Storage Node computer should have at least 2 GB of available physical memory for deduplication to function flawlessly.

Setting up a centralized managed vault with deduplication

  • Vault data and vault database folders should reside on different HDDs to avoid performance degradation;
  • If vault data is stored on a NAS, make network connection as fast as possible. Gigabit Ethernet is recommended;
  • If vault data is stored on locally attached HDDs, use the fastest controllers and high RPM drives. I/O is the main bottleneck for deduplication speed;
  • Having one deduplication vault per Acronis Storage Node is the best practice;
  • Make sure there is plenty of free space on the deduplication vault storage. You can estimate the recommended free space being equal to 110% of occupied space. For example, if the vault data occupies 10 GB, you should have 11 GB of free space.

Settings for client machines and backup plans/policies

  • Speed of backup to deduplicated vault can be increased by turning off deduplication at source (enable Deduplicate backup only after transferring it to the vault (do not deduplicate at source) option in Additional Settings of Backup options;
  • Client machines should be on fast Ethernet connection (Gigabit Ethernet is recommended);
  • Performance degradation starts to occur when deduplication database is larger than 20 GB. It is thus recommended to limit the number of client machines to 10-20 per deduplication vault.

Setting up scheduled tasks to the deduplication vault

  • The indexing task can process only 20 GB of unique data per hour or 500 GB per day. So, please plan the scheduled tasks accordingly: if overall data stream during the backup will be more than 500 GB per day, such backup tasks will fail. In this case it is necessary to change the schedule, i.e. set the scheduled tasks to start every 3 or 4 days instead of everyday backups.

I would like to thank you for your patience and cooperation. Please accept our profound apologies for the miunderstanding and inconvenience caused, this will not happen again. Be sure that our Management team is aware of the situation.

Please let me know in case there is something still confusing you - I will be glad to clarify.

Thank you!

Tue, 06/22/2010 - 17:08
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 8

Thanks Yana.

currently my storage node is also my management server. It is a Dual processor, Quad Core Xeon CPU, 16Gb RAM. It has the Storage hosted on a NAS that has 16 x 2Tb SATA disks ( and will have another 24 at least in a week or two ) which over 8Tb free space currently ( soon to grow to be 20+TB free ). The NAS is connected to the Storage Node via a dedicated gigabit ethernet port. The Vault DB is on a FiberChannel attached LUN from our SAN which is striped across 16 x 15k SCSI disks, which outperforms local disk by a long way.

This to me suggests that our hardware is well above what you are suggesting to me already.

Given that I have dedup to happen at the source, what exactly is the index task doing ?

I currently have over 10Tb that I need to backup on a weekly basis. If the indexing task is unable to process more than 500Gb per day, then I think we're in a lot of trouble. And to be honest that 500Gb a day seems to be a very optimistic approach. I set up a single vault for a 1Tb volume and did a single backup. The index task has been running for 3 days 8 hours and is at 51%

Tue, 06/22/2010 - 19:08
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Dear Paul!

Thank you for your reply and for detailed answer.

You are correct, the hardware is far better than we're suggesting so this shouldn't be the issue. So in case you have 1 deduplication vault for 1 ASN and separated the database and the vault, then everything should work perfectly well. There should also be no issues with processing 500 Gb, you are correct. Currently it's hard to say what's wrong, and I will make our Experts to look into this thread ASAP, and will keep you posted.

Thank you for your question, I'll be glad to shed the light to the situation.

Indexing task is a part of deduplication process  (1. indexing task 2. compacting task). You can find the detailed description on how it works on page 75 in the User's Guide. The indexing task may take a considerable time to complete, and it depends on various circumstances like archive size, location of the vault, etc.

Indexing is performed for the chain of the backups starting from the latest full image. Thus it starts the task for the full, than for the Incremental_1, than Incremental_2 and so until there are not backups left in the chain. I completely agree that deduplication may be too slow, and - according to the Experts team - we are working on improving the situation. Still Indexing task will be a resource-intensive process, as you can see.

I assume you've already seen KB article regarding deduplication, but will leave this link here, maybe it will be useful for those who'll visit this thread. We have also Product Management answers in this thread starting from comment #32, you may find it interesting.

I would like to thank you once again for understanding and patience -  I really appreciate it.

Tue, 06/22/2010 - 19:51
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 0
Comments: 4
Paul Czarkowski wrote:

So I tried your idea. I backed up a single volume to it's own Vault ... It was just over 1Tb and was compressed/deduped down to show an Occupied space of '745.7 GB'. The Indexing task has been running for 2 days and 3 hours and is only at 34%. Does this not seem a little crazy ?

Hello all,

I am glad to have found this interesting thread. I am having exactely the same problem. A simplified explanation is: I backup 1 Server to 1 Depot over one Storage Node. I Backup the system and one data disk seperately. The system disk does not take long but my 1,5 TB data disk (750GB used storage) takes approx. 24 hours to backup. The index task is always running. I cannot stop it. Even if I try to stop it, its only trying to stop but the management server keeps on indexing. When I restart the mgmnt server the index task restarts itself.

The indexing of 600 GB compressed files is taking days already. And I am still under 10%. The mgmnt server runs with 50% cpu constantly.

The main problem is I cannot even complete a differential backup of these files in one night. Even a diff backup takes more than 20 hours while indexing runs. (I guess, because since I started with Acronis indexing is running and has never finished...)

Even my transfer rates are very slow. At 10 MB/s I cannot expect a fast backup. I should at least get 30-45 MB/s considering my network, server and backup depot.

Ironically the same backups with Acronis True Image for Server v9 took full only 9 hours and 2 with a diff backup. All possible to let it run at night.

Right now my dedup rate is non exsitent. All backups use full space. I guess this is because it was never indexed and compressed.

I even talked to the german support about this. I had the feeling he did not really understood what I was talking about. He just said the index task had to be completed. But this would take all summer long... My backup strategy would start working around christmas time.

If there is a solution to this problem I would greatly appreciate it!!

Greeting from Germany!

Wed, 06/30/2010 - 14:32