What is New in HQbird 2027
This document lists the changes of HQbird 2027, newest first. Each part begins with the number of the release and its date. A new release adds its part at the top; the parts below it stay as they were.
- 2027.2.34 and later: one part for each release.
- 2027.2.33: the whole HQbird 2027 at that release, compared with HQbird 2024.
- The notes of each kit from 2027.2.8 to 2027.2.33 are in hqbird2027-whats-new-2027.2.8-2027.2.33.md on the download site.
Installers: HQbird 2027 Download.
Downloads: https://ib-aid.com/download/hqbird/v2027/
(Windows setup .exe and Linux .run for Firebird 2.5, 3.0, 4.0 and 5.0;
SHA256SUMS has the checksums).
Docker images: ghcr.io/ibsurgeon/hqbird2027-fb25, -fb30, -fb40, -fb50.
2027.2.35 (2026-11-18)
Versions
| Component | Version | Changed |
|---|---|---|
| HQbird agent (fbagent, enroll) | 3.6.0 | yes |
| HQbird Monitor | 1.59.0 | yes |
| Config editor (in HQbird Monitor) | 1.63.0 | yes |
| HQbird RCM | 2027.5.13 | yes |
| HQCluster node | 2027.5.13 | yes |
| fbmcp (MCP server for Firebird) | 2027.2.24 | no |
| Firebird | 2.5.9.27194, 3.0.15.33893, 4.0.8.3332, 5.0.5.1917 | no |
Cluster: reinit after a backup and restore of a master database
- A backup and restore (gbak) of a master database gives it a new GUID, and
its replicas cannot apply its journal any more. The node sees this in a
few seconds, pauses the shipping to each replica (reason
master_db_replaced) and sets the master toNEEDS_REINIT, as before. - New: RCM decides what to do next, by the setting
auto_reinit.on_master_restoreinrcm.json(also on the Settings page):auto: RCM reinits every replica of the database by itself, after a wait of 300 seconds (auto_reinit.master_restore_settle_sec);window: RCM reinits them in its automatic-reinit window;propose: RCM starts nothing and waits for an operator.
- Without the setting nothing changes:
windowwhen the automatic reinit is on,proposewhen it is off. - The row of the master database on the Databases page says what happened and what RCM does. The new button Reinit all replicas now starts the reinit of all replicas, one after another. Snooze holds it back.
- The node reacts to any replacement of the database file: a restore made
by hand, or the backup-restore cycle of the agent. Checked on Firebird
2.5, 3.0 and 5.0. The alert
master_db_replacedgoes to the notification channels of RCM.
Cluster: replication of HQbird 2024 (FBDataGuard) goes to RCM
- On a server updated from HQbird 2024 the agent reads the replication settings of FBDataGuard (roles, journal and archive folders, replica targets) and gives them to RCM.
- RCM links the replica hosts by itself. A host it cannot link is shown as a candidate on the Link hosts page.
- RCM then takes over the replication of the databases as it is. It does not reinit a replica, does not restart Firebird and does not delete files. It waits while FBDataGuard still runs.
- The page Settings → Import from FBDataGuard shows the state of the
import and repeats it. The command line has
hqbirdrcm dg-import statusandhqbirdrcm dg-import retry. - The node reads the blocks that FBDataGuard wrote in
replication.confand the journal segments it renamed to.uploaded. - The import was tested on Linux servers.
RCM: the Databases page
- The line of a master database with publication on shows how many tables
are in the publication and how many the operator took out, for example
publication on · tables: 118 · taken out: 2.
Installers: the first RCM password
- After an install with RCM, the Linux installer shows the generated
password of
rcmadminon the terminal, with the path of its file. The Windows setup shows it on the result page. - The password is shown on a terminal only. It is not written to a log, a pipe or the install result file.
HQbird Monitor: the time of the range
- The time fields of the time range (dashboard, database pages, Logs,
Errors) are two typed fields, hours and minutes, in place of the lists.
The up and down arrows change a value by 1,
:moves from the hours to the minutes, and a short list offers 15-minute steps.
Config editor in HQbird Monitor
- A time stamp is the exact time. Its age (“23 min ago”) is in the tooltip.
- The outcome panel of a backup job has a Size row: the backup file of the run, and the database that its test restore built.
- The agent configuration pages fit a phone and a 1280 px screen: the tab row wraps, Settings shows its entries as one scrolling line, and the Jobs and Backups tables no longer scroll sideways at 1280 px.
Fixes
- HQbird 3.0 on a server updated from HQbird 2024 did not start after the
cluster setup (“Incorrect version of replication config file”): Firebird
loaded the old copy of the replication plugin from the
pluginsfolder. The copy is now kept outside that folder. - The node applies a change of
limits.rescan_interval_secwithout a restart.
Upgrading
- Install or update with the 2027.2.35 Windows setup or Linux
.run. A server with automatic updates takes the agent 3.6.0 and HQbird Monitor 1.59.0 by itself. - In a cluster, update RCM before the nodes, or at the same time. RCM 2027.5.13 works with older nodes; the import from FBDataGuard needs nodes 2027.5.13.
- A scheduled backup-restore cycle on a master database of a cluster: set
auto_reinit.on_master_restoretoauto. Otherwise the replicas get no changes after the cycle until an operator starts the reinit. - Docker: pull the 2027.2.35 image and start a new container on the same volumes.
2027.2.34 (2026-11-17)
Versions
| Component | Version | Changed |
|---|---|---|
| HQbird agent (fbagent, enroll) | 3.5.0 | yes |
| HQbird Monitor | 1.58.0 | yes |
| Config editor (in HQbird Monitor) | 1.62.0 | yes |
| fbmcp (MCP server for Firebird) | 2027.2.24 | no |
| HQbird RCM | 2027.5.12 | no |
| HQCluster node | 2027.5.12 | no |
| Firebird | 2.5.9.27194, 3.0.15.33893, 4.0.8.3332, 5.0.5.1917 | no |
The log of a gbak job is kept whole
- Before, the agent cut the middle out of a gbak log larger than 16 MiB. Now
the log of each phase of a backup or restore job is one
.log.ziparchive with everything gbak printed. - Beside the archive the agent keeps a small text file with the last 100 lines of the output and of the errors.
- In the config editor Download log saves the archive. The new button Last lines, in the log line of a job and in the restore history, shows the end of the log without a download.
- An archive larger than 30 MB is not sent to HQCenter. Its line says kept on the server only, and Download log shows the path of the archive on the server. The last lines are still sent.
- Logs written by earlier versions (
.log.gz) are kept and download as before.
HQbird Monitor on a phone
- On a screen 768 px wide or narrower the header is one row: the back arrow, the server name and a menu button. The button opens the server menu, Settings, the language and Log out as a panel. Before, the header took three rows and showed four of the seven menu items.
- The time range is one button. It opens the date, the interval and the presets as a panel. The Include and Exclude filters of Logs, Errors and Conflicts fold under a Filters button.
- On a screen 600 px wide or narrower the servers, the databases of the dashboard, the errors and the log records are cards. Nothing scrolls sideways.
- Buttons and fields are at least 44 px high, and the text of a field is 16 px, so Safari on iPhone does not zoom the page when you tap a field.
Database pages in HQbird Monitor
- A database page keeps the server menu: Logs, Configs, Errors, Conflicts, Perf Report, Jobs and Backups are one click away. Before, the database items took the place of the server menu.
- The database items (Database, Metrics, Clients Versions, Statistics, Performance report) are in a row under the header. The row starts with the DB label and the database name, and it stays in place when you scroll.
- Click the database name to see the databases of the server: the name, the path and the size of each. Another database opens on the same page, day and time range. From 8 databases the list has a search field.
- Perf Report shows the row of a database while that database is chosen in the Database list.
- The logo on a database page is no longer a link to the dashboard; the server name is.
- The User Guide (English and Brazilian Portuguese) is updated, with new pictures.
Linux installer
- ALT Linux. On a clean ALT 11 the kits for Firebird 3.0, 4.0 and 5.0 stopped with code 6, because the installer asked for Debian package names. The installer now knows ALT Linux and installs the right packages.
sudofor one group only. On a system where only a group may runsudo(ALT Linux: the groupwheel), the install rolled back. The installer now adds the account of the agent to that group and says so. It stops, with the reason, when that group may run every command without a password or when only root may runsudo.- A failed install leaves nothing behind. The rollback now stops a Firebird service that ran from the removed folder and held the port, and it removes the agent folder and its sudoers file. The next try starts clean.
- SELinux. On AlmaLinux 8 HQbird Monitor was not installed: its unit file had a wrong SELinux label. The installer now sets the label.
Docker images
- A cluster router (HAProxy) now starts in the container. Before, the router service did not start in the image.
- A new container on the volumes of an old one, with a router on them, no longer stops in a restart loop.
Fixes
- HQbird Monitor on a phone: the Jobs and Backups items showed for a server whose agent has no configuration editor.
Upgrading
- Install or update with the 2027.2.34 Windows setup or Linux
.run. A server with automatic updates takes the agent 3.5.0 and HQbird Monitor 1.58.0 by itself. - An HQCenter needs HQbird Monitor 1.58.0 to download the new
.log.ziplogs of its agents. Update the HQCenter before the agents, or at the same time. - A proxy in front of HQbird Monitor that filters response content types
must allow
application/ziponapi/joblog. - Docker: pull the 2027.2.34 image and start a new container on the same volumes.
2027.2.33 (2026-11-16): HQbird 2027 compared with HQbird 2024
State of the source code on 2026-11-16. The released kit was 2027.2.33 (2026-11-16). This part gives the whole picture against HQbird 2024.
1. Summary
- The Java tool FBDataGuard is replaced. Its work is now done by a service, fbagent, and by a web console, HQbird Monitor.
- New: HQbird Cluster. A cluster manager (RCM) and a node on each server give replica setup from a web page, switchover, failover and rejoin.
- New: HQCenter. Your own central server for many HQbird servers: one console, config delivery, updates, licenses, problem watch.
- New: fbmcp. An MCP server that lets an AI assistant work as a Firebird DBA. Critical changes need the approval of a person outside the AI client.
- New installers. One offline setup per Firebird major version, for Windows
(
.exe) and Linux (.run), with several Firebird major versions and several instances on one server. Docker images for each major version. - New licensing. Signed license files, a trial with no registration for 7 days, license zones EU / RU / BR.
- Automatic updates of the agent, HQbird Monitor, fbmcp, the cluster programs and Firebird, with signature checks and rollback.
- Engine. NGRAM index, materialized views,
CREATE INDEX CONCURRENTLY,CREATE TABLE AS SELECT, advanced trace options, a connection limit per database, Active Directory login on Linux.
2. Components: 2024 and 2027
| HQbird 2024 | HQbird 2027 |
|---|---|
| FBDataGuard (Java, web console on port 8082) | fbagent (service) + HQbird Monitor (web console) + config editor inside the Monitor |
| Advanced Monitoring Viewer (AMV), desktop tools | HQbird Monitor pages: dashboard, performance report, errors, conflicts, statistics |
| Replication set by hand or in FBDataGuard, manual failover | HQbird Cluster: RCM + node, switchover, failover, routers |
| No central server | HQCenter (Linux) for a fleet of servers |
| No AI tools | fbmcp, an MCP server with about 120 tools |
| One Windows setup with components, a Linux script | One offline setup per Firebird major version, .exe and .run, Docker images |
| Activation by e-mail and password | Signed license file, trial, license zones |
| E-mail alerts from FBDataGuard | E-mail from HQCenter status watch; Telegram, webhooks and e-mail from the agent |
3. Versions
| Component | Version in kit 2027.2.33 |
|---|---|
| Firebird (HQbird builds) | 2.5.9.27194, 3.0.15.33893, 4.0.8.3332, 5.0.5.1917 |
| fbagent | 3.4.0 |
| HQbird Monitor | 1.57.0 |
| Config editor (in the Monitor) | 1.61.0 |
| HQbird RCM / cluster node | 2027.5.12 |
| fbmcp | 2027.2.24 |
| HQCenter (goafts, site stack) | 1.22.0 |
| fblogspacker (inside fbagent) | 1.5.12 |
4. Firebird engine (HQbird builds)
HQbird builds of Firebird have server-level features (plugins and core changes) that the vanilla Firebird of the same version does not have. The table shows each feature and the Firebird major versions that have it. The source is the page HQbird 2027 Server-Level Improvements.
| Feature | What it gives | Parameter | Major versions |
|---|---|---|---|
| NGRAM index | Indexed substring search (LIKE '%search%') for VARCHAR and text BLOBs |
- | 5.0 |
| Materialized views | CREATE MATERIALIZED VIEW, for BI and complex queries. Uses bulk insert |
- | 5.0 |
| Table as a query result | CREATE TABLE AS SELECT. Uses bulk insert |
- | 5.0 |
| Index creation under load | CREATE INDEX ... CONCURRENTLY: the table stays available |
- | 5.0 |
| Faster MON$ tables | Turns off the collection of data that is not needed | FillMonCompiledStatements, FillMonStatements, FillMonCallStack |
5.0 |
| Easy migration to 5.0 | Old-style literals are recognized; COUNT(*) is described as INT for old applications |
LegacyTimeLiterals, LegacyIntForCount |
5.0 |
| GSSAPI/SSPI authentication | gssauth plugin for Active Directory; Windows and Linux servers and clients |
- | 5.0 |
| No logging of INET errors | Network errors are not written to firebird.log |
DisableLogNetIOErrors |
5.0 |
| Lightweight monitoring | Server state tracking with no load | MonitoringPlugin |
2.5, 3.0, 4.0, 5.0 |
| Limit of connections to a database | Protection against connection spikes | WarnCountAttachments, MaxCountAttachments |
3.0, 4.0, 5.0 |
| Advanced trace options | Tracking of conflicts (deadlocks) and of changes (for example, a change audit) | - | 3.0, 4.0, 5.0 |
| Query substitution on the fly | The server replaces the query text. The new text is visible in trace and MON$ | SqlSubstDirectory |
2.5, 3.0, 4.0, 5.0 |
| BLOB cache in temporary space | BLOBs are 15-200% faster | BlobTempSpace |
2.5, 3.0, 4.0, 5.0 |
| Log of queries with large sorts | The query text is written to firebird.log |
TempSpaceLogThreshold |
2.5, 3.0, 4.0, 5.0 |
| External data sources: MySQL and ODBC | EXECUTE STATEMENT ... ON EXTERNAL to MySQL and ODBC |
- | 3.0, 4.0, 5.0 |
| Streaming / CDC (Kafka, RabbitMQ, JSON, Mongo) | Sends INSERT/UPDATE/DELETE of chosen tables, based on replication. On request | - | 4.0, 5.0 |
| Full-text search (Lucene) | Open-source UDR, and a plugin based on streaming | - | 3.0, 4.0, 5.0 |
| Auto-correction of cache parameters | Corrects wrong DefaultDbCachePages values in firebird.conf / databases.conf |
DefaultDbCachePages, MinDbCachePages, MaxDbCachePages |
4.0, 5.0 |
| HQbird version masking | Sets whether the Firebird API returns the HQbird version string | HQbirdVersionString |
2.5, 3.0, 4.0, 5.0 |
| Database encryption (plugin) | AES-256, 4-20% overhead. On request | - | 3.0, 4.0, 5.0 |
| JOIN optimizer | Implicit inner joins become explicit | LeftJoinConversion |
3.0, 4.0 |
| Cache of prepared queries | Prepared queries stay in the connection memory | DSQLCacheSize |
3.0, 4.0 |
| Multi-thread backup, restore, sweep, index creation | Up to 4-6x faster backup and sweep, 2-4x faster restore (8 cores, SSD) | - | 2.5, 3.0, 4.0 |
| Native replication | Plugin; records with no PK/UK can be excluded | - | 2.5, 3.0 |
| Optimizer of large sorts | Refetch plan | SortDataStorageThreshold |
2.5, 3.0 |
| Parallel data reading | make_dbkey() and a shared snapshot |
- | 2.5, 3.0 |
| Pool of external connections | Parallel external queries to Firebird | ExtConnPoolSize, ExtConnPoolLifeTime |
2.5, 3.0 |
| Backups to Amazon S3 (plugin) | On request | - | not stated |
5. fbagent: the agent that replaces FBDataGuard
One agent serves one Firebird instance. Several agents can run on one host. The agent works with Firebird 2.5, 3.0, 4.0 and 5.0 on Windows and Linux.
5.1 Backups
- Verified backup (gbak) for one database or a group of databases in folders, with an optional test restore.
- Incremental nbackup, levels 0 to 4, in simple, advanced or group mode.
- nbackup plan mode: rules give the level, days and time. The editor shows a calendar and a storage forecast. Retention keeps a level 0 with its increments.
- Backup-restore cycle: backup, restore and swap of the live database, with rollback after a crash.
- Restore jobs from
.fbkor.nbk, local or from S3. - Compression: deflate, zip, gz, zstd.
- Encryption: AES-256 zip archives with key escrow.
- Cloud: streaming backup to S3 with no local file; copy to S3 and FTP/FTPS.
- Backup inventory: a record of every backup file and every restore, with size, time and the verify result.
- Command history: up to 50 launches per job, with gbak logs.
5.2 Maintenance
- Sweep, index statistics,
gfixvalidation, SQL scripts with a run window, metadata tracking. - A cron schedule and an execution window for every job.
- Run now for important jobs: locally, or remotely through HQCenter, with progress and cancel.
- A disk speed test in a night window.
5.3 Health checks
- Server status about every 10 minutes. Each finding has a level, an evidence line and a hint. The status shows trends (for example, the time until a disk is full) and names the transaction or program behind a problem.
- Host metrics: CPU and memory by program, disk latency and IOPS per disk, which service uses the disk, databases in the OS cache.
- Linux limits: TasksMax, NPROC, NOFILE, OOM kills.
- Disk space: free-space floors and fast-filling detection.
- Logs:
firebird.logandreplication.logare classified by signature, for example probable corruption. - Database state from the header page: shutdown, nbackup lock, replica, read-only.
- Firebird mode: SuperServer, SuperClassic or Classic, with a finding when a mode change waits for a restart.
- Prometheus
/metricsendpoint with a token. - A resource guard limits the agent’s own CPU and memory. It never pauses a backup.
5.4 Performance
- Continuous trace with a watchdog.
- Performance report per time window: rankings by duration, frequency, total time, fetches, reads and writes; plans, procedures, triggers; who ran a statement, when and from where; failed runs.
- Performance report on demand for a chosen range and database.
- Lock conflicts and deadlocks with the SQL of both sides.
- Trace errors by class, with the client application and address.
- Lightweight monitoring through the
fblwmonplugin.
5.5 Configuration
- The agent reloads its config with no restart: validation, backup, and rollback on an error.
databases.confeditor (aliases.confon 2.5): checks per engine version, a backup copy before save, comments are kept.- Users: the list of users of a security database, and Create user.
- Config delivery from HQCenter with a state for each change: sent, applied, rejected, drift.
5.6 Log delivery (fblogspacker)
- The agent sends only new data to HQCenter: the new tail of
firebird.logandreplication.log, per-minute trace and monitoring files, metrics, the server status. - Archives have a size cap (120 MiB by default). Big files go in pieces.
- Backups and databases are never sent.
6. HQbird Monitor: the new web console
One console per Firebird instance (port 20000 + the Firebird port, for example 23050), or one central console for all servers of an HQCenter.
- Servers: all servers with status, Firebird version and mode, agent version, license, and small charts.
- Dashboard: CPU, memory, connections; CPU by program; who uses the disk and memory; temp files; disk space, latency and speed; a database table with state badges. A click on a minute shows that minute.
- Server health report: a matrix of 18 systems for 24 hours, 7 days or 14 days; a problem chronology; findings by area; tables for disks, transactions, replication, errors, queries and backups. Action buttons open the fix in the editor.
- Database page: charts of monitoring, I/O and transactions; top queries and connections for a chosen minute.
- Perf Report: 10 rankings, runs by hour, a comparison of two windows, a 30-day history of a statement, a report on demand.
- Errors and Conflicts: trace errors with CSV export; lock conflicts and deadlocks per minute.
- Statistics: gstat analysis with recommendations, trends and forecasts, Excel and JSON export.
- Logs and Configs:
firebird.logandreplication.logby day with filters; the change history of the.conffiles. - Jobs, Backups, Activity: the embedded config editor and the backup inventory.
- Licenses, Updates, Users, Clusters, Settings.
- Notifications page (the button is on the Servers page): who sends (the agent, the HQCenter, both or nobody), channels, test messages, the chat ID of a Telegram bot, the last 50 deliveries. The page never shows a stored token, URL or password.
- Languages: English, Russian, German, Brazilian Portuguese, Spanish.
- Access: one login or many users with a server list and an admin role; an audit log; light, dark and high-contrast themes; demo mode that masks names and SQL literals. It works with no internet.
7. HQbird Cluster: RCM and node
HQbird 2024 had replication, but no cluster manager. HQbird 2027 adds one.
- Parts. A node beside each Firebird instance, and one RCM per cluster with a web console (HTTPS, port 7444), a command line and an API.
- Replication is asynchronous. Firebird 4.0 and 5.0 use native replication. HQbird 2.5 and 3.0 use the replication plugin.
- A cluster with no HQCenter.
fbagent --cluster-initcreates the RCM and the first admin. The Link hosts page joins other servers with a one-use token. The cluster is off by default; you turn it on at install or from HQbird Monitor. - Replica setup from the console: enroll a database, set the publication, initialize. The copy is made with nbackup. Smooth reinit waits for long writing transactions. The node never overwrites a working database.
- Takeover of databases that already replicate from a hand-made config.
- Several replicas of one master.
- States and lag for every database (in sync, lagging, needs reinit, and others), each with a reason.
- Verify: a row count comparison of master and replica, on demand or on a schedule.
- Services: one logical database on several hosts.
- Switchover with no data loss, then the old master rejoins as a replica.
- Manual failover when the master host is lost, with a data-loss report.
- Automatic failover per service, off by default. It needs routers.
- Routers (HAProxy, Linux) give clients one stable address.
- Console: 6 languages, a read-only viewer role, an audit log, alerts with a runbook for each code.
- Alert channels (Telegram, webhooks, e-mail) for problems of severity
warnand higher. The Alerts page has a Test button for each channel. - Security: mutual TLS under a cluster certificate authority, automatic certificate renewal, signed releases.
Limits: no synchronous replication through the cluster; only tables with a primary or unique key are published; at most 3 hosts per cluster by license; one RCM per cluster; routers on Linux only. Switchover was lab-tested on Firebird 5.0 on Linux.
Guides: cluster guide, cluster runbook.
8. HQCenter: a central server for many HQbird servers
- What it is. A Linux server in your network. Agents enroll in it and upload their data. It has a central HQbird Monitor and an admin panel.
- Install with one command on Ubuntu 22.04 / 24.04 / 26.04 or AlmaLinux 9 / 10. A closed network is supported: install from a carried bundle.
- Enrollment: the agent creates its own key. An operator approves it, or a license token approves it while seats are free. All agent traffic uses mutual TLS.
- Fleet table: agent and Firebird versions, last contact, release channel.
- Config delivery to agents, with history and restore. Run important jobs now on any server.
- Updates for the fleet: the agent, HQbird Monitor, cluster programs and Firebird come from the HQCenter catalog. Vendor signatures are checked.
- HQCenter updates itself from a signed stack, with checks and automatic rollback. The owner can turn this off.
- Status watch: new, escalated and cleared problems of all servers, with e-mail and a weekly report. Telegram, webhook and SMTP channels, quiet hours and “silent server” events.
- Licenses: upload, assign to agents, seat counts.
- Request audit: who changed what on a server.
- API with scoped tokens; Prometheus metrics and a Grafana dashboard for HQCenter itself.
- Admin panel in 4 languages: English, Brazilian Portuguese, Russian, German.
Guide: site-install.md.
9. fbmcp: Firebird tools for AI assistants
- An MCP server on the database host. An AI client (for example Claude Desktop or Claude Code) uses it to inspect and manage Firebird 2.5 to 5.0.
- About 120 tools: queries with plan and statistics, schema, sessions,
index advice, gstat, trends; backup, test restore, validation, sweep;
DDL and migrations; users and grants; trace;
firebird.conf; a scheduler; about 30 tools for fbagent (status, reports, jobs, license, updates); the cluster (link, enroll, reinit, verify, switchover, failover). - Safety by tiers:
- Reading needs no approval. It runs in a read-only transaction.
- An ordinary change is confirmed in the AI client with a one-time token.
- A high-impact change is approved only outside the AI client (a tray window on Windows or a command on the server). It also needs an open maintenance window and a verified backup less than 24 hours old.
- Dropping a database is turned off.
- Every decision goes to an audit log.
- The HQbird setups install fbmcp by default, for local use only. Remote use needs HTTPS and an API key.
10. Installers
Windows
- Four setups, one per Firebird major version (
fb25,fb30,fb40,fb50). Each is offline: all files are inside. - Each setup installs Firebird, fbagent, HQbird Monitor and fbmcp. The cluster programs are copied and stay off until you turn them on.
- Several Firebird major versions on one server, and several instances of one major version.
- Wizard pages for the trial, a license file, the connection to HQCenter and automatic updates.
- Silent install with a switch for every page.
- 8 wizard languages: English, Brazilian Portuguese, German, Russian, Spanish, Polish, Turkish, Simplified Chinese.
- The setup and the uninstaller have an Authenticode signature.
- Uninstall removes one instance or all. Databases are always kept.
Guide: HQbird Windows Installation Guide.
Linux
- One offline
.runfile per Firebird major version. Only missing OS packages are downloaded. - Hosts: x86_64 with systemd and apt, dnf/yum or zypper (Ubuntu, Debian, AlmaLinux, Rocky, RHEL, Oracle Linux, openSUSE, RED OS). SELinux in enforcing mode works.
- Full-screen text interface by default, in English, Russian, Brazilian
Portuguese and German.
--no-tuigives plain text mode. - Several instances on one host (Firebird 2.5: one instance).
- Unattended install with
--yesand options.
Guide: HQbird Linux Setup Guide.
Docker
- Public images
ghcr.io/ibsurgeon/hqbird2027-fb25,-fb30,-fb40,-fb50. One container holds one instance with all components. - The images are signed with cosign.
- Cluster role
HQBIRD_CLUSTER_ROLE=master|replicawith compose files. - The image folders are closed to other users, and a new container keeps the RCM account.
Guide: Docker guide.
11. Licensing and trial
- Signed license files. The agent checks the vendor signature. Licensing never stops a database.
- Trial: 7 days with no network step. A work e-mail and a 6-digit code extend it to 30 days.
- License zones EU, RU and BR, each with its own keys.
- Offline: a license file at install; the Windows setup can make a license request file.
- With HQCenter: licenses are uploaded once and assigned to agents.
- A new license arrives by itself. An agent that got its license with a trial request asks the vendor’s license server once an hour. It installs the license the server has for it: a longer trial, a paid license made from the trial, or the next period of a subscription. Nothing is done on the server. The vendor’s license servers start to serve such licenses step by step.
- A trial request can also be sent after the 30 days of the trial: the e-mail address may belong to a customer with a license.
12. Automatic updates
- The agent updates itself. It checks the vendor signature, refuses a downgrade and can roll back.
- The agent updates HQbird Monitor, fbmcp, the cluster programs and Firebird. A Firebird update has a backup, an apply window, a health check and a revert.
- With HQCenter: updates come from the HQCenter catalog by release channel.
- With no HQCenter: updates come from the vendor zone. Modes:
all,agent(Firebird waits for the administrator),off. The Updates page in HQbird Monitor shows the state.
13. Alerts and notifications
- HQCenter status watch sends e-mail about problems of the fleet. The cluster console shows alerts.
- The agent sends its own messages about server problems: when a problem is new, when it gets worse and when it is gone. All changes of one status check go in one message.
- The channels are a Telegram bot of your own, webhooks (Slack, Teams, Discord, Mattermost, Rocket.Chat, ntfy) and e-mail (SMTP), with a severity filter and quiet hours. You can have several channels. Nothing is sent until you add a channel.
- Daily summary: one message a day with the open problems
(
notify.daily_summary, off by default). - With several agents on one machine, only one of them sends the problems of the machine itself (disk, memory).
- Two agent commands:
--notify-history [N]prints the last deliveries,--notify-test <channel>sends a test message. - The agent does not send while its license does not allow it.
- HQbird Telegram bot: a server or an HQCenter with a valid license links a chat with a one-time code. No own bot is needed. The vendor’s servers do not offer this service yet; until they do, use your own Telegram bot, a webhook or e-mail.
- RCM sends cluster alerts to the same channel kinds (
notify.channelsinrcm.json).
14. Security
- Mutual TLS for agents, HQCenter and the cluster.
- Signed releases: the agent refuses an update with no valid vendor signature.
- Authenticode on Windows setups and programs; cosign on Docker images.
- AES-256 encryption of backup archives.
- Secrets are kept out of command lines and config snapshots.
- A request audit log on the agent; audit logs in HQbird Monitor, HQCenter, RCM and fbmcp.
- Remote commands can be turned off on a server
(
--remote-commands off).
15. Upgrading from HQbird 2024
- The 2027 setup finds HQbird 2024, updates Firebird in place and keeps the old folder as a copy.
- FBDataGuard jobs are imported once, at the first start: gbak, nbackup (levels 0 to 4), group backup, sweep and index statistics. The agent continues the existing backup sets.
- Not imported: replication, trace, file transfer, cloud backup, restore, validation. Set them again in the editor.
- The 2024 license is not transferred. The new agent starts in trial mode. Install a 2027 license.
- Removed: the FBDataGuard console on port 8082, AMV, VSS backup, the FTP server, SFTP upload.
- Scripts for the 2024 setup: switches with a 2027 equivalent are accepted. Other switches are refused with a message that names the replacement.
- The import registers the databases of FBDataGuard in the Firebird
aliases file (
databases.conf, oraliases.confon Firebird 2.5). The old file is copied first. A database is left out when its path is already in the file or its file does not exist. A file with anincludedirective is not changed. - The import removes the old monitoring logs of FBDataGuard (the folders
mon\outcomingandmon\outtrace). Nothing is removed while a service of the old HQbird runs. The removal cannot be undone. - Both are on by default. To turn them off, set
hqbird_import.register_databasesorhqbird_import.clean_mon_logstofalse, or use--no-register-databasesand--no-clean-mon-logswith--import-hqbird-config.