Converse agora com nosso suporte
Chat com o suporte

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

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.

Configuring replication monitoring

Previous Next



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.

To configure replication monitoring:
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.

Continue to the next topic to make additional changes.

Configuring virtual appliance (VA) monitoring

Previous Next



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.

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

Set this value to “true” to enable monitoring of the VA.

This setting is the maximum number of times that a particular VA failure can be logged to the Event log before a success. Change the value of “7” to the preferred value, ensuring the quotation marks remain.

This setting is intended to limit the number of messages in your event viewer. A refresher message appears periodically based on the next value.

This value determines how often the refresher message occurs for a failed VA check after the FailureLogMax value has been reached. The default is 6, which indicates that it logs an event every six hours.

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.

Continue to the next topic to make additional changes.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação