Backup Exec Utility

Last Published:
Product(s): Backup Exec (22.0)
  1. Backup Exec Utility
    1.  
      About Backup Exec Utility
    2.  
      Starting the Backup Exec Utility
    3. About Backup Exec Utility general tasks
      1. Adding Backup Exec servers
        1.  
          Select Backup Exec server options
      2.  
        Adding a new Agent for Windows computer
      3. Viewing server properties for the Agent for Windows computer
        1.  
          Server properties for the Agent for Windows computer
      4. Viewing system properties for the Agent for Windows computer
        1.  
          System properties for the Agent for Windows computer
      5. Creating a new Backup Exec server group
        1.  
          New Backup Exec server group options
      6.  
        Deleting a Backup Exec server from the Backup Exec Utility list of known Backup Exec servers
      7.  
        Deleting a computer on which the Agent for Windows is installed
      8. Deleting a Backup Exec server group
        1.  
          Delete Backup Exec Server Group
      9.  
        Running Backup Exec diagnostics
      10. Enabling debug logs
        1.  
          Enable debug log configuration options
      11. Setting the size of the debug logs
        1.  
          Set debug log size options
      12. Setting debug logging and the debug log sizes for Agent for Windows computers
        1.  
          Debug log options and debug log size options for Agent for Windows computers
      13. Setting the location for the job log and the catalogs
        1.  
          Job log and catalog location change options
      14. Viewing server properties for the Backup Exec server
        1.  
          Server properties for a Backup Exec server
      15. Viewing a list of licensed and installed options for a Backup Exec server
        1.  
          Licensed and installed Backup Exec options on a Backup Exec server
      16. Viewing system properties for a Backup Exec server
        1.  
          System properties for a Backup Exec server
      17.  
        Managing security certificates
    4. About Backup Exec Utility services tasks
      1.  
        Stopping Backup Exec services
      2.  
        Starting Backup Exec services
      3. Changing service accounts
        1.  
          Change service account options
      4. Editing Backup Exec server configurations
        1.  
          Edit configuration options
      5.  
        Moving an existing Backup Exec server
    5. About Backup Exec Utility CASO tasks
      1.  
        Enabling communications with the managed Backup Exec server
      2.  
        Disabling communication with the managed Backup Exec server
      3.  
        Moving a managed Backup Exec server
    6. About Backup Exec Utility database tasks
      1.  
        Checking the database consistency
      2.  
        Aging the database
      3.  
        Compacting a Backup Exec Database
      4.  
        Dumping a Backup Exec Database
      5.  
        Rebuilding Backup Exec Database indices
      6.  
        Repairing a Backup Exec Database
      7. Recovering a Backup Exec Database
        1.  
          Recover database options
      8. Changing database access
        1.  
          Change Database Access options
      9.  
        Changing the Backup Exec database location
      10. Copying a database
        1.  
          Copy database options
    7. About Backup Exec server group tasks
      1.  
        Adding a Backup Exec server to a Backup Exec server group
      2.  
        Removing a Backup Exec server from a Backup Exec server group
      3.  
        Setting a central administration server for the Backup Exec server group
    8. About configuring columns
      1.  
        Hiding a column
      2.  
        Displaying a column
      3. Rearranging columns
        1.  
          Column settings options
      4. Sorting columns
        1.  
          Sorting column information
  2.  
    Index

Recover database options

Recover Database lets you recover a database that has been lost or corrupted.

See Recovering a Backup Exec Database.

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 the Export-BEItemsBlocked BEMCLI command and then import the copy of the blocked items using the Import-BEItemsToBlock BEMCLI 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 the Export-BEItemsBlocked BEMCLI command and then import the copy of the items files using the Import-BEItemsToBlock BEMCLI 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 the Dump Database option to back up the database to your hard drive before you use the option Drop existing database and reload from base. For blocked items, run the Export-BEItemsBlocked BEMCLI command to back up any blocked items. You must import the blocked items using the Import-BEItemsToBlock BEMCLI 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.