Backups and Data Retention

Database Backups

Database backups for both Production and Non-Production environments are performed 7 days a week. Full backups are performed every Saturday. Incremental backups are performed Sunday through Friday.
All databases are backed up online using vendor native tools (DB2, Oracle)
Database backups are written to database server filesystems (locally)

Filesystem Backups

Filesystem backups for both Production and Non-Production environments are performed 7 days a week. Production filesystem backups are taken every 3 hours (8x day). Non-production filesystem backups are taken every 12 hours (2x day)
Filesystem backups (including database backup files) are copied to a secondary IBM Cloud data center in the same country or geography as the primary data center
Production backups are kept for thirty one (31) days. Non-production backups are kept for seven (7) days.
All backups are AES-256 encrypted and can only be restored to servers with the appropriate encryption key

Restores

IBM can perform a restoration of client’s content upon client request via case ticket. Restores can be performed within 1-3 business days, depending on urgency
Databases can be restored to any point in time (limitation for production is 31 days prior, limitation for non-prod is 7 days prior).
Database restores can also be performed by customers using the Self Service Portal (if the database backup was taken using the portal). These can only be restored to the point in time the source backup was taken.

Logs

All database transaction logs and application server (JVM) logs are saved to each server’s local filesystem
Logs are stored in standard default locations. There is no set retention period for logs. Logs are rolled based on size. Size varies depending logging level and amount of activity. Customers can obtain read-only access to Application Server logs via SFTP. Database transaction logs are not accessible to customers.

Customer Data at Contract Termination

Before expiration or termination of the Cloud Service, client can use any of the provided reporting or export features of the Cloud Service to extract data.
Customers can export databases at any time using the Self Service Portal
Exports can also be requested via case ticket
Upon receiving a support request from client within 30 days of the Cloud Service expiration or termination date, IBM will return to client an electronic copy of client’s content in the native format (DB2 or Oracle export; zip file of Application Server customizations and attached documents).

Click here for specific information on Maximo SaaS Flex Disaster Recovery

Click here for specific information on TRIRIGA Disaster Recovery:
TRIRIGA SaaS Standard Disaster Recovery
TRIRIGA SaaS Flex Disaster Recovery

Data Archiving (IBM Maximo and TRIRIGA SaaS)

IBM Maximo and TRIRIGA SaaS offerings do not offer a data archiving solution. Customers typically desire archiving for two main reasons:

They wished to minimize the investment in high-end hardware for their production servers; removing old or stale data from their production database decreases the database size and processing power for larger amounts of data, helping minimize their investment
There are concerns a growing production database will affect performance of the application.

Neither of these are an issue within the IBM Cloud environment. The hardware needed is included in the subscription and clients will consume what is needed as part of this cost. There is no increase in subscription cost based on database size. The modern versions of DB2 and Oracle are very efficient when it comes to performance, and Maximo and TRIRIGA databases are relatively small by modern storage standards. The queries within the Maximo and TRIRIGA application are tuned to handle large databases and there has not been a real need to manage the size of the database to ensure performance is maintained.

If a client has a requirement where archiving is a potential solution, this would need to be discussed with the IBM SRE team to determine if there are other options to meet that requirement within the Cloud offering.