V3.0 / 3.0.2026
V3 enhances database lifecycle operations for PostgreSQL Community, MongoDB Percona and Neo4j Enterprise through the DBaasNow Broker.
Database lifecycle
- Provision standalone and replicated/clustered projects from the licence-granted catalogue.
- Convert a standalone project's plan and add members.
- Add and delete database nodes.
- Perform planned database switchover.
- Apply approved database version updates.
- Start and stop database services or DNCollector.
- Follow database-server migration stages.
- Decommission a managed project.
Database administration
| Engine | Administration coverage |
|---|---|
| PostgreSQL | Create/delete databases, create/change/delete users, parameters and extensions |
| MongoDB Percona | Create users with database access, change/delete users, member settings, replication settings and default read/write concern |
| Neo4j Enterprise | Create/delete databases, create/change/delete users and database leadership operations |
See the Operation Guide for forms, confirmation controls and verification steps.
Licensing and platform setup
POC licences use self-registration for a free 30-day evaluation. Paid production licences are issued through the Sales Team. The licence grant determines catalogue availability and capacity.
The fresh-install package establishes the Gateway, Broker, Plugin, Monitor, Repository and Coordinator. See installation and activation.
Installation configuration and customer access
The current installation configuration provides three Repository password settings: repository_sys_password, repository_pdb_admin_password and repository_dbaasnow_password. Each can use an approved configured value or be left blank for double-entry prompting. Replace shared presets before production use.
Customer setup-administrator fields and prompts are removed. The three Repository credentials are separate from customer Broker access. Fresh-install console login is still admin/admin; change its password immediately. See installation configuration.
Operational limitations and checks
| Symptom | Recommended action |
|---|---|
| Provisioning partially completes | Check every selected host before Re-Provision |
| A rejected or removed member remains displayed | Compare current membership and Activity before retrying |
| User or settings information does not refresh | Verify the operation's result before submitting another change |
| Host patch/configuration information is incomplete | Check DNCollector and observation freshness |
| Historical panels show a retired member | Check current membership and monitoring time range |
| MongoDB Percona on SLES | Treat the configuration as pilot and agree suitability before production use |
| PostgreSQL extension changes | Confirm installed-release support and affected database/port before changing an extension; see Extension Management |
| Initial Neo4j standalone-to-cluster conversion | Prepare the complete topology and an outage; confirm the installed form supports that conversion before submission |
| Active multi-node Neo4j project retirement | Agree cluster-retirement prerequisites before decommissioning; see Decommission Neo4j |
Review environment coverage for tested version/OS combinations and qualifications. Confirm Neo4j role-conversion availability before planning that change.
Dedicated platform upgrade and V2 migration guidance remain outside this release guide.