Chat now with support
Chat mit Support

vRanger 7.6.3 - User Guide

Introduction Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring a physical server 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
Add-BackupJobTemplate Add-CIFSRepository Add-DdbReplicationRepository Add-DdbRepository Add-EsxHost Add-HypervCluster Add-HypervHost Add-HypervRestoreJobTemplate Add-NFSRepository Add-NVSDRepository Add-PhysicalMachine Add-RdaRepository Add-ReplicationJobTemplate Add-RestoreFromManifestJobTemplate Add-RestoreJobTemplate Add-VirtualAppforLinuxFLR Add-VirtualAppforLinuxFLRVA Add-VirtualCenter Disable-Job Dismount-LinuxVolume Enable-Job Get-AddressBook Get-BackupGroupEntity Get-CatalogSearchData Get-CatalogStatus Get-ConfigOption Get-Connection Get-CurrentTemplateVersionID Get-Datastore Get-GlobalTransportFailover Get-InventoryEntities Get-IsInventoryRefreshing Get-Job Get-JobTemplate Get-MonitorLog Get-Network Get-PhysicalMachineDiskMap Get-Repository Get-RepositoryJob Get-RepositorySavePoint Get-RestoreDiskMap Get-SavepointDisk Get-SavepointManifest Get-Savepoints Get-TransportFailover Get-VirtualApplianceConfig Get-VirtualApplianceDeploymentStatus Get-VirtualApplianceReconfigStatus Get-VirtualMachinesUnderInventory Get-VmDisk Get-VMDKVolume Install-VirtualAppliance Mount-LinuxVolume New-BackupFlag New-BackupGroupMember New-Daily Schedule New-EmailAddress New-IntervalSchedule New-MonthlySchedule New-ReplicationFlag New-RestoreFlag New-SMTPServer New-TransportConfiguration New-VirtualAppliance New-WeeklySchedule New-YearlySchedule Remove-AllMount Remove-BackupGroupEntity Remove-BackupGroupMember Remove-Catalog Remove-DdbStorageUnit Remove-JobTemplate Remove-LinuxVolume Remove-Repository Remove-SavePoint Remove-VirtualAppliance Remove-VirtualApplianceConfiguration Run-JobsNow Run-ReplicationFailover Run-ResumeReplicationFailover Run-TestReplicationFailover Set-Cataloging Set-CBTonVM Set-LinuxVolume Set-MountPath Set-Resources Stop-vRangerJob Update-BackupJobTemplate Update-GlobalTransportFailover Update-HypervRestoreJobTemplate Update-Inventory Update-ReplicationJobTemplate Update-RestoreJobTemplate Update-VirtualAppliance Update-VirtualApplianceConfiguration
About us

Managing job configuration settings

Previous Next


Configuring vRanger > Configuring vRanger manually > Managing job configuration settings

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
3
In the Resource Management section, set a maximum for the number of tasks that can be run:
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

Enabling cataloging options

Previous Next


Configuring vRanger > Configuring vRanger manually > Enabling cataloging options

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.

To enable cataloging options:
1
2
Under the My Jobs node, click Catalog.
3
Select Enable Catalog Data Collection.
4

About catalog filtering

Previous Next



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

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.

Managing Transport Failover options

Previous Next


Configuring vRanger > Configuring vRanger manually > Managing Transport Failover options

Managing Transport Failover options

Replication transport actions occur through HotAdd — LAN-free or network. If one transport method is not available, vRanger attempts to perform the replication task using one of the other transport methods. The order in which you should sort the transport options depends on what type of host you have. The VA-based Network option is the slowest of the three, and should be configured last. For VMware® ESXi™ hosts, configure the transport order to VA-based HotAdd > VA-based Network.

To manage transport failover settings:
1
2
Under the My Jobs node, click Transport Failover.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen