[SERVER-84119] Investigate risks of cross-version restores Created: 12/Dec/23 Updated: 16/Jan/24 Resolved: 16/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Participants: | |||||
| Description |
|
A discussion around cross-version restores arose in the 6 week for PM-2209. Cloud currently offers users the ability to restore a backup on a cluster that is exactly one binary version greater (e.g. 7.0 -> 8.0). This circumvents the regular upgrade procedure. This process poses some risks. Starting a node on backed up data files is considered restoring from an unclean shutdown, and doing this on a different binary version may break some assumptions the server holds. This ticket should investigate the risks associated with performing a cross-version restore, and outline them in a document. |