DBaasNow V3

Grow Neo4j into a cluster

Converting a managed standalone Neo4j project to a cluster changes both its catalogue plan and its database topology. Plan Conversion updates the project plan; it does not itself create cluster members or copy data.

Prepare the conversion

Confirm that the activated licence grants the intended cluster plan and sufficient capacity. Prepare the existing standalone host and at least two additional hosts for the complete cluster topology. Confirm approved versions, OS compatibility, storage, remote credentials and member connectivity.

Plan an interruption to database service. The conversion stops and reconfigures the existing standalone database and prepares the new members. It is not the same procedure as adding one member to an already running cluster.

Retain verified backups outside the managed paths. Agree application downtime, target member roles, routing, the recovery plan and the completion checks with the database owner.

Convert the project plan

  1. Open the standalone project's Home information.
  2. Select Plan Conversion beside the current catalogue plan.
  3. Review Existing Plan and select the licence-granted cluster plan in Into New Plan.
  4. Enter Remarks and choose Convert Now.
  5. Verify the updated plan and its Activity entry.

If the required plan is absent, review licence entitlements with the administrator.

Submit the topology conversion

Use the project's Add DB Node workflow only after confirming that the installed UI can submit the complete standalone-to-cluster topology, including the required additional hosts. Do not submit successive single-host additions as a substitute for the initial conversion. If the form cannot represent that topology, contact Support for the supported procedure for the installed release.

Review host validation and the complete scope before submitting. Follow Activity for the original host and new members. Preserve the first error and the actual service state if conversion fails; a plan change is not proof that conversion completed.

Verify before reopening application access

Confirm the intended members, roles, database availability, synchronization and leadership. Check application routing and access, then verify DNCollector observations and Monitor metrics for all hosts.

Record the completed topology and any remaining issue before releasing the change. Subsequent growth of an established cluster follows the normal add-node procedure.


Guide overview ยท Documentation home