vRanger 7.7 - Installation/Upgrade Guide

Bandwidth to repositories

Bandwidth to repositories

While performance varies based on environmental factors, data throughput during a single backup task can reach up to 100 MB/s. If you assume a standard case of a repository connected by using a Gigabit network, as little as 10 concurrent jobs can saturate the link to that repository.

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.

Repository size

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 in the following list.

 

NOTE: The volume limitations described in this topic are limitations within the Windows® environment.

•	Default configuration: A standard volume, with an MBR partition on a basic disk, has a limit of 2 TB. This configuration is the default for Windows Server® 2003. In this configuration, the vRanger repository cannot exceed 2 TB.

•	Dynamic disks: Dynamic disks contain dynamic volumes, including simple volumes, spanned volumes, striped volumes, mirrored volumes, and RAID-5 volumes. A repository on dynamic disk volumes can be as large as 64 TB.

•

GPT volumes: GUID partition table (GPT) volumes provide 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

Configuring vCenter permissions

vRanger requires a VMware® 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 VMware vSphere® 5 or later, see the following topic.

Using vSphere 5.5 or later

Using vSphere 5.5 or later

Starting with VMware vSphere® 5.5, the permissions required for backup and restore operations in a vSphere environment differ slightly from the permissions required for previous versions of VMware® vCenter™. If you have migrated to vSphere 5 or later after creating a vRanger user account, update the permissions accordingly to avoid job interruption.

To create a vRanger user on vSphere 5 or later:

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 to the following table:

 

Section	Privileges
Datastore	• Allocate space • Browse datastore • Low level file operations • Remove file
Global	•   • Licenses • Log event
Host > Local Operations	• Create virtual machine • Reconfigure virtual machine
Host > Inventory	• Modify Cluster
Network	• Assign network • Configure
Profile-driven storage	• Profile-driven storage view
Resource	• Assign vApp to resource pool • Assign virtualmachine to resource pool
vApp	• Add virtual machine • Assign resource pool • Create • Delete • Import • Move • Power Off • Power On • Rename
Virtual Machine > Configuration	• Select all privileges in this section
Virtual Machine > Interaction	• Configure CD media • Configure floppy media • Console interaction • Device connection • Power Off • Power On • VMware Tools Install
Virtual Machine > Inventory	• Create new • Remove •
Virtual Machine > Provisioning	• Allow disk access • Allow read-only disk access • Allow virtualmachine download • Allow virtualmachine files upload • Clone template •
Virtual Machine > Service Configuration	• Modify service configuration
Virtual Machine > Snapshot management	•   • Select all privileges in this section

5	Navigate to the Inventory view.

6	Right-click the applicable level to grant user permission, such as the main vCenter level, and click Add Permission.

7	Add and locate the applicable user account, select the recently created User Role, and click Add.

8

Click OK.

 

NOTE: When you add the vCenter to the vRanger inventory, use this account for authentication.