<

Moving the Backup Exec 2012 Database to a New Server with a New Name

Posted on
7,740 Points
1,440 Views
3 Endorsements
Last Modified:
Experience Level: Beginner
6:49
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility.

Video Steps

1. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. Then, update the existing server to these latest versions to ensure they are on the same versions. The licenses will have to be moved, but this is a separate process.

2. Stop all services on both servers. This may take several minutes.

3. Locate the BEUtility. Typically, located in <drive letter>:\Program Files\Symantec\Backup Exec\”. Once located, double-click to launch it.

4. Highlight All Backup Exec Servers, then right-click and select New Backup Exec Server

5. Enter the name of the new Backup Exec Server. It may take several minutes for the server to appear.

6. Right-click the new server and select Copy Database

7. Browse the to the location of the database bedb_dat.mdf. This is typically located <drive letter>:\Program Files\Symantec\Backup Exec\Data.

8. Next, browse the to the location of the log file bedb_log.ldf. This is typically located <drive letter>:\Program Files\Symantec\Backup Exec\Data.

9. Once these two files have been located, click OK, then answer Yes to acknowledge the existing database will be overwritten.

10. The utility will then copy the files and restart the services on the new server. Once completed, the message will indicate the process was successful.

11. If the environment is running under a domain services account, the application will launch successfully. However, if this is a workgroup environment, the service account needs to be changed to the local server. To do this, launch the BEUtility on the new server.

12. In the utility, select either Change Database Service Account or Change Database Access and enter the credentials of the new server

13. Launch Backup Exec 2012 to verify the launch is successful. There will still need to be some configuration on the new server such as storage to address the specifics of the new server.

3
Comment
0 Comments

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

Join & Write a Comment

Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month