This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Disasters are unpredictable, but your response to them shouldn’t be. A well-thought-out disasterrecovery (DR) plan is your best defense against unexpected disruptions. Being able to choose between different compute architectures, such as Intel and AMD, is essential for maintaining flexibility in your DR strategy.
One common question that comes up in all disasterrecovery planning is, “What type of storage should be used for disasterrecovery?” Here I am going to outline the primary factors I’d consider when choosing storage for disasterrecovery. How many recovery points do you need?
To navigate these challenges, organizations must adopt a comprehensive disasterrecovery (DR) strategy. Networking ensures the rapid recovery of critical systems and data, directly influencing key metrics like Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs).
Weve watched in awe as the use of real-world generative AI has changed the tech landscape, and while we at the Architecture Blog happily participated, we also made every effort to stay true to our channels original scope, and your readership this last year has proven that decision was the right one. Well, its been another historic year!
Pure Storage and Rubrik are expanding their partnership to offer a holistic and secure reference architecture that tackles the challenges of managing and securing unstructured data at scale. The Pure Storage platform also offers built-in disasterrecovery to protect unstructured data after an incident.
Related on MHA Consulting: The Cloud Is Not a Magic Kingdom: Misconceptions About Cloud-Based IT/DR The Cloud Is Not a Plan A common misconception today is that the shift from company-owned data centers toward cloud-based environments means companies can quit worrying about IT disasterrecovery (IT/DR). (IT/DR
Solutions Review’s listing of the best backup and disasterrecovery companies is an annual sneak peek of the solution providers included in our Buyer’s Guide and Solutions Directory. These changes speak to the cloud’s continued rise, significantly impacting the backup and disasterrecovery market over recent years.
In part I of this series, we introduced a disasterrecovery (DR) concept that uses managed services through a single AWS Region strategy. Architecture overview. The application diagram presented in Figures 2.1 In our architecture, we use CloudWatch alarms to automate notifications of changes in health status.
Solutions Review’s listing of the best DisasterRecovery as a Service companies is an annual sneak peek of the solution providers included in our Buyer’s Guide and Solutions Directory. Technically speaking, DisasterRecovery as a Service (DRaaS) tools are often labeled as stand-alone offerings.
The cost of not having an IT disasterrecovery team can range from being unable to recover from a disruption, to overspending. Related on MHA Consulting: Who Does What: The Most Critical Job Roles in IT DisasterRecovery The Price of Neglecting IT/DR Being a business continuity consultant can be frustrating.
Solutions Review’s listing of the best cloud disasterrecovery solutions is an annual sneak peek of the solution providers included in our Buyer’s Guide for DisasterRecovery as a Service. To make your search a little easier, we’ve profiled the best cloud disasterrecovery solutions all in one place.
This post is the third in a series of three that explores some insights from the IDC white paper, sponsored by Zerto— The State of DisasterRecovery and Cyber Recovery, 2024–2025: Factoring in AI ¹. With a wide array of options available, it can be overwhelming to determine which solution best meets your needs.
Building a multi-Region application requires lots of preparation and work. Many AWS services have features to help you build and manage a multi-Region architecture, but identifying those capabilities across 200+ services can be overwhelming. Finally, in Part 3, we’ll look at the application and management layers.
In this blog post, we share a reference architecture that uses a multi-Region active/passive strategy to implement a hot standby strategy for disasterrecovery (DR). DR implementation architecture on multi-Region active/passive workloads. Fail over with event-driven serverless architecture. Figure 1.
Firms designing for resilience on cloud often need to evaluate multiple factors before they can decide the most optimal architecture for their workloads. Example Corp has multiple applications with varying criticality, and each of their applications have different needs in terms of resiliency, complexity, and cost. Trade-offs.
Solutions Review’s listing of the best disasterrecovery tools for healthcare is an annual mashup of products that best represent current market conditions, according to the crowd. To make your search a little easier, we’ve profiled the best disasterrecovery tools for healthcare providers all in one place.
In this submission, Veeam ‘s Dave Russell covers the disasterrecovery preparedness gap for containerized applications. DisasterRecovery (DR) is protecting containerized applications or infrastructure in a specific geography to reduce business impact when faced with unforeseen failures.
Solutions Review’s listing of the best data replication tools for disasterrecovery is an annual mashup of products that best represent current market conditions, according to the crowd. To make your search a little easier, we’ve profiled the best data replication tools for disasterrecovery all in one place.
In my first blog post of this series , I introduced you to four strategies for disasterrecovery (DR). The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. I use Amazon DynamoDB for the example architecture in Figure 2.
Since the primary objective of a backup site is disasterrecovery (DR) management, this site is often referred to as a DR site. DisasterRecovery on AWS. DR strategy defines the recovery objectives for downtime and data loss. The workload has a recovery time objective (RTO) and a recovery point objective (RPO).
In this submission, Scality Co-Founder and CTO Giorgio Regni offers a commentary on backup and disasterrecovery strategy in the new era of remote work. The shift to work-from-home and hybrid work models has put renewed focus on the importance of backup and disasterrecovery plans. Storage in the Hybrid Cloud.
In Part 1 of this blog series, we looked at how to use AWS compute, networking, and security services to create a foundation for a multi-Region application. Data is at the center of many applications. For this reason, data consistency must be considered when building a multi-Region application.
New capabilities include powerful tools to protect data and applications against ransomware and provide enhanced security with new Zerto for Azure architecture. Around the same time, HPE GreenLake for DisasterRecovery , built with Zerto and integrated into the HPE GreenLake Platform, became generally available.
Welcome to the third post of a multi-part series that addresses disasterrecovery (DR) strategies with the use of AWS-managed services to align with customer requirements of performance, cost, and compliance. We’ll use the A/A solution as this provides a better recovery time objective (RTO) for the overall approach.
What does static stability mean with regard to a multi-Region disasterrecovery (DR) plan? In the simplest case, we’ve deployed an application in a primary Region and a backup Region. Amazon Route 53 ApplicationRecovery Controller (Route 53 ARC) was built to handle this scenario.
In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. As a refresher from previous blogs, our example ecommerce company’s “Shoppers” application runs in the cloud. The monolith application is tightly coupled with the database.
This 3-part blog series discusses disasterrecovery (DR) strategies that you can implement to ensure your data is safe and that your workload stays available during a disaster. This example architecture refers to an application that processes payment transactions that has been modernized with AMS.
Database contents change depending on the applications they serve, and they need to be protected alongside other application components. Zerto, a Hewlett Packard Enterprise company, simplifies the protection of a business’s most precious assets by providing disasterrecovery for databases at scale.
Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. Architecture Overview.
In a zero trust model, all users, devices, and applications must be verified and authenticated before they are granted access to resources on the network. Integrating a disasterrecovery solution into zero trust architecture is crucial. Learn more about security and hardening with Zerto here.
That’s why many customers replicate their mission-critical workloads in multiple places using a DisasterRecovery (DR) strategy suited for their needs. Depending on the RPO and RTO of the mission-critical workload, the requirement for disasterrecovery ranges from simple backup and restore, to multi-site, active-active, setup.
A zero trust network architecture (ZTNA) and a virtual private network (VPN) are two different solutions for user authentication and authorization. Now they need to access data using an internal business application. application username and password) to authenticate into the software and access data. What Is VPN?
In Part I of this two-part blog , we outlined best practices to consider when building resilient applications in hybrid on-premises/cloud environments. In Part II, we’ll provide technical considerations related to architecture and patterns for resilience in AWS Cloud. Considerations on architecture and patterns.
Data protection is a broad field, encompassing backup and disasterrecovery, data storage, business continuity, cybersecurity, endpoint management, data privacy, and data loss prevention. Acronis offers backup, disasterrecovery, and secure file sync and share solutions. Note: Companies are listed in alphabetical order.
At the end of November, I blogged about the need for disasterrecovery in the cloud and also attended AWS re:Invent in Las Vegas, Nevada. In short, the sheer scale of the cloud infrastructure itself offers layers of architectural redundancy and resilience. . Let me explain a little more what that is. .
Cyber Recovery vs. DisasterRecovery by Pure Storage Blog Data infrastructures aren’t just built for storage, performance, and scale—they’re designed for resilience. Two key areas of concern include disasterrecovery in general, and, more specifically, cyber recovery.
You can use these fault boundaries to build multi-Region applications that consist of independent, fault-isolated replicas in each Region that limit shared fate scenarios. However, applications typically don’t operate in isolation; consider both the components you will use and their dependencies as part of your failover strategy.
HPE GreenLake for DisasterRecovery Is Generally Available Experience Zerto wherever and however you want! Now customers can also experience Zerto as a simple, flexible SaaS-based disasterrecovery (DR) solution on HPE GreenLake, the edge-to-cloud platform. What Is the HPE GreenLake Edge-to-Cloud Platform?
These backup appliances are also dabbling in delivering disasterrecovery capabilities using VM snapshots. Apart from traditional VM backup, software-based backup solutions are also looking to deliver disasterrecovery capabilities using VM snapshots. Scale-out architecture, scale from a few VM to thousands with ease.
In the challenging landscape of keeping your IT operations online all the time, understanding the contrasting methodologies of high availability (HA) and disasterrecovery (DR) is paramount. Here, we delve into HA and DR, the dynamic duo of application resilience. What Is High Availability?
Stateful vs. Stateless Applications: What’s the Difference? by Pure Storage Blog “Stateful” and “stateless” describe what, if anything, an application records around processes, transactions, and/or interactions. Stateful applications retain data between sessions, stateless applications don’t. Money in, candy out.
Taming the Storage Sprawl: Simplify Your Life with Fan-in Replication for Snapshot Consolidation by Pure Storage Blog As storage admins at heart, we know the struggle: Data keeps growing and applications multiply. This consolidation simplifies management, enhances disasterrecovery (DR), and offers a treasure trove of benefits.
Being able to migrate, manage, protect, and recover data and applications to and in the cloud using purpose-built cloud technologies is the key to successful cloud adoption and digital transformation. This feature can greatly help solutions architects design AWS DR architectures (2).
Growing in both volume and severity, malicious actors are finding increasingly sophisticated methods of targeting the vulnerability of applications. Victims are either forced to pay the ransom or face total loss of business-critical applications. by protecting any application using continuous data protection (CDP).
We organize all of the trending information in your field so you don't have to. Join 25,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content