Skip to main content

Storage Node location number limit?

Thread solved

Good day,

 

I would like to find out if there is a limit to the number of locations that can be added to a single Storage Node?

Thanks for any assistance.

1 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Nick,

There is no hard limit (limit imposed by UI) to amount of vaults per Acronis Storage Node (ASN). Normally we see that no more than 10-20 vaults per ASN are created and that's the max amount we use in our internal QA testing. If you plan to use larger amount of vaults please clarify the scenario where this might be required. Likely we will be able to suggest a better way to manage the data than creating excessive amount of vaults.

The exception from this rule is recommendation to keep only 1 vault with enabled deduplication per ASN – this recommendation is present in deduplication best practices description in the documentation.

Thank you.

Hi Vasily,

Thank you for your response, I have no immediate scenario that requires a large number of vaults. I have a customer asking if there is a limit.

I wanted to also find out. Is this "soft limit" that you use in your QA environmnet due to performance concerns or ease of management? If one was to exceed 20 locations would performance suffer noticbly and would it be possible to "brute force" the performance hit with hardware upgrades?

Thank you again for your help

 

Nick.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Nick,

We don't use large number of vaults in our QA environment mostly to simplify the management of the tests - it takes less time to prepare the environment (including auto-tests flows) and it's easier to troubleshoot. In theory there should be no "hard stop" behavior when the number of locations increases - it should be close to linear performance impact, which can be mitigated with hardware upgrades (more RAM/CPU resources). Still we can't say for sure without specific testing which we haven't performed since there was no real scenario reported to us so far which would've required huge ASN-managed locations number.

P.S. Locations managed by ASN are designed to be a single connection point to backup storage used by multiple machines - that's the core value of ASN (besides deduplication) where the same secure channel is used to transfer the data over single port. This allows to get away from requirement to set up/secure SMB/sFTP/NFS "Agent<->storage" channels separately.

Thank you.