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

Integrating and monitoring vRanger

Previous Next


Integrating and monitoring vRanger

Integrating vRanger: overview

Like any component of your virtual infrastructure, vRanger can be used with other applications to achieve more complex tasks.

•
Performing vRanger sweep-to-tape using Quest NetVault Backup
•
Using deduplication with Quest NetVault SmartDisk and vRanger
•
Using Data Domain and vRanger repositories

Performing vRanger sweep-to-tape using Quest NetVault Backup

Previous Next


Integrating and monitoring vRanger

Integrating vRanger: overview

Like any component of your virtual infrastructure, vRanger can be used with other applications to achieve more complex tasks.

•
Performing vRanger sweep-to-tape using Quest NetVault Backup
•
Using deduplication with Quest NetVault SmartDisk and vRanger
•
Using Data Domain and vRanger repositories

Performing vRanger sweep-to-tape using Quest NetVault Backup

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Performing vRanger sweep-to-tape using Quest NetVault Backup

Performing vRanger sweep-to-tape using Quest NetVault Backup

Sweeping vRanger backups to tape using NetVault Backup lets you combine the vRanger high-speed backup and recovery capabilities with the NetVault Backup inexpensive, long-term offsite-storage technology.

To configure the vRanger sweep-to-tape feature, both vRanger and NetVault Backup must point to a common vRanger repository folder located locally on the vRanger server.

The vRanger backup administrator creates an on-demand (not scheduled), incremental job with a specific name, appending -Tape as a case-sensitive suffix — for example, any-jobname-Tape. The -Tape suffix can be changed by editing the Windows PowerShell® script if you prefer something else. There should be a dedicated repository for each on-demand job.

The tape backup software administrator schedules a recurring incremental backup job whose PRE field calls a .cmd file containing the PowerShell script that searches for and then starts the vRanger on-demand jobs with the -Tape suffix.

The vRanger on-demand job performs the incremental backup, placing the savepoint files in the repository and updating the repository’s global manifest file.

After the vRanger job completes — for example, the job status equals either success or failure — the PowerShell script exits, thus completing the PRE command.

With the PRE command of the tape backup software completed, the tape backup software, which is also pointing to the vRanger repository folder, runs its scheduled incremental job, backing up the vRanger savepoints and global manifest file to tape.

To perform vRanger sweep-to-tape using NetVault Backup, complete the following tasks:

•
Ensuring that system requirements are met
•
Checking the list of prerequisites
•
Preparing the systems
•
Preparing for vRanger sweep-to-tape using NetVault Backup
•
Performing backup operations
•
Performing restore operations

Ensuring that system requirements are met

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Performing vRanger sweep-to-tape using Quest NetVault Backup > Ensuring that system requirements are met

Ensuring that system requirements are met

For vRanger:

•
vRanger on Windows Server® 2008, 2008 R2, or 2012.
•
Virtual or physical machines protected by vRanger.

For NetVault Backup:

•
A properly configured NetVault Backup Server.
•
Single Stand-Alone External Tape Drive or a Single Internal Tape Drive in a Library. For example, Quest PowerVault LTO standalone and library-based tape devices are ideal for this solution.
•
Windows Server 2008, 2008R2, or 2012.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen