Let’s go through the key steps which need to follow during SAP Cloud Connector upgrade in high availability on Linux environment. If you have set up a master and a shadow instance, you can perform the upgrade without downtime in high availability.
Preparations:
Check the compatibility and readiness of source system for upgrade.Check and take the status screenshot of connectivity to the SAP Cloud Platform sub accounts.Check and take the status screenshot of all the connection to back-end systems.Take the backup of config, scc_config folder under /opt/sap/scc file system in both the nodes(master & shadow).Take the screenshot of OS filesystem, env etc.VM Snapshot backup for both the master and shadow nodes before starting the upgrade.Check Cloud connector and JVM version : The current version can be found by navigating to the top right corner and clicking on the expand option at the side of the Username and select the option About. It will show version of Cloud Connector as well as jvm version.
Download the new release version of Cloud connector and jvm from https://tools.hana.ondemand.com/#cloud
Now unzip the downloaded file and upload on both the server nodes or place it on share file system (you can also use the unzip command on Linux OS).
Upgrade:
As said Cloud Connector environment is running in high availability, so we need to follow the below steps.
First upgrade the shadow instance.Post upgrade of shadow instance, switch over the node role using Switch Role function in Cloud Connector and it will swap the instance role from Master node to the Shadow node.The Shadow instance (upgraded node) will become the master node and previously master node become Shadow node, now start upgrade on shadow instance.
Shadow Node Upgrade
Recheck : Make sure pre-steps and VM Snapshot has been completed.Login to the shadow instance at os level and check the status of service.Status check command : systemctl status scc_daemon
Now stop the Cloud Connector services: systemctl stop scc_daemon with root user and recheck the service status.
You can also check the status using shadow node link.
First upgrade the jvm using sudo rpm -U sapjvm-8.1.101-linux-x64.rpm command where 8.1.101 is the jvm version.
Upgrade CC->Run the new release RPM Package as root user using the command sudo rpm -U com.sap.scc-ui-2.17.1-5.x86_64.rpm where 2.17.1-5 is Cloud Connector version.
Upgrade completed on shadow node, check the service status post upgrade using systemctl status scc_daemon, it should be up and running.
Check the upgraded version on shadow node.
Check the connectivity from master node to shadow node –> login to shadow node –>Shadow Connector
Due to upgrade, connectivity between Shadow node and Master node has broken, we need to reconnect using edit option from Connection to Master screen as highlighted in yellow. Fill the details of Mater node and click on save, it ill prompt for user name/ password.
Now both nodes are connected. We can do some sanity check on Shadow node.
Mater Node upgrade:
As upgrade has completed on Shadow node, so now it’s time to upgrade the master node.
To upgrade Master node:
Switch over the node role using Switch Role function from Master node Cloud Connector and it will swap the instance role from Master node to the Shadow node, then Shadow (upgraded node) will become the master node and previously master node become Shadow node, now start upgrade on shadow instance.Login to Master Node and go to High Availability tab and select the switch role.
Need your confirmation to switch the role
Now your master node become shadow node.
Start your upgrade on Shadow instance same as we follow the steps during previously Shadow node upgrade.
Post upgrade activity:
Perform the sanity check like connectivity, connection etc.Review the SCC Administrator portal for the Master -shadow configuration and if they are in sync.Check the alerts, log for any unusual error.
I would welcome to your comment, feedback, suggestion if you have any.
Thanks.
Reference:
2539713 – Upgrade to a new version of the Cloud Connector
Let’s go through the key steps which need to follow during SAP Cloud Connector upgrade in high availability on Linux environment. If you have set up a master and a shadow instance, you can perform the upgrade without downtime in high availability.Preparations:Check the compatibility and readiness of source system for upgrade.Check and take the status screenshot of connectivity to the SAP Cloud Platform sub accounts.Check and take the status screenshot of all the connection to back-end systems.Take the backup of config, scc_config folder under /opt/sap/scc file system in both the nodes(master & shadow).Take the screenshot of OS filesystem, env etc.VM Snapshot backup for both the master and shadow nodes before starting the upgrade.Check Cloud connector and JVM version : The current version can be found by navigating to the top right corner and clicking on the expand option at the side of the Username and select the option About. It will show version of Cloud Connector as well as jvm version. Download the new release version of Cloud connector and jvm from https://tools.hana.ondemand.com/#cloud Now unzip the downloaded file and upload on both the server nodes or place it on share file system (you can also use the unzip command on Linux OS).Upgrade:As said Cloud Connector environment is running in high availability, so we need to follow the below steps.First upgrade the shadow instance.Post upgrade of shadow instance, switch over the node role using Switch Role function in Cloud Connector and it will swap the instance role from Master node to the Shadow node.The Shadow instance (upgraded node) will become the master node and previously master node become Shadow node, now start upgrade on shadow instance. Shadow Node UpgradeRecheck : Make sure pre-steps and VM Snapshot has been completed.Login to the shadow instance at os level and check the status of service.Status check command : systemctl status scc_daemon Now stop the Cloud Connector services: systemctl stop scc_daemon with root user and recheck the service status. You can also check the status using shadow node link. First upgrade the jvm using sudo rpm -U sapjvm-8.1.101-linux-x64.rpm command where 8.1.101 is the jvm version. Upgrade CC->Run the new release RPM Package as root user using the command sudo rpm -U com.sap.scc-ui-2.17.1-5.x86_64.rpm where 2.17.1-5 is Cloud Connector version. Upgrade completed on shadow node, check the service status post upgrade using systemctl status scc_daemon, it should be up and running. Check the upgraded version on shadow node. Check the connectivity from master node to shadow node –> login to shadow node –>Shadow Connector Due to upgrade, connectivity between Shadow node and Master node has broken, we need to reconnect using edit option from Connection to Master screen as highlighted in yellow. Fill the details of Mater node and click on save, it ill prompt for user name/ password. Now both nodes are connected. We can do some sanity check on Shadow node. Mater Node upgrade:As upgrade has completed on Shadow node, so now it’s time to upgrade the master node.To upgrade Master node:Switch over the node role using Switch Role function from Master node Cloud Connector and it will swap the instance role from Master node to the Shadow node, then Shadow (upgraded node) will become the master node and previously master node become Shadow node, now start upgrade on shadow instance.Login to Master Node and go to High Availability tab and select the switch role. Need your confirmation to switch the role Now your master node become shadow node. Start your upgrade on Shadow instance same as we follow the steps during previously Shadow node upgrade. Post upgrade activity:Perform the sanity check like connectivity, connection etc.Review the SCC Administrator portal for the Master -shadow configuration and if they are in sync.Check the alerts, log for any unusual error. I would welcome to your comment, feedback, suggestion if you have any.Thanks.Reference: 2539713 – Upgrade to a new version of the Cloud Connectorhttps://help.sap.com/docs/PRODUCTION_CONNECTOR/199521d998ec49f48311f59e13f8ee85/6498d78f54fd4a26ba06333ec5b8bab0.html Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
