Load into KiviDB: migrate from DigitalOcean to KiviDB

From a copy tool: start KiviDB first, with TLS if your clients will keep using it, then run the tool with KiviDB as the writer, as above:

Self-hosted KiviDB

From a copy tool: start KiviDB first, with TLS if your clients will keep using it, then run the tool with KiviDB as the writer, as above:

kividb --port 6380 --tls-port 6381 --tls-cert-file server.pem --tls-key-file server.key \
  --requirepass "$KIVIDB_PASSWORD" --dir /var/lib/kividb

From an RDB file:

kividb --dir /var/lib/kividb --preload-file rdb:/backups/dump.rdb

The server does not start if the file cannot be read, so you never get an empty server by mistake. Every numbered database in the file is loaded.

KiviDB Cloud

  1. Create the database with the add-ons your cluster needs (Lua scripting, TLS). Turning either on later restarts the database.
  2. Allow the copy machine under Configuration → Network → Allowed IPs.
  3. Download the CA certificate from Configuration (kividb-ca.pem). RIOT needs it to verify the database's certificate.
  4. Take the host, port and kividbapp password from the overview, and run the copy tool with them, as above.

With an RDB file: Snapshots → Import a snapshot, upload the .rdb file, and create a database from it, or restore it into an existing one. The file can't be larger than the database's data size.