Converse agora com nosso suporte
Chat com o suporte

vRanger 7.8.5 - User Guide

Introduction vRanger overview Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring an encrypted VMware VM Performing a full restore for VMware VMs Performing a full restore for Hyper-V® VMs Performing a full restore for VMware vApps Performing a full restore of a physical machine Performing an FLR on Windows Performing an FLR on Linux Restoring from manifest
Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details

Managing physical machine licensing

Before you start this process, make sure that you have imported the license file and confirmed that it is adequate for managing the number of physical machines you want to protect. The Currently Installed Licenses section includes the total number of physical machine licenses available, and the number being used currently. These numbers increment and decrement based on the selections you make in this dialog box.

To manage physical machine licensing:
1
On the Main toolbar, click Tools > Options.
2
Under the Licensing node, click Physical Machine.
3
In the Currently Installed Licenses section, view the Machines Allowed value to confirm the total number of physical machines licenses available.
The number of licenses currently allocated is shown in the Machines Used column.
The Licensed Physical Machine section lists the physical machines in the vRanger inventory, and indicates whether each machine is licensed for backup.
4
In the Physical Backup column, select or clear machines until you have used all the available licenses, or until all your machines are protected.
5
Click OK.

Managing job configuration settings

Through the Configuration Options dialog box, you can set limits for the number of tasks running, the time frame for task execution, and the space allowed on a datastore to accommodate snapshot growth.

The maximum number of tasks are defined in the following table.

 
Table 1. Maximum number of tasks

On vRanger

The maximum number of backup, restore, and replication tasks running on this instance of vRanger at any one time.

off a LUN

The maximum number of tasks allowed on any particular logical storage device.

on a host

The maximum number of tasks running on a host at any given time.

per repository

The maximum number of tasks allowed on any specific repository at any specific time.

locally

The number of backup and restore tasks that are physically running on the local vRanger machine.

per VA

The number of replication tasks running on a vRanger virtual appliance (VA).

To manage job configuration settings:
1
On the Main toolbar, click Tools > Options.
2
Under the My Jobs node, click Configuration.
3
In the Resource Management section, set a maximum for the number of tasks that can be run:
•
On vRanger (>=1): Default is 100.
•
Off a LUN (1 to 5): Default is 3.
•
On a host (1 to 4): Default is 1.
•
Per repository (>=1): Default is 3.
•
Locally (1 to 20): Default is 3.
•
Per VA (1 to 18): Default is 2.
4
In the Timeout section, populate the Task Timeout (1 - 999 hours) field — the default is 24.
5
In the Minimum space needed on host (GB) field, enter a number — the default is 6.
6
Click OK.

Enabling cataloging options

The vRanger cataloging function must be enabled before data collection can begin. The Catalog dialog box includes the option to enable or disable catalog collection, and displays the status of the Catalog Service.

 
* 
NOTE: For Catalog collections to function, the Catalog Service must display a status of “Running.”
To enable cataloging options:
1
On the Main toolbar, click Tools > Options.
2
Under the My Jobs node, click Catalog.
3
Select Enable Catalog Data Collection.
4
Click OK.
 
* 
NOTE: Cataloging must also be enabled for each backup job for which you want to collect catalog data.

About catalog filtering

While there are thousands — or hundreds of thousands — of files in a typical VM, most are not relevant to FLR operations. To streamline cataloging operations, and reduce impact to the catalog database, vRanger filters files to be indexed in two ways:

•
Path: By default, vRanger does not catalog any files in the following directories. Path filtering is determined by entries in the PathFilterTokens.txt file, at C:\Program Files\Quest\vRanger\Configuration.
 
 

 

Program Files

Windows

$Extend

$TxfLog

$Txf

RECYCLER

System Volume Information

I386

•
File: By default, vRanger does not catalog files of the following type. File filtering is determined by entries in the FilesFilterTokens.txt file, at C:\Program Files\Quest\vRanger\CatalogManager\Config\Files.
 
 

 

.lnk

$MFT

$Volume

$AttrDef

$BitMap

$Boot

$BadClus

$Secure

$UpCase

$Quota

$ObjID

$Reparse

$RmMetadata

$Repair

$Tops

$TxfLog

 
* 
NOTE: File filtering applies to un-filtered paths. If a path is filtered, files in that path do not need to be.

For most situations, the default filtering options are sufficient. If you want to filter out additional paths or files, simply add the path or file to the appropriate text file.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação