SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

  • Home
  • Products
    • SIOS DataKeeper for Windows
    • SIOS Protection Suite for Linux
  • News and Events
  • Clustering Simplified
  • Success Stories
  • Contact Us
  • English
  • 中文 (中国)
  • 中文 (台灣)
  • 한국어
  • Bahasa Indonesia
  • ไทย

12 Questions to Uncomplicate Your Cloud Migration

September 10, 2021 by Jason Aw Leave a Comment

12 Questions to Uncomplicate Your Cloud Migration

12 Questions to Uncomplicate Your Cloud Migration

Cloud migration best practices 

The “cloud is becoming more complicated,” it was the first statement in an hour-long webinar detailing the changes and opportunities with the boom in cloud computing and cloud migration.  The presenter continued with an outline of cloud related things that traditional IT is now facing in their journey to AWS, Azure, GCP or other providers.

There were nine areas that surfaced as complications in the traditional transition to cloud:

  • Definitions
  • Pricing
  • Networking
  • Security
  • Users, Roles, and Profiles
  • Applications and Licensing
  • Services and Support
  • Availability
  • Backups

As VP of Customer Experience for SIOS Technology Corp I’ve seen how the following areas can impact a transition to cloud. To mitigate these complications, consumers are turning to managed service providers, cloud solution architects, contractors and consultants, and a bevy of related services, guides, blog posts and related articles. Often in the process of turning to outside or outsourced resources the complications to cloud are not entirely removed.  Instead, companies and the teams they have employed to assist or to transition them to cloud still encounter roadblocks, speed bumps, hiccups and setbacks.

Most often these complications and slowdowns in migrating to the cloud come from twelve unanswered questions:

  1. What are our goals for moving to the cloud?
  2. What is your current on-premise architecture?  Do you have a document, list, flow chart, or cookbook?
  3. Are all of your application, database, availability and related vendors supported on your target cloud provider platform?
  4. What are your current on-premises risks and limitations?  What applications are unprotected, what are the most common issues faced on-premises?
  5. Who is responsible for the cloud architecture and design?  How will this architecture and design account for your current definitions and the definitions of the cloud provider?
  6. Who are the key stakeholders, and what are their milestones, business drivers, and deadlines for the business project?
  7. Have you shared your project plan and milestones with your vendors?
  8. What are the current processes, governance, and business requirements?
  9. What is the migration budget and does it include staff augmentation, training, and services? What are your estimates for ongoing maintenance, licensing, and operating expenses?
  10. What are your team’s existing skills and responsibilities?
  11. Who will be responsible for updating governance, processes, new cloud models, and the various traditional roles and responsibilities?
  12. What are the applications, services, or functions that will move from IaaS to SaaS models?

Know Your Goals for the Cloud

So, how will answering these twelve questions will improve your cloud migration. As you can see from the questions, understanding your goals for the cloud is the first, and most important step.  It is nearly universally accepted that “a cloud service provider such as AWS, Azure, or Google can provide the servers, storage, and communications resources that a particular application will require,” but for many customers, this only eliminates “he need for computer hardware and personnel to manage that hardware.” Because of this fact, often customers are focused on equipment or data center consolidation or reduction, without considering that there are additional cloud opportunities and gaps that they still need to consider. For example, cloud does eliminate management of hardware, but it “does not eliminate all the needs that an application and its dependencies will have for monitoring and recovery,” so if your goal was to get all your availability from the cloud, you may not reach that goal, or it may require more than just moving on premises to an IaaS model.   Knowing your goals will go a long way in helping you map out your cloud journey.

Know Your Current On-Premises Architecture

A second critical category of questions needed for a proper migration to the cloud, (or any new platform) is understanding the current on-premises architecture. This step not only helps with the identification of your critical applications that need availability, but also their underlying dependencies, and any changes required for those applications, databases, and backup solutions based on the storage, networking, and compute changes of the cloud.  Answering this question is also a key step in assessing the readiness of your applications and solutions for the cloud and quantifying your current risks.

A third area that will greatly benefit from working through these questions occurs when you discuss and quantify current limitations.  Frequently, we see this phase of discovery opening the door to limitations of current solutions that do not exist in the cloud.  For example, recently our services team worked with a customer impacted by performance issues in their SQL database cluster.  A SIOS expert assisting with their migration inquired about the solution and architecture, and VM sizing decisions. After a few moments, a larger more application sized instance was deployed correcting limitations that the customer had accepted due to their on-premise restrictions on compute, memory, and storage.  Similarly we have worked with customers who were storage sensitive.  They would run applications with smaller disks and a frequent resizing policy, due to disk capacity constraints. While storage costs should be considered, running with minimal margins can become a limitation of the past.

Understand Business and Governance Changes

The final group of questions help your team understand schedules, business impacts, deadlines, and governance changes that need to be updated or replaced because they may no longer apply in the cloud. Migrating to the cloud can be a smooth transition and journey.  However, failing to assess where you are on the journey and when you need to complete the journey can make it into a nightmare. Understanding timing is important and can be keenly aided by considering stakeholders, application vendors, business milestones, and business seasons.  Selfishly, SIOS Technology Corp. wants customers to understand their milestones because as a Service provider it minimizes the surprises. But, we also encourage customers to answer these questions as they often uncover misalignment between departments and stakeholders. The DBAs believes that the cutover will happen on the last weekend of the month, but Finance is intent on closing the books over the final weekend of the same month; or the IT team believes that cutover can happen on Monday, but the applications team is unavailable until Wednesday, and perhaps most importantly the legal team hasn’t combed through the list of new NDAs, agreements, licensing, and governance changes necessary to pull it all together.

As customers work through the questions, with safety and empathy, what often emerges is a puzzle of pieces, ownership, processes, and decision makers that needs to be put back together using the cloud provider box top and honest conversations on budget, staffing, training, and services.  The end result may not be a flawless migration, but it will definitely be a successful migration.

For help with your cloud migration strategy and high availability implementation, contact SIOS Technology Corp.

– Cassius Rhue, VP, Customer Experience

Learn more about common cloud migration challenges.

Read about some misconceptions about availability in the cloud.

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Amazon AWS, Amazon EC2, Azure, Cloud, High Availability, migration

3 Steps to Effective IT System Redundancy

September 5, 2021 by Jason Aw Leave a Comment

3 Steps to Effective IT System Redundancy

3 Steps to Effective IT System Redundancy

In some industries duplicate tasks can be a waste of company resources and could introduce unintended human error and loss of time. But in the IT world of managing systems and data, the duplication process referred to as “redundancy” is critical to the continued success of your organization.

1.  Protect Both Your Devices and Software with Redundancy Tools

IT tools that provide redundancy ensure your system and software assets are protected from loss or corruption. They should also provide for a timely recovery to restore interruptions of your business.

Redundancy in IT systems means having the ability to duplicate your system components, whether on hardware, VMs, or the cloud. At the user level, a simple example is making a copy of the user’s PC system and storing it on another PC as a spare in case the user’s PC fails.

This same concept can be applied to any other computer component, including servers, storage devices, and networking equipment. For example, “mirroring” is the mechanism for writing the same data to multiple disks, making those disks redundant.

Redundancy enables you to recover from a device failure by switching to a spare device as soon as possible. Businesses rely heavily on their IT systems, and a service outage caused by a system failure can cause considerable downtime of operations. As a result, redundancy is indispensable for the IT system to remain resilient to failure and reduce the risk of business interruption. Depending on your organization’s size and geographical locations, this could be difficult, time-consuming, and costly.

2. Keep All Data Current and Synchronized with Clustering

Having redundant devices with the same specifications and environment (operating system and software) does not automatically safeguard the loss of user files and emails, and mission-critical application data when there is a failure. This is true for not only an individual user’s PC but also the larger enterprise scale, across multiple servers and storage devices. Failure of a data storage device could render your business operations to significant delays without access to the latest data. For large applications like SQL Server, Oracle, or SAP, recovery time could be significant.

Unfortunately, many companies believe their risk is reduced by simply backing up their data. However, until a production device suddenly fails, most people do not realize how difficult it is to actually restore the data to a standby device from the backup copy.

In stark contrast, with a standby device that already has the ability to use the same data that was on the failed production device, all you have to do is start up the standby machine and switch to it. The recovery work will be much easier. This is possible with a High Availability (HA) cluster system.

Clustering helps improve reliability and performance of software and hardware systems by creating redundancy to compensate for unforeseen system failure. The HA cluster system consists of redundant servers in the active and standby systems and external storage (e.g., shared disk) that both servers can access. In the unlikely event that the operating server fails, by switching to the standby server, the service can be continued with the combination of the standby server and the external storage containing the latest data.

By the way, the same function can be achieved with “replication“, which synchronizes data between disks inside the server in real time. Replication is also an excellent measure against Disaster Recovery because it does not require the installation of expensive external storage and keeps the latest data on both instances. Depending on the location of the secondary instance, data is either synchronously or asynchronously replicated. Be aware that how the data is replicated impacts Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPO).

3.  Automate Failover

Whether you utilize an HA cluster system or replication, the best practice is to avoid manual switch-over of your server when a failure occurs. Instead, automate the process so that it is performed without delay in a process called failover. Configuring an automated failover of the HA cluster system / replication minimizes downtime as much as possible and reduces human error.

SIOS SAN-based and SANLess clustering solutions provide high availability and disaster recovery for mission-critical applications in physical, virtual, cloud or hybrid cloud environments. For further information, refer to our Windows and Linux high availability products.

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Redundancy

Migrating Applications To The Cloud

August 29, 2021 by Jason Aw Leave a Comment

Migrating applications to the cloud

Migrating Applications To The Cloud

How do we get there?

In your journey to the cloud and higher availability, consider the advice of author and entrepreneur  Nilofer Merchant (having the one link below is fine).

In less than 72 hours, I’ve answered the same question multiple times: How do you get there?  It started with one of my older daughters asking me how to get to a school-related appointment, followed by a younger child asking me what route we were taking to a store, and finally my oldest daughter asking me how to get to a particular destination somewhere in the state. They all asked the same question. But in each case, the context of the question and the expected answer was very different. As author and entrepreneur Nilofer Merchant says, a lot about the answer to the question ‘how do you get there?’ depends not only on your there, but also on your here.

What is your “here” with current applications?

The first step in figuring out how to move your application there (to the cloud, or to higher availability in the cloud) is to name “here” correctly.  So, what’s your “here”?  Your answer to this question can be as varied as the locations in my conversations with my daughters. One of my daughters asked from the context of our house. Another’s context was from a starting point in a different state, and the youngest was asking from a place of theory (hoping that we’d get milkshakes).

As you consider your definition and the details of “here” start by asking some basic questions:

  1. What are your critical applications, and how are they protected?
  2. Where are you in your deployment of high availability protection for your application?
  3. How is your critical data protected?
  4. What is the size of your current team?
  5. How confident are you in your solutions and services for protecting your application and data?
  6. Where are your critical enterprise systems and application workloads currently running?
  7. If you are on-premises, is that an on-premises server, or virtual machine? Or is here a private cloud, or public cloud without HA?
  8. What is your budget for the move to the cloud and for managing your application in the cloud moving forward?
  9. What weariness, uncertainty, uneasiness, or dissatisfaction do you feel “here”?

Defining “here” is the starting point, which helps us feel our way towards a better “there,” so take your time.  Think about what else shapes, defines, restricts, or exists within the parameters of your “here”?  Is “here” a multi-product deployment, global IT Team infrastructure, or some other multiple location, multiple office arrangement?  Are your teams globally distributed, outsourced, or a combination?  If you looked at your “here” what things stand out, what are your team, company, product, or enterprise markers?  What are the key and commonly recurring pain points, such as lack of training, missing redundancy, incomplete architecture guides, disappointment with the incumbent solutions, cloud complexity,

What’s your “there”? Private, public, hybrid or multi-cloud?

After you have figured out your “here”, the second step to lift from Merchant’s article is “figuring out what ‘there’ might be. As VP of Customer Experience, I have worked with a number of customers who want a “there” to be an environment with zero downtime, planned or unplanned, or one in which application failovers are seamless and complete within two minutes or less. Other customers have less lofty goals, seeking downtime that fits within a five (5) to nine (9) minute window, or who prefer longer windows with options for manual overrides based on responses to failure notifications. Still other customers want a “there” with better notifications, clear resolutions and recommendations, application-specific orchestration, and a way to augment their teams with experts from vendors and partners.  So what are the key features of your ‘there’? What can you afford?

When you look over the painstaking answers of “here,” what stood out?  What items from “here” need to be addressed to create a more desirable future version of your team, enterprise, availability, datacenter, and life. Does your “there” include more resiliency and redundancy, more application orchestration, better analytics, or lower costs?  Where does private, public, hybrid, or multi-cloud figure into your “there”?  How does your “here” improve because you have made it to “there.”

From “here” to “there”

The final step, according to Merchant, is “figuring the way we get from ‘here’ to ‘there’. If it is hard to be in your “here”, it only makes sense to put in the work to think about what “there” could be. In other words, think beyond simply moving your application to the cloud. Consider the resources and services you’ll need to create a result that meets all of your expectations. Think about the vendors, solution providers, services teams, and companies that specialize in purpose-built high availability solutions can help you get “there”.

Unlike my daughter’s “there”, there is no Waze for plotting a journey from “here” to “there” or cloud migrations. However, by carefully thinking through both your current situation, including your pains, frustrations, budget limitations, and your desired outcome, you can arrive at a solution that is more than a simple cloud migration. It can mean a more gratifying daily experience unencumbered by the fear of application failure and downtime and the hassle of troubleshooting and end-user complaints.

Taking Merchant’s advice when planning an application migration to the cloud can lead you to a wide range of possibilities from defining a more robust architecture, changing HA software solutions, engaging in services providers, moving to a multi-cloud, hybrid cloud, or other cloud model.  It might even mean moving back to using your own datacenter.

For more than 20 years, SIOS has been helping companies implement high availability and disaster recovery protection for critical applications on premises, in the cloud and hybrid cloud environments. We can provide the expertise to help you through your application HA and DR journey from ‘here’ to ‘there’ and beyond. For more information, contact SIOS

– Cassius Rhue, VP, Customer Experience

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Applications, Cloud

Clustering SAP #ACS And #ERS On #AWS Using Windows Server Failover Clustering

August 25, 2021 by Jason Aw Leave a Comment

Clustering SAP #ACS And #ERS On #AWS Using Windows Server Failover Clustering

Clustering SAP #ACS And #ERS On #AWS Using Windows Server Failover Clustering

When ensuring high availability for SAP ASCS and ERS running on Windows Server, the primary cluster solution you will want to use is Windows Server Failover Clustering. However, when doing this in AWS you will quickly discover that there are a few obstacles you need to know how to overcome when deploying this in AWS.

I recently wrote this Step-by-Step guide that was published on the SAP blog that walks you through the entire process. If you have any questions, please leave a comment.

Reproduced with permission from Clusteringformeremortals

Filed Under: Clustering Simplified Tagged With: Clustering

Glossary: Windows Server Failover Clustering (WSFC)

August 19, 2021 by Jason Aw Leave a Comment

Glossary Windows Server Failover Clustering

Glossary of Terms: Windows Server Failover Clustering
(WSFC)

Definition: A Windows Server Failover Clustering (WSFC) cluster is a group of independent servers that work together to increase the availability of applications and services. SQL Server 2017 takes advantage of WSFC services and capabilities to support Always On availability groups and SQL Server Failover Cluster Instances. SIOS DataKeeper is integrated with WSFC adding the configuration flexibility to build WSFC clusters in the cloud.

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: glossary, Windows Server Failover Clustering

  • « Previous Page
  • 1
  • …
  • 52
  • 53
  • 54
  • 55
  • 56
  • …
  • 104
  • Next Page »

Recent Posts

  • Transitioning from VMware to Nutanix
  • Are my servers disposable? How High Availability software fits in cloud best practices
  • Data Recovery Strategies for a Disaster-Prone World
  • DataKeeper and Baseball: A Strategic Take on Disaster Recovery
  • Budgeting for SQL Server Downtime Risk

Most Popular Posts

Maximise replication performance for Linux Clustering with Fusion-io
Failover Clustering with VMware High Availability
create A 2-Node MySQL Cluster Without Shared Storage
create A 2-Node MySQL Cluster Without Shared Storage
SAP for High Availability Solutions For Linux
Bandwidth To Support Real-Time Replication
The Availability Equation – High Availability Solutions.jpg
Choosing Platforms To Replicate Data - Host-Based Or Storage-Based?
Guide To Connect To An iSCSI Target Using Open-iSCSI Initiator Software
Best Practices to Eliminate SPoF In Cluster Architecture
Step-By-Step How To Configure A Linux Failover Cluster In Microsoft Azure IaaS Without Shared Storage azure sanless
Take Action Before SQL Server 20082008 R2 Support Expires
How To Cluster MaxDB On Windows In The Cloud

Join Our Mailing List

Copyright © 2025 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in