[DOCS-8405] Add warning about directoryPerDB not supported in restorations to OpsMgr doc, to match CloudMgr doc. Created: 21/Jul/16  Updated: 27/Jul/16  Resolved: 27/Jul/16

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

Type: Improvement Priority: Major - P3
Reporter: Akira Kurogane Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 7 years, 29 weeks, 6 days ago
Story Points: 0.25

 Description   

A user ran into the problem where you cannot do a backup restoration if your live replica set is using the directoryPerDB option.

On the /core/restore-overview/ page for Cloud Manager docs this warning was added:

IMPORTANT

Under certain conditions, an automated restore fails because either:

  1. The backup and destination databases’ storage engines do not match.
  2. The destination database uses settings that are not currently preserved in the backup itself.

If the backup and destination database storage engines do not match, mongod cannot start once the backup is restored. At this time, you can either:

  1. Not restore this snapshot.
  2. Change the storage engine of the destination sharded cluster or replica set to match the configuration of the snapshot.

If the destination database uses any of the following settings, an automated restore fails:

  • storage.directoryPerDB
  • security.enableEncryption (WiredTiger only)
  • storage.wiredTiger.engineConfig.directoryForIndexes (WiredTiger only)

The user complained that it should be in the equivalent Ops Manager docs page (/v2.0/core/restore-overview/) too. So far as I see the advice is valid for Ops Manager too. Could it be added there too?


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