MongoDB Production Depoloyment Techniques (.0 and .ns files)

[Narasimha Rao]

We are using Mango db and just wanted to deploy .0 and .ns extension files in production environement. Could you please suggest better ways to deploy .ns and .0 files.

Thanks in advance and waiting for quick response

[Stephen Steneker]

On Tuesday, 25 April 2017 23:35:38 UTC+10, Narasimha Rao wrote:

We are using Mango db and just wanted to deploy .0 and .ns extension files in production environement. Could you please suggest better ways to deploy .ns and .0 files.

Hi,

The files you have described are a subset of the data files used by a deployment using the MMAP storage engine in MongoDB. In order to have a consistent backup of your data, you should be following one of the supported MongoDB Backup Methods in the manual for your version of MongoDB.

For copying files from a development environment, the easiest way to ensure consistency would be to shutdown your MongoDB server before copying all files in the dbPath. The backup methods in the manual include further details relevant to different backup approaches and deployment types.

If you need more assistance, please confirm the following details for your development and production environments:

• Specific version of MongoDB server

• Type of deployment (standalone, replica set, or sharded cluster)

• O/S version

• Backup method you are using

I would also note that the default storage engine in MongoDB 3.2+ has changed from MMAP to WiredTiger. WiredTiger has several significant improvements over MMAP including document-level concurrency control and data/index compression. For a new production deployment I would encourage deploying with a recent production release of MongoDB (i.e. latest 3.4.x) as well as the WiredTiger storage engine.

Regards, Stennie

[Narasimha Rao]

Hi,

   Thanks for you reply, currently we are copying the files and generating .msi(Installation setup). Requirement is best way instead of copying and for generating .msi 

[Stephen Steneker]

On Wednesday, 26 April 2017 20:39:30 UTC+10, Narasimha Rao wrote:

   Thanks for you reply, currently we are copying the files and generating .msi(Installation setup). Requirement is best way instead of copying and for generating .msi 

Hi,

Can you provide some more detail on your use case as well as information on the environment (specific version of MongoDB server, type of deployment, O/S version).

Creating an MSI to install data files sounds like an unusual way to seed a production deployment. It would be more typical to load data into a fresh MongoDB deployment using one of the supported backup & restore methods. Is this a custom installer for an application that you are distributing to end users? Are you doing a one-off install of data or do you also plan to provide updates?

Regards,

Stennie

[Narasimha Rao]

Hi,

   We are using below versions 

Mongo db version  --     3.0.2

Type of deployment -    Standalone (.msi setup)

OS Name:                   Microsoft Windows 8.1 Pro

OS Version:                 6.3.9600 N/A Build 9600

OS Manufacturer:         Microsoft Corporation

OS Configuration:         Member Workstation

OS Build Type:            Multiprocessor Free

BIOS Version:             Dell Inc. A14, 11/1/2016

Thanks

Narasimha