Chat now with support
Chat with 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

Using Data Domain and vRanger repositories

Previous Next


Integrating and monitoring vRanger > Performing vRanger sweep-to-tape using Quest NetVault Backup > Using Data Domain and vRanger repositories

Using Data Domain and vRanger repositories

vRanger and EMC® Data Domain® appliances provide a simple and efficient method for backing up and recovering VMware® environments. vRanger provides significant enhancements regarding architecture, performance, and communications over traditional backup solutions. Data Domain provides superior data de-duplication capabilities. The combination of vRanger and Data Domain Technology dramatically reduces your backup and recovery time for VMs on VMware® ESXi™ hosts.

For more information about integrating vRanger and Data Domain, see the Quest vRanger Integration Guide for EMC® Data Domain® Boost (DD Boost™).

Monitoring vRanger

Previous Next



Monitoring vRanger

vRanger can be configured to log events to the Windows® Event Viewer on the vRanger machine. These events can be filtered and monitored using the Microsoft System Center Operations Manager to monitor replication functions in line with other IT operations. When monitoring is enabled, vRanger creates a vRanger Service node on the local Event Viewer.

The events currently monitored and logged by vRanger include:

Replication task failure: logged as an error, event ID 10001

VA not powered on: logged as an error, event ID 11001

VA connection failure: logged as an error, event ID 11002

VA credential failure: logged as an error, event ID 11003

VA unknown failure: logged as an error, event ID 11999

VA return to normal: logged as an Information event, ID 11998

Datastore threshold exceeded: logged as an error, event ID 12000

Datastore unknown failure: logged as an error, event ID 12099

Datastore return to normal: logged as an Information event, ID 12098

About event monitoring configurations

Previous Next


Integrating and monitoring vRanger > Monitoring vRanger > About event monitoring configurations

About event monitoring configurations

The configurations for event monitoring are done by way of the configuration file for the Quest vRanger Service, Vizioncore.vRanger.Service.exe.config. This file is located in the vRanger installation directory. The default is C:\Program Files\Quest\vRanger.

Opening the configuration file

Previous Next



Opening the configuration file

Complete the steps in the following procedure to open the configuration file.

To open the configuration file:
1
Open the Vizioncore.vRanger.Service.exe.config file with your text editor of choice.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating