Deploying OrientDB with Simplyblock Storage

OrientDB is a multi-model database that supports graph, document, key-value, and object data. While it is flexible, performance depends on how well its data and transaction logs are stored. Using slow or zone-limited storage can result in query delays, replication lag, and issues during backups.

Simplyblock provides NVMe-over-TCP storage with zone-independent volumes, allowing OrientDB clusters to remain fast, reliable, and scalable.

OrientDB Efficiency Through Proper Storage

OrientDB requires efficient storage for write-ahead logs, databases, and backups. When storage performance drops, replication slows, queries take longer, and crash recovery becomes less predictable.

By placing OrientDB files on simplyblock volumes, administrators gain high throughput and consistent performance across nodes and zones. This ensures OrientDB’s multi-model engine can handle mixed workloads smoothly.

🚀 Use simplyblock with OrientDB for Multi-Model Data
Simplyblock delivers reliable storage for graph and document workloads in OrientDB.
👉 Use simplyblock for GKE →

Step 1: Preparing a Simplyblock Volume for OrientDB

Start by creating a volume for OrientDB data and logs:

sbctl pool create orientdb-pool /dev/nvme0n1

sbctl volume add orientdb-data 150G orientdb-pool

sbctl volume connect orientdb-data

Format and mount the volume:

mkfs.ext4 /dev/nvme0n1

mkdir -p /var/lib/orientdb

mount /dev/nvme0n1 /var/lib/orientdb

Persist it in /etc/fstab:

/dev/nvme0n1 /var/lib/orientdb ext4 defaults 0 0

With this setup, OrientDB stores its databases and logs directly on simplyblock volumes for durability.

Step 2: Configuring OrientDB to Use Simplyblock

Point OrientDB to the mounted simplyblock directory. In orientdb-server-config.xml:

<entry name=”db.path” value=”/var/lib/orientdb/databases”/>

<entry name=”log.path” value=”/var/lib/orientdb/logs”/>

Restart OrientDB:

sudo systemctl restart orientdb

This configuration ensures OrientDB’s database and log files are persisted on Simplyblock-backed storage. See the OrientDB configuration reference for details.

Step 3: Expanding OrientDB Volumes for Growth

As OrientDB databases grow, scale the simplyblock volume without downtime:

sbctl volume resize orientdb-data 300G

resize2fs /dev/nvme0n1

 This allows OrientDB to handle larger datasets and mixed workloads. It also aligns with Hybrid Multi-Cloud Storage.

Step 4: Keeping OrientDB Online Across Zones

OrientDB clusters may span multiple zones to improve resilience. Traditional storage tied to one zone risks downtime during rescheduling or failovers.

Simplyblock’s zone-independent volumes ensure OrientDB data remains accessible regardless of zone.

This supports recovery plans similar to Reduction of RPO and RTO.

Step 5: Replicating OrientDB Data with Simplyblock

Add storage replication to strengthen OrientDB’s resilience:

sbctl volume replicate orientdb-data –zones=zone-a,zone-b

 This ensures OrientDB can recover quickly after failures, minimizing data loss. For replication commands and HA setup, see the OrientDB HA SET guide.

High-Volume OrientDB Scaling with Simplyblock

Enterprises running OrientDB need storage that performs well while remaining simple to manage. Simplyblock supports provisioning, resizing, and replication with a single CLI workflow.

Features like VMware Storage make it easier to deploy OrientDB in hybrid environments. Technical references can be found in the simplyblock Documentation.

Questions and Answers