{"id":2620,"date":"2017-09-28T12:47:08","date_gmt":"2017-09-28T11:47:08","guid":{"rendered":"https:\/\/www.threesl.com\/blog\/?p=2620"},"modified":"2017-10-16T14:53:11","modified_gmt":"2017-10-16T13:53:11","slug":"storing-project-databases-nas","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/storing-project-databases-nas\/","title":{"rendered":"Storing Project Databases in NAS"},"content":{"rendered":"

We are sometimes asked about storing project databases in NAS (network attached storage), is it possible, is it a good idea, and how to do it.<\/p>\n

NAS<\/h2>\n

Network attached storage<\/em> is a type of storage device that attaches directly to a network. It is typically a RAID array<\/em> of disks with one or more interfaces and some management software. It provides network storage without a need to manage a server with attached storage.<\/p>\n

\"A
A Typical NAS Device<\/figcaption><\/figure>\n

Storing Project Databases in NAS<\/h2>\n

Each Cradle project database<\/em> is a directory of files and subdirectories. It can be stored anywhere. So, yes, you can store a Cradle database<\/em> on a NAS device<\/em>.<\/p>\n

Since the NAS device<\/em> is not a server in the normal sense, it will not be running any part of Cradle<\/em> and, in particular, will therefore not be running the Cradle Database Server (CDS)<\/em>.<\/p>\n

Therefore storing Cradle database(s)<\/em> on a NAS device<\/em> means that you are storing them remote form the CDS<\/em>.<\/p>\n

Storing Project Databases in Server Storage<\/h2>\n

For the same reason, you can store a Cradle project database<\/em> on a server that is separate from the computer that runs the CDS<\/em>.<\/p>\n

Therefore storing Cradle database(s)<\/em> on a separate server means that you are storing them remote form the CDS<\/em>.<\/p>\n

Advantages and Disadvantages<\/h2>\n

If you don’t have a server<\/em> in your network, then a NAS device<\/em> is a cost-effective means to add centralised storage.<\/p>\n

NAS devices<\/em> are often used to collate data for backup. Storing Cradle databases on a NAS device<\/em> eliminates the need to copy the databases onto the NAS device<\/em> for backup.<\/p>\n

Not storing Cradle databases<\/em> on the machine that runs the CDS<\/em> adds considerable latency between the CDS<\/em> and the disk(s) that store the databases. Increasing latency worsens the performance of the CDS<\/em>.<\/p>\n

How to Store Cradle Databases on NAS<\/h2>\n
    \n
  1. Specify the location of the database’s directory using a UNC pathname, of the form: \\\\hostname\\path<\/samp><\/li>\n
  2. Ensure that the access rights of the database’s NAS<\/em> directory are accessible RW by the Windows ‘System’ user of the computer that runs the CDS<\/em> or, for Linux, either root or whatever user your CDS<\/em> runs as on its local machine<\/li>\n<\/ol>\n

    Recommendations<\/h2>\n

    In general, we do not recommend storing project databases in NAS<\/em> or indeed in any network-based resource.<\/p>\n

    If possible, only store your Cradle databases<\/em> on the machine that runs the CDS<\/em> and backup your databases regularly!<\/p>\n