SIOS SANless clusters

SIOS SANless clusters High-availability Machine Learning monitoring

August 10, 2024

How to Perform Performance Testing Replication with SIOS DataKeeper

How to Perform Performance Testing Replication with SIOS DataKeeper

How to Perform Performance Testing Replication with SIOS DataKeeper

Configuring replication for a production database can be a pretty daunting task especially if you have not done your research in advance. This blog will cover many parts of the trickiest aspect of setting up your environment properly… performance. Understanding these key points will put you ahead of the pack and ensure your production Go-Live does not have any last minute hiccups.

The first and most basic point to consider is choosing the correct mirror type for your configuration. SIOS DataKeeper comes with two options for mirror type during the creation process, Synchronous and Asynchronous. Either of these options have their own benefits and drawbacks depending on your environment.

Selecting Mirror Type

Synchronous mirrors excel best in LAN environments with high speed connections and provide 1:1 write consistency at time of commit to the primary system. However if the network, or target storage is unable to keep up with the throughput of the primary system you will see reduction in write speed to maintain synchronous write consistency. Therefore synchronous mirroring would not be recommended for WAN or high latency environments.

Asynchronous mirrors however are perfect for a WAN environment. Asynchronous mirrors provide all the same functionality of ensuring 1:1 write consistency between the nodes, but the difference is that writes are committed to the primary system before the write is committed to the target system. This is possible due to the utilization of a bitmap also known as an intent log, a bitmap tracks all of the changes that occur on the system at a block level and writes data to the target as quickly as it can through a backlog known as a write queue. The write queue can be limited by number of writes or total MB in data and when the limit is hit the mirror will pause and the data will sync, preventing a failover while the data is not in sync.

Hardware Configuration:

Now that you have decided which mirror type fits your environment best it is important to understand that DataKeeper is not magic, DataKeeper can only write and replicate as fast as your systems allow so having hardware capable of achieving the throughput needed by your applications is crucial. Here is some advice and tips for ensuring you have the hardware needed to achieve your replication goals.

  1. Ensure that your Primary and Target systems have identical storage hardware. For example target IOPS should be equal to the source IOPS. Otherwise the slowest component in the environment will prove to be the bottleneck of the write speed. Matching hardware will always provide better performance.
  2. Understanding the importance of the bitmap, the easiest and cheapest way to provide a significant boost in performance is to store the bitmap on its own dedicated high speed storage. The bitmap is very small so provisioning a 5 or 10GB SSD will be sufficient and provide great return on performance
    enhancement.
  3. Test the standalone hardware with an understanding that replicating data will introduce some overhead. For example if you have a requirement to attain 10,000 IOPS in your environment, ensure that your hardware can at a bare minimum attain consistent 10,000 IOPS standalone on all nodes that will be part of the cluster. If you are intending to perform synchronous mirroring ensure that you have beyond the bare minimum requirements as further overhead is introduced to maintain synchronous consistency. Network will also need to be load tested to ensure you can transfer the data required for your replication scheme.
  4. Know how to test properly. When utilizing a test environment to verify production capabilities it is important to mimic the setup as closely as possible. It is understood that you cannot set up an entire production database clone just to test replication but utilizing the correct data generation tool can provide better indication of current performance capabilities. Diskspd is a free tool that can be used for some basic testing, but in the world of SQL, HammerDB provides a much better indicator of real world performance.

DiskSpd: https://github.com/microsoft/diskspd
HammerDB: https://www.hammerdb.com/

  1. Lastly we have DataKeeper tuning, there are configurable settings beyond the mirror type within DataKeeper. Modifying these is generally a bit more nuanced and best done under the advice of the SIOS support team. However if you have confirmed that all of the other recommendations are squarely in place then tuning some DataKeeper parameters may provide that last boost in performance needed to meet your required metrics. Some examples of tuning would be increasing the number of outstanding writes that can be in your write queue or modifying how often the bitmap file is flushed to disk.

Reproduced with permission from SIOS
August 5, 2024

Creating a SQL Server 2019 Cluster on GCP with SIOS DataKeeper

Creating a SQL Server 2019 Cluster on GCP with SIOS DataKeeper

Creating a SQL Server 2019 Cluster on GCP with SIOS DataKeeper

Create a SQL Server 2019 Cluster on Google Cloud Platform (GCP) with our step-by-step guide. Using SIOS DataKeeper Cluster Edition for SANLess clustering, our guide simplifies the process with pre-scripted steps and builds on Google’s documentation for ease and consistency.

Reproduced with permission from SIOS
July 31, 2024

Navigating the Transition from Nutanix Xi Leap: Why SIOS is Your Ideal Disaster Recovery Partner

Navigating the Transition from Nutanix Xi Leap Why SIOS is Your Ideal Disaster Recovery Partner

Navigating the Transition from Nutanix Xi Leap: Why SIOS is Your Ideal Disaster Recovery Partner

Preparing for the End of Nutanix Xi Leap

As Nutanix plans to discontinue support for Xi Leap on April 16, 2025, organizations are faced with the challenge of finding a new disaster recovery (DR) solution. Rather than viewing this as a setback, it’s an excellent opportunity to implement a more advanced and tailored DR solution with SIOS. By starting your transition early, you can ensure a seamless migration and maintain your business continuity without interruption.

Why Early Planning for a DR Solution is Crucial

Given that a typical migration to a new DR solution can take months, beginning the transition process well ahead of time is essential. Delaying this could result in significant obstacles, putting your data and business operations at risk.

Key Features to Consider in Your New DR Solution

Customized HA/DR Solutions for Your Unique Needs

It’s important to choose a DR provider that offers flexibility and scalability tailored to your organization’s specific requirements. SIOS excels in delivering High Availability (HA) and DR software solutions for both Windows and Linux environments, providing a perfect fit for diverse business needs.

Rapid Disaster Recovery and Reliable Response

Minimizing downtime is a top priority during any disruption. SIOS’s real-time block-level replication technology ensures superior Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO), enabling swift and effective recovery during emergencies.

24/7 Expert Support

Around-the-clock support is vital to ensure continuous protection and prompt assistance. SIOS offers dedicated 24x7x365 support, staffed by knowledgeable technical experts, to give you peace of mind and reliable help whenever necessary.

Real-Time Data Replication and Cluster Integration

SIOS specializes in real-time data replication and seamless cluster integration, offering the best RTO/RPO in the industry. Our technology also simplifies the failback process after a disaster, ensuring your operations can return to normal quickly and efficiently.

The Advantage of Choosing SIOS for Your Disaster Recovery Needs

Selecting a disaster recovery partner with a proven track record and in-depth expertise is crucial. SIOS not only meets these criteria but also ensures a smooth transition from Nutanix Xi Leap, keeping your data secure and minimizing any disruption to your business operations.

Flexibility in Hosting Your DR Solution

One of the key benefits of SIOS’s solutions is the flexibility they offer. You can choose to host your disaster recovery on-premises or in the cloud, depending on what best suits your organization’s strategy. This adaptability, coupled with control over your own data, provides a higher level of security compared to traditional DRaaS solutions.

Start Your Disaster Recovery Transition with SIOS Today

As Nutanix phases out Xi Leap, seize this opportunity to upgrade to a more tailored, secure, and responsive disaster recovery solution with SIOS. Our dedication to your business continuity and operational efficiency makes us the perfect partner for your disaster recovery needs.

If you have any questions or require assistance in selecting your new disaster recovery solution, please reach out to us. Discover how SIOS can help safeguard your business-critical workloads and ensure a smooth transition from Nutanix Xi Leap.

Reproduced with permission from SIOS
July 27, 2024

White Paper: The Buyer’s Guide to Choosing the Right Cloud Storage for High Availability

The Buyer’s Guide to Choosing the Right Cloud Storage for High Availability

White Paper: The Buyer’s Guide to Choosing the Right Cloud Storage for High Availability

High availability is non-negotiable for business essential applications, but with so many cloud storage solutions on the market, how do you choose? This white paper discusses the 10 key questions you should ask before you buy to ensure high availability, seamless disaster recovery, and cost-effective scalability that’s right for you.

Reproduced with permission from SIOS
July 21, 2024

CloudStrike Downtime Debrief: Practical Ways To Use HA For Patching

CloudStrike Downtime Debrief Practical Ways To Use HA For Patching

CloudStrike Downtime Debrief: Practical Ways To Use HA For Patching

As a company dedicated to protecting critical applications from downtime, we want to share some context and practical advice about IT patching policies and the role of high availability.

Patching policies have evolved significantly over the years. From a cautious approach that prioritized extensive testing to the current urgency-driven model addressing zero-day exploits, the landscape of software patch management has transformed in response to escalating cyber threats. This blog delves into this evolution, the driving forces behind these changes, and how SIOS Technology’s LifeKeeper and DataKeeper high availability (HA) solutions play a crucial role in enabling customers to balance the need for security with operational stability.

The Traditional Approach

Historically, organizations adopted a conservative stance toward patching – particularly in highly critical environments – that was driven by several factors:

  1. Stability Concerns: Patching could potentially introduce new bugs or compatibility issues, leading to system instability.
  2. Complex Environments: Enterprise IT environments are complex, with numerous interdependencies. A patch might fix one issue but break another, necessitating thorough testing.
  3. Operational Downtime: Applying patches often requires system downtime, which could disrupt business operations and lead to financial losses.

In this traditional model, patches were rigorously tested in staging environments that mirrored production systems. Only after exhaustive testing and validation would patches be deployed to production. This approach minimized risks but also meant that systems remained vulnerable to known threats for extended periods.

The Shift: Zero Day Exploits Driving Immediate Patching

The emergence of zero-day exploits has fundamentally changed patching policies. Attackers exploit security flaws before the vendor is aware of them and can issue a patch. Time is of the essence. No one wants to be hacked via a vulnerability addressed in a patch that IT has been slow to apply. The increasing frequency and sophistication of these exploits have forced organizations to prioritize speed over caution.

The New Imperative: Patch Immediately

Several high-profile incidents, such as the WannaCry ransomware attack in 2017, highlighted the devastating potential of zero-day vulnerabilities. These incidents underscored the need for immediate patching to protect against exploits that could cause significant damage.
However, this urgency comes with its own set of challenges:

  1. Increased Risk of Downtime: Rapid deployment of patches without thorough testing can lead to system crashes and service interruptions.
  2. Operational Strain: IT teams must work quickly to assess, test, and deploy patches, often under immense pressure.
  3. Resource Allocation: Prioritizing patching over other IT tasks can strain resources and divert attention from other critical projects.

SIOS High Availability for Rolling Maintenance

SIOS high availability (HA) solutions are a crucial component in modern patch management strategies. SIOS clustering software is designed to ensure continuous operation, even during maintenance activities such as patching. Here’s how SIOS LifeKeeper and DataKeeper software solutions enable organizations to balance the need for security with operational stability:

Seamless Patching and Testing

  1. Redundancy and Failover: SIOS clusters use redundancy and failover mechanisms to maintain service availability. In a SIOS environment, critical applications are run on a primary server node and “clustered” with a secondary node so that if the primary fails, the secondary is ready to automatically take over operation. This setup allows patches to be applied in a “rolling maintenance” strategy. That is, IT applies patches to the secondary node while the primary continues to handle the workload, thereby minimizing downtime. After the maintenance is complete on the secondary node, operation can be moved to the secondary node and the original primary node can be updated.
  2. Staged Rollouts: SIOS HA architectures facilitate staged rollouts of patches. Organizations can deploy patches to a subset of servers or nodes and monitor their impact before applying them to the entire system. This staged approach helps identify and mitigate potential issues without affecting the entire infrastructure.

Benefits of SIOS HA for Patching

  • Minimized Downtime: By ensuring that at least part of the system remains operational during patching, SIOS LifeKeeper and DataKeeper solutions reduce the risk of service disruptions.
  • Improved Testing: Staging environments within SIOS HA configurations allow for real-time testing and validation of patches without impacting the production environment.
  • Enhanced Security: Faster deployment of critical patches reduces the window of vulnerability to exploits, enhancing overall security posture.

Conclusion

The evolution of patching policies from a cautious, test-first only approach to the urgency-driven, immediate deployment model reflects the growing threat landscape and the need for rapid response to zero-day exploits. While this shift has introduced challenges, SIOS provides a robust framework for balancing security and stability. By leveraging SIOS’ HA solutions, organizations can ensure continuous operation, even during critical patching activities, thereby safeguarding their systems and data against emerging threats without compromising on performance and uptime.

Reproduced with permission from SIOS
  • Results 6-10 of 923
  • < Page 2 of 185 >

  • Join Our Mailing List