The next aspect of the configuration is the determination of the backup strategy to support the requirements as well. With required up time, there is no maintenance window to perform a typical offline backup. Within the solution, the products all support different type of offline and online backups. To effectively make the decision, each product’s service must be determined as a criticality factor to know the risk for the data within the service. 

Here is the breakout by service and its own criticality: 

GLYPH<SM590000> Case Manager and Content - Critical service. This is because this is the main service for the entire solution. 

GLYPH<SM590000> Content Manager OnDemand - Mostly Critical. The source of the information is within the main hospital system. Although a significant inconvenience, the information is available in some form if this system is unavailable. 

GLYPH<SM590000> Capture Process (Datacap, Content Collector for Email and Content Classification) - Critical service. This brings in information about the given patient and identifies it. This service also has a limited exposure of data, because all information is processed through these products in moments, and no data is stored within them. 

GLYPH<SM590000> Content Manager OnDemand - Nice to have service. This functionality is not mission critical, despite having a great benefit. A patient can be seen and worked on without this service. 

The main service to backup is the case and content system. Though the content service supports online backups, the current release of this case does not. 

Therefore, this does not enable the uptime requirements. There are options to address such a constraint. 

For this solution, the DR site is used to perform the backup. There is a risk in this approach, because the sync link between the two solutions would need to be stopped, the snapshot performed, and then the link re-established. During this time there is a business risk of lost data while the link is not in operation. 

The time frame is small, because the ability and power of data snapshots can be performed in seconds. Therefore although there is a risk, it is limited. In this specific use case, this is an acceptable risk. 

Note:  This approach enables the availability of Case and Content to be continuously available. 

Content Manager OnDemand is a mostly critical service, because the product itself only supports an Active/Passive availability mode. This configuration counts against the overall availability of the solution. Because the data itself is in other systems, the limitation is acceptable. 

