Configuring or Moving Database Location

By default, the Zoom database is installed in the following locations:

WindowsC:\Program Files (x86)\Evolphin\DAM\db directory

There are a number of sub-folders that are contained within the db folder. The db has a few components:

filedataStores the file data information for any of the assets stored in Zoom.
redoThe transaction logs for the server.
dbStores the system database information.
db-redo.bakBackup for redo transaction log.

It is configurable to change the locations of each of these components, however, the default install keeps these in the same location.

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.

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

Moving DB Location

New DB Storage OptionsCaveatsComments
NFSBest 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 volumeIf 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
SMBCareful 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 for explanation.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
DASDirect 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 workloadThis 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
SANUsing HBA card a SAN can be connected with FC to the database server for fast database workloadsFor 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.
  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 directory.
    Refer to the following link for more details on Zoom server checkpointing on restart
    • For versions below 5.2, checkpointing is performed every time on the Zoom Server startup.
    • For versions after 5.2. restart can be configured to be done with or without checkpoint through server.xml
  2. Ensure that you have backed up the [ZoomDir]/conf directory and [ZoomDir]/db directory on your Zoom server:
    Refer to the following link for more details on backing up your zoom server
WindowsC:\Program Files (x86)\Evolphin\DAM\db directory
WindowsC:\Program Files (x86)\Evolphin\DAM\conf directory
  1. Stop the Zoom Server and Zoom Preview Server.
  2. Move your current Zoom DB directory to the desired location If placing the DB on a network share, it is necessary for the server to be mapped beforehand.
  3. Navigate to [ZoomPath]/conf/.
  4. Open the server.xml file.
  5. Search for a section called <dbspec>.
  6. Under the tag <defaultRoot>, change the path to the network path. If placing the DB on a network share, it is necessary for the server to be mapped beforehand.
  7. Under the tag <redoLogDir>, change the path to the network path.
  8. Under the tag <fileDataDir>, change the path to the network path.
  9. Save and close the file.
  10. Start the Zoom Server and Zoom Preview Server services.
  11. Open your web browser and navigate to the Web Management Console (http://localhost:8443) and confirm that the server is running. If the server is not running, troubleshoot using your server_log located in [ZoomPath]/logs/

Leave a Comment