--- schema_version: "1" id: 4a0f13eeb8b3f9fb5a16ad75804fe5d120a207ca09c52e5c9b9fc1e4892c68c0 title: Migrating Anypoint Platform PCE v3.X to v4.X collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/private-cloud/4.2/upgrade.md canonical_url: https://docs.mulesoft.com/private-cloud/4.2/upgrade source_site: docs.mulesoft.com content_type: documentation content_hash: 18363c021b271f1d49c5cedd8084003277c2a8c9716e5486250dc91162cfb516 description: MuleSoft Documentation Site release: "4.2" latest: false --- --- product: Anypoint Platform Private Cloud Edition version: 4.2 --- # Migrating Anypoint Platform PCE v3.X to v4.X > For the full documentation index, see: https://docs.mulesoft.com/llms.txt > [!NOTE] This procedure is also applicable if you need to migrate from PCE 4.x to PCE 4.x instead > of an in-place upgrade. Replace the 3.x system with your source PCE 4.x system in the procedure > below. > [!NOTE] Contact MuleSoft Professional Services or your Anypoint PCE Certified Partner to perform a > migration of your Anypoint Platform PCE. To migrate an Anypoint Platform Private Cloud Edition (Anypoint Platform PCE) deployment from version 3.x to 4.x, perform a full state backup on your existing source cluster (Cluster 1) and restore that data onto a newly provisioned target cluster (Cluster 2) running Anypoint Platform PCE 4.x. Before proceeding, make sure that in your source Anypoint PCE 3.x cluster, you have `ssh` access to your cluster nodes and the necessary `kubectl` permissions for both environments. ## Configure Environment and Security Before generating the backup files, you must correctly identify the platform via DNS and secure it with valid certificates. ### Define DNS and Platform Identification 1. In Amazon Route 53, create a new A or CNAME record to point your load balancer to the PCE 3.x DNS (for example, `pce3.mulesoft.com`). 2. In the Anypoint Platform UI, navigate to **Access Management > DNS/IP** and enter the Platform DNS address hosting your 3.x instance. 3. In the Anypoint Platform UI, click **Save** to apply the DNS changes to the platform configuration. ### Set Up SSL Certificates 1. In your local terminal, generate a 2048-bit RSA key and a self-signed certificate by running the provided `openssl` command. openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout key.pem -out cert.pem 2. In the Anypoint Platform UI, navigate to **Access Management > Security**. 3. In the Anypoint Platform UI, click **Choose File** for both the **Certificate** and **Private Key** fields to upload the `cert.pem` and `key.pem` files generated in the previous step. ## Back Up Platform State and Infrastructure This section focuses on capturing the database state and service configurations using the Gravity and Kubernetes CLI tools. ### Patch Kubernetes Configuration 1. In the PCE Cluster Terminal, apply the configuration patch to exclude incompatible secrets and buckets from the 4.x migration. kubectl apply -f pce3-update-config.yaml apiVersion: v1 kind: ConfigMap metadata: name: backup-restore-config data: namespaces: "default access-management amf amc arm audit-log api-designer api-manager core-paas design-center exchange mocking mozart pce pce-core visualizer dias monitoring-center" ignore-buckets: "cpc-resources static-assets healthz" ignore-databases: crowdmigrator ^db\\S\*$ sw\_database ignore-secrets: "objectstore-s3-secret telegraf-influxdb-creds nginx-ssl cluster-ca cluster-default-ssl dias-insight-cassandra-connection-password hybrid-rest-cloudhub-keystore hybrid-rest-root-cert runtime-manager-keystore runtime-manager-truststore cloudhub-mcm-keystore" #these hybrid/runtime-manager secrets are ignored since they are generated based on the platform DNS, which is not modified by b/r. See https://github.com/mulesoft/onprem-config-api/blob/master/assets/cloudhub-mcm-keystore/create-keystore.sh ignore-releases: "core-paas-namespaces stolon stolon-amv pce-seaweedfs-app pce-cluster-ssl-app dias-prov-k8s-am-influxdb-comp dias-prov-k8s-am-ingestor-comp" pvc-to-delete: "dias-prov-k8s-cassandra-comp dias-prov-k8s-insight-comp" skip-version-check: "true" apiVersion: v1 data: backup\_s3\_continue\_if\_error: "false" backup\_s3\_max\_attempts: "3" backup\_s3\_sequentially\_bucket\_names: "" backup\_s3\_sleep\_time\_seconds: "30" ignore-buckets: cpc-resources static-assets healthz ignore-databases: crowdmigrator ^db\\S\*$ sw\_database ignore-releases: core-paas-namespaces stolon stolon-amv pce-seaweedfs-app pce-cluster-ssl-app dias-prov-k8s-am-influxdb-comp dias-prov-k8s-am-ingestor-comp ignore-secrets: objectstore-s3-secret telegraf-influxdb-creds nginx-ssl cluster-ca cluster-default-ssl dias-insight-cassandra-connection-password hybrid-rest-cloudhub-keystore hybrid-rest-root-cert runtime-manager-keystore runtime-manager-truststore cloudhub-mcm-keystore namespaces: default access-management amf amc arm audit-log api-designer api-manager core-paas design-center exchange mocking mozart pce pce-core visualizer dias monitoring-center pithos\_pod\_count: "2" pvc-to-delete: dias-prov-k8s-cassandra-comp dias-prov-k8s-insight-comp restore\_in\_parallel: "false" restore\_s3\_max\_attempts: "3" restore\_s3\_sleep\_time\_seconds: "30" skip-version-check: "true" kind: ConfigMap metadata: name: backup-restore-config ### Execute Gravity System Backup 1. In the PCE Cluster Terminal (Backup Node), trigger the core platform state backup by executing the gravity backup command. gravity backup /var/lib/gravity/planet/share/backup-3x-$(date +%d-%m-%y).tar.gz 2. In the PCE Cluster Terminal (Backup Node), generate the Anypoint Monitoring and Visualizer (AMV) specific backup using the internal restore script. /var/lib/gravity/site/packages/unpacked/gravitational.io/anypoint/3.2.0\*/resources/kubernetes/amv-backup-restore/amv-backup-restore.sh ## Preserve Persistent Data (NFS/EFS) In addition to the database state, you must manually preserve the project files and working directories stored on the distributed file system. ### Mount the External Storage 1. In the PCE Cluster Terminal, create a mount point and install the necessary NFS utilities. mkdir nfs\_mount\_folder sudo yum install nfs-utils -y 2. In the PCE Cluster Terminal, mount your AWS EFS (or external NFS) to the local directory. sudo mount -t nfs4 -o rw,vers=4.1 :/ /home/ec2-user/nfs\_mount\_folder ### Compress and Offload Assets 1. In the PCE Cluster Terminal, navigate to the mounted folder and compress the project and working directories. tar -cvzf projects.tar.gz projects tar -cvzf working\_Directories.tar.gz working\_Directories 2. In your Local Terminal, securely download the four critical artifacts (Platform Backup, AMV Backup, Projects Archive, and Working Directories Archive) to your local machine. scp -i your-key.pem ec2-user@:/tmp/backup-files/\*.tar.gz ~/Downloads/pce\_migration\_assets/ ## Initialize the Target 4.x Environment Before restoring data, you must configure the new cluster to recognize the platform identity and security parameters. ### Update Platform Routing and Identification 1. In Amazon Route 53, update your DNS records to point the load balancer to the new Anypoint PCE 4.x cluster (Cluster 2). 2. In the Anypoint Platform UI (New Cluster), navigate to **Access Management > DNS/IP** and enter the new DNS address assigned to your PCE 4.x instance. ### Apply New Security Certificates 1. In the Anypoint Platform UI (New Cluster), navigate to **Access Management > Security** and upload the certificates generated for the 4.x environment. 2. In the PCE 4.x Cluster Terminal, monitor the cluster to ensure all jobs related to DNS and certificate updates complete successfully and that all platform pods are in a `Running` state. ## Transfer and Stage Migration Assets Move the data extracted from PCE 3.x into the target 4.x infrastructure. ### Mount the Target External Storage 1. In the PCE 4.x Cluster Terminal, create the `nfs_mount_folder` and ensure the `nfs-utils` package is installed on the node. 2. In the PCE 4.x Cluster Terminal, mount your AWS EFS or external storage to the local mount point using the `mount -t nfs4` command. ### Upload and Extract Backup Data 1. In your Local Terminal, transfer the backup archives and project directories from your local machine to the new EC2 instance using the `scp` command. 2. In the PCE 4.x Cluster Terminal, extract the `projects.tar.gz` and `working_Directories.tar.gz` files into their respective persistent storage paths. ## Execute the Restoration Process Finalize the migration by updating system flags and triggering the restoration services via API. ### Adjust Kubernetes Migration Settings 1. In the PCE 4.x Cluster Terminal, open the backup-restore configuration for editing by running the `kubectl edit` command. kubectl edit cm backup-restore-config -n pce-core 2. In the editor, update the `skip-version-check` property to true to authorize the version-jump migration. ### Invoke Restoration Services via API 1. In your Local Terminal, obtain an authentication bearer token by providing your credentials to the login endpoint. curl -k --request POST \\ --header "Content-Type: application/json" \\ --data '{"username":"", "password": ""}' \\ https:///accounts/login 2. In your Local Terminal, trigger the core platform restoration using the backup file and target NFS server details. curl -k https:///platform/restore -X POST \\ -H "Authorization: Bearer ${token}" \\ -H "Content-Type: application/json" \\ -d "{\\"backup-file-name\\": \\"${backupFileName}.tar.gz\\", \\"nfs-server\\": \\"${fileSystemDns}\\", \\"nfs-path\\": \\"/\\"}" 3. In your Local Terminal, trigger the AMV restoration to migrate Monitoring and Visualizer data. curl -k https:///platform/amv/restore -X POST \\ -H "Authorization: Bearer ${token}" \\ -H "Content-Type: application/json" \\ -d "{\\"backup-file-name\\": \\"${backupFileName}.tar.gz\\", \\"nfs-server\\": \\"${fileSystemDns}\\", \\"nfs-path\\": \\"/\\"}" ## See Also - [Anypoint Platform PCE Overview](https://docs.mulesoft.com/private-cloud/4.2/) - [Installing or Upgrading Anypoint Platform Private Cloud Edition (Anypoint Platform PCE)](https://docs.mulesoft.com/private-cloud/4.2/install-workflow)