[DOCS-6813] Title misleading: split concepts here (Backup data locality vs multiple backup databases) Created: 14/Dec/15  Updated: 11/Jan/17  Resolved: 27/Jul/16

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

Type: Bug Priority: Major - P3
Reporter: Andrew Davidson Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/tutorial/configure-backup-data-locality/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/tutorial/add-existing-mongodb-processes/
Screen Resolution: 1920 x 1080
repo: REPONAME
source: tutorial/configure-backup-data-locality


Participants:
Days since reply: 7 years, 29 weeks ago
Epic Link: OM Backup Daemon

 Description   

This page incorrectly combines two concepts
1) Configuring >1 backup database
2) Using multiple backup databases to ascertain data locality in terms of where snapshots are stored

These are independent concepts (but 2 requires 1) yet the title and TOC are misleading



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

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