Converse agora com nosso suporte
Chat com o suporte

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

Adding a physical machine

Previous Next



Adding a physical machine

The Physical Machine Information page appears. Before vRanger can add physical source objects to the My Inventory pane, you must configure a connection to a physical server.

To add a physical machine:
1
In the Physical Machines section, click Add.
2
In the DNS Name or IP field, enter the FQDN or IP address of the server.
3
In the User Name field, enter an account for the server.
4
In the User Password field, enter the password for the preceding account.

In the Agent Location field, enter the preferred directory — on the physical machine — to which the physical client should be installed. The default is C:\Program Files\Dell\vRangerPhysicalClient.

6
In the Port Number field, enter the preferred port for vRanger to use to communicate with the physical client on the source server.

This port must be open between vRanger and each physical server — the default is 51000.

7
Click Connect.

The server appears in the My Inventory pane. You may also create a backup group to combine multiple physical servers into one backup job. For more information, see Adding a custom backup group.

Selecting physical machines for licenses

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Selecting physical machines for licenses

Selecting physical machines for licenses

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 on this page.

To select physical machines for licenses:
1
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.

2
In the Physical Backup column, select or clear machines until you have used all the available licenses, or until all your machines are protected.
3

Deploying and configuring the VA from the Startup Wizard

Previous Next


Configuring vRanger > Configuring vRanger through the Startup Wizard > Deploying and configuring the VA from the Startup Wizard

Deploying and configuring the VA from the Startup Wizard

vRanger uses a virtual appliance (VA) for Linux® file-level restore (FLR), standard backup and restore, and for replication to and from VMware® ESXi™ servers.

There are two ways to deploy and configure a VA: the Startup Wizard and the Tools menu.

If you do not want to complete the Virtual Appliance Information page of the Startup Wizard now, you may skip this step and continue with the Startup Wizard. You can access the Virtual Appliance Configuration dialog box at any time by way of the Options available from the Tools drop-down menu.

To complete the Virtual Appliance Information page of the Startup Wizard and deploy and configure a VA now, complete the following procedure.

To deploy and configure the VA from the Startup Wizard:
1
On the Virtual Appliance Information page of the Startup Wizard, start the Virtual Appliance Deployment Wizard from the Startup Wizard by clicking Deploy Virtual Appliance.
3
To add a VA configuration, click Add, and then complete the following steps:
a
In the Add Virtual Appliance Configuration dialog box, select a VA from the inventory tree.
b
Under Virtual Appliance Properties, do any of the following:
Select Override IP Address, and then enter a new IP address in the IP Address field.
Select Use as default virtual appliance for cluster, to use this VA for all machines that are a part of the associated cluster.
c

In the Modify Virtual Appliance Configuration dialog box, edit any of the following settings:

For more information, see Changing the VA configuration.

b
Click Remove.

The Removing VA dialog box appears.

d
In the Confirm Delete dialog box, click OK.

If you want to remove the entire VA rather than a single job, first select Delete the virtual appliance from the host, and then click OK.

7
Click Next.

Adding a repository

Previous Next



Adding a repository

vRanger uses repositories to store backup archives. vRanger supports the following options for repository connections.

Windows Share (CIFS)

NFS (version 3)
NetVault SmartDisk (NVSD): The Quest disk-based data-deduplication option which reduces storage costs with byte-level, variable-block-based software deduplication. For more information on NetVault SmartDisk, see http://quest.com/products/netvault-smartdisk/ or the Quest vRanger Integration Guide for Quest NetVault SmartDisk.
EMC Data Domain Boost (DDB): Integrating EMC Data Domain Boost (DD Boost) with vRanger is achieved by adding a Data Domain appliance running DD Boost to vRanger as a repository. Backups written to that repository are deduplicated according to your configuration. For more information on DD Boost, see http://www.emc.com/data-protection/data-domain/data-domain-boost.htm or the Quest vRanger Integration Guide for EMC Data Domain Boost (DD Boost).
Quest Rapid Data Access (RDA): Provided by the Quest DR Series appliances — purpose-built, disk backup appliances that use Quest deduplication technology to improve backup and recovery processes. For more information on Quest DR Series appliances, see http://quest.com/products/dr-series-disk-backup-appliances/ or the Quest vRanger Integration Guide for Quest DR Series Disk Backup Appliance.

The following procedure shows mounting a CIFS share to the My Repositories pane. The procedures for the other repository types are described in Supplemental instructions: additional repository types

To add a repository:
1
Under Repositories, select Windows Share (CIFS).
2
Populate the Repository Name field.

This value appears in the My Repositories pane.

3
Populate the Description field.
4
Enter a username and password in the appropriate fields.
5
Select a Security Protocol from the drop-down list: NTLM (Default), or NTLM v2
6
In the Server field, type the UNC path to the preferred repository directory.

Alternatively, enter a partial path, and click Browse to find the target directory.

CAUTION: If you use the Encrypt all backups to this repository feature, make certain to retain the password you enter. There is no back-door or administrator-level password. If the password is unknown, the backups are not usable.
7
If you want these backups password-protected, select Encrypt all backups to this repository, enter a Password for the encrypted repository, and then confirm the password by re-entering it.
NOTE: Encryption is not supported for NetVault SmartDisk and DD Boost repositories.
9
Click Save.

The connection to the repository is tested and the repository is added to the My Repositories pane and the Repository Information dialog box.

vRanger checks the configured repository location for existing manifest data to identify existing savepoints.

Import as Read-Only: To import all savepoint data into the vRanger database, but only for restores, click this button. You cannot back up data to this repository.
Import: To import all savepoint data into the vRanger database, click this button. vRanger is able to use the repository for backups and restores. vRanger requires read and write access to the directory.
Overwrite: To retain the savepoint data on the disk and not import it into vRanger, click this button. vRanger ignores the existence of the existing savepoint data and treats the repository as new.
11
Click Next.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação