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
  • ไทย

What is Amazon CloudWatch?

July 12, 2020 by Jason Aw Leave a Comment

What is Amazon CloudWatch

 

What is Amazon CloudWatch?

What you can do with CloudWatch and some hurdles to consider

With AWS boasting a dominant share of the cloud market, many companies are migrating their on-premises systems to the cloud with Amazon AWS.  So, how should a system running in the AWS environment be managed?

In this blog post, we will introduce the features of Amazon CloudWatch, a monitoring service provided by AWS, as well as the challenges of implementing it and how to solve them.

Using Amazon CloudWatch to closely monitor your AWS environment

To ensure that you have a stable cloud environment, it is important to detect anomalies (“system impairments”) quickly and respond in a timely manner.  Monitoring becomes an important and necessary task for any organization moving to the cloud.  This is no different than if you were managing on-premises applications and infrastructure. So, how should you monitor in an AWS environment?  One choice is to use Amazon CloudWatch, which monitors CPU, memory, and disk usage and notifies you when a predetermined threshold is exceeded.  Plus, you can set up your own metrics to monitor various items such as application logs.

The best part about Amazon CloudWatch is that it’s a service provided by AWS itself.  It has a high affinity with Amazon EC2 and other AWS services, so it can quickly respond to frequent functional extensions and specification changes, and can easily support AWS Auto Scaling, which automatically increases or decreases resources according to the load.  Amazon CloudWatch provides precise monitoring tailored to each environment’s unique circumstances.

Amazon CloudWatch implementation challenges

While Amazon CloudWatch is an ideal fit for organizations with experienced cloud engineers and DevOps teams, there are some things the average users should be aware of.

Amazon CloudWatch is effective for monitoring an organization’s AWS environment, but it requires a certain level of skill and knowledge to configure and deploy.  Especially when you set your own metrics, are setting up alerts, or taking into account Auto Scaling, the complexity increases. For example, If you’re setting up monitoring, it’s easy, but if you’re setting up email, rebooting, AutoScaling, etc., depending on the resource situation, it can be difficult.

If you want to automate the recovery process with instructions such as “restart the server when an error occurs”, you must first create a recovery scenario with an AWS Lambda script that provides a detailed description of the conditions and actions to be taken.  How familiar is your team with AWS Lambda?

The principal advantage of Amazon CloudWatch is that you can monitor your environment closely, but in order to do that, you must properly design in advance for each system what items to monitor and when, threshold values, etc.  These design tasks can take a lot of time.  Of course, your mission-critical systems need to be closely monitored in this way, but this level of detail and sophistication is not appropriate for all systems. For some, such as internal websites or WordPress servers, you will want to minimize your operating and labor costs. In such cases, we would like to suggest you consider a tool that can be more easily operated and managed.

For mission-critical applications, you need high availability protection with SIOS clustering software. Add SIOS DataKeeper software to a Windows Server Failover Clustering environment to create a SANless cluster in Amazon EC2 that fails over across availability zones and regions.  Use SIOS Protection Suite for Linux for application-aware clustering designed to simplify complexity and orchestrate failover according to application-specific best practices.

 Contact the SIOS availability experts today to learn more about achieving maximum uptime for your mission-critical applications.

Reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Amazon AWS, AppKeeper, Application availability, application monitoring

Enterprise Availability: Lessons from the Court

June 29, 2020 by Jason Aw Leave a Comment

Enterprise Availability: Lessons from the Court

Enterprise Availability: Lessons from the Court

I love basketball. I love to play it, watch it, and think through the cerebral aspects of the game; the thoughts and motivations, strategy and tactics. I like to look for the little things that work or fail, the screen set too soon or the roll that happened too late. I like defense and rotation. I like to know the coaches’ strategy for practice, walkthroughs, travel, and so on.  So naturally a few months ago, when I had a day off from the 24/7 world of availability, imagine that, I took my day off to watch basketball, and more specifically my daughter’s middle school basketball practice.

About a third of the way through watching, I couldn’t contain myself. I whistled to and “prodded” the young girl lollygagging and trotting up the court and yelled, “Run! Hustle!”  And she did, as did the teammates within earshot.  The next few minutes, plays, and drills were filled with energy, crisp cuts, smooth motions, and drive.  But, it didn’t last.  Instead, there were more whistles required, more emphatic pleas to move and run, to play hard, make sharp cuts, dive, pay attention, focus, learn, and correct. When the 2 hours were nearly over I took my last moment of attention to prophesy, “The way you practice will be the way you play!”

I can almost feel you channeling the spirit of AI, not Artificial Intelligence (AI), Allen Iverson (AI).  “Are we talking about, practice.  Practice!”  I thought this was about availability.  Well, my love for basketball met my passion for availability when I considered my daughter and her teammates. How?

Three Ways Basketball Strategies Are Like Availability Strategies:

  • In basketball, every team needs a plan, ditto for enterprise availability.
  • In basketball, every team needs to practice that plan, ditto for availability, disaster recovery, and especially planned maintenance.
  • In basketball, the plan when tested under fire will hold up only as good as those plans were practiced

Enterprise Availability Needs a Plan 

Your availability, specifically your disaster, planned maintenance, and outage recovery strategies, are only as good as those you create. Simply put, what is your plan for an outage (note clouds fail, servers crash, networks get saturated, and human error— enough said).  Do you have a documented plan?  Do you have identified owners and backups owners?  Do you know your architecture and topology (what server does what, where is it located, what team does it belong to, what function does it serve, what business priorities are tied to it, and what SLO/SLA does it require)?  Who are your key vendors, and what are their call down lists?  What are your checkpoints, data protection plans, and backup strategies?  And what are your test plans and validation plans for verification of this plan?

Enterprise Availability Needs Practice 

A good plan, check. Now what about practice.  Implementing disaster recovery steps and unplanned outage strategies are a necessary component of every, every enterprise configuration. But, a strategy that is not rehearsed is not really a strategy. In that case it is simply a possible and proposed approach.  It is more like a suggestion, rather than an actual plan of record. The second step is practice. Walk through the strategies of your plan. Rehearse maintenance timings. Restore backups and data. Validate assumptions and failure modes.

Enterprise Availability Requires Testing 

A plan and a walkthrough, check. Now that you have two of the three let me go back to my daughter’s team.  My parting words, as an “unofficial coach “ were as follows: “The way you practice will be the way you play!”  Fast forward three days. The game is down to the final minutes. The team they are playing is athletically mismatched, and outsized just as they were last year when that year’s game was over by halftime.  But this year, the undermanned and undersized team had clearly come in more prepared. What should have been an easy win now enters the final minute nearly tied. The home team, the opponent, begins a press— something my daughter’s team had prepared for, albeit haphazardly and lethargically, during that fateful practice.  What ensued wasn’t pretty. Four unforced turnovers, two critical fouls during three-pointer attempts, a four to nothing run, and a bevy of frustrations culminating in a devastating one-point loss as time expired.

My final point, how well are you practicing for your real outage, disaster, or planned maintenance?  Do you practice with real data, real clients, and with a real sense of urgency?  How often does your upper management check-in?  Trust me, the presence of a boss in pressure-packed moments makes people do strange and unwise things!  Does your sandbox and test system look like production?  In a past life, I once worked with a customer who had different hardware, storage and Linux OS versions between prod and QA. When they went into prod with application updates, disaster struck hard.  Do you have users and data, and jobs that run during your testing? What about actual disaster simulation?  It’s a hard pill to swallow, testing a hard crash with potentially destructive consequences, recovery from offsite, and even harder to simulate simultaneous multi-point, multiple systems failures, but the unpracticed is often the weak point that turns a 2 hour planned maintenance into an eight-hour multi-team corporate disaster.  The under-practiced or poorly practiced is the difference between a stunning victory for your strategy and team, or a crushing defeat and costly failure for team, vendors, enterprise, and customers.

In basketball, the plan under fire will hold up only as good as the plan was practiced.  When implementing a recovery and disaster plan a good plan and validation are key, but great practice is king.

Contact a rep at SIOS to learn how our availability experts and products can help you with the plan, procedures, and practice.

Visit back for a post on tests you should never avoid simulating.

— Cassius Rhue, VP, Customer Experience

Article reproduced from SIOS

Filed Under: Clustering Simplified Tagged With: Application availability, disaster recovery, Enterprise Availability

Managing Alert-Stress for AWS EC2 with SIOS AppKeeper

April 7, 2020 by Jason Aw Leave a Comment

Managing Alert-Stress for AWS EC2 with SIOS AppKeeper

Managing Alert-Stress for AWS EC2 with SIOS AppKeeperHas this ever happened to you? You receive an alert about an application issue when you are out of the office, and you don’t have the information you need to address it? And you either need to access your cloud management console from an inconvenient location or pass the information on to another colleague to address? Or you are investigating an alert when another one comes in requiring your attention? Research has shown it can take the average person 23 minutes to recover from unexpected interruptions.

With companies moving to the cloud and having to manage more complex computing environments, this “alert stress” is starting to take a toll on workers’ productivity and mental health. Cloud monitoring solutions are trying to give you more information so you can resolve issues faster, but the depth of information they provide and the volume of alerts can be overwhelming.

Is Application Performance Management for AWS Enough?

Migrating to an AWS cloud infrastructure means that you often have to adopt new ways of managing and monitoring your applications. You can take advantage of AWS’s native cloud management functionality for your EC2 environment. But many companies quickly outgrow the functionality of these tools and deploy commercial Application Performance Management (APM) solutions for wider coverage and deeper insights.

But here’s the thing. These sophisticated APM solutions can be creating more work for you.  Yes, they often come with alert notification workflows to put the right information into the right person’s hands quickly.  But they do very little to fix the situation without manual intervention. The result: lots of stress-inducing alerts needing your immediate attention.

That’s why we created SIOS AppKeeper. It is the industry’s first out-of-the-box solution to automatically respond to service outages on Amazon EC2 instances. AppKeeper allows companies to protect applications from service interruptions and downtime while eliminating the need for costly and time-consuming manual intervention.

AppKeeper Automatically Restarts Failed Services in AWS EC2

SIOS AppKeeper not only identifies and sends notifications for failures. But it will also automatically attempt to restart failed services or reboot the instance if necessary. Our users have found that AppKeeper automatically addresses almost 85% of the application service failures that occur.  Without having to disrupt you, your I.T. or Development team or third-parties.

SIOS customers and partners in Japan have been using SIOS AppKeeper since 2017 to protect their AWS environments. ForgeVision is an AWS Advanced Consulting partner, integrates AppKeeper into its cloud management console. It has been allowing it to monitor and recover customers’ failures more cost-effectively. And AppKeeper is allowing Hobby Japan, a publishing company in Tokyo, to create a maintenance-free, low-cost environment.

We invite you to learn more about SIOS AppKeeper by watching this short video or by signing up to use AppKeeper for free until June 30th.

Then you can see for yourself what it’s like to have systems failures in AWS EC2 automatically addressed.

– Daisuke Yoshioka, Manager, Business Development for SIOS AppKeeper.

 

Reproduced from SIOS

Filed Under: Blog posts Tagged With: Amazon AWS, AppKeeper, Application availability, application monitoring

  • « Previous Page
  • 1
  • …
  • 5
  • 6
  • 7

Recent Posts

  • Fail Open vs. Fail Closed: Why It’s a False Dilemma (and How True HA Fixes It)
  • The 5-Step Checklist for Validating Your Failover Setup
  • Managing an Inherited DataKeeper Cluster: Challenges and Best Practices
  • Setting Up Nginx Load Balancer on AWS
  • With Great Power: Cluster Maintenance Best Practices

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 © 2026 · Enterprise Pro Theme on Genesis Framework · WordPress · Log in