docs(kb): per-VM DR recovery requires a tenant-to-tenant sync#486
Open
CarlRodabaugh wants to merge 1 commit into
Open
docs(kb): per-VM DR recovery requires a tenant-to-tenant sync#486CarlRodabaugh wants to merge 1 commit into
CarlRodabaugh wants to merge 1 commit into
Conversation
A provider-to-provider sync replicates the whole production system into the DR provider, so there's no clean handle to restore an individual VM. For per-VM DR testing/recovery, use a tenant-to-tenant sync (prod tenant -> DR tenant) and recover the VM's snapshot inside the DR tenant. Don't run both syncs at once. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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
New KB article correcting a common DR-topology assumption: a provider-to-provider sync replicates the entire production system into the DR provider, so there's no clean handle to restore an individual VM. For per-VM DR testing/recovery, use a tenant-to-tenant sync (prod tenant → DR tenant), then recover the target VM's snapshot from inside the DR tenant in isolation. Also warns against running both syncs at once (double overhead, no benefit).
Type
Conceptual / Troubleshooting (DR topology)
Source
Recurring support pattern — two customer cases. Promoted from internal support KB.
Note for reviewers
The live docs brand the umbrella feature Site Sync; this article uses the three sync directions (provider-to-provider, provider-to-tenant, tenant-to-tenant). There's no dedicated tenant-to-tenant how-to page yet — this links
Configuring a Site Syncas the closest published guide. Happy to adjust terminology to match whatever the team prefers.Checks
validate_frontmatter.pypasses locallysync-configuration,vm-snapshots-restores)🤖 Generated with Claude Code