This chapter answers frequently asked questions concerning the content described in this book and includes the following information:
How do I failover to a Backup System when the Main Manager System has failed?
How do I recover when a complex object's Metadata file is corrupted in the Main Manager System?
How do I recover a complex object's Metadata file when it is corrupted in the Backup Manager System?
How do I recover when a complex object's Metadata file is manually deleted in Main Manager System?
How do I recover when the backup disk fails, or gets corrupted, on the Main Manager System?
How do I configure a full backup to start when the Backup Service starts?
How do I locate a complex object's Metadata inside the Metadata Database?
How does the Metadata Database maintain its recovery window when a complex object is deleted?
Can the DIVArchive Manager and Oracle Database be installed on separate servers?
Does the recovery window apply to both Oracle Secure Backups and Metadata Backups?
How do I estimate the size for the Metadata Database location?
Is the information stored in the Metadata Database irreplaceable or mission critical?
Why is this information not being stored in the existing Oracle Database?
What if a customer has, for example, 1,000,000 objects, each with 100,000 files?
Does the storage location of the live database affect performance or space, and is it critical?
Can the location of the Metadata Database backups be configured?
Check the DIVArchive Backup Service status using the dbbackup status
command from the command-line interface. See DIVArchive Backup Service Status Command for detailed information.
See Failure Scenarios and Recovery Procedures for the complete procedure.
The DIVArchive Backup Service backs up the Metadata Database file by file. After the file is backed up to the backup systems, any corruption to, or modifications of, the Metadata files are not propagated to the backup systems.
If a complex object Metadata file is corrupted, restore the Metadata file from one of the backup systems.
In the unlikely event of disk corruption due to hardware failure occurring before the Backup Service has backed up the Metadata files, the non-backed up Metadata files can only be restored from a tape or disk. The feature to restore Metadata files from tape or disk is not currently available in this DIVArchive release. Contact Oracle Support for assistance.
Oracle recommends always making backup copies to two separate backup systems to handle these scenarios. Restore the Metadata file from the Secondary Backup System or Main Manager System.
Manually deleted Metadata files are not propagated to any backup systems.
Execute the dbbackup.bat reconcile
command to identify which complex object is missing the Metadata file. Restore the Metadata file from one of the backup systems.
You can restore Metadata files from tape or disk. The feature to restore Metadata files from tape or disk is not currently available in this DIVArchive release. Contact Oracle Support for assistance.
Disk failures, or corruption, requires a failover to the Backup Manager. See Failure Scenarios and Recovery Procedures for the complete procedure.
The DIVArchive Backup Service automatically determines if a full backup is required when it starts. There is no configuration required.
Contact Oracle Support for assistance.
See Database Backup Recovery Window for detailed information.
You can turn off notifications by deselecting the check box for the Database Backup Notification parameter under the Manager Setting panel in Configuration Utility.
No, they must be installed on the same server because the DIVArchive Backup Service does not support Manager and Oracle installations on separate servers in this DIVArchive release.
Yes, the recovery window setting applies to both backups.
See Sizing the Metadata Database for detailed information.
You configure the location of the Metadata Database using the Complex Objects Metadata Location parameter in the Manager Setting panel in Configuration Utility.
All file details including file names, folder names, location, size, checksums, and so on.
Oracle always recommends having at least two backup copies of the Metadata Database. You use the DIVArchive Backup Service to back up the Metadata Database. In a worst case scenario, use the Oracle Archive eXchange Format Explorer to recover the object from tape if the Metadata Database file of a particular object is lost.
The amount of Metadata information is huge. Complex objects are supported up to 1,000,000 files. Currently, the Oracle Database in use does not have any scalability features to support complex object workflows.
See Sizing the Metadata Database for detailed information.
The Metadata Database is very scalable and can handle this amount with no issues.
You will not be able to process complex object requests if the database becomes inoperable. You can restore from one of the backup copies if the database becomes corrupt, or is missing.
In this case you will not be able to process any complex object requests. See Sizing the Metadata Database for detailed information.
Currently there are no tools that exist to check the database integrity. Contact Oracle Support if you need assistance.
Always use the DIVArchive Backup Manager Service to back up the Metadata Database.
See Failure Scenarios and Recovery Procedures for the complete procedure.
Yes, it is both performance and space critical. See Chapter 2 for installation and configuration procedures.
Yes, you can configure the backup location. See Chapter 4 for DIVArchive Backup Service installation and configuration procedures.