Consolidating unmounted and open snapshots after virtual machine backup

At times, one or more disks from a virtual machine will remain mounted and snapshots will remain following the backup of a virtual machine. The cause of this is generally due to their not being enough time to unmount the disks and consolidate the snapshots when the job completes. This would require user interaction to … More Consolidating unmounted and open snapshots after virtual machine backup

Configure vRanger Date Format to use system locale

The date format within the vRanger Backup & Replication product, does not use the system locale and by default is configured to use ‘en-US’ . In order for the date format to use the system locale, you will need to remove the default ‘ForceCulture’ value in the ‘C:\Program Files\Dell\vRanger\Vizioncore.vRanger.Client.Shell.exe.config’ file. The default value is as … More Configure vRanger Date Format to use system locale

Using a least privilege user account for vRanger

I was recently configuring a vRanger deployment to which I wanted to configure the service account running the various services to run under the context of a least privelage user. The service account will require log on as a service permissions, db_owner permissions to the vRanger database on the SQL Server instance and also write … More Using a least privilege user account for vRanger

vRanger Pro Powershell: Could not connect to http://localhost:2480/VAPIHost.svc

I recently compiled a number of powershell scripts (https://deangrant.wordpress.com/2013/10/01/report-job-status-from-vranger-to-nagios/)  with the vRanger Pro Powershell snap-in which queried the job status, using the Get-JobTemplate cmdlet. I have since noticed I have received an error message on a number of occasions where the status is failed to be retrieved with the following: Get-JobTemplate : Could not connect … More vRanger Pro Powershell: Could not connect to http://localhost:2480/VAPIHost.svc

vRanger backup jobs fail with host could not be identified

I recently was investigating an issue where backup jobs in vRanger failed for all VMs with the following error message: An internal error occurred during execution, please contact Quest support if the error persists. Error Message: <VM>’s host could not be identified This appears to be an inventory issue between vRanger and the vCenter server … More vRanger backup jobs fail with host could not be identified