4 key challenges of migrating Domino servers to Azure

This is the next post in our series about migrating IBM Domino servers to Microsoft Azure. In earlier posts, we talked about the benefits of moving your Domino server workloads to the cloud, plus the reasons why they’re a great place to start. Here, we go over some scenarios to watch out for as you migrate (and how to fix).

Challenge 1: Consolidating servers

Before you migrate, you should look for ways to set yourself up to run fewer Domino servers. The more you consolidate, the fewer servers you’ll have to move to Azure (and the fewer you’ll have to run when you get there). As an example, the graphic on the left shows a common configuration in which an organization uses an extra Domino hub server. 

How to fix: Ideally, you shouldn’t need to replicate each Notes database on a Domino server in Azure. That means you should no longer need a hub server, either. So you can simplify your server configuration to something like the example on the right below.


Before: A Domino hub server

After: No Domino hub servers


Challenge 2: Running on a non-Windows platform

You might find that some of your Domino servers are running on a non-Windows platform. This can make it a bit trickier to move them over to Azure. But the good news is that Azure supports virtual machines.

How to fix: Use virtual machines in Azure to run Domino servers on non-Windows operating systems. Of course, if your Domino server is running on an I-series (i.e. OS/400 and formerly known as AS/400), you should move any Notes applications to either a Linux or Windows virtual machine on Azure.

Domino on Azure | Binary Tree 

Challenge 3: Connecting to non-Domino applications

Some of the applications running on your Domino servers might connect to non-Domino applications running on other servers. Often, this is to read and/or write data. You should find and update these interdependencies as early as possible in the migration process, so there’s no breakdown in connectivity later.

How to fix: Although the end-point stays the same, you might need to use a site-to-site virtual private network (VPN) or a dedicated wide area network (WAN) to keep the applications connected. Your best option might be to set up an ExpressRoute IPVPN connection. IPVPN providers (typically MPLS VPN) offer any-to-any connectivity between your organization’s branch offices and data centers. This means you can connect the Microsoft cloud to your WAN and make the cloud look just like any other branch office.


Challenge 4: Non-Domino applications connecting to Domino servers

Some of your non-Domino applications might connect to applications running on Domino servers. Often, the purpose for this connection is to read and/or write data to an application running on the Domino server. Again, you should pinpoint these types of external connections before you start your migration, so things don’t break later. 

How to fix: Start by checking the server log records to find any external connections. Then you might need to update the connection statement in the non-Domino application to reflect a new Domino server end-point.

What’s next

These are some of the challenges you’ll face when migrating Domino server workloads. In our next post, we’ll share a three-step process to migrate Domino server workloads to Azure. Contact us if you’d like even more help solving your Domino server challenges.  we’d be happy to walk you through it.


More in the series