Configuring datastore monitoring

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:

▪	DatastoreMonitoringEnabled: line 218

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

▪	DatastoreMonitoringSpaceThresholdValue: line 220

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

▪	DatastoreMonitoringSpaceThresholdType: line 222

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

▪	DatastoreMonitorCheckIntervalInMinutes: line 224

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

▪	DatastoreMonitoringEventLogFailureLogMax: line 227

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.

▪	DatastoreMonitorSecondaryIntervalInHours: line 230

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.

2	Save and exit the file.

Restarting the Quest vRanger Service

Restarting the Quest vRanger Service

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

To restart the service:

1	On the vRanger machine, click Start > Run.

2	Type “services.msc” and click OK.

3	Find the vRanger Service. Right-click the service, and click restart.

 

Using the vRanger Console

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

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.

2	At the prompt, type the following command, and press Enter.

Set-ExecutionPolicy RemoteSigned

 

NOTE: PowerShell and vAPI commands are not case-sensitive.

3	When the prompt re-appears, close and re-open the vRanger Console.

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.