If the client option RESOURCEUTILIZATION is set to a value that is greater than the default, the concurrent workload for the server increases.
number of clients x sessions for each client x files stored
during each transaction x log space needed for each fileThis calculation is used in the example in the following table.
| Item | Example values | Description | |
|---|---|---|---|
| Maximum number of client nodes that back up, archive, or migrate files concurrently at any time | 300 | 1000 | The number of client nodes that back up, archive, or migrate files every night. |
| Possible sessions for each client | 3 | 3 | The setting of the client option RESOURCEUTILIZATION is larger than the default. Each client session runs a maximum of three sessions in parallel. |
| Files stored during each transaction | 4096 | 4096 | The default value of the server option TXNGROUPMAX is 4096. |
| Log space that is required for each file | 3053 | 3053 | The value of 3053 bytes for each file in
a transaction represents the log bytes needed when backing up files
from a Windows client where
the file names are 12 - 120 bytes. This value is based on the results of tests performed under laboratory conditions. Tests consisted of clients performing backup operations to a random-access disk (DISK) storage pool. DISK pools result in more log use than sequential-access storage pools. Consider a value larger than 3053 bytes if the data being stored has file names that are longer than 12 - 120 bytes. |
| Active log: Suggested size | 26.5 GB 1 | 51 GB 1 | The following calculation was used for 300
clients. One GB equals 1,073,741,824 bytes. (300 clients x 3 sessions for each client x 4096 files stored during each transaction x 3053 bytes for each file) ÷ 1,073,741,824 = 10.5 GB Increase that amount by the suggested starting size of 16 GB: 10.5 + 16 = 26.5 GB The following calculation was used for 1000 clients. One GB equals 1,073,741,824 bytes. (1000 clients x 3 sessions for each client x 4096 files store during each transaction x 3053 bytes for each file) ÷ 1,073,741,824 = 35 GB Increase that amount by the suggested starting size of 16 GB: 35 + 16 = 51 GB |
| Archive log: Suggested size | 79.5 GB 1 | 153 GB 1 | Because of the requirement to be able to
store archive logs across three server-database backup cycles, the
estimate for the active log is multiplied by 3: 10.5 x 3 = 31.5 GB 35 x 3 = 105 GB Increase those amounts by the suggested starting size of 48 GB: 31.5 + 48 = 79.5 GB 105 + 48 = 153 GB |
| 1 The example values
in this table are used only to illustrate how the sizes for active
logs and archive logs are calculated. In a production environment
that does not use deduplication, 16 GB is the suggested minimum size
for an active log. The suggested minimum size for an archive log in
a production environment that does not use deduplication is 48 GB.
If you substitute values from your environment and the results are
larger than 16 GB and 48 GB, use your results to size the active log
and archive log. Monitor your active log and adjust its size if necessary. |
|||