Skip to Content
Author's profile photo Simen Huuse

High availability for SAP Cloud Connector – 2.10

The preferred way of connecting your SAP cloud application or HANA in the cloud to your SAP on-premise components is by using the SAP Cloud Connector (SCC). I’m sure that if you read this, then you already know the capabilities of the cloud connector. If not, read this.

When you get serious about your cloud portfolio running together with your on-prem and require a certain level of service quality, you probably want to eliminate the SCC as a single point of failure in your landscape. Hence, you can take use of the high availability setup in SCC.

Murali Shanmugham wrote a great blog post last year on how to set up high availability for SCC. However, after Murali wrote the blog, some cosmetic changes in the later versions of the SCC (2.10.1 in my case) makes the look and feel a bit different. I want to share some updated details with you in this blog.

Before you start

Prerequisites for achieving high availability is that you have two SAP Cloud Connector installed. During first installation, you are asked if you want to set up a master or shadow system. So going forward, you want one master and one shadow. Ideally, they should not be located on the same infrastructure to optimize redundancy.

The not so dirty dirty-work:

Log on to your master instance, go to the High Availability menu and click the magic want “Enable” button.


This will make the master instance accept the request coming in from the shadow later on. You will be warned that a shadow instance is not setup:

That’s ok. Lets move on to the shadow. Logon to it, and click the pencil under “Shadow Connector” – “Connect To Master”.

Now, we must tell the shadow about the master. On the shadow instance, fill in the details of the master instance:

Save it.


Ready to connect

You are now ready to connect. Click the “Connect” icon:

You are prompted for the username and password of the master instance. Fill in and click OK:

The shadow will try to connect to the master:

After a few seconds, it should connect ok:

You should be able to see the mirrored connections when you click “Mirrored Subaccounts”:

Are we there yet?

Now, you can go on to verify that the setup works by switching of the master instance and checking the connection from your SAP Cloud Platform account.

If you did this on an pre-existing SCC, chances are that your newly setup shadow instance is on a higher version or patch level than your master. You will be warned like this:  

Good thing you have set up high availability – because now you can upgrade your master with very little down time!

From your master, click “Swith Roles” in the “High Availability” menu:

When complete, you can shut down the master and perform the upgrade. Phil Cooley explains:

When the upgrade is complete, you should start your newly upgraded SCC. If you are particular about which instance is master and shadow, you should switch them again.

With both SCCs on the same level, you get a nice green color on the version attributes:


That’s it. High availability ready to go!











Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Morten Wittrock
      Morten Wittrock

      Hi Simen

      One small detail: Even with high availability configured, upgrading Cloud Connector is not zero downtime. When the roles are switched, there is a small window in which the configured resources are not available. However, that window is much, much shorter, of course, than if you were to upgrade without high availability.



      Author's profile photo Simen Huuse
      Simen Huuse
      Blog Post Author

      Hi Morten,

      That's right. In my setup it seems to be about two seconds of disconnection. Will update the text.

      Thanks for pointing that out!

      All the best,


      Author's profile photo Murali Shanmugham
      Murali Shanmugham

      Hi Simen,

      Thanks for posting an updated blog on this topic and touching on the additional features :). I have updated my blog with a link to this one. Cheers

      Author's profile photo Simen Huuse
      Simen Huuse
      Blog Post Author

      Thanks, Murali! Your work was crucial to get this going in the first place 🙂

      All the best,


      Author's profile photo Phil Cooley
      Phil Cooley

      Thanks Simen Huuse for the mentions and like Murali have updated both of my blogs with a link to yours to explain High Availability in the new version. Thanks!

      Author's profile photo Simen Huuse
      Simen Huuse
      Blog Post Author

      Thanks, Phil! 🙂 Stay in touch.


      Author's profile photo Domaine Technical Operations
      Domaine Technical Operations

      Hello Simen,

      Would you know a way to identify the master from the shadow SCC easily before trying and connect to one of the nodes?

      Best regards.

      Author's profile photo Nagarajan M
      Nagarajan M

      Hi Simen Huuse

      Hi Murali Shanmugham

      Let’s take I enabled HA setup but still its two different installation.

      When I shift to secondary the IP/hostname will get change right?

      Do we have any option to connect these two SCC via common IP/hostname?