Setting MMS backup agent for my server.

I want to start MMS backup agent for my replicaset (2 data+1 arbiter node) and 1 stand alone instance. I've a set of questions,can you please ask your technical team to answer these questions for me?The questions are:

1. Can I do it for  a standalone instance?

2. Can I restore a single database of an instance using point in time recovery,instead of recovering full instance?

3. How long will it take to recover a database/instance?

Also I want to know where this backup will be stored,can we store it at our own storage like AWS s3?

Also I want to know If I can install both MMS agents on server running arbiter node or I'll reqwuire a new server,as Mongodb recommend installing it on separate server because of common resource requirement?Arbiter server that I'm using  is a t1.micro aws EC2 instance.

I'd be happy to help you with this. I'll handle your questions in order:

1) MMS Backup uses the oplog, so you cannot backup a standalone instance. You can, however, backup a single-member replica set.

2) You cannot restore a single database using PIT recovery. However, you can use tools like mongodump and mongorestore to pull out individual databases and collections from a restore file and push them into your running mongoD processes.

3) That depends entirely upon the database size and network throughput available.

4) The Monitoring Agent has very minimal system requirements, but the Backup Agent requires at least 3GB of dedicated RAM and a dedicated CPU core, more than a micro instance can provide (especially if it's also running an arbiter and the Monitoring Agent!).

Thanks for asking about MMS. Let me know if there's anything else I can help you with!

Thanx for your guidance, it helped a lot.But still I'm having anoather set of questions:

1.What will be procedure of recovery,in case of PIT recovery will it be done using just clicking something and it will be done automatically or I'll have to run set of commands like downloading backup and restore.

2.what IOPS should we use with AWS ebs volume.(I've 24 GB data in my data directory,with 100s of databases)

3.Should we get an EC2 instance in advance to use at the time of PIT recovery,or how we can achieve it?

4.where it(backup) will be saved,can we save it on our own preferred location like AWS s3 storage?

Thanks for writing in. I'll jump right into it here:

1. Check out our instructions for point in time recovery here. The quick summary is we deliver (via either SCP or HTTPS) custom MongoDB data files that you can simply run a mongoD on top of.
2. That depends entirely upon how many updates you will have in your system. There is no general answer for this, and estimates for it is a bit out of my wheelhouse, and may be better estimated by others in this community.
3. That is one option. Then you can use an SCP "push" restore directly into the new instance. Or you can use an HTTPS "pull" down to a local machine and then back up to your instance, or directly into the instance. Really, there's tons of options here.
4. The restore files are just mongoD data files. Put them wherever you like.

I hope this helps clear things up with respect to MMS Cloud Backup. Let me know if there's anything else I can help you with.