Backup Several Machines Simultaneously

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 5

We will have 1G network backbone for the backup system and about 60 machines (15G of data/each) require backed up.
1. With regards to the network consumption and CPU loading for the Storage Node, how many machines can I include in the same scheduled backup plan to back them up (Disk/Volume backup) simultaneouly? What will be the best practice?
2. I know for some other backup software, you can set up the parameter in the backup plan to limit number of disk/volume backups simutenously. For example, i only allow 4 machines to be backup at one time. But I don't see such a parameter for Acronis. Is that ture?
3. What will happen if i include the disk/volume backup for all 60 machines in one plan? For example, if the best practice is for 5x machines to be backep simutenously, do need need to set up 12 backup plans for all 60 machines?
4. If I separate two backup plans in two different time windows, and the data in these two plans are to be backed up to the same centralized deduplication vault with deduplication enabled, what will happen if the second backup plan starts when the first one has not finished? Will the first backup plan locks up the vault and I get an error for the second backup plan or the second backup plan just wait for the first plan to finish first?
5. If I have a centralized vault set up on the management server/storage node (same machine), when i set up a plan to do a disk back up for the management server, will the software smart enough to exlude the data in the centralized vault from backing up?

Thanks!

Tue, 10/30/2012 - 21:37
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 0
Comments: 1379

Storage node has parameters that limit number of simultaneous connections and backup operations that it can perform. They are configured via administrative template ( http://www.acronis.com/support/documentation/ABR11.5/index.html#15436.h… ) or directly in HKLM\SOFTWARE\Acronis\ASN\Configuration\StorageNode branch.
They apply to the storage node as a whole, regardless of number of vaults on it.
Some of them are
BackupQueueLimit
ClientConnectionLimit
FastOperationQueueLimit
I failed to find their exact meaning except for what is written in the explanation in the administrative template.

You can set 'distribute start time' in schedule options to distribute start time randomly within specified range.
Deduplication on agent side torned on may reduce network load. Starting all 60 initial full backup in the same time to the same storage node is definitely bad.

Now some numbered answers -

1. It depends on amount of data backed up in each backup if it is not configured as full backup daily.

3. Some backups will succeed, other connections will be rejected by Storage Node and either will continue reattempts until Storage Node allows the operation or will fail.

2/4 It doesn't matter if they belong to the same plan or not. Each agent, after centralized plan was deployed on it, performs backups independently. Storage node separates backup from each agent internally and it doesn't matter if they are backup up as a part of the same backup plan or not.

5. No . You need to exclude these explicitly.

Wed, 10/31/2012 - 09:24