Core maintenance
Track storage growth
Use Node Exporter / Nodes to track physical free space on the filesystem backing application data, usually /mnt/irisplus-data.
Also check filesystems backing database volumes and registry storage. If you do not know which filesystems these are, reach out to Irisity.
Compare growth with retention settings and backup activity. Follow the installation manual for storage changes. Do not treat a storage claim's capacity as free space.
Confirm backups and cleanup ran
Open Rancher → Workloads → CronJobs. A CronJob schedules work; each run creates a Job.
Namespace | CronJob | Packaged schedule |
|---|---|---|
app | innovi-core-storage-cleaner | Hourly. |
data | postgres-backup-cronjob | Every 12 hours. |
data | postgres-backup-cleanup-cronjob | Daily at 04:00 in the controller's time zone. |
Read the installed schedule and suspension state. Open the latest Job to check its status and container logs.
Through an authorized Core-host session, inspect /mnt/irisplus-data/db-backup. Check timestamps and nonempty output for these three files from each backup run:
- backup_innovidb_*.sql: product database.
- backup_kratosdb_*.sql: identity database.
- backup_dashboard_*.sql: dashboard database.
File timestamps can differ within one backup run.
Match each file's timestamp to the Job's start and completion times, accounting for time zones. An older dump cannot replace missing output.
If you lack host access, ask the installation administrator to verify those files. The packaged script can report Succeeded after an earlier dump failed.
Check that backups are copied to separate storage. Copies on the same data disk do not protect against that disk's failure.
Successful Jobs and nonempty files do not prove recovery works. Verify recovery using the accepted procedure on a separate test system.
Database dumps do not cover the whole Core. Search data, media and configuration need separate coverage.
Before restoring, obtain the release-specific recovery procedure from Irisity. This guide does not supply an accepted whole-system restore procedure.
Upgrade a Core
Back up first. At least confirm a recent set of database dumps, as described above. Then follow the installer manual chapter for the release that the Core runs now. The manual is on the 2026 R2.1 Core Installation page.
Release the Core runs now | Upgrade to a newer 2026 release | Manual chapter |
|---|---|---|
A 2026 release | Re-run the newer installer on the same server. It upgrades in place. | Day-Two Operations - Upgrading |
2024 R3 | Not in place. The chapter covers its own backup, uninstall, reinstall and restore steps. | Upgrade from 2024 R3 — Single Server |
For an appliance with insufficient GPU memory, follow the upgrade runbook on the same page. For other releases, reach out to Irisity.
The manual does not say whether an upgrade avoids downtime. Plan a maintenance window. After the upgrade, repeat the Core review.
To move a Core to another server, reach out to Irisity.
Maintain accounts and certificates
Replace initial passwords and use individual accounts with the permissions each role needs. Your installation administrator provides the accounts for each tool.
Use the browser's certificate viewer to check expiration and hostname validity.
Prepare support information
If you need assistance, reach out to Irisity through Submit a support request. Include:
- The installed version and affected function.
- The time range, including the time zone.
- The error text, relevant logs and dashboard screenshots.
- Recent changes and the checks already completed.
An authorized SysAdmin or Support user can create a support bundle in the Portal. The Portal's Console menu is separate from Rancher.
- Open Portal → Console.
- Select System Accounts.
- Open the Support tab.
- Select Create.
- Wait until collection finishes.
- Select Download.
Bundles can contain credentials, personal data and system backups. Store them securely, and transfer them through the agreed secure support channel.