[DOCS-7572] Document automation configuration processes.backupRestoreUrl in Ops/Cloud Manager Public API Created: 04/Apr/16  Updated: 07/Jun/16  Resolved: 25/Apr/16

Status: Closed
Project: Documentation
Component/s: Cloud Manager, Ops Manager
Affects Version/s: None
Fix Version/s: v20160510

Type: Improvement Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-5465 Restore from backup doesn't integrate... Closed
is related to DOCS-6394 API: automationConfig: create automat... Closed
Participants:
Days since reply: 7 years, 44 weeks, 6 days ago
Epic Link: C/OM Update API

 Description   

Please document the processes.backupRestoreUrl field in Ops/Cloud Manager -> Public API Resources -> Automation Configuration.

The purpose of the field is to kick off a restore (from backup). The URL should be set to the delivery.url from the Restore Jobs public API.

For an example, see https://jira.mongodb.org/browse/CS-29491?focusedCommentId=1221535&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1221535



 Comments   
Comment by Bob Grabar [ 07/Apr/16 ]

Thanks!

Comment by Timothy Olsen (Inactive) [ 07/Apr/16 ]

They're each two halves to a restore.

The restoreJob endpoint will create tarballs of the restore.

The automationConfig endpoint will take those tarballs and restore them to a cluster or replica set.

Comment by Bob Grabar [ 07/Apr/16 ]

tim.olsen,

Am I understanding this correctly? Do both of these trigger a restore job:

- automationConfig endpoint. Post the automation config with the backupRestoreUrl field.

- restoreJob endpoint. Post either the snapshotId, checkpointId, or timestamp.

Generated at Thu Feb 08 07:54:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.