Quantcast
Channel: Software Communities : Popular Discussions - vRanger
Viewing all 1662 articles
Browse latest View live

Get-InventoryEntity Issue

$
0
0

Hello and thanks in advance!

 

Im hitting a strange issue with vRanger 6.0.1 and 6.0.2 trying to run Get-InventoryEntity.

 

I'm trying to extract all the active backup job VM names to combine with a script to clean out our repo's. Im working through piece by piece to understand vRanger's structure and data model. I'm trying to follow https://support.quest.com/SolutionDetail.aspx?id=SOL102603 to get the VM names, but everytime I run this line (with a foreach loop passing the uuid in):

 

 

get-inventoryentity -type virtualmachine | where {$_.UUID -eq "**UUID HERE**"} | ForEach-Object {write $_.Name}

 

I get this error:

 

Get-InventoryEntity : The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:GetInventoryEntitiesByTypeResult. The Inne

rException message was 'Maximum number of items that can be serialized or deserialized in an object graph is '65536'. Change the object graph or increase the MaxItemsInObjectGraph quota. '.  Please see InnerExceptio

n for more details.

At line:1 char:20

+ Get-InventoryEntity <<<<  -type VirtualMachine | where {$_.UUID -eq "**UUID**"} | ForEach-Object {write $_.Name}

    + CategoryInfo          : InvalidOperation: (vRanger.API.Pow...ventoryEntities:GetInventoryEntities) [Get-InventoryEntity], NetDispatcherFaultException

    + FullyQualifiedErrorId : 1,vRanger.API.PowerShell.InventoryShell.GetInventoryEntities

 

I get this just running get-inventoryentity as well.

 

Anyone seen this before? workarounds?



vRanger 6.0.1 w/ vSphere 5.1 fails to consolidate VMs randomly

$
0
0

We run a vRanger 6.0.1 nightly job to back up approximately 180 VMs residing across 4 vSphere 5.1 hosts.  Every morning there are several VMs in vCenter that show up with the "virtual machine disks consolidation is needed" yellow exclamation warning on them.  It is not always the same VMs, just a random handful every night.  Manual consolidation is needed on them as the delta files are left on the VMs.  The vRanger task log for a problem VM indicates no problems, "Removing snapshot for vRanger completed."  There isn't a single error throughout the task log.  So from the vRanger standpoint, it thinks it completed correctly.  I assume this is because of poor error handling however as if you look at the events for the VM in question in vCenter, coinciding at the same time as vRanger removing the snapshot line in its log, you see events for "Task: Remove snapshot" followed within seconds by "Virtual machine disks consolidation is needed" followed immediately by "Virtual machine disks consolidation failed."  So the reference to the snapshot is being removed but consolidation fails leaving the snapshot in an orphanned ghosted state and growing until manual consolidation is performed.

 

All of these VMs that experience this problem are using Machine-based VDDK SAN "HotAdd" so I am assuming that the physical server that runs vRanger is not letting go of the VMDK before consolidation is attempted so the VMDK lock is preventing the consolidation from occurring.  The SANs in question are a pair of EqualLogics connected via iSCSI to both the vSphere hosts and the physical server that runs vRanger.

 

Any ideas how to prevent this from happening?

how to import catalog from other site

$
0
0

Hi all,

I copied catalog backup from one site to another site.

I create a new repository from the directory imported but I'm not be able to see catalog from this repository....any ideas ?

thanks in advance

Andre

Upgrade to 6.0.2, Catalog database failed to install - Reason: -1

$
0
0

Hi,

 

I have just gone through and tried to upgrade from 5.0 to 6.0.2 and got the error of "Catalog database failed to install - Reason: -1" when trying to install/upgrade the catalogue DB.

 

Everything goes through with out a hitch until we get to the catalogue error and then it roles it all back.

 

the log is below for the catalogue upgrade

 

Install Started: 15/04/2013 (Monday) 9:33:42

...Initializing Installation

Installation Start: 15

CatalogManager Version 1.0.520.22810 is already installed on your system. Upgrading to Version 6.0.0.33307

...Upgrading CatalogManager to Version 6.0.0.33307.

..Quest Catalog Service stopped.

..Copying files to temp folder

...Installing CatalogManager files.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\Config\Files

Extracted ..\..\Service\Release\Config\Files\BulkImportMap.fmt successfully.

Extracted ..\..\Service\Release\Config\Files\FileFilterTokens.txt successfully.

Extracted ..\..\Service\Release\Config\Files\ActivateWorkflowConfig.xml successfully.

Extracted ..\..\Service\Release\Config\Files\DeleteWorkflowConfig.xml successfully.

Extracted ..\..\Service\Release\Config\Files\SaveWorkflowConfig.xml successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.WCF.Service.exe successfully.

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.WCF.Service.exe.config successfully.

Extracted ..\..\Service\Release\Autofac.dll successfully.

Extracted ..\..\Service\Release\Gurock.SmartInspect.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.CoreLibrary.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.DataAccess.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.WCF.Library.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.CatalogManager.Workflow.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.Common.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.Cryptography.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.DataAccessExt.dll successfully.

Extracted ..\..\Service\Release\Vizioncore.Logging.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller

Extracted ..\..\Setup\DatabaseInstaller\Autofac.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Gurock.SmartInspect.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.CatalogManager.CoreLibrary.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.CatalogManager.DataAccess.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.CatalogManager.DatabaseInstaller.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.Common.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.vRangerExternals.Localization.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.Cryptography.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.DataAccessExt.dll successfully.

Extracted ..\..\Setup\DatabaseInstaller\Vizioncore.Logging.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\zh-CN

Extracted ..\..\Setup\DatabaseInstaller\zh-CN\Vizioncore.vRangerExternals.Localization.resources.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\ja-JP

Extracted ..\..\Setup\DatabaseInstaller\ja-JP\Vizioncore.vRangerExternals.Localization.resources.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\de-DE

Extracted ..\..\Setup\DatabaseInstaller\de-DE\Vizioncore.vRangerExternals.Localization.resources.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\fr-FR

Extracted ..\..\Setup\DatabaseInstaller\fr-FR\Vizioncore.vRangerExternals.Localization.resources.dll successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\Scripts\SchemaManager

Extracted ..\..\Setup\DataAccess\Scripts\SchemaManager\Create.sql successfully.

...Extracting Files to C:\Program Files (x86)\Quest Software\CatalogManager\DatabaseInstaller\Scripts\Catalog

Extracted ..\..\Setup\DataAccess\Scripts\Catalog\UserAdmin\CreateMixedModeUser.sql successfully.

Extracted ..\..\Setup\DataAccess\Scripts\Catalog\Upgrades\201008160922.sql successfully.

Extracted ..\..\Setup\DataAccess\Scripts\Catalog\Upgrades\201107211110.sql successfully.

Extracted ..\..\Setup\DataAccess\Scripts\Catalog\Upgrades\201110311124.sql successfully.

Extracted ..\..\Setup\DataAccess\Scripts\Catalog\Upgrades\201201191000.sql successfully.

CatalogManager Installation Completed.

...Installing Catalog Database

Installing Database Loudly

Catalog database failed to install - Reason: -1

...CatalogManager Installation failed. Rolling back changes.

...CatalogManager Installation failed. Rollback completed.

 

any help would be appreciated

 

Thanks

vRanger Pro 5.2.1 backup fails with Error Message: Index was outside the bounds of the array.

$
0
0

 

 

 

 

vRanger Pro 5.2.1 backup gets to 33%, Then fails with error message: Index was outside the bounds of the array

vRanger v5.3.0.23489 Backup is Very Slow

$
0
0

I have started the upgrade of my VMware Infrastructure from ESX v4.1 Update 1 WITH the Service Console to ESX 5i (obviously with no Service Console).  I wiped the system disks and loaded ESX 5i cleanly.  I have noticed that "some" of my vRanger backups are taking an extremely longer amount of time to run.  This does not happen all of the time, but it is occurring fairly regularly.  Also, most all of my backup times are taking longer than in the past to complete.  My vRanger configuration is setup to run within a VM in a VMware cluster with my vCenter server.  My VMFS data stores are running FC disks over a SAN connection via dual HBA's.  We are writing to a backup location accross the LAN.

 

I read an earlier Quest forum post from around May 2011 stating that vRanger v5.0 was experiencing performance problems due to the lack of a Service Console.  The post stated that because of the lack of a Service Console that vRanger now had to read the data over the LAN instead of using the Service Console and reading the data over the SAN and that was what was causing the performance issues.  The post went on to state that this problem was supposed to be fixed with v5.1 of vRanger.  I am currently running vRanger v5.3.0.23489 on a fresh install of vRanger (not upgraded from an earlier version of vRanger) on a newly installed VM that is Windows 2008 R2 with 2 vCPU's and 4.0 GB of RAM.

 

Does anyone know if the performance problem I am seeing is related to the lack of a Service Console in ESX 5i?  Has anyone else noticied this behavior?  Is there a fix?



Auto delete Exchange 2010 Logs after Backupjob with vRanger 5.2.1

$
0
0

Hey guys.

 

I have a problem with the logs from Exchange 2010 VM after a Backupjob. Normaly the vRanger delete the logs automatically after the job is finished.

But since a few weeks the logs are not deleted. Have anyone an idea what will be happen or what is wrong??

 

Versions:

Exchange --> 2010 on 2008R2 Standard

vRanger --> 5.2.1

vSphere --> ESXi 4.1 Update 2

 

Thanks for help in advanced!

 

Greets, Matthias

Help! VRanger Crashes every time

$
0
0

hi

i've installed the new vRanger version 6.0.1

now when i click in to the Inventory Menu on some of my jobs, vranger Crashes and i cannot enter the job setup.

Also the right Side of the Menü is Black.

 

I get this error message

 

One ot more execptions occured while firing the topic "Global:vRanger//ActiveGroupChanged"

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

Microsoft.Practices.CompositeUI.EventBroker.EventTopicException: One or more exceptions occurred while firing the topic 'Global::vRanger//ActiveGroupChanged'

   at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.CallSubscriptionHandlers(Object sender, EventArgs e, EventTopicFireDelegate[] handlers)

   at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Object sender, EventArgs e, WorkItem workItem, PublicationScope scope)

   at Microsoft.Practices.CompositeUI.EventBroker.EventTopic.Fire(Publication publication, Object sender, EventArgs e)

   at Microsoft.Practices.CompositeUI.EventBroker.Publication.PublicationHandler(Object sender, EventArgs e)

   at Vizioncore.vRanger.Client.Shell.vRangerRootWorkItem.OnActiveGroupChanged(String newActiveGroup, String fromGroup)

   at Vizioncore.vRanger.Client.Shell.ShellLauncher.MainExplorerBar_SelectedGroupChanged(Object sender, GroupEventArgs e)

   at Infragistics.Win.UltraWinExplorerBar.SelectedGroupChangedEventHandler.Invoke(Object sender, GroupEventArgs e)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.OnSelectedGroupChanged(GroupEventArgs e)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.FireEvent(UltraExplorerBarEventIds id, EventArgs e)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.PerformListbarPostAnimationTasks()

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.AnimateGroupSelection(UltraExplorerBarGroup newSelectedGroup, Boolean animationEnabled)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.set_SelectedGroup(UltraExplorerBarGroup value)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBarGroup.DoHeaderClick()

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBarGroupHeaderUIElement.OnClick()

   at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)

   at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)

   at Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)

   at Infragistics.Win.UltraControlBase.OnMouseUp(MouseEventArgs e)

   at Infragistics.Win.UltraWinExplorerBar.UltraExplorerBar.OnMouseUp(MouseEventArgs e)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

Vizioncore.vRanger.Client.Shell

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.Shell.exe

----------------------------------------

Infragistics.Practices.CompositeUI.WinForms

    Assembly Version: 1.0.20103.1000

    Win32 Version: 1.0.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics.Practices.CompositeUI.WinForms.DLL

----------------------------------------

Microsoft.Practices.CompositeUI.WinForms

    Assembly Version: 1.0.51205.0

    Win32 Version: 1.0.51205.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Microsoft.Practices.CompositeUI.WinForms.DLL

----------------------------------------

Microsoft.Practices.CompositeUI

    Assembly Version: 1.0.51205.0

    Win32 Version: 1.0.51205.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Microsoft.Practices.CompositeUI.DLL

----------------------------------------

System.Security

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Security/2.0.0.0__b03f5f7f11d50a3a/System.Security.dll

----------------------------------------

System

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

Microsoft.Practices.ObjectBuilder

    Assembly Version: 1.0.51206.0

    Win32 Version: 1.0.51206.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Microsoft.Practices.ObjectBuilder.DLL

----------------------------------------

Infragistics2.Win.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.v10.3.DLL

----------------------------------------

Vizioncore.Windows.Forms

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Windows.Forms.DLL

----------------------------------------

System.Windows.Forms

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5460 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5462 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

Vizioncore.Logging

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Logging.DLL

----------------------------------------

Vizioncore.Common

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Common.DLL

----------------------------------------

System.Configuration

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

Gurock.SmartInspect

    Assembly Version: 3.1.0.8000

    Win32 Version: 3.1.0.8000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Gurock.SmartInspect.DLL

----------------------------------------

Vizioncore.Cryptography

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Cryptography.DLL

----------------------------------------

System.Core

    Assembly Version: 3.5.0.0

    Win32 Version: 3.5.30729.5420 built by: Win7SP1

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

Vizioncore.vRanger.Localization

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Localization.DLL

----------------------------------------

Vizioncore.vRanger.Exceptions

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Exceptions.DLL

----------------------------------------

Vizioncore.Common.ErrorHandler

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Common.ErrorHandler.DLL

----------------------------------------

Vizioncore.vRanger.Client.Common

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.Common.DLL

----------------------------------------

Vizioncore.vRanger.Facade

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Facade.DLL

----------------------------------------

Infragistics2.Win.Misc.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.Misc.v10.3.DLL

----------------------------------------

Infragistics2.Shared.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Shared.v10.3.DLL

----------------------------------------

Vizioncore.vRanger.Localization.resources

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/de-DE/Vizioncore.vRanger.Localization.resources.DLL

----------------------------------------

Vizioncore.vRanger.Client.Service

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.Service.DLL

----------------------------------------

Vizioncore

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.DLL

----------------------------------------

System.Runtime.Remoting

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

Infragistics2.Win.UltraWinDock.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinDock.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinToolbars.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinToolbars.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinExplorerBar.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinExplorerBar.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinStatusBar.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinStatusBar.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinTabbedMdi.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinTabbedMdi.v10.3.DLL

----------------------------------------

Vizioncore.Licensing.CoreLibrary

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Licensing.CoreLibrary.DLL

----------------------------------------

Vizioncore.Shell

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.Shell.DLL

----------------------------------------

Vizioncore.vRanger.Client.LicensingModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.LicensingModule.DLL

----------------------------------------

System.Data

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

ltk-ni4s

    Assembly Version: 1.0.51205.0

    Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

Vizioncore.vRanger.Client.ReportViewModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.ReportViewModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.StartupWizardModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.StartupWizardModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.ConfigOptionsModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.ConfigOptionsModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.RepositoryModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.RepositoryModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.FileLevelRestoreModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.FileLevelRestoreModule.DLL

----------------------------------------

Vizioncore.vRanger.FLR

    Assembly Version: 1.0.0.0

    Win32 Version:

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.FLR.DLL

----------------------------------------

Vizioncore.vRanger.Client.JobModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.JobModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.MyJobsModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.MyJobsModule.DLL

----------------------------------------

Infragistics2.Win.UltraWinGrid.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinGrid.v10.3.DLL

----------------------------------------

Vizioncore.vRanger.Client.InventoryModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.InventoryModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.JobWizardModule

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.JobWizardModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.CatalogModule

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.CatalogModule.DLL

----------------------------------------

Vizioncore.vRanger.Client.VirtualAppliance

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Client.VirtualAppliance.DLL

----------------------------------------

Infragistics2.Win.UltraWinTabControl.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinTabControl.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinTree.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinTree.v10.3.DLL

----------------------------------------

VimService50

    Assembly Version: 0.0.0.0

    Win32 Version: 0.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/VimService50.DLL

----------------------------------------

VimService20

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/VimService20.DLL

----------------------------------------

Infragistics2.Win.UltraWinSchedule.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinSchedule.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinPrintPreviewDialog.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinPrintPreviewDialog.v10.3.DLL

----------------------------------------

Infragistics2.Win.UltraWinGrid.ExcelExport.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Win.UltraWinGrid.ExcelExport.v10.3.DLL

----------------------------------------

Infragistics2.Excel.v10.3

    Assembly Version: 10.3.20103.1000

    Win32 Version: 10.3.20103.1000

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Infragistics2.Excel.v10.3.DLL

----------------------------------------

Accessibility

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

System.Runtime.Serialization.Formatters.Soap

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Serialization.Formatters.Soap/2.0.0.0__b03f5f7f11d50a3a/System.Runtime.Serialization.Formatters.Soap.dll

----------------------------------------

msvcm90

    Assembly Version: 9.0.30729.6161

    Win32 Version: 9.00.30729.6161

    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57/msvcm90.dll

----------------------------------------

Vizioncore.BET

    Assembly Version: 6.0.0.30972

    Win32 Version: 6.0.0.30972

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.BET.DLL

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 8.0.0.0

    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

Vizioncore.vRanger.Reports

    Assembly Version: 6.0.1.31606

    Win32 Version: 6.0.1.31606

    CodeBase: file:///C:/Program%20Files%20(x86)/Quest%20Software/vRanger/Client/Vizioncore.vRanger.Reports.DLL

----------------------------------------

System.Web

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.5456 (Win7SP1GDR.050727-5400)

    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.


Error Message: The operation has timed out

$
0
0

We've been having trouble with vRanger since version 3 as some of the backup jobs would fail. Fortunately that only happened once or twice a month so it wasn't a big problem. But after upgrading from 5 to version 6 the failed jobs are way more frequent - every day or every second day. Every day it's a different machine, but it's almost always this error message ("The operation has timed out" or "Unable to locate host esx1.local").

 

Now the actual question is if anyone knows if there is a config setting in the vRanger xml file that would increase this timeout?

vCenter & ESXi 5.1UP1

$
0
0

Hello,

 

Is vRanger compatible with vCenter and ESXi 5.1 UP 1?

 

Thanks.

Out Of memory issues

$
0
0

Im just racking these discussions up... :-)

 

Anyone having issue with vRanger 6.0.2 running in a Win2k8 R2 Sp1 VM and getting dotnet issues? (Out of Memory, parameter not valid, etc)?

 

I have a large environement and the think the issue has to do with 32 bit memory management of .net and how vRanger is enumerating all the objects.

 

Im guessing here, but anyone deal with this before?

 

Im working with Quest support (who's doing a really awesome job of working through this with me) and we already adjusted the IRPStackSize reg key which helped, until i went to create a new backup job... weird...

 

Thanks!

Error Message: 2654 - can't read vix... at io_size:125

$
0
0

Hi everybody,

 

I've got one question with no answer from Quest Software...

 

Here is my configuration :

 

2 x ESXi 5 with VMware Essential Plus Acceleration Kit

1 x physical vRanger Server 5.2 with vCenter 5 Server.

 

San configuration : my physical vRanger can see all VMware Datastore Luns in windows disk manager (diskpart with automount disable and automount scrub).

 

vRanger configuration : VDDK SAN transport for lan free backup and lan backup if lanfree failed.

 

My problem :

 

I can't backup my VMs with LAN-free :

 

Capture.JPG

 

Lan Backup is ok.

 

My vRanger Server is not a VM so i don't need the hot-add function.

Authentication is ok to vCenter Server and ESXi host (with root account).

 

Does anyone have an idea ??

 

Thanks,

 

Regards.

Fehlermeldung beim Backup

$
0
0

Hallo zusammen,

 

Habe beim Backup eines VM's folgende Meldung:

 

An internal error occurred during execution, please contact Quest support if the error persists. Error Message: API Call failed with message: Datei ist größer als die vom Datenspeicher '' unterstützte maximale Größe

Die einzige Partition die ich gerne sicheren will ist das C-LW und ist 25GB gross. Das 2. LW ist ein virtuelles LW, den ich gar nicht sichern will (s. Bild unten, oder Anhang)


 

und der Repository hat noch genügend Kapazität (s. Bild unten):

 

 

Trotzdem bekomme ich die Fehlermeldung !

 

Was läuft hier ab und wie kann ich es in Griff bekommen ?

 

Herzlichen Dank im Voraus und

Viele Grüsse aus der Schweiz

 

Farouq


Restore VM to new system without vRanger from vmdk.var archive file?

$
0
0

Hi,

 

I have a vRanger backup from a ESX4 VM that I wish to restore to a completely different system and not located in anything managed or accessible by the vRanger that did the backup. Is it possible to restore from this vmdk.var file to .vmdk or at least something VMware workstation and ultimately ESXi 5 can run?

 

On the forums it appears that some extraction scripts/command line tools exist but the links are all to visioncore and those are broken. Could I use a trial version of VRanger 6 and do something here.

 

There are 3 files I can see in the vRanger backup copied to an external HD. It appears to be from vRanger v 4.5.2.16370

 

EMC_20121021_010007_F.Manifest.metadata

EMC_20121021_010007_F.VmConfig.metadata

EMC_20121021_010007_F_1_EMC-flat_vmdk.var

 

Part of the vmconfig follows

 

vRangerVersion>4.5.2.16370</vRangerVersion><CurrentSnapshot /><SnapshotLayouts /><VMConfig><changeVersion xmlns="urn:vim25">2012-10-13T23:53:41.168746Z</changeVersion><modified xmlns="urn:vim25">1970-01-01T00:00:00Z</modified><name xmlns="urn:vim25">EMC</name><guestFullName xmlns="urn:vim25">Ubuntu Linux (64-bit)</guestFullName><version xmlns="urn:vim25">vmx-07</version><uuid xmlns="urn:vim25">4230e631-b23b-01cd-83ed-2afd031cc393</uuid><instanceUuid xmlns="urn:vim25">50304715-cdbe-c5a1-11d2-bfc18080fd53</instanceUuid><npivWorldWideNameType xmlns="urn:vim25" /><npivTemporaryDisabled xmlns="urn:vim25">true</npivTemporaryDisabled><locationId xmlns="urn:vim25">564da9e8-622e-6303-3fc3-b6863b83e34a</locationId><template xmlns="urn:vim25">false</template><guestId xmlns="urn:vim25">ubuntu64Guest</guestId><alternateGuestName xmlns="urn:vim25">Ubuntu Linux (64-bit)</alternateGuestName><annotation xmlns="urn:vim25">vRanger Pro Backup: Type [Full] Result [Success] Time [2012/10/14 01:52:16 AM]

Quest Catalog Service did not respond

$
0
0

We have updated vRanger to the latest version (5.5) and we have a problem with the Quest Catalog Service.

 

After i updated vRanger the catalog service didnt started.

When i try to start the service i got the following error:

"Windows could not start the Quest Catalog Service on local computer. Error 1053: The service did not respond to start or control request in a timely fashion."

 

In the eventlog i see following message:

"A timeout was reached (393216 milliseconds) while waiting for the Quest Catalog Service service to connect."

and

"The Quest Catalog Service service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion."

 

I have already checked the database user accounts und rights but everything is correct.

I start the service with a local account who has administartor rights.

 

For the vRanger and Catalog DB we use a external MSSQL database.

 

We use the same hardware and software on 3 other sites and there we do not have this problem.

 


Configuration change logs, do they exist?

$
0
0

I have a handful of jobs that appear to be altered and im trying to figure out when and who altered them. Are there any sort of loge in Vranger that will help me track this down? I do have support debugging on, i just was hoping to see if its feasble before i called support.

 

Thanks

Backup to NAS FTP/SFTP Problem

$
0
0

Hello,

 

i just connected a NAS for backup. Connecting ist as CIFS (Windows Share) is working fine. If i try to connect it as FTP or SFTP repository vRanger can connect to it.

 

Failed to connect to repository.  Please verify your credentials (if applicable) and ensure the directory path is correct.

 

I used the same credentials as for the CIFS. What i am doing wrong?

 

Regards

Mathias

how to import catalog from other site

$
0
0

Hi all,

I copied catalog backup from one site to another site.

I create a new repository from the directory imported but I'm not be able to see catalog from this repository....any ideas ?

thanks in advance

Andre

vRanger Maintanence

$
0
0

Ok everyone, Im gonna throw this one out there and see what everyone else does...

 

First, the requirements and settings...

 

The company Im working at is contractually obligated for the following:

  • keep a backup of the systems for 45 days (ie, be able to restore a VM for up to 45 days from current day)
  • as part of the backup/45 day restore combined with other business processes, do 1 full backup only, on every system 1 once per week
  • Audit data (proof of backup, backup outcome, restore outcome, etc) must be available for any system (still running or deleted) for 1 year.

 

So, now my big question is, what/how should maintenance be carried out on the vRanger instances we have running?

 

Ideally, I would like the following:

  • to keep the actual file contents of the repos as small as possible (deleting any old contents that doesn't fit into the above req's) as they are deduped/replicated via DataDomain to a DR site.
  • to keep the vRanger DB as clean/small as possible
  • to keep ALL report/job search data available for any system vRanger touched for up to 1 year from current day.

 

I'm seeing this as potentially a PoSH script to read vRanger job data, purge Repo data, purge savepoints, purge DB data (although Im not sure how these objects work in context of vranger, it would be great if someone could clarify the mechanism, or point me to the tech doc that does, thx)

 

Anyone done any housekeeping like this? I have a rather large environment (2700 vm's) and we are looking into the re-architecture of it for scalability and cleanliness over time.

 

Thanks!

 


What changed in vRanger 6.0.2 in case of RAM snapshots

$
0
0

Hello Quest Community,

 

we had several issues with vRanger 6.0.1 because the snapshots took too long to complete. The reason was that vRanger took RAM snapshots by default in that version. This problem could be solved by increasing the maximum time for the snapshots in the vRanger config. Whith vRanger 6.0.2 I don´t have any of these issues.

 

My question is: Does vRanger 6.0.2 still include the RAM of the VM in the backup? Is there now a possibility to turn this on or off?

 

Regards,

Tobias

Viewing all 1662 articles
Browse latest View live