Chat now with support
Chat with Support

vRanger 7.6.4 - 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

Configuration overview

Previous Next


Introduction > Configuration overview

Configuration overview

vRanger requires some basic configuration before data protection can begin. The bulk of this configuration is driven by the Startup Wizard which starts the first time the application is opened. For more information, see Configuring vRanger.

The following topics describe the primary configurations you need to make.

•
Adding inventory for protection
•
Adding repositories
•
Deploying virtual appliances (VAs)
•
Adding physical servers to inventory
•
Scheduling a backup job
•
Scheduling a replication job

Adding inventory for protection

Before you can begin backups, you must add at least one of the following to the vRanger inventory:

•
One or more VMware® vCenter Servers™.
•
One or more Hyper-V® clusters.
•
One or more VMware® vCloud Director® servers.
•
One or more physical servers.
•
Individual Hyper-V® or VMware® ESXi™ hosts not associated with a cluster or vCenter.

To add a vCenter, you need to have credentials with administrator access to the vCenter, along with root-level credentials for each host managed by the vCenter. To add a Hyper-V cluster, you must have domain administrator privileges. You can exclude hosts from the vRanger inventory, which also excludes them from licensing.

Adding repositories

Previous Next


Introduction > Configuration overview > Adding repositories

Adding repositories

Repositories are where vRanger stores the savepoints created by each backup job. You can create a repository from a standard Network File System (NFS)or Common Internet File System (CIFS). You may also deduplicate vRanger backups by sending them to a Quest DR RDA, EMC® Data Domain® (DD Boost™), or Quest NetVault SmartDisk repository. To add a repository, you need the name of the server and share, and an account with access to that share. If you are using Quest RDA or DD Boost repositories, you can also set up repository replication with another repository of the same type. For more information on replication, see Managing repository replication.

Deploying virtual appliances (VAs)

Previous Next


Introduction > Configuration overview > Deploying virtual appliances (VAs)

Deploying virtual appliances (VAs)

vRanger uses a VA for replication to and from VMware® ESXi™ servers, for Linux® FLR, and optionally for backups and restores. Before fully utilizing vRanger, you need to deploy and configure VAs to your ESXi servers. For more information, see the Quest vRanger Installation/Upgrade Guide.

Adding physical servers to inventory

Previous Next


Introduction > Configuration overview > Adding physical servers to inventory

Adding physical servers to inventory

vRanger includes the ability to back up and restore physical servers. Before you can back up a physical server, you must add it to the vRanger inventory and supply credentials with Administrator access to the server.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating