Recover database options
Recover Database lets you recover a database that has been lost or corrupted.
Related information
Table: Recover Database options
| Item | Description |
|---|---|
| Backup Exec | Displays the name of the Backup Exec server on which you want to recover the database. |
| Database instance | Indicates the name of the Backup Exec Database that you want to recover. You can perform this operation on only one database at a time. |
| Use best recovery method for current configuration | Attempts to fix and recover the existing database. |
| You can select this option to attempt to fix and recover the existing database. | |
| However, if the database cannot be fixed, Backup Exec does the following: | |
| - Deletes the database and then creates a new one. | |
| - Deletes the database and then recovers it from a previous database dump. | |
| Note: Use this option only under the guidance of Technical Support. The database recovery operation may result in the loss of existing information if there are changes to the blocked items since the last BEDB backup. To ensure that you have the latest blocked items information, it is recommended to back up the BEDB using the dump database option before proceeding with the database recovery operation. Optionally, you can also back up the imported blocked items by running theExport-BEItemsBlockedBEMCLI command and then import the copy of the blocked items using theImport-BEItemsToBlockBEMCLI command, after the operation is complete. | |
| Drop existing database and reload from backup | Deletes the existing database and restores the backup. |
| This option works with the Backup Exec option Save contents of database to the Backup Exec data directory , which you can find in Database Maintenance . | |
| When you set this option, Backup Exec automatically dumps the database to the Backup Exec server's hard drive at a predetermined schedule that you define. When you run the Backup Exec Utility task Recover Database and you select this option, the existing database is deleted. The database is replaced with the copy of the database that was dumped to the Backup Exec data directory. | |
| Note: Use this option only under the guidance of Technical Support. The database recovery operation may result in the loss of existing information if there are changes to the blocked items since the last BEDB backup. To ensure that you have the latest blocked items information, it is recommended to back up the BEDB using the dump database option before proceeding with the database recovery operation. Optionally, you can also back up the imported blocked items by running theExport-BEItemsBlockedBEMCLI command and then import the copy of the items files using theImport-BEItemsToBlockBEMCLI command, after the operation is complete. | |
| See the Backup Exec Administrator's Guide . | |
| Drop existing database and reload from base | Deletes the existing database and replaces it with the base database called BEDB_Dat.bak. |
| After your initial installation of Backup Exec, a copy of the original, empty production Backup Exec Database is created, named BEDB_Dat.bak. The empty database copy resides in the directory where Backup Exec is installed. | |
| Note: This operation deletes the existing database and replaces it with the base database. Backup Exec logon accounts, jobs, media sets, disk storage folders, information about blocked items, encryption keys, and other settings will be discarded. You will have to create or configure all of these items again. Use theDump Databaseoption to back up the database to your hard drive before you use the optionDrop existing database and reload from base. For blocked items, run theExport-BEItemsBlockedBEMCLI command to back up any blocked items. You must import the blocked items using theImport-BEItemsToBlockBEMCLI command after the database recovery operation is complete. | |
| See Dumping a Backup Exec Database . | |
| If you roll back the Backup Exec Database and then experience problems restarting the Backup Exec services, a Backup Exec Database schema mismatch may have occurred. You should check the Windows Event Viewer for confirmation. If a schema mismatch occurs, you must re-apply all Backup Exec hotfixes and services packs that were installed on the original production database. This process should resolve the issue. | |
| Only use this option under the guidance of technical support. |