A single, scalable database platform for both feature and application data greatly simplifies backup and recovery procedures, as all transactional states for the planning and data capture process (including comprehensive workflow state in the BPEL dehydration store) are held in a single self-consistent location.
It is advised that in a recovery situation, a full database recovery is performed to ensure that all components of the 1Spatial Management Suite are in a consistent state.
Note: Partial database recovery is not supported.
The dynamic data for the 1Spatial Management Suite is entirely stored in the database, therefore there are no other data backup requirements. For information about backing up Oracle databases, refer to the Oracle Documentation Library.
Backup and restore should be performed at a database-wide level. This guarantees both consistency between the feature database and the component metadata states, and is also Oracle's recommended safe way for backing up and restoring workspaces (1Spatial Management Suite uses Oracle's Workspace Manager technology).
All persistent data is stored in the database; backup and recovery is restricted purely to managing the feature and component repository database.
