Which Domino Workloads to Migrate to Azure FirstApril 13, 2018
Last time, we talked about the many benefits of moving your Domino workloads to Microsoft Azure. In this post, we talk about where to start.
Many organizations start a Domino migration by moving their mail and file workloads to the cloud. In other words, they start with workloads that fall under Infrastructure as a Service (IaaS), shown below. To reduce their capital expenses, organizations often look at which of their remaining physical servers and networking hardware can move. These workloads are typically placed in data centers.
Source: Microsoft - What is IaaS?
Start with Domino servers
Of the IaaS workloads, we recommend that you start by moving Domino server workloads to Azure. These type of server migrations can be quick wins for moving to the cloud. Reason being, Domino servers tend to be isolated from other workloads and hosted on a stand-alone Windows server. So, these can often be easier to move first, without impacting other applications.
Plus, moving the Domino servers helps you reduce spend and increase security in these ways:
- Reduce the physical server footprint by moving to Azure
- Lower operating expenses even more by using managed services
- Take advantage of Azure features without having to increase capital expenditures
- Implement Azure security features to protect applications and data
- Ensure full compliance with regulatory requirements (like the GDPR)
Scenarios to watch out for
As you migrate your Domino servers, you’ll need to watch out for (and mitigate) these scenarios:
- Some Domino servers might be running on a non-Windows platform.
- Some applications running on a Domino server may be connecting to non-Domino applications running on other servers. The purpose for this connection is to read and/or write data. Though the end-point stays the same, a site-to-site virtual private network (VPN) or a dedicated wide area network (WAN) link maybe required.
- Some non-Domino applications may be connecting to applications running on Domino servers. The purpose for this connection is to read and/or write data to an application running on the Domino server. The connection statement in the non-Domino application may need to be updated because the Domino server endpoint might need to change.
We’ll talk about these issues (and more) in the next blog in this series. For now, this hopefully helps you start thinking through the process of moving workloads to the cloud. And if you’d like even more help, we’d be happy to walk you through it. See more about how Binary Tree can help you modernize your applications.
Here are some key Microsoft resources about IaaS that you might find helpful:
- What high availability looks like in Azure
- Clustering and high-availability
- What to do when an Azure service disruption impacts Azure VMs
- Azure to Azure replication architecture