지금 지원 담당자와 채팅
지원 담당자와 채팅

vRanger 7.8 - User Guide

Introduction Configuring vRanger
Configuration overview Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore Replicate VMs Reports Integrating and monitoring vRanger Using the vRanger Console vAPI Cmdlet details
Add-BackupGroupEntity 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-InventoryEntity 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

Performing a full restore of a physical machine

Previous Next


Restore > Performing a full restore of a physical machine

IMPORTANT: The procedures for creating a bootable CD differ widely depending on the operating system and software used. The following procedures show how to use the native Windows® 7 utility to create a bootable CD. If you have a different image burning application, follow the instructions for that application.
2
3
If necessary, copy the vzRestore-<version>.iso file to the machine with the writable CD/DVD drive.
4
Right-click the ISO file, select Open with, and then click Windows Disk Image Burner.
6
Click Burn.
NOTE: There are no native Windows® utilities for creating a bootable USB drive from an IMG file. The following procedure was created using a freeware application, Image Writer for Windows. Follow the instructions for your application.
2
Download the vRanger BMR Restore Image (IMG Bootable USB Drive) file from http://support.quest.com/vranger.
3
If necessary, copy the vzRestore-<version>.img file to the machine with the blank USB drive.
5
In the Device drop-down list, ensure that the correct USB drive is selected.
6
Click Write.
7
Click Exit.
If no DHCP server is detected, each Ethernet device shows as “Disconnected.” Select the preferred network device. If only one device is present, it is automatically selected. Press Enter to select the highlighted network interface. You are then prompted to select either Use DHCP, which attempts to obtain an IP address again, or Configure Static IP.
3
Press Enter to select the highlighted network interface.
You are then prompted to select either Use DHCP, which attempts to obtain an IP address again, or Configure Static IP.
5
In the Setting Static IP dialog box, enter the IP address, subnet mask, and gateway information, and then select Submit.
1
3
In the Working Repository pane, select a savepoint to restore.
NOTE: For the procedures on restoring from a manifest file, see Performing a full restore from manifest for VMware VMs.
Click Next.
1
On the Disk Mapping page, in the Restore Machine IP Address field, enter the IP for the target server; for more information, see Booting the target server.
2
Click Map Disks.
3
For each disk you want to recover, select the appropriate target disk in the Restore to Disk drop-down menu; for disks that you do not want to recover, select Skip this Disk.
4
Click Next.
1
On the Recurrence Schedule Selection page, select from the options described in the following table.
Daily: The daily option can be scheduled to run the report every weekday or every x number of days.
Weekly: vRanger can be configured to run on weekly intervals, from every week to every 99 weeks. The day of the week on which to run reports can be configured.
Monthly: The monthly option offers the following configurations:
Day [x] of every [y] month:
x can be any value from 1 to 31. This value determines the day of the month on which the job occurs.
y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the job to run every other month.
The [f] [d] of every [y] month(s):
f can be either: first, second, third, fourth or last.
d can be: weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
y can be any value from 1 to 99. This value determines the monthly interval — for example, every two months sets the report to run every other month.
Yearly: The yearly option offers the following configurations:
Every [m] [x]:
m is any month of the year. This value determines the month of the year in which the report occurs.
x can be any value from 1 to 31. This value determines the day of the month on which the report occurs.
The [f] [d] of [m]:
f can be either: first, second, third, fourth, or last.
d can be: day, weekday, weekend day, Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, or Saturday.
m is any month of the year. This value determines the month of the year in which the report occurs.
Interval: The interval option lets you select the number of days, hours, and minutes that should pass between jobs.
No end date: The job recurs until it is stopped.
End after: Select the number of occurrences.
End by: Select the date by which to end the recurrence.
2
Click Next.
To add or edit email addresses, see Setting up the SMTP server.
1
On the Email Notification Selection page, in the Selected column, select the address to which notifications should be sent.
2
Click Next.

Starting the restore job

Previous Next



1
On the Summary page, review the data displayed in the tree view.
3
Click Finish.
c
In the Confirm Run Job dialog box, click Yes.
5
To check progress or confirm completion, click My Jobs, and then click Recent Jobs.

Performing an FLR on Windows

Previous Next


Restore > Performing an FLR on Windows

You can restore a file from a savepoint by accessing the File Level Restore command in the My Repositories view. FLR is accessible regardless of how the savepoints are sorted. You can right-click the savepoint in the Working Repository pane to select the command or you can click to select the savepoint and then click the FLR icon on the toolbar.
NOTE: If the volume was created on Windows Server ® 2012 or later, the vRanger machine must also use Windows Server 2012 or later to complete FLR. Older systems may not show data on GPT disks.

VMs with dynamic disks are not supported for FLR.

Performing an FLR using Catalog Search

Previous Next


Restore > Performing an FLR on Windows > Performing an FLR using Catalog Search

1
On the main vRanger UI, navigate to the My Repositories pane, and then select the repository in which you want to search.
Click the Catalog Search Icon .
On the Menu Bar, click the Tools menu, and then click Catalog Search.
The Catalog Search & Browse dialog box appears.
The Advanced option lets you limit the search to a repository or VM (savepoint).
5
Select the preferred savepoint, and click FLR for File Level Restore, or Restore for the Full Restore.
NOTE: Catalog searching supports the traditional wildcard character (*) in any position. The search string can be as short or as long as you prefer; however, the shorter the string, the longer the search takes. SQL Server® Express is limited to one CPU and 1 GB of RAM; a short search string — for instance, “dot” — could result in very slow searching, and SQL Server Express could run out of memory. To minimize performance issues during Catalog Search, make the search string as specific as possible.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택