amazon ec2 - Mongodb EC2 EBS Backups -


i have confusion on need here. new mongo. have set small mongo server on amazon ec2, ebs volumes, 1 data, 1 logs. need backup. it's okay take db down in middle of night, @ least currently.

using boto library, ebs snapshots , python backup, built simple script following:

sudo service mongodb stop run backup of data run backup of logs sudo service mongodb start

the script ran through , restarted, noted in aws console snapshots still being created, through boto has come back, mongo has restarted. not ideal.

i checked mongo docs, , found explanation on backups:

http://docs.mongodb.org/ecosystem/tutorial/backup-and-restore-mongodb-on-amazon-ec2/#ec2-backup-database-files

this info, bit unclear. if using journaling, are, says:

if dbpath mapped single ebs volume proceed backup database files.

we have single volume data. so, i'm assuming means bypass steps on flushing , locking. @ end of backup database files, discusses removing locks.

so, i'm bit confused. read originally, don't need - can run backup, , not worry flushing/locking period. don't need take db down. paranoid part of me says no, sounds suspicious.

any thoughts on this, or experience, or old fashioned knowledge?

since using journaling, can run snapshot without taking db down. fine long journal files on same ebs volume, unless symlink them elsewhere.

we run lot of mongodb servers on amazon , how too.


Comments

Popular posts from this blog

java - JavaFX 2 slider labelFormatter not being used -

Detect support for Shoutcast ICY MP3 without navigator.userAgent in Firefox? -

web - SVG not rendering properly in Firefox -