An issue currently exists in vRanger where backups are consuming memory on the vRanger machine which results in failed backups.
Errors associated with this issue are:
"Error Message: 2129 - can't write cifs:Repository_Name;user@192.168.0.1/File_Path/GlobalManifest.metadata"
&
"Error Message: Exception of type 'System.OutOfMemoryException' was thrown."
A memory leak issue with the vRanger processes in certain conditions is causing vRanger to become unresponsive.
A workaround for this issue is to use a restart script (attached) together with Windows Task Scheduler once a day, when tasks are not running. This is a Powershell script that requires the Powershell Snapin to be enabled.
The script does the following when executed:
1. Checks if Powershell Snapin is Enabled
2. Checks if jobs are currently running (If jobs are running, services will not restart)
3. If jobs are not running the following services will be stopped: vRanger API Service,
vRanger FLR Service, vRanger Service; the following processes will be stopped also: vddk, backup
The following KB shows how to schedule a Powershell Script using task scheduler in Windows 2008 R2: https://support.quest.com/SolutionDetail.aspx?id=SOL92676
As of the release of vRanger 6.0.2 dated March 26 2013 this defect is fixed please visit vRanger downloads page to upgrade\ install vRanger 6.0.2
http://support.quest.com/softwaredownloads.aspx?pr=268446589
