1 On the Main toolbar, click Tools > Options.
2 Under the My Jobs node, click Configuration.
3 In the Timeout section, change the Task Timeout field to 100 or more, depending on the size of the environment.
4 Click OK.
Table 4. Supported operating systems
Before installing vRanger on Windows Server 2012 R2, the updates listed in Additional required software must be installed.
In addition to a supported version of Windows® and a supported VMware® Infrastructure, you may need some additional software components, depending on your configuration.
• Microsoft® .NET Framework: vRanger requires the .NET Framework 4.5. The vRanger installer installs it if not detected.
• SQL Server: [Optional] vRanger utilizes two SQL Server® databases for application functionality. vRanger can install a local version of SQL Express 2014 SP3 or you can choose to install the vRanger databases on your own SQL instance.
• Windows PowerShell 3 or above.If you are installing vRanger on Windows 2008 R2 SP1, you will need to install Windows PowerShell 3 or above before installing vRanger
• vRanger virtual appliance (VA): The vRanger VA is a small, pre-packaged Linux® distribution that serves as a platform for vRanger operations away from the vRanger server. vRanger uses the VA for the following functions:
▪ Replication to and from VMware® ESXi™ hosts.
• Updates for Windows Server 2012 R2: Before installing vRanger on Windows Server 2012 R2, ensure that the Windows updates listed below are installed:
You may choose to install vRanger with a new instance of SQL Server® Express or on an existing SQL Server.For more information, see the Quest vRanger Installation/Upgrade Guide.
vRanger requires some basic configuration before data protection can begin. The bulk of this configuration is driven by the Startup Wizard which starts the first time the application is opened. For more information, see the Quest vRanger Installation/Upgrade Guide.
• Add source servers: Before you can begin backups, you must add one or more source objects to the vRanger inventory. Source objects can include VMware® vCenter™ or ESXi™ hosts, Hyper-V® clusters or hosts, or physical machines.
• Add vRanger virtual appliances (VAs): vRanger VAs allow you to distribute the backup workload and gain direct access to target VM’s storage for improved performance.
• Add repositories: Repositories are where vRanger stores the savepoints created by each backup job. For the purposes of this integration, a Quest Rapid Data Access (RDA) repository should be used.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center