Back up and restore

An effective backup strategy considers the key components in your deployment and assess the impact of creating replica versions versus the cost of replacing those components if the system fails. All production deployments of i2 Analyze should have a backup and restore strategy in place.

The following components of an i2 Analyze deployment should be backed up to provide a comprehensive backup strategy:

  • The configuration

  • The Solr search index and ZooKeeper configuration (If you have an Information Store or Chart Store)

  • The database (If you have an Information Store or Chart Store)

When you create a backup strategy, consider the following items:

  • The amount of time, if any, that is acceptable for a system to be offline to create backups.

  • The amount of time that is acceptable for a system to be offline while recovery is in progress.

  • The amount of time between backups, for each component.

In a deployment of i2 Analyze that contains a database, the database is the source of truth about the data contained in a deployment.

This means that the Solr search index must be backed up before the database is and that the database must be restored before the Solr search index. If any data in the Information Store was modified after the Solr search index was backed up, the changes are updated in the index after the restoring.

The i2 Analyze deployment toolkit contains toolkit tasks that you can use to back up and restore each component of i2 Analyze. You can choose to use the toolkit tasks to back up all components, or you can use the toolkit tasks to back up a subset and use the native back up and restore procedure provided by other components. For example, if your organization has existing processes for backing up and restoring databases but not a Solr search index, you can use the existing process to back up the database in a deployment and the provided toolkit task to back up the Solr search index.