{"id":1155,"date":"2014-09-16T13:39:07","date_gmt":"2014-09-16T13:39:07","guid":{"rendered":"http:\/\/evolphin.com\/help\/?p=1155"},"modified":"2020-08-04T10:18:55","modified_gmt":"2020-08-04T14:18:55","slug":"configuring-database-location","status":"publish","type":"post","link":"https:\/\/evolphin.com\/help\/administration-server\/configuration-server\/database\/configuring-database-location\/","title":{"rendered":"Configuring or Moving Database Location"},"content":{"rendered":"\n

By default, the Zoom database is installed in the following locations:<\/p>\n\n\n\n

OS<\/th>Path<\/strong><\/th><\/tr><\/thead>
Linux<\/td>[ZoomDir]\/db<\/td><\/tr>
Windows<\/td>C:\\Program Files (x86)\\Evolphin\\DAM\\db directory<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

There are a number of sub-folders that are contained within the db folder. The db has a few components:<\/p>\n\n\n\n

Folder<\/th>Description<\/strong><\/th><\/tr><\/thead>
filedata<\/strong><\/td>Stores the file data information for any of the assets stored in Zoom.<\/td><\/tr>
redo<\/strong><\/td>The transaction logs for the server.<\/td><\/tr>
db<\/strong><\/td>Stores the system database information.<\/td><\/tr>
db-redo.bak<\/strong><\/td>Backup for redo transaction log.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

It is configurable to change the locations of each of these components, however, the default install keeps these in the same location.<\/p>\n\n\n\n

A common practice is for the db to be stored on a remote file share such as a SAN. The following instructions are a guide to how to move the database files to the new location.<\/p>\n\n\n\n

If you current database volume is filling up and you are looking at moving to a network storage, please keep the following in mind:<\/p>\n\n\n\n

Moving DB Location<\/h3>\n\n\n\n
New DB Storage Options<\/th>Caveats<\/th>Comments<\/th><\/tr><\/thead>
NFS<\/td>Best to avoid using NFS as NFS client drivers running on the database server make heavy use of file caching and can play havoc with write-consistency of a database volume<\/td>If you are an expert with NFS tuning and the underlying NFS enterprise storage supports write-consistency by disabling NFS client caching completely, you can tread with caution. If you have never attempted this before then stay away from NFS<\/td><\/tr>
SMB<\/td>Careful tuning of SMB allows write-through model for strong write-consistency. With such a setup it’s viable to use an SMB share for database storage. See this article from Microsoft<\/a> for explanation.<\/td>Core concept is data records must commit to disk, and not get stuck in caches for durability & data integrity. Please check if you have experience running database workloads off a write-consistent SMB share. Also shares will need to be mounted to a mount path with fail-fast behavior. If you don’t know what that means stick to the options below<\/td><\/tr>
DAS<\/td>Direct attached Storage such as a giant RAID box with direct connection to the file system device on the database server is typical for a database workload<\/td>This is the easiest option for most teams as all you need to do is plug the DAS into the server to get a resilient storage connection with RAID modes setup for disk failover and avoid using any network protocol for database writes<\/td><\/tr>
SAN<\/td>Using HBA card a SAN can be connected with FC to the database server for fast database workloads<\/td>For scaling the database to TBs of storage this is often the best option that offers strong durability & write-consistency guarantees via a file system drive that doesn’t cache on the client side.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
  1. Prior to moving your Zoom Database to a new location, ensure that the checkpointing is completed by referring to the server_log.0 under [ZoomDir]\/logs <\/span> directory.
    Refer to the following link for more details on Zoom server checkpointing on restart<\/a><\/div>