-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation
Description
Summary
Documentation is needed for the new N+2 (RF3) vSAN redundancy feature introduced in 26.1.2, including configuration steps, requirements, and whether it can be enabled on existing systems post-install.
Type
How-to Guide
Suggested Content
- Audience: VergeOS administrators and support engineers
- Prerequisites: Understanding of vSAN tiers and existing N+1 redundancy
- Key sections:
- What is RF3 / N+2 redundancy and how it differs from standard N+1
- Minimum node count and hardware requirements for RF3
- How to enable RF3 during a fresh install
- Whether RF3 can be enabled on existing vSAN tiers post-install (and if so, the procedure)
- Storage capacity overhead / impact of RF3 vs N+1
- Monitoring RF3 status and health
- Limitations or known considerations
Context
Requested via support interaction. This has come up 2-3 times already from customers asking whether RF3 settings are configurable after initial deployment. Currently the only documentation is a brief mention in the 26.1 release notes — there is no dedicated guide or KB article covering setup, requirements, or post-install configurability.
Release notes reference: https://docs.verge.io/release-notes/26-1-release-notes/
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation