Chat now with support
Chat with Support

vRanger 7.8.2 - Installation/Upgrade Guide

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

Migrating content from an FTP or SFTP repository

Previous Next


Upgrading vRanger > Migrating content from an FTP or SFTP repository > Migrating content from an FTP or SFTP repository > Migrating content from an FTP or SFTP repository

Migrating content from an FTP or SFTP repository

You can migrate content from one repository (or repository type) to another simply by copying the repository contents to the new location.

To migrate a repository:
IMPORTANT: Do not select Delete all savepoints in this repository. By not selecting this option, you will remove the repository from vRanger but maintain the data in the repository location.

vRanger editions

Previous Next


Upgrading vRanger > Migrating content from an FTP or SFTP repository > vRanger editions

vRanger editions

With replication now integrated into vRanger, and vRanger being offered in multiple versions, there are several upgrade options available.

Customers of both vRanger and vReplicator: The upgrade procedures differ depending on whether you want to manage replication from the disaster recovery (DR) site, or combine backup and replication management on the production site.
DR site: If you want to manage replication from the DR site to ease failover, follow both of the preceding procedures, upgrading the vRanger installation on the production side and the vReplicator installation on the DR site. You may use a combined license file for both installations, if the combined CPU count for each protection type — backup and replication — for both sites does not exceed the total licensed number of CPUs.
Production site: When both backup and replication are managed from the production site, start with Upgrading a previous vRanger installation, and skip to Step 4 of the Upgrading a previous vReplicator installation procedures.

If you purchase vRanger SE, you can purchase an upgrade to vRanger Backup & Replication. Similarly, you can also purchase an upgrade from vReplicator 5.0 to vRanger Backup & Replication 7.8.2.

Supported upgrade paths

Previous Next


Upgrading vRanger > Migrating content from an FTP or SFTP repository > vRanger editions > Supported upgrade paths

Supported upgrade paths

Due to architectural differences, a direct upgrade to vRanger 7.8.2 from older vRanger versions may not be possible.

Supported for direct upgrade: If you are using one of the following vRanger versions, you may upgrade directly to vRanger 7.8.2.
Requires intermediate upgrade: The following versions are not supported for direct upgrade to vRanger 7.8.2. If you are using one of these versions, you must first upgrade to vRanger 7.6.x before upgrading to the latest version.

Backing up the vRanger database

Previous Next


Upgrading vRanger > Backing up the vRanger database

Backing up the vRanger database

vRanger utilizes a SQL Server® database to store application and task configuration data. The database can be either the embedded SQL Server Express instance — the default — or a SQL Server database running on your own SQL Server or SQL Server Express instance. If you want to back up the SQL Server database before installing an upgrade, you must use SQL Server Management Studio.

3
Right-click vRangerPro Database, select Tasks, and then select Backup.
4
In the Back Up Database Wizard, verify that the Disk option is selected in the Destination section.
a
Click Add.
c
After identifying the applicable path, enter vRangerPro.bak after the last backward slash in the path name, and click OK.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating