Skip to main content
  • EN

Regarding the guidelines in the K10 documentation K10 Resource Requirements does the “Dynamic” specification of 1 core + 1GB RAM mean that this is required per concurrent policy/job run or that 1 core + 1GB RAM is generally suitable for 100 applications as the guide seems to indicate.

If the latter further assuming that some sort of internal throttling occurs if all 100 policies are set to run at the same point in time?

Trying to accurately gauge K10 backup processing insertion impact on cluster compute...

Hi Ronn,

 

This is a key note on the docs.kasten.io site:

“ Backup Requirements: Resources for backup are required when data is transferred from volume snapshots to object storage or NFS file storage. While the backup requirements depend on your data, churn rate, and file system layout, the requirements are not unbounded and can easily fit in a relatively narrow band. Providing additional resources can also speed up backup operations. To prevent unbounded parallelism when protecting a large number of workloads, K10 bounds the number of simultaneous backup jobs (default 9). The backup resource footprint is dynamic and scales down to zero when a backup is not being performed. “

By default, we will only run 9 concurrent backup jobs - each concurrent backup job requiring 1 core and .4 GB of ram in the cluster.

Thanks Adam! Not sure how I missed that but definitely did somehow...

Comment


Terms & Conditions