Chat now with support
Chat with Support

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

Configuring datastore monitoring

Previous Next



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.

To configure datastore 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 datastores.

This setting is the threshold value for a datastore space before a warning is sent. This value is modified by the DatastoreMonitoringSpaceThresholdType setting.

This value determines whether vRanger checks for percentage of free space or an absolute value in GB. Set “0” for percent, “1” for GB.

How often vRanger checks the datastores for low space (in minutes) — the default is 30 minutes.

The maximum number of times a particular datastore monitor failure can be logged to the Windows event log before a success — the default is 7.

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 datastore that has reached its space threshold value after the FailureLogMax value has been reached. The default is 6, which indicates it logs an event every six hours.

Restarting the Quest vRanger Service

Previous Next



Restarting the Quest vRanger Service

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

To restart the service:
2
Type “services.msc” and click OK.

 

Using the vRanger Console

Previous Next



Using the vRanger Console

vRanger Console overview

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.

The snap-in includes the vAPI cmdlets required to create and manage jobs and view relevant information data reading your virtual environment.

For more information on PowerShell, see https://technet.microsoft.com/library/dn425048.aspx.

Configuring the vRanger Console

Previous Next


Using the vRanger Console > Configuring 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.

To configure the vRanger Console:
1
Click Start > All Programs > Quest > vRanger Backup & Replication > vRanger Console.

When opening the vRanger Console for the first time, you see an error message stating that the execution of scripts is disabled on your system. This issue is due to the default PowerShell execution policy, which must be enabled.

When the vRanger Console restarts, you should see a screen with a blue background and a list of vAPI cmdlets.

The vRanger vAPI is now configured and ready for use.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating