Upgrading the management server on zCX
Prerequisites
Docker (version 18 or later) or Podman (version 4.4.1 or later)
Upgrading from a specific version
Select the version you need to upgrade from.
Task 1: To obtain the installation files
Go toElectronic Product Distribution (EPD) and log in.
- Using the search bar, search for either BMC AMI Cloud Data or BMC AMI Cloud Vault. Both product files are composed with the same binaries.
- Click the version that you want to download.
- On the Product tab, select the files and click Download.
Task 2: To upload the s390x installation zip file
Upload the s390x installation zip to the zCX instance using scp or any other tool in binary mode.
Copy the s390x installation zip from the zCX instance to the alpine container:
Task 3: To stop the BMC AMI Cloud application container
Stop the server and remove the BMC AMI Cloud container that is running by using the following commands:
docker rm model9-v4.0.1
Task 4: To prepare the installation artifacts
In the Alpine container, open the BMC AMI Cloud artifact:
docker exec -it dummy sh
cd /root
unzip /root/model9-v4.1.1_build_dbdaead-server-s390x.zip 'model9*'
# Verify the existence of the diag directory. Create it if needed.
mkdir diag
# Backup the /conf directory.
tar -czf conf-backup.tar.gz conf
# Exit from the alpine container.
exit
Copy the docker container images from the alpine docker container (the one that was used during the initial installation):
Task 5: To load the new release artifacts
Load the new release docker containers:
Task 6: To back up the server before the upgrade
Run each command separately and check the results:
docker cp dummy:/root/conf-backup.tar.gz ./conf-$fileStamp.tar.gz
docker exec -it model9db pg_dump -p 5432 -U postgres -d model9 -f /tmp/model9db-$fileStamp.dump
docker cp model9db:/tmp/model9db-$fileStamp.dump ./model9db-$fileStamp.dump
docker exec -ti model9db rm /tmp/model9db-$fileStamp.dump
Task 7: To start the BMC AMI Cloud server
Run the new release container using the following command:
--sysctl net.ipv4.tcp_keepalive_time=600 \
--sysctl net.ipv4.tcp_keepalive_intvl=30 \
--sysctl net.ipv4.tcp_keepalive_probes=10 \
-v model9:/model9:z -h $(hostname) --restart unless-stopped \
--env-file <user home directory>/model9.env \
--network model9network \
--name model9-v4.1.1 model9:v4.1.1.dbdaead
Task 1: To obtain the installation files
Go toElectronic Product Distribution (EPD) and log in.
- Using the search bar, search for either BMC AMI Cloud Data or BMC AMI Cloud Vault. Both product files are composed with the same binaries.
- Click the version that you want to download.
- On the Product tab, select the files and click Download.
Task 2: To upload the s390x installation zip file
Upload the s390x installation zip to the zCX instance using scp or any other tool in binary mode.
Copy the s390x installation zip from the zCX instance to the alpine container:
Task 3: To stop the BMC AMI Cloud application container
Stop the server and remove the BMC AMI Cloud container that is running by using the following commands:
docker rm model9-v4.0.0
Task 4: To prepare the installation artifacts
In the Alpine container, open the BMC AMI Cloud artifact:
docker exec -it dummy sh
cd /root
unzip /root/model9-v4.1.1_build_dbdaead-server-s390x.zip 'model9*'
# Verify the existence of the diag directory. Create it if needed.
mkdir diag
# Backup the /conf directory.
tar -czf conf-backup.tar.gz conf
# Exit from the alpine container.
exit
Copy the docker container images from the alpine docker container (the one that was used during the initial installation):
Task 5: To load the new release artifacts
Load the new release docker containers:
Task 6: To back up the server before the upgrade
Run each command separately and check the results:
docker cp dummy:/root/conf-backup.tar.gz ./conf-$fileStamp.tar.gz
docker exec -it model9db pg_dump -p 5432 -U postgres -d model9 -f /tmp/model9db-$fileStamp.dump
docker cp model9db:/tmp/model9db-$fileStamp.dump ./model9db-$fileStamp.dump
docker exec -ti model9db rm /tmp/model9db-$fileStamp.dump
Task 7: To start the BMC AMI Cloud server
Run the new release container using the following command:
--sysctl net.ipv4.tcp_keepalive_time=600 \
--sysctl net.ipv4.tcp_keepalive_intvl=30 \
--sysctl net.ipv4.tcp_keepalive_probes=10 \
-v model9:/model9:z -h $(hostname) --restart unless-stopped \
--env-file <user home directory>/model9.env \
--network model9network \
--name model9-v4.1.1 model9:v4.1.1.dbdaead