The following procedures are considered "system-altering", and requires advance preparation by the administrator:

• Adding or removing a high availability (HA) system
• Updating the system to a later version by using an ISO update file
• Upgrading the system by redeploying the system from a OVA file for the upgrade version
• Expanding the system size from the current size to a larger size

You will put the system in maintenance mode when performing these procedures. Because of this, you may want to schedule several of these procedures together; for example, expanding the system and updating the system during the same maintenance window.

Keep in mind the following constraints:

• If you have already added HA to your system, and would like to expand or upgrade the system, then you will need to redeploy the HA system again, following the upgrade. System expansions or upgrades requires the deployment of a new system, with the transfer of the system data to the expanded or upgraded system. When deploying a new system, you are asked to choose between deploying a primary system or the HA system - you cannot deploy both at once. Therefore, you must first deploy the primary system with the OVA file, then deploy the HA system, with the same OVA file used for the primary system.
• If you are planning to add a HA system, as well as update it (with an ISO update file), then we recommend you first add the HA system, then update the combined (primary and HA) system. The update procedure updates the entire system, with or without a HA system. If you update the system first, then to add HA, you first need to deploy the HA system, then update the HA system (so both the primary and HA systems are at the same version). If you add HA first, then the update procedure updates the combined primary and HA system at the same time.
• The update procedure updates the entire system, with or without an Internet Reverse Proxy.