[DOCS-8640] A cluster can be backed up by multiple OM deployments Created: 22/Aug/16  Updated: 07/Jun/17  Resolved: 07/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Bob Grabar Assignee: Anthony Sansone (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Participants:
Days since reply: 6 years, 36 weeks ago
Epic Link: C/OM Backup
Story Points: 1

 Comments   
Comment by Jordan Sumerlus [ 07/Jun/17 ]

Agree with Steve, I don't think we should document this since it can have issues. We should fix the issues rather than release a buggy solution.

Comment by Tomer Yakir [ 25/Jan/17 ]

steve.briskin

In the current state, would the following be possible?
Backup Agent #1 stops the balancer and while it takes the clustershot Backup agent #2 starts the balancer.

If so, wouldn't we end up with an inconsistent snapshot?

Comment by Tomer Yakir [ 24/Jan/17 ]

Hi steve.briskin

Sadly, we have a customer who's running with this configuration (Sharded cluster backed up by OM/CM simultaneously).

What's the worst thing that could happen to them right now?
(and out of curiosity) what was the worst thing that could've happen prior to the CLOUDP ticket.

Comment by Tomer Yakir [ 24/Jan/17 ]

steve.briskin

AFAIK, it was OK to backup a replica set from 2 OM groups prior to CLOUDP-15741.
So effectively, from a customer perspective, there's no change?

Comment by Tomer Yakir [ 23/Jan/17 ]

I think this has to be at least included in the release notes

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