This chapter describes an overview of the DIVArchive databases and the DIVArchive Backup Service, and includes the following information:
The DIVArchive Database and Backup Service components are installed as an integral part of the standard DIVArchive system installation. The components are typically installed on the same server as the DIVArchive Manager. The database is backed up using the RMAN components that are distributed as part of the Oracle Database Server package. The DIVArchive Backup Service manages and monitors the entire backup process. You can configure scheduled backups in the Backup Service's configuration file.
DIVArchive uses a Metadata Database to support complex object workflows. The DIVArchive Backup Service ensures reliability and monitoring of both the Oracle Database backups and Metadata Database backups.
DIVArchive 7.6.2 supports minimum Oracle Database Server 11.2.0.4.
Caution:
See the Oracle DIVArchive Supported Environments Guide in the Oracle DIVArchive Core documentation library to confirm disk partitioning and recommended block sizes before proceeding.By default, objects archived with more than 1,000 files are considered Complex Objects. Complex objects have Metadata stored in both the Oracle Database and Metadata Database. You can configure the threshold on the number of files before an object is considered complex in the Manager service configuration file. You can only store complex objects in AXF format within the DIVArchive system. You must use the DIVArchive Backup Service to back up the Oracle Database and Metadata Database when complex object workflows are used.
Caution:
When using complex objects, you are strictly required to use the DIVArchive Backup Service. The DIVArchive Backup Service is the only component backing up the Metadata Database and removing outdated Metadata files. When a Delete request for a complex object is sent and processed, the data is removed from the Oracle Database, but the Metadata Database file is not deleted. It is removed by the Backup Service after the configured clean up period (defined by the Recovery Period parameter) has been reached.The DIVArchive Backup Service is the component responsible for backing up the DIVArchive system database. The DIVArchive Backup Service uses the Oracle Secure Backup Scripts to perform Oracle Database backups. The Backup Service has a scheduler function enabling customizable backup schedules. The DIVArchive Backup Service has features to configure separate backup intervals for the Oracle Database and Metadata Database.
If a database or system failure (or both) occurs, where restoring from a system backup is necessary, restoration of a stored backup is done manually and should only be performed by Oracle Support personnel.
Oracle Database backups and Metadata Database backups are incrementally replicated to one or more remote back up systems by the DIVArchive Backup Service. depending on your configuration.
The Backup Service files are located in the %DIVA_HOME%\Program\conf\db_backup.conf, and the %DIVA_HOME%\Program\DBBackup folders.
The Backup Service monitors and sends backup status messages to the DIVArchive Manager. The Manager relays any errors and warning messages received from the service to all connected Control GUIs that are listening for messages from the Manager. The Manager records all events to the Events Log. The Control GUI displays the messages in a dialog box. If no Control GUIs are connected at the time of the error or warning, no error dialog boxes are displayed.
Before DIVArchive 7.0, you were required to install the Oracle Secure Backup Scripts separately from DIVArchive System installation. Starting with DIVArchive 7.0 no separate installation of Oracle Secure Backup Scripts are required. All Oracle Secure Backup Scripts are now installed during the standard DIVArchive installation and are located in the %DIVA_HOME%\Program\DBBackup\rman\bin folder.
The DIVArchive Backup Service uses Oracle's RMAN Database Backup Utility to generate Oracle Database backups. Full and incremental back up files are generated in the DB_BACKUP_LOCATION as defined in the configuration file.
By default, the DIVArchive Backup Service generates a full database backup every 24 hours, and an incremental backup every 15 minutes. The backup files are compressed with 7zip tool with the .gz extension. See Chapter 3 for a list of prerequisites.
The Backup Service incrementally replicates all the backup files to all configured DB_BACKUP_REMOTE_DESTINATIONS as set in the configuration file. All of the remote backup destinations must be RSYNC modules. See Chapter 3 for information on configuring an RSYNC module.
Oracle recommends having the same backup location on all main and remote backup destination systems. For example, if the DB_BACKUP_LOCATION is set to H:\oraback\, on the main system, you must have the Backup Service copy the backups to the same location on all remote backup destination systems. Therefore, you must configure the RSYNC module to H:\oraback\ on all remote backup destination systems. If the paths are different, the correct Oracle Secure Backup paths must be mentioned and updated in the Oracle RMAN Backup Tool during failover. See Chapter 4 for more details.
The Metadata Database is a binary file in the file system. To support the Recovery Window for the Metadata Database, the DIVArchive Backup Service uses the following techniques:
Whenever a new complex object is archived, the Manager creates complex object Metadata files in the Metadata Database Path you configured in the Configuration Utility.
By default, the DIVArchive Backup Service backs up Metadata files inside the Metadata Database every 15 minutes. The Metadata file is transferred to all backup systems shortly after creation so that file alterations do not influence the backup copies.
Note:
If there is a failure backing up to one of the configured Backup Systems, the Backup Service will continue to retry the failed backup until all backups to all configured Backup Systems are successful. Metadata Files are not marked as being successfully backed up until the backup to all configured Backup Systems is successful.During every Metadata Database backup, the Backup Service searches for any complex object Metadata files that are not backed up, and replicates them to all of the FBM_BACKUP_REMOTE_DESTINATIONS you configured in the configuration file. All of the remote backup destinations must be RSYNC modules. See Chapter 3 for information on configuring a RSYNC module.
Oracle recommends having the same Metadata Database Location on all main and remote backup destination systems. For example, if the Metadata Database Location is set to H:\metaback\, on the main system, you must have the Backup Service copy the Metadata Database backups to the same location on all remote backup destination systems. Therefore, you must configure the RSYNC module to H:\metaback\ on all remote backup destination systems. If the paths are different, you must update the Metadata Database Location in the Oracle Database after an Oracle Database restore during failover. See Chapter 4 for more details on failovers.
The following are recommended practices for the DIVArchive Backup Service:
The Backup Service must be installed on the same server as the DIVArchive Manager and Oracle Database.
At least two Backup Systems are always required to store backups. Oracle DIVArchive Actor computers can serve dual purposes and be used as both backup computers and Actor computers.
Oracle Incremental backups should be performed every 15 minutes.
Metadata Database backups should be performed every 15 minutes.
The Backup Recovery Window should be set to value greater than, or equal to, 10 days.
The Backup Clean-up function should be performed every 24 hours.
Oracle Full Backups should be performed every 24 hours.
If required, restoration of a system backup must only be performed by Oracle Support.
Oracle Database data files, Oracle Database backups, and the Metadata Database must be stored on RAID disk array.
You must allocate equal backup disk space on the main and all remote backup systems.