18
Chapter 2
Before You Install
Although there is no ability to throttle data transmissions from a source server vRanger can limit the
number of simultaneous backup tasks on a per-repository level.
Note: This configuration is a global configuration, meaning that it applies to all repositories.
2.6.3
Repository Size
There is no limit to the number of savepoints that can be stored in a vRanger repository. There are,
however, environmental limits on the size of a single directory. The available options, and their limits,
are described below.
Note: The volume limitations described in this section are limitations within the Microsoft Windows
environment.
Dynamic Disks - Dynamic disks contain dynamic volumes, including simple volumes, spanned
volumes, striped volumes, mirrored volumes, and RAID-5 volumes. A repository located on
dynamic disk volumes can be as large as 64 TB. For more information, see the Microsoft
TechNet article: http://technet.microsoft.com/en-us/library/cc773268(WS.10).aspx
2.7.0
Default Configuration- A standard volume, with an MBR partition on a basic disk, has a limit of
2 TB. This is the default configuration for Windows Server 2003. In this configuration, the
vRanger repository cannot exceed 2 TB.
GPT Volumes - GPT provides a more flexible mechanism for partitioning disks than the older
Master Boot Record (MBR) partitioning scheme that has been common to PCs. GPT partitions
are supported on Windows Server 2003, SP1 and later, and can reach up to 256 TB. For more
information, see http://www.microsoft.com/whdc/device/storage/GPT_FAQ.mspx
Configuring vCenter Permissions
vRanger requires a vCenter account to function properly. To comply with security best practices,
Quest recommends creating a vCenter user account with the minimum required permissions for
vRanger to use.
The procedures differ slightly depending on which version of vCenter you are using. For vSphere 5.x,
see the section below. For vCenter 4.0, please see vSphere 4.x.
2.7.1
vSphere 5
The permissions required for backup and restore operations in a vSphere 5 environment differ
slightly from the permissions required for previous versions of vCenter. If you have migrated to
vSphere 5 after creating a vRanger user account, please update the permissions accordingly to
avoid job interruption.
To create a vRanger user on vSphere 5:
1. Navigate to Administration > Roles.
2. Select Add Role.
3. Enter a name for the role, such as “vRanger Non-Admin”.
4. In the Privileges section, set the permissions according the table below:
Section
Privileges
Datastore
Allocate space
Browse Datastore
Low level file operations
Remove file