[SERVER-4456] Journal archiving for physical/disaster recovery Created: 08/Dec/11 Updated: 06/Dec/22 Resolved: 16/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dave Sisk | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All. |
||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Journals are written if journaling is enabled, and these do prove effective for crash recovery. However, there is no way to perform disaster recovery using journals. Provide a means to 1) archive journals to separate files that can be copied/rsynced/etc to other locations, and 2) replay them. With this capability, a physical backup could be restored from tape, then journals copied off to another location could be replayed to bring the database back up to date. |