Upgrade a Galaxy Repository node

Important: Upgrade the GR node before upgrading other nodes.

When you upgrade a GR node, the local Platform and all hosted objects are undeployed and the database schema is migrated from the existing schema to the Application Server 2023 R2 SP2 schema. Existing data from the GR is also migrated to the new schema.

You must upgrade all Application Server components (IDE, Bootstrap, and GR) to the same version that are installed on the GR node.

SQL Server Considerations

If the GR node contains less than the recommended RAM amount, system performance may be impacted as SQL Server will use more CPU to compensate for the lower amount of available memory. To improve system performance, set the SQL Server minimum memory (min server memory) to 1/3 of total physical memory. See "Allocating Galaxy Repository Node Memory" in the Application Server User Guide for additional information.

To upgrade the GR node

1. Review the status of objects deployed in the system and take appropriate action, if needed.

2. Run Setup.exe from the install media.

3. When the Installation Complete dialog box appears, select Configure to continue. Reconfigure any components as required.

   Important: Configure all GR nodes in multi-galaxy environments to point to a single System Management Server.

4. Close the Configurator and restart the computer to complete the upgrade.

5. When the GR node has been upgraded, open the IDE and connect to the galaxy. The galaxy will be automatically migrated to System Platform 2023 R2 SP2.

   Note: If you are using a remote IDE node to connect to the galaxy, make sure that you have upgraded the IDE node before connecting to the galaxy.