Chatta subito con l'assistenza
Chat con il supporto

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

Enabling VMware Changed Block Tracking (CBT)

Previous Next


Backup > Performing optional configurations > Enabling VMware Changed Block Tracking (CBT)

Enabling VMware Changed Block Tracking (CBT)

VMware® CBT reduces the time needed for incremental and differential backups by only backing up the portions of a disk that have changed since the last backup. By determining which blocks changed within the VMDK file, vRanger only backs up the portions of a disk that have changed since the last backup. This often results in shorter backup operations, and reduced resource consumption on network and storage elements.

VMware vSphere® supports CBT, and most VMs running in this environment can use it. The VMs must be Hardware Version 7 or later, and have been created and hosted in VMware® ESXi™ 5.0 or later hosts. VMs that are created in VMware® ESX® 4 or earlier must be migrated to Hardware Version 7 or later for CBT to be supported. CBT must be enabled for each VM with which CBT is to be used.

Change Block Tracking is enabled or disabled on a per-VM basis. There are two methods to enable CBT:

In the Options Selection page of the vRanger Backup Wizard, select Enable Change Block Tracking.
In the My Inventory view, right-click the VM for which want to change the CBT setting, and then select Enable Change Tracking. The Changed Block Tracking Icon appears next to any VM on which CBT is enabled.

Adding a custom backup group

Previous Next


Backup > Performing optional configurations > Adding a custom backup group

Adding a custom backup group

This feature lets you organize physical servers, Hyper-V® servers, or VMware® vCenter™ objects — VMs, hosts, and folders — into groups, which lets you create a backup job for only the selected nodes. This feature provides additional flexibility for creating backup jobs.

IMPORTANT: A backup group must contain only physical objects, only Hyper-V objects, or only VMware® objects. You cannot combine VMware, Hyper-V, and physical objects into a single backup group.
To add a custom backup group:
1
In the My Inventory view, select the VMware, Hyper-V, or Physical tab.
Click the Add Icon, and select Backup Group.
Expand the Backup Group panel in the Inventory pane. Right-click an empty spot, select Add, and then click Backup Group.
3
Enter a name for the Backup Group, and click to select the nodes to include in the group.
4
Click Add.

Your new backup group is listed in the Backup Groups pane.

You can edit or remove a group by right-clicking it and selecting Edit or Remove.

Configuring VSS tools for VMware VMs

Previous Next


Backup > Performing optional configurations > Configuring VSS tools for VMware VMs

Configuring VSS tools for VMware VMs

VSS Tools are only available for VMware® VMs and do not apply to Hyper-V® VMs or physical machines.

There are two ways to configure VSS Tools: automatically and manually. The following topics describe the procedures for the two available methods of configuring VSS Tools with vRanger.

Configuring VSS tools using the automated method

Previous Next


Backup > Performing optional configurations > Configuring VSS tools for VMware VMs > Configuring VSS tools using the automated method

Configuring VSS tools using the automated method

In addition to the standard quiescing implementation using VMware® Tools, vRanger provides an optional method for application quiescing on VMware VMs. This optional method uses a small executable tool — vzShadow.exe — deployed to the source VM and is enabled by VMware Tools during quiescing. The vRanger VSS Tools must be deployed to each VM for which you need application-consistent backups. For more information, see Application consistency for virtual backups.

NOTE: This method is available only for powered-on VMs running Windows Server® 2008 or later. For VMs running older Windows® operating systems, install vzShadow.exe manually, as described in Configuring VSS tools using the manual method.
To configure VSS tools using the automated method:
1
When viewing the My Inventory View, right-click the preferred VM, and select Configure VSS Tools.
2
When the Configure VSS Tools dialog box appears, enter the name and password for an account with administrative privileges on the VM, and click Next.

If the selected VM has more than one disk, the available disks are shown in the Disk for VSS snapshot section.

4
If preferred, select Perform application log truncation.
5
Click Configure, and click Next.

vRanger performs the following actions:

Creates the C:\Program Files\Quest\vRanger\VSS directory, and populate the directory with the vzShadow executable and supporting files.
Creates the C:\Program Files\VMware\VMware Tools\backupscripts.d directory, and creates a freeze.bat file in that directory that contains the appropriate contents based on your selections.
Removing VSS tools

To remove the vRanger VSS Tools and batch file from the source VM, complete the steps in the following procedure.

To remove VSS tools:
1
When viewing the My Inventory View, right-click the preferred VM, and select Configure VSS Tools.
2
When the Configure VSS Tools dialog box appears, enter the name and password for an account with administrative privileges on the VM, and click Next.
3
Click Remove.

The files are removed from the VM, but the directories remain.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione