[DOCS-4485] Document Some of the Internals for the restore process in OnPrem Created: 08/Dec/14  Updated: 24/Feb/16  Due: 20/Mar/15  Resolved: 20/Mar/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: mms-1.5, mms-1.6

Type: Improvement Priority: Major - P3
Reporter: Peter Garafano (Inactive) Assignee: Allison Reinheimer Moore
Resolution: Done Votes: 0
Labels: ides
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to DOCS-4834 Document backup flows for MMS Backup ... Closed
is related to DOCS-3790 Add diagrams to on-prem MMS backup se... Closed
Participants:
Days since reply: 9 years, 9 weeks ago

 Description   

Describe (or diagram) the moving parts for each type of restore

  • Point-in-time
    • HTTP
    • Multiple File SCP
    • Single File SCP
  • Snapshot
    • HTTP
    • Multiple File SCP
    • Single File SCP

When doing an SCP restore, what machine does the SCP?



 Comments   
Comment by Peter Garafano (Inactive) [ 17/Dec/14 ]

Currently, each restore type works as follows:

Restore Type MMS Backup Daemon MMS Backup Blockstore MMS Application
Point-in-Time HTTP Restore (Pull) ✔ (Generates Restore from OpLog and Snapshot) ✔ (In Memory Only)
Point-in-Time Multiple File SCP (Push) ✔ (Generates Restore from OpLog and Snapshot and performs SCP) x
Point-in-Time Single File SCP (Push) ✔ (Generates Restore from OpLog and Snapshot and performs SCP) x
Snapshot HTTP Restore (Pull) x ✔ (In Memory Only)
Snapshot Multiple File SCP (Push) ✔ (In Memory Only push over SCP) x
Snapshot Single File SCP (Push) ✔ (Writes snapshot to disk to obtain single tar.gz file and performs SCP) x
Generated at Thu Feb 08 07:48:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.