Only v7.1 and later can be upgraded to v7.7.0. If running an earlier version, you must upgrade to version 7.1 or later before upgrading
If upgrading from a version prior to Version 7.5.0. due to changes to the Jobs system introduced in 7.5 it is necessary to recompile and distribute the rules so that the jobs have their correct titles. Additionally, the Jobs history will be reset on upgrade.
If the current version of Protector is lower than Version 7.4.0 and push upgrades are required it is necessary to push upgrade the clients first before the master. Protector 7.4.0 introduces increased security of its inter-node communications. Due to this it's not possible for Version 7.4.0 to communicate to older versions of the software. So when crossing the 7.4.0 boundary its important to first push upgrade any clients to 7.4.0 before upgrading the master node. Any clients that are push upgraded to 7.4.0 or later will show as offline until the master is upgraded. Once the master node is upgraded to any older clients will show offline and will need to be installed by running the installer on the client directly.
Version 7.1 uses a new backend database to store logs and recovery points. If upgrading from a pre v7.0 version, the recovery point database is automatically built. However, the logs database is empty after upgrade, which affects both the logs and some historic reports. If required, you can import the old logs into the new system using a CLI tool. Importing logs may take some time, however the import runs at the same time as the services so that daily operations can continue. For details, see the user guide.