SOLR DISASTER RECOVERY

Disaster recovery for Apache Solr involves the process of restoring the Solr instance and its data in the event of a disaster such as hardware failure, software failure, natural disasters or human errors.

For businesses with aggressive RTO and RPO requirements, a duplicate infrastructure that mirrors your primary production environment in real-time may be needed. SearchStax offers a Hot Disaster Recovery option that augments your production deployment and provides the highest level of redundancy and resource capacity during a disaster. 

To achieve this level of redundancy, we create a “hot” standby or secondary deployment in a different region than your production deployment. This secondary deployment is a full replica of your primary production environment and is kept in sync with your production system at all times. That means that an interruption in service at the primary site for the production system can be met by a near instantaneous switchover to the standby site.

For businesses with aggressive RTO and RPO requirements, a duplicate infrastructure that mirrors your primary production environment in real-time may be needed. SearchStax offers a Hot Disaster Recovery option that augments your production deployment and provides the highest level of redundancy and resource capacity during a disaster. 

To achieve this level of redundancy, we create a “hot” standby or secondary deployment in a different region than your production deployment. This secondary deployment is a full replica of your primary production environment and is kept in sync with your production system at all times. That means that an interruption in service at the primary site for the production system can be met by a near instantaneous switchover to the standby site.

For some businesses, downtime is not a critical requirement. Under the Cold Disaster Recovery option, the restoration process starts after the disaster occurs. A new Solr cluster is created and the data and configurations are then restored from a backup file. 

The SearchStax Cold Disaster Recovery handles this process for you and uses backup files that are stored in different cloud regions and provides a higher level of recovery than backups stored in the same region. While everyone should maintain regular backups of their deployments, the Cold Disaster Recovery option takes this to the next level by storing the backups in a different cloud region from the primary system. If the production site goes down, we will start a deployment in the same region as the backup and restore it.

Recovery Time Objective, or RTO, is the amount of time that your Solr service can be unavailable in case of an emergency. This could be caused by a corrupt Solr Index or Solr replicas going into recovery mode. A cloud provider region could go down because of a natural disaster or a cyber attack.

In any of these situations, your business might have to face some downtime. RTO defines the maximum acceptable time for your application to recover when such an event occurs.

Recovery Point Objective, or RPO, defines the amount of data that your business can tolerate losing in case of an emergency. For example, if your business can tolerate losing four hours of history in order to get back on line quickly, then your RPO would be four hours.