Chatta subito con l'assistenza
Chat con il supporto

vRanger 7.8.5 - 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

Configuring replication monitoring

Replication monitoring logs replication task failures to the Windows® event log with the Event ID of 10001. The log also includes the error message and information about the task such as source VM, target host, and vCenter.

1
In the Vizioncore.vRanger.Service.exe.config file, scroll to line 162 or search for Replication FailureWriteEventLog.
2
Change the value “false” to “true”, ensuring the quotation marks remain.

Configuring virtual appliance (VA) monitoring

When enabled, at the specified interval, the vRanger VA monitor goes through all the configured VAs and checks to make sure that their power is turned on. The vRanger VA monitor also verifies that vRanger is able to connect to the VAs using the specified IP addresses and credentials.

1
In the Vizioncore.vRanger.Service.exe.config file, find the lines corresponding to the preferred setting:
This setting determines how often vRanger checks the connection to configured VAs. The default is 5, which indicates that it checks the connection every five minutes.

Configuring datastore monitoring

When enabled, at the specified interval, the datastore monitor goes through all the configured datastores and determines if the space available on the datastore exceeds the specified threshold. This check might be either by percentage or a specific value in gigabytes. When this exception occurs, an event is logged in the Windows® event log with an ID of 12000.

1
In the Vizioncore.vRanger.Service.exe.config file, find the lines corresponding to the preferred setting:

Restarting the Quest vRanger Service

For the changes to take effect, you must restart the vRanger Service.

2
Type “services.msc” and click OK.

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione