[SERVER-10440] snapshoting ebs volumes Created: 06/Aug/13  Updated: 10/Dec/14  Resolved: 12/Aug/13

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.4.5
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: kishore battula Assignee: Stennie Steneker (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

backing up ebs volume


Participants:

 Description   

I have three servers running on amazon aws. each host contains a config server, a mongos instance and a mongod which is part of replica set. All of them save data and logs to ebs RAID10 disc mounted on /ebs folder. Now if i want to take snap shot of the database i will go to on of the host running secondary and will lock the database, snapshot it and then will unlock it. My question is do i need to lock the config sever also? If yes how do i do that? Is it as usual as locking mongodb or not. The RAID consists of 4 discs
The above described is my actual question. But by searching over net and discussion on google groups i found if i am using journal there is no need to lock database. But my question is as i am taking snapshot of discs one after the other until all 4 are completed, how consistency is achieved while writes happen to other discs while i am taking snapshot



 Comments   
Comment by Stennie Steneker (Inactive) [ 12/Aug/13 ]

Hi Kishore,

The SERVER project is for reporting bugs or feature suggestions for the MongoDB server.

For MongoDB-related support discussion you should post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow.

I see that you already posted this question on the mongodb-user group and there has been some discussion since the server issue was created.

The MongoDB manual has complete instructions on Backup Strategies and how to Create a Backup of a Sharded Cluster with Filesystem Snapshots.

As per the documentation, you need to stop the balancer and shutdown one of the config servers to avoid metadata changes during the backup process. This will give you an approximate point-in-time backup if you allow writes to continue while the backup snapshots are created.

If anything seems unclear, I would suggest you continue your questions on the mongodb-user discussion thread you already started.

Thanks,
Stephen

Generated at Thu Feb 08 03:23:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.