Open topic with navigation

# Checklist: Upgrading Your On-premises Environment

Throughout the rolling upgrade process, services not actively being upgraded would continue to be available. Services that utilize the ArcSight Database, such as event ingestion and search, would be interrupted during the Database upgrade phase, but any in-flight data would be cached and processed as soon as the Database upgrade completes.

If you deployed and configured your system for high availability, during the rolling Kubernetes worker node upgrade process, services delivered by pods on the affected worker node would be restarted on another worker node. Similarly, the upgrade of Kubernetes pods is performed in a rolling manner, so there would be a brief pod-level service pause as pods are restarted to perform the upgrade. Some services, such as Transformation Hub, can be configured for high availability with pod replicas so that there are no service pauses during the rolling upgrade.

Caution: For on-premises deployments only, when upgrading to ArcSight Platform 23.2 there is a defect within the Kubernetes upgrade process that results in more downtime of Transformation Hub services than is normally expected. Transformation Hub’s Kafka service is unavailable for approximately 3 minutes (in a 3-master deployment) or 10 minutes (in a 1-master deployment). After Transformation Hub’s Kafka resumes service, events already received are available to Transformation Hub’s consumers and any events that were cached by SmartConnectors begin flowing to Transformation Hub. This is a defect in the upgrade to ArcSight Platform 23.2 that we anticipate will not be present in future upgrades. Tracking Id: OCTCR33I555045.

Use this checklist to complete the upgrade tasks in the listed order.

| Task | See
--- | --- | ---
| Ensure that you are upgrading from and to the correct version of ArcSight Platform | ArcSight Platform Upgrade Paths
| Consult the Platform Release Notes to identify the product versions, specific files to download, and known issues related to the upgrade | See "Downloading the ArcSight Platform Installation Files" in Release Notes for ArcSight Platform 23.3
| Download the installation packages | Downloading the Installation Packages for an On-Premises Deployment
| Back up the ArcSight Platform configuration data; the Postgres database, which contains the configuration of your deployed capabilities; and, if you have Intelligence or Recon deployed, the ArcSight Database | Backing Up and Restoring
| Backing Up the Elasticsearch data | Backing Up Elasticsearch Data
| (Conditional) If your deployment includes Intelligence or Recon, upgrade the Database | Upgrading the ArcSight Database
| Use the arcsight-install tool to upgrade the OMT infrastructure | Upgrading OMT with the ArcSight Installer
| Upgrade the deployed capabilities | Upgrading Deployed Capabilities
| Complete post-upgrade tasks | Completing Post-Upgrade Tasks
| (Conditional) If your environment includes ESM, you should upgrade to the latest version | Upgrading ESM
| (Conditional) If you have purchased licenses for additional capabilities, deploy them to your environment | Adding Additional Capabilities to an Existing Cluster