Avoid Losing Valuable Sales and Customer Data by Using Backup and Recovery in Depth

  • by Judith M. Myerson , Systems Engineer and Architect/Owner
  • April 15, 2010
Find out why multiple, in-depth layers of recovery parameters are more effective than a single layer when backing up and recovering SAP CRM data, business processes, and event logs.
Key Concept
Backup and recovery in depth refers to the strategy of creating multiple layers of recovery parameters (rather than a single layer) to better back up and recover the SAP CRM infrastructure in case of a major system or data issue. Parameters such as a recovery point objective, recovery time objective, and maximum tolerable downtime are all part of an in-depth backup and recovery strategy for SAP CRM. The benefit of this strategy is that if a layer in layered backup fails, another one can take over — or the system returns to a previous layer and updates it before continuing to other aspects of the layered backup.

An organization often needs more than the standard practices for backing up and restoring SAP CRM databases to comply with data retention policies for industries such as retail, health care, energy services, manufacturing, and media. A standard backup and recovery strategy usually includes backup sources, destinations, frequency, and scheduling, as well as security policies. It does not include multiple layers of recovery parameters to measure the effectiveness of backing up and recovering data in each layer. Some examples of the benefits of a multi-layer backup and recovery strategy include cost savings, risk mitigation process improvement, offsite storage, and the security of continuous backup.

To achieve this level of security, you need the backup and recovery in depth model to include layered recovery parameters such as length of recovery time and maximum downtime after a disaster event. This allows you to more quickly restore SAP CRM data, business processes, email messages, and event logs. This strategy of layered backup and recovery helps maintain consistency between the SAP CRM data that is being backed up and the linked SAP ERP and SAP NetWeaver BW systems while complying with data retention requirements. The backed-up SAP CRM data may include data from smartphones for the on-the-go SAP CRM users, including mobile developers, sales representatives, field service employees, managers, and hospital physicians. (For an overview of the terms I use, refer to the “Glossary of Terms” sidebar at the end of the article.)

Judith M. Myerson

Judith M. Myerson is a systems architect and engineer and an SAP consultant. She is the author of the Enterprise System Integration, Second Edition, handbook, RFID in the Supply Chain: A Guide to Selection and Implementation, and several articles on enterprise-wide systems, database technologies, application development, SAP, RFID technologies, project management, risk management, and GRC.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.