Straight answers about CertiHANA

No. CertiHANA connects through the HANA SQL port with a dedicated technical user. For host-level tasks such as trace cleanup, file-based offsite copies or the rclone engine it optionally uses SSH to the HANA host. Nothing is installed inside the database.

SAP HANA 2.0 from SPS 04 onwards, SYSTEMDB and tenant databases, on any Linux host (SUSE or Red Hat). The current release is verified on SAP HANA 2.0 SPS 08, revision 87, with SAP Business One 10.0 tenants. CertiHANA itself runs as a Windows Service on Windows Server 2016 or later, or Windows 10/11.

Yes, Business One is a first-class citizen. CertiHANA reads the company registry, shows company databases with version and localisation, exports and imports company schemas, clones and masks test companies, and includes Business One guidance in the health check and recommended jobs.

A documented set of system privileges such as BACKUP ADMIN, CATALOG READ, MONITOR ADMIN, LOG ADMIN, TRACE ADMIN and, on the SYSTEMDB, DATABASE ADMIN, DATABASE BACKUP ADMIN and DATABASE RECOVERY OPERATOR. A commented grant script ships with the product, and the compatibility check in the console lists every task that is not yet permitted.

Yes. Backups can go to the file system or to a third-party backup tool through the SAP Backint interface, and CertiHANA prepares and closes data snapshots for storage-based backups. Retention and the full-backup-with-cleanup task handle Backint copies as well.

SMB/CIFS shares, FTP/FTPS, SFTP, WebDAV (Nextcloud, ownCloud, Synology), S3-compatible object storage (AWS S3, MinIO, Wasabi, Backblaze B2, Ceph, Hetzner, IONOS), Azure Blob Storage, Microsoft OneDrive and SharePoint document libraries, Google Drive, Dropbox, local or UNC paths, and through rclone any further provider such as Box, pCloud, Mega or Google Cloud Storage.

Client-side AES-256-GCM encryption is optional. The key stays in CertiHANA's encrypted store and can be exported for safekeeping, and a standalone script decrypts the copies without CertiHANA. A manifest next to the files documents the offsite set, so the data is never locked in.

Every full backup is checked with hdbbackupcheck, the recovery chain is validated daily with hdbbackupdiag and the RPO check, and the automated test restore recovers the latest full backup into a sandbox tenant, verifies it and drops it again. The result of every step is recorded and reported.

The recovery planner computes the chain for any point in time, generates the complete RECOVER statements and a runbook, and tenant recoveries can be executed from the console under a typed confirmation phrase. Backups that only exist offsite are fetched back to the host first.

Per managed SAP HANA system: the SYSTEMDB and each tenant count separately. The key is bound to the Hardware ID of the CertiHANA server and is verified offline. Standard, Professional and Enterprise editions differ in the number of systems and the support agreement; every feature is included in every edition.

There is no trial mode. Without a licence the console starts with built-in demo systems that show every page and report, but no live HANA system can be registered. We are happy to run a demo on your landscape or to issue an evaluation key under a written offer.

Thirty days before the end a banner appears and administrators are mailed at 30, 14, 7 and 1 days. During the grace period everything keeps working; afterwards no task runs on live systems and no system can be registered until a renewed key is activated. Configuration, history and data stay untouched.

Run the new installer over the existing installation. It keeps configuration, certificates, data and the licence, restarts the Windows Service and finishes in a few minutes. Silent installation and update are supported for automated rollouts.

No. Licence keys are verified offline, and no configuration, credentials or database content leave your server. Support cases are handled over e-mail with the information you choose to share.