Chatee ahora con Soporte
Chat con el soporte

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

About event monitoring configurations

Previous Next


Integrating and monitoring vRanger > Monitoring vRanger > 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.
1
Open the Vizioncore.vRanger.Service.exe.config file with your text editor of choice.
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.
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.
1
In the Vizioncore.vRanger.Service.exe.config file, find the lines corresponding to the preferred setting:
2
Type “services.msc” and click OK.

Using the vRanger Console

Previous Next



vRanger uses Windows PowerShell® with a Quest snap-in to provide scripting access to vRanger features and functions. This feature lets vRanger integrate with other data protection solutions and offers an efficient configuration option for advanced users.

vRanger Console overview

Previous Next


Using the vRanger Console

vRanger uses Windows PowerShell® with a Quest snap-in to provide scripting access to vRanger features and functions. This feature lets vRanger integrate with other data protection solutions and offers an efficient configuration option for advanced users.

Configuring the vRanger Console

Previous Next


Using the vRanger Console > Configuring the vRanger Console

The vRanger installer automatically installs Windows PowerShell® 1.0 and the vAPI snap-in during the product installation. Before using the vAPI cmdlets, you must first configure the PowerShell execution policy to run the vRanger scripts. This process is a one-time configuration that does not need to be repeated.
1
Click Start > All Programs > Quest > vRanger Backup & Replication > vRanger Console.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación