Why is a disaster recovery checklist necessary?

Even on a stable system, the following risks always exist:

• Failed upgrades

• Corrupt virtual machines

• Hardware crashes

• Human error

Preparing for these scenarios now will save significant time and stress later.

Recovery essentials:

VM Snapshot

• Best to set up a daily or weekly snapshot schedule.

• Always take an extra snapshot before any major configuration change or upgrade.

• Snapshot includes full system state (OS, TrendMiner, configurations, etc.)

• Easiest way to recover.

Remote Full Backup (Documentation full back-up)

• Best to set up a daily or weekly remote back-up schedule.

• Stored on cloud or local S3 storage.

• Includes database, index data, and basic system configuration.

• Also easy to recover from disaster.

Local Database Backup (Documentation database back-up)

• Always take this before a major configuration change or upgrade.

• Download outside of the VM.

• Does not include index data, system configuration, PMML models, etc.

• Mainly useful for troubleshooting and data comparison, but not suitable for full disaster recovery.

Configuration Notes

• Document all configured settings in Confighub and Edge manager.

• Store in a secure shared location.

When all of the above recovery essentials are in place you can rest assured that if anything goes wrong, you will lose minimal time in getting TrendMiner up and running again.