W-23431158-hadr-restructure-kt#453
Open
kevintroller wants to merge 6 commits into
Open
Conversation
… the hub Create a Hybrid Standalone High Availability and Disaster Recovery page covering clustering-based HA, shared-responsibility DR, and clustered-topology considerations, and add it to the nav. Add a hub pointer to the CloudHub 2.0 HA/DR page for a consistent cross-deployment experience. Co-authored-by: Cursor <cursoragent@cursor.com>
… the shared skeleton Co-authored-by: Cursor <cursoragent@cursor.com>
…or AI retrieval Co-authored-by: Cursor <cursoragent@cursor.com>
….0 and Hybrid Standalone HA/DR pages Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…stances Move the hybrid-standalone-hadr page from a top-level nav item to a child of Managing Hybrid Standalone Instances (after Managing Clusters) and add a matching entry to the managing-hybrid-standalone index page. Co-authored-by: Cursor <cursoragent@cursor.com>
kevintroller
changed the title
| === Considerations for Disaster Recovery Implementations | ||
|
|
||
| Implementing a Disaster Recovery (DR) strategy for applications deployed to CloudHub 2.0 requires careful consideration of several key factors. | ||
| A DR strategy for applications deployed to CloudHub 2.0 requires you to weigh several factors. |
Contributor
There was a problem hiding this comment.
Suggested change
| A DR strategy for applications deployed to CloudHub 2.0 requires you to weigh several factors. | |
| A DR strategy for applications deployed to CloudHub 2.0 requires you to consider several factors. |
| === Considerations for Disaster Recovery Implementations | ||
|
|
||
| Implementing a Disaster Recovery (DR) strategy for applications deployed to CloudHub 2.0 requires careful consideration of several key factors. | ||
| A DR strategy for applications deployed to CloudHub 2.0 requires you to weigh several factors. |
Contributor
There was a problem hiding this comment.
Per our standards, we should avoid using "weigh" here, because it can be interpreted differently. Use the simpler term, which is "consider".
| The Anypoint Control Plane encompasses additional Anypoint services apart from CloudHub 2.0. For more details, refer to the https://compliance.salesforce.com/en/documents/a005A00000vvLBjQAM[DR Test Summary]. | ||
| * Keep your integrations stateless. | ||
| * Don't share transactional information between client invocations or scheduled executions. | ||
| * When the middleware must retain data because of a system limitation, persist it in an external store, such as a database or a messaging queue, rather than in the middleware infrastructure or memory. |
Contributor
There was a problem hiding this comment.
Suggested change
| * When the middleware must retain data because of a system limitation, persist it in an external store, such as a database or a messaging queue, rather than in the middleware infrastructure or memory. | |
| * If the middleware must retain data because of a system limitation, persist it in an external store, such as a database or a messaging queue, rather than in the middleware infrastructure or memory. |
bjoson-mulesoft
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of the HA/DR documentation restructure (GUS W-23431158). This repo hosts two deployment models, so both changes ship in one PR.
hybrid-standalone/.../hybrid-standalone-hadr.adoccovering clustering-based HA (shared memory, automatic failover), shared-responsibility DR, and clustered-topology considerations (concurrent-restart caution, cluster rejoin, Object Store persistence/lock caveats). Added to the Hybrid Standalone nav.cloudhub-2/.../ch2-ha-dr.adoc): added a top-of-page pointer to the Mule Runtime HA/DR hub for a consistent cross-deployment experience. Existing content unchanged.Related PRs (same effort, one branch name per repo)
Notes
Test plan
Made with Cursor