Nodes that are already running a 7.x release can upgrade directly to 8.0 or 184.108.40.206.
For nodes running older releases (6.x), the boot partitions will need to be expanded prior to upgrade. nodes running releases older than 220.127.116.11 must first be upgraded to 18.104.22.168. See the table below.
Client SMB connections must be remounted when upgrading from 6.2 or 6.3 to 8.x. Remount is required only for Windows 8, Windows 10, and Windows 2012 clients (clients that support SMBv3).
If you are deploying a new node, see the installation guide for your platform (hardware, ESXi VM, AWS AMI, or Azure instance).
- FD- 6000 series supports CloudFS 7.1.6.x and above.
- FD - 5000 series supports CloudFS 22.214.171.124 and above.
The following table shows the upgrade path for each CloudFS version.
Note: For help upgrading boot partitions on the AMI platform, contact Panzura Support.
|Earlier than 6.3.1||You must first upgrade to 126.96.36.199, then use the upgrade steps listed above for 188.8.131.52.|
To install the new image:
On nodes running 184.108.40.206 or later, use these steps to install the new image and reboot:
- In the WebUI, navigate to Maintenance > System Operations > Upgrade.
- Select Image.
- Select Local or Panzura, depending on where the node will look for the image file.
- Click Select Image.
- Click Upgrade.
(Earlier than 220.127.116.11 only) Expand VM Boot Partition
If you’re running a VM node on ESXi on a CloudFS release earlier than 18.104.22.168, use these steps to expand the boot partition.
In the following steps, the screen shots of ESXi might vary based on your version of vSphere.
- Power off the Panzura VM.
- Right click on the Panzura VM instance and select Power Off.
- Expand the boot partition.
- Right-click the Panzura instance and select Edit Settings.
- If the size of the boot disk or first hard disk is less than 50GB, change it to 50GB and click OK.
- Power on the VM.
(Earlier than 22.214.171.124 only) Run Partitioning Script
If you’re running a CloudFS release earlier than 126.96.36.199, use these steps to expand the boot partition before upgrading to 188.8.131.52.
- Log in to the WebUI and select Maintenance > Diagnostics.
- Select staging-8.0-upgrade from the Command Type menu and click Run. (Example: staging-8.0-upgrade)
The partitioning script takes a few minutes to run on VM nodes and up to 20 minutes on a physical node. While the script runs, messages are displayed in the output area.
- For ESXi, the process includes an automatic shutdown of the VM. After the VM shuts down, restart the VM to complete the partitioning process. Contact Panzura Support for assistance with the upgrade to 184.108.40.206.
- For a physical node, the processing does not include an automatic shutdown. When you see the success message, reboot the node to complete the process. Contact Panzura Support for assistance with the upgrade to 220.127.116.11.
Upload the Key File
After you have completed any upgrade, you must update the encryption settings from the Key Master:
- Navigate to Configuration > Encryption Settings > Authentication Keys.
- Click Export to export the pairing.key file to your local system.
- Navigate to Configuration > Encryption Settings > Authentication Keys on each of the Subordinate nodes in the CloudFS and upload the pairing.key file.
nodes that are already running on an 18.104.22.168 release need to be downgraded to 22.214.171.124 (the landing release) before downgrading to any other 7.x release.
On nodes running release versions (7.1.9 or earlier), you can directly downgrade to any 7.x or 6.x release version without any stopover in between.
To Downgrade to any release version, click Configuration > Upgrade and follow the downgrade steps below.
The following table displays the downgrade path for each CloudFS version.s:
Later than 126.96.36.199
|7.x earlier than 188.8.131.52||