Operational maintenance
Keep the platform's access, configuration, capacity, backups and monitoring ready for database operations.
Routine review
| Area | Review |
|---|---|
| Licence | Validity, granted technologies and request/host capacity |
| Broker accounts | Named users, active state, roles and assigned organizations |
| Service credentials | Ownership, scope, validity and planned rotation |
| Server pool | Accurate hostnames and active project associations |
| Versions | Approved package availability and update planning |
| Activity | Failed, pending or repeated operations |
| Monitor | Observation freshness, alert rules and notification delivery |
| Storage | Platform records, installation files, logs and monitoring retention |
Make account, inventory and configuration changes through the appropriate Setup pages. Use the engine's lifecycle forms for database changes.
Backup responsibilities
Plan Repository backups, Monitor data/configuration protection and managed-database backups separately. An installation package does not contain the customer's current operational records or database contents.
Assign owners, retention and restoration checks. Keep credential backups through the approved secret-management process.
Maintenance changes
Record the scope, affected applications, maintenance time, previous settings and recovery plan. Complete one project operation at a time, follow Activity and verify the result.
Preserve failure evidence before log rotation or cleanup. Use support engagement when the required recovery is unclear.