The ability to restore a DSR database from a database backup file can aid in disaster recovery. Oracle recommends backing up the database on a regular basis, perhaps as part of routine daily operations.
After a backup has been created, the file can be transferred to an external server in a secure location.
The database backup process allows capturing and preserving vital collections of Configuration data. Data is safely collected from the database management system without impact to database users. The Configuration Data is data used to configure a system and the applications that run in the system.
A backup of data can be performed only from the Active Network OAM&P and can include all Configuration data.
The backup process collects all files required to perform the requested backup and stores them as a single file in the File Management Storage Area. The backup process operates asynchronously from the Status & Manage GUI screens, allowing the user to perform other operations and monitor progress.
Example of a backup file name: Backup.Appworks.teks5001401.Configuration.NOAMP.20090223_031500.MAN.tbz2
Although the backup process is designed to be used without interruption to provisioning service, it may be desirable to disable provisioning briefly in order to note exactly which data has and which data has not been provisioned to the network when the backup is taken. Provisioning can be enabled after the backup has started; it is not necessary to wait until the backup is finished to enable provisioning again.
Automatic backups are scheduled and are executed for Configuration data on Active Network OAM&P servers. By default, automatic backups for Configuration data are scheduled for 2:45 AM, local time.
Automatically generated backup archive files are stored in the File Management Storage Area. The File Management Storage Area is pruned as part of the automatic backup process to remove any automatic backup archive files that are older than 14 days.
The automatically generated backup archive files include an “AUTO” extension to distinguish them from manually generated backup archive files.
The ability to restore a DSR database from a database backup file can aid in disaster recovery. Oracle recommends backing up the database on a regular basis, perhaps as part of routine daily operations.
Database backup files can be used to restore Configuration data to servers in a network. The very nature of database restoration is destructive. Operators need to take great care to know exactly what data is being restored and how it differs from the existing data.
The Database restoration requires careful planning and execution and taking some sensible precautions. Contact your My Oracle Support (MOS) for assistance before attempting a database restore.
The security logs of both the controlled and the controlling server can be checked to determine how a restoration has progressed.