SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Mongo Jumbo Backups


Mongo Jumbo Backups

Author
Message
Tony Davis
Tony Davis
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: Administrators
Points: 1751 Visits: 1171
Comments posted to this topic are about the item Mongo Jumbo Backups
patrickmcginnis59 10839
patrickmcginnis59 10839
SSCertifiable
SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)

Group: General Forum Members
Points: 6553 Visits: 6133
This question is for Tony, whats the largest mongodb installation that you've administered?

to properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
Jim P.
Jim P.
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2617 Visits: 2215
Another consideration is what is your business and is a point in time recovery (PIT) worth the time after 4 or 24 hours?

If a manager were to delete the days transactions at 4P and realized it at 5P then yes a PIT is probably the best way. But if the manager deleted the records from before 01/01/2014 when it was supposed to be a date of 01/01/2013 and he finds out two days later a PIT back to two days ago loses all work done for the past two days at a cost to the all the employees that use the DB for double-entry, while trying to maintain normal production.

I have always looked at a PIT as essentially a 24 hour or less decision. The daily backups should be used to restore in parallel and then copy the data across.



----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
davewithers-574156
davewithers-574156
SSC Rookie
SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)SSC Rookie (47 reputation)

Group: General Forum Members
Points: 47 Visits: 97
great editorial...thought I was missing something about Mongo's backup capabilities on shards...now I know I'm not Smile

a correction tho, mongo is a document-store (JSON/BSON) database, not a "key-value" store (like hadoop) as mentioned in the writing.
Gary Varga
Gary Varga
SSC-Dedicated
SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)SSC-Dedicated (35K reputation)

Group: General Forum Members
Points: 35134 Visits: 6562
For me this highlights, for what for me is, the fact that NoSQL databases are not replacements for relational databases and have totally different operational profiles. This may mean that backups are superfluous (may, MAY!!!) but, of course, it depends.

As data professionals (DBAs, developers, architects of various types etc.) we need to consider data backup NOT database backup. I make this distinction because we need to consider why a backup is needed e.g. it may be "good enough" to generate it or even lose it - these are not offered as THE choices, just possible ones amongst many.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Dave Poole
Dave Poole
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23996 Visits: 3482
From a developer perspective the NOSQL databases do cool stuff and make the developers task of interacting with data much simpler.

The boring stuff that makes it all work is the really hard stuff. Distributed computing is hard. There is no getting away from it, there is no magic wand. The NOSQL databases allow you to make an informed choice. I will buy this way of doing stuff because I can bear the cost of doing it that way.

The problem is that the choice isn't always that well informed or even informed.

One of the selling points of a distributed system is that fault tolerance is built in by holding multiple copies of everything. Because of this extra level of redundancy, the argument goes, you can run this little lot on commodity kit.

Commodity kit is much more reliable than it was but using commodity kit should be done with the expectation of hardware failure. What we really need to do is rehearse disaster recovery scenarios, learn from the mistakes and share the knowledge just as we used to do back in the early days of SQL Server/ORACLE/DB2/Sybase etc.

LinkedIn Profile
www.simple-talk.com
Jim P.
Jim P.
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2617 Visits: 2215
David.Poole (2/3/2014)
From a developer perspective ... The problem is that the choice isn't always that well informed or even informed.

But I have seen some of the uninformed development types. And that was with a set of Access DBs for ETL (stove piped systems). After the uninformed dev type was no longer with the company we rebuilt all his stuff from the ground up and regained about 25-30 hours of processing time from/for the level I staff.

One of the selling points of a distributed system is that fault tolerance is built in by holding multiple copies of everything. Because of this extra level of redundancy, the argument goes, you can run this little lot on commodity kit.

The problem with going to the commodity kit model is the typical management staff doesn't understand that buying a bunch of Dell Tungsten level servers with a RAID setup is still never going to have the same performance of a full up server designed with the production model in mind.

So there is a combo of problems. And I have run into it before. I have had delivered apps that I delved into the SQL code and it was horrible on the SQL side. I had no clue of the exe/dll content, but the SQL didn't reassure me. The DB normalization was very questionable. It looked mostly like a 4th level norm then bast***tized to a 2nd level.

The devs who are writing very questionable code meet up with the the user/buyer company management that will only buy crap commodity equipment and your app runs like crap.

The buyer company IT team is screwed by management and the dev company because the end-user says "I should use a typewriter and a form." And what's sad is they are right.

So I look at the NoSQL as a waste until the devs can do efficient code and the management is willing to invest in infrastructure.



----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.
Dave Poole
Dave Poole
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23996 Visits: 3482
Jim, my experience is that you will rarely get isolated pockets of woes.

If you don't like the SQL then a good developer will find that the code is wonky. A good network guy will find horrors in the network infrastructure. A good business analyst will look at the business processes and diplomatically say WTF!

All in all you will have a system that isn't exactly uncrap

LinkedIn Profile
www.simple-talk.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search