Informing the IBM Community

Bring Power to the cloud with Northdoor and Skytap


For organisations that run their x86 workloads on Azure, Skytap offers the ability to bring IBM Power workloads into the same cloud, co-located for low latency and high performance. With your AIX, IBM i and Linux on Power workloads in Azure, you benefit from flexible capacity and pricing with no need to refactor or re-write your applications.  And you gain the ability to augment your applications with Azure services such as analytics and machine learning.

Whether your long-term goal is to keep workloads on IBM Power or replace them, Northdoor can help you get them out of the data centre and into the Azure cloud. We remove any concerns about in-house skills with full managed services for the platform or even for the applications themselves, leaving you free to focus on running your business. And if you decide to replace your Power workloads, Northdoor’s expert application practice can help you every step of the way.

For more information on how Northdoor can migrate your existing Power workloads to run natively on Azure, get in touch today to arrange a demonstration or full proof-of-concept for the Skytap cloud platform.

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.


2 responses to “Bring Power to the cloud with Northdoor and Skytap”

  1. Mr M Ryan avatar
    Mr M Ryan

    Really interesting.

    Is it possible to set up a dormant IBM i Partition (Low Cost) that can be ressurected in the event of a disaster (Real cost)? We could then Attach that host to our Azure Volume Backup, which we already have in our Azure environment.

    Mike Ryan

    1. Hi Mike,

      In a word – yes! You can create an LPAR for DR purposes and then shut this down whilst not in use. There’s still a ongoing cost for the storage as you always want to preserve the image of the LPAR but this is a small percentage of the overall cost of having the system running – the majority is in the CPU and Main Storage.

      You then have options either to periodically bring the LPAR back up to restore changes to keep it closer to the Production LPAR or just leave it shut down and restore all changes in the case of a disaster.

      Clearly you also have the option of leaving the LPAR running (but on minimal CPU and Main Storage to reduce cost) and replicating data into the Azure LPAR with a logical replication tool if you’re after a DR with a tighter RPO.

      Hope that helps,


Leave a Reply

Your email address will not be published. Required fields are marked *