Chat now with support
Chat mit Support

vRanger 7.8.3 - User Guide

Introduction vRanger overview Configuring vRanger
Configuring vRanger through the Startup Wizard Configuring vRanger manually Supplemental instructions: additional repository types
Using vRanger Backup Restore
Restoring an encrypted VMware VM 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 About us

Configuring email notifications

Previous Next


Restore > Performing a full restore of a physical machine > Creating the boot media > Configuring email notifications

Configuring email notifications

The Email Notification Selection page lets you select the email addresses to which notifications should be sent for this job. You can also request that a report be sent to the recipients identified after the job is complete.

To add or edit email addresses, see Setting up the SMTP server.

To configure email notifications:
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



Starting the restore job

The final page in the Restore Wizard displays a summary of the selections you made for the job.

To start the restore job:
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

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.

There is no need to copy or recreate the contents of the disk. The data remains compressed. When you make an FLR request, only the relevant files are moved from the repository to the designated computer.

A key component of the vRanger FLR is the vRanger catalog functionality. While you can use FLR without cataloging enabled, it is much easier to find a preferred file by using a catalog search than through manual browsing of savepoints.

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

Performing an FLR using Catalog Search

Cataloging lets you search and browse savepoints for files inside the backup archives. Cataloging must be enabled at the start of the backup job to function, and also enabled globally in the Configuration Options dialog box.

Catalog Search has the following parameters:

To perform 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.

Entering a search string in the Catalog Search Criteria field searches all repositories and savepoints for the string.

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.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen