---
title: "DataStore Server"
description: ""
url: "https://docs.itrsgroup.com/docs/opsview/6.11.7/administration/distributing-functionality/datastore/index.html"
---
The Opsview Datastore is a persistent NoSQL database.

- It may be accessed via `http://<server_IP_address>:5984/_utils/#`
- The initial password is held within the opsview_deploy servers `/opt/opsview/deploy/etc/user_secrets.yml` file.

## Dependencies

It uses our version of Erlang - `opsview-erlang`.

## Installation

Refer to [Advanced Automated Installation](https://docs.itrsgroup.com/docs/opsview/6.11.7/install/advanced-installation/index.html).

## Configuration

We ship the `opsview-datastore` with the configuration tuned for high-performance. Any configuration overrides should be placed in a `.ini` file in `/opt/opsview/datastore/etc/local.d` directory.

## Management

### Debians

Watchdog service files are now managed by the package, doing a remove would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package managed config files are as follows:

- /opt/opsview/watchdog/etc/services/opsview-datastore.conf
- /opt/opsview/datastore/etc/local.d/custom.ini

### RPMs

Watchdog service files are now managed by the package. Any modifications will be saved at upgrade and remove time.

 - /opt/opsview/watchdog/etc/services/opsview-datastore.conf
 - /opt/opsview/datastore/etc/local.d/custom.ini


**Note**


For hostname changes, datastore as an Erlang component does not handle hostname changes well and reconfiguration or reinstallation is required.



Opsview Datastore logs via syslog using local6 facility.

As root, start, stop and restart the service using:

```
/opt/opsview/watchdog/bin/opsview-monit <start|stop|restart> opsview-datastore
```


