How to Copy the Backup Exec Database (BEDB) from an existing Backup Exec Server to a new Media Server with the same or different server name.
|Article:TECH49757|||||Created: 2006-01-25|||||Updated: 2013-05-31|||||Article URL http://www.symantec.com/docs/TECH49757|
How to Copy the Backup Exec Database (BEDB) from an existing Backup Exec Server to a new Media Server with the same or different server name
Copy Database copies on an existing Backup Exec Database from a computer using a specific name to another computer using the same or different name. For example, if the media server is replaced with a new one and the computer name is same, Copy Database copies the Backup Exec database to the new computer with all database data intact.
If Copy Database is used to copy the Backup Exec database to a computer with a different computer name, some database data will be lost.
Before starting the process, Stop the Backup Exec services on the old server, including the Sql server(BKUPEXEC) service. Copy the bedb_dat.mdf & bedb_log.ldf files to the new server.
1. Start BEUtility.exe.(From Backup Exec Installation folder /Program Files/Symantec/Backup Exec).
2. On the task pane, under Database Tasks, click Copy Database.(as Displayed in Figure 2)
Or, Right Click the Server Name and Click on Copy Database. (as Displayed in Figure 3)
3. Enter the name of an existing database file from which to copy, or click Browse to navigate to the location of the existing database. The database file uses the file name extension, .mdf (bedb_dat.mdf) (as Displayed in Figure 4)
4. Enter the name of an existing database log file from which to copy, or click Browse to navigate to the location of the existing database log file. The log file uses the file name extension .ldf (BEDB_log.ldf). (as Displayed in Figure 5)
5. Click OK, a prompt would appear on the screen which states that current Backup Exec Database would be overwritten (as Displayed in Figure 6). Click on Yes to Proceed.
6. After the operation completes successfully, click Close. (as Displayed in Figure 8)
Article URL http://www.symantec.com/docs/TECH49757