Chatee ahora con Soporte
Chat con el soporte

vRanger 7.8.6 - Installation/Upgrade Guide

Introduction Before you install System requirements and compatibility Installing vRanger Upgrading vRanger

Database options

The database deployment occurs during the initial installation of vRanger. The default installs a SQL Server® Express database on the vRanger server. You can also install vRanger using a separate SQL Server instance. If you intend to use your own SQL Server instance and want to use the vRanger cataloging feature, the SQL Server instance must be installed on the vRanger server. For more information, see Installing the databases.

•
Default: By default, the Installation Wizard uses the selection to install vRanger with the embedded SQL Server® 2014 SP3 Express database. The SQL Server Express database can only be installed on the vRanger server.
 
* 
NOTE: While the embedded SQL Server Express database is free and simple to install, there is a size limit of 10 GB per database.
•
External SQL Server Instance: The Installation Wizard guides you through configuring vRanger with an external SQL Server® database. There is also an option in the Install Wizard to configure the database connection manually, but the guided approach is recommended.
 
* 
IMPORTANT: For a list of supported SQL Server database versions, see System requirements and compatibility.

Installing the databases

When installing vRanger, consider the database selection carefully as migrating from a SQL Server® Express installation to an external SQL Server database carries a risk of corrupting application data.

If you do not intend to use cataloging, to provide the most flexibility, Quest recommends that you install vRanger using an external SQL Server database server. This step allows you to relocate the vRanger installation simply by installing the application in another location, and pointing the Install Wizard to the existing database.

Sizing the catalog database

The vRanger catalog process collects and records metadata and path information for files updated since the last backup and catalog entry. Depending on the number of VMs protected, and the number of files in each VM, the catalog database may grow rapidly.

Actual database growth varies depending on the Guest OS and the number of files changed between backups, but the following information can be used as an approximate guide.

•
With default filtering, the full catalog of a generic Windows Server® 2012 VM is approximately 500 files, or approximately 0.2 MB.
 
* 
NOTE: Many Windows® files are not cataloged due to filtering; for more information about catalog filtering, see the Quest vRanger User’s Guide. An amount of data equal to a standard Windows Server® 2012 installation results in a larger catalog footprint.
•
Incremental and differential backups only catalog changed files, making the catalog record for these backups considerably smaller. Using incremental or differential backups, or both, allows you to store catalog data for many more savepoints than if you used only full backups.

Installing the vRanger virtual appliance (VA)

The vRanger VA can process backup and restore tasks in addition to replication tasks. This setup allows you to scale backup, restore, and replication activity across multiple hosts or clusters, while maintaining central scheduling and reporting control from a single vRanger server.

While the deployment and configuration of the VA are covered in the Quest vRanger User’s Guide, the following information might help you understand the usage of the VA.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación