Before upgrading vRanger
Deprecated repository types
•
Migrating content from an FTP or SFTP repository
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.
5 When the upgrade is completed, you can add the new repository to vRanger. Refer to the instructions in the “Configuration” chapter of the vRanger User’s Guide if necessary.
vRanger editions
• 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.
Supported upgrade paths
• Supported for direct upgrade: If you are using one of the following vRanger versions, you may upgrade directly to vRanger 7.7.1.
• Requires intermediate upgrade: The following versions are not supported for direct upgrade to vRanger 7.7.1. If you are using one of these versions, you must first upgrade to vRanger 7.6.x before upgrading to the latest version.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center