All runtime data is stored in the data tier. Therefore, you can backup the entire system relatively easily, and recover data as required. The recovery and post-recovery process you employ varies depending on the failure scenario you are addressing. Always diagnose your failure before following a particular course of action.
Exclusions: This documentation does not address system restoration or disaster recovery. For disaster recovery, you may need to work with third-party vendors who provide the necessary solutions. Furthermore, complete restoration (that is, the return of the system to its original runtime state before the failure occurred) cannot be guaranteed in any mobile environment.
| Stage | Activity | Frequency |
|---|---|---|
| Planning | Identify the artifacts to be backed up and set the backup schedule. | Infrequent. Typically, before installing, or as business requirements or policies dictate. |
| Test responses to all failures, including media failure, user error, application error, and component failure. | Occasional, as the deployment environment or scale changes. | |
| Implementation | Configure backup in installed components, primarily data tier components. | One-time, or as change in frequency requires. |
| Secure backup artifacts. | One-time, or as backup environment or number of artifacts change. | |
| Maintenance | Monitor the backup environment. | Routine. |
| Test the backup to ensure it is viable. | Routine. | |
| Evaluation | Assess the issue and determine if recovery is required. | As needed. |
| Recovery | Recover from data loss or failure. | As needed. |
| Postrecovery | End user follow up activities to return it to its production-ready state. | As needed |
| Troubleshooting | Resolve any issues relating to the backup and recovery processes. | As needed. |