Table of Contents
Advertisement
Figure 6: vRanger Resource Management
The configuration options available are:
•
•
•
•
•
8
Maximum number of task running on vRanger (>=1): This value limits the total number of simultaneous tasks for the
vRanger machine. This is affected by machine type and hardware as well as deployment architecture. The default
value is 100, which does not normally need to be changed as other limits take effect before this value is reached.
Maximum number of task running off a LUN (1–5): In order to avoid storage I/O contention issues, it is
recommended to limit the number of tasks that can be processed based on their storage location. vRanger defaults
to a limit of three backup tasks per LUN. Note: This assumes a 1:1 mapping between the underlying LUN and the
Datastore.
Maximum number of tasks running on a host (1–4): This setting should be set fairly low as all of the backup
processing (for Service Console backups) occurs on the host. The default per-host limit is set to one. Due to the
amount of CPU and memory used by the host to process backups, it is recommended to use caution when changing
this value.
Maximum number of tasks running per Repository (>=1): Bandwidth to the Repository is the main limiting factor
here. For the StoreOnce Backup System on a Gigabit network the recommendation is a maximum of three
concurrent backups, which can consume 75 percent of the bandwidth of the Repository. Monitor network utilization
in the StoreOnce Backup System web GUI. Consider use link aggregation or 10GbE network for increased
throughput.
Maximum number of tasks running locally (1–20): This option applies to the Hot Add and Proxy Server modes of
vRanger and limits the number of simultaneous tasks on the vRanger server. The recommended maximum is one
task per CPU core for the Proxy Server mode and one to two tasks per vCPU for the Hot Add mode (start with one
task per vCPU and increase if CPU allows). Also reserve 1 one core/vCPU for the operating system and vRanger.
For example, a quad-core physical machine or four vCPU virtual machine is able to run three simultaneous
backups. Monitor CPU utilization and increase number of CPUs if needed to be able to process more backups
(see the licensing section below).
Advertisement
Table of Contents
