How to change the Backup Exec Database (BEDB) location using BEUTILITY.

Article:TECH37752  |  Created: 2005-01-12  |  Updated: 2012-12-19  |  Article URL http://www.symantec.com/docs/TECH37752
Article Type
Technical Solution

Product(s)

Issue



How to change the Backup Exec Database (BEDB) location using BEUTILITY.


Solution



The New Backup Exec Database Location feature is introduced with Backup Exec 10.x and above.  

The New Backup Exec Database Location enables the Microsoft SQL Server instance that the Backup Exec Database is using to be relocated. The new location can be on another computer running Microsoft SQL Server, or on the same computer running a different instance of SQL Server.


Note: SQL Server Services will be stopped and restarted during this process. Any negative impact on a production environment should be considered before scheduling this move.


Backup Exec database: (BEDB)

Backup Exec software can install the Microsoft SQL server 2000 Desktop Engine (MSDE 2000) or SQL Express on the local computer to create an instance on which to store the Backup Exec database, or an existing SQL server 2000 or SQL 2005 instance on the network.


By default, Backup Exec selects the first option, which installs the light weight MSDE 2000 or SQL Express instance on the local computer to store the Backup Exec database.



When to move the database:

1. User can move the database if the local MSDE or SQL Express services are stopping intermittently during backup.

2. User can move the database if the setup environment demands a network MSDE 2000 or SQL Express instance/Microsoft SQL server instance to store the Backup Exec database.

3. User can move the database to an existing SQL server to overcome 2 GB storage capacity limitation provided by MSDE or SQL Express engine.



Caution: Backup Exec database is the most critical part of the Backup Exec application, and therefore to avoid any data loss during the change of the database location, make sure to have a backup of the Backup Exec database which is the BEDB.BAK file automatically created by Backup Exec during regular maintenance at 4:00am.

Location for BEDB.BAK file: \Program files\Symantec\Backup Exec\Data  



Steps:

1. Open the BEUTILITY console
Location: X:\Program Files\Symantec\Backup Exec 
Where X:\ is the Drive on which Backup Exec is installed

2. Right-click on All media servers and select the new media server


3. Browse and select the respective media server and click OK


Note:Check the server status on the right hand side pane; the server should be up and running.


4. Right-click the media server and select New Backup Exec database location

 

5. In the Change Backup Exec database location window, select the Destination SQL server instance where to place the Backup Exec database, from the drop-down menu

 


Note: The name of the SQL server instance can be typed in manually, if it is not shown in the drop-down list.


6. Once the SQL server instance name has been selected, click OK


7. The change of BEDB location is in progress


 


8. BEDB is getting detached and re-attached to the new SQL server instance

 


9. Backup Exec database location has been changed successfully

 

To verify:

1. Go to the services.msc applet in the Control Panel and open the previous Backup Exec database SQL server (MSDE) or SQL Express instance.
For example, SERVER\BKUPEXEC

 


The old MSDE or SQL Express instance is no longer showing any dependencies for Backup Exec services:
SERVER\BKUPEXEC


2. Now, open the new Backup Exec database SQL server (MSDE) instance:
SERVER\BKUPEXECNEW

Here, the Backup Exec services are shown under dependent services.

 

The Backup Exec database location has been changed successfully.


Moving BEDB from MSDE or SQL Express to SQL server:

The same procedure is also applicable for moving the Backup Exec database (BEDB) from the default MSDE 2000 or SQL Express instance to an existing SQL server instance.


1. Provide the "SQL SERVER" instance name (default or named instance) as shown below

Note: Do not create the BEDB database on the SQL server before starting this process. This will be created automatically by Backup Exec.


 


2. BEDB migration is in process

 


3. BEDB is getting "detached" from the MSDE instance and getting "attached" to the SQL Server instance

 


4. BEDB migration has been completed successfully

 


5. The new BEDB is now part of the SQL server instance

 


6. To confirm the successful migration, check the services.msc applet. BEDB no longer requires MSDE services or SQL Express.

 


7. This can also be confirmed by checking the MSSQL Server properties

 



 



Legacy ID



275658


Article URL http://www.symantec.com/docs/TECH37752


Terms of use for this information are found in Legal Notices