Need to manually upgrade Backup Exec from a previous version.
The recommended upgrade method is to allow the Backup Exec (BE) installer upgrade BE and its database during the installation. If that fails to occur or a saved database from a previous BE version needs to be added to a newer BE version, the BEMIG tool can be used. This tool follows the same upgrade version rules that the BE installer has. This is noted in the chart below.
Note: If the .mdf and .ldf files are from an older version of Backup Exec installed on a different server then please do not follow the procedure below if any of the following are true:
- Backup Exec is clustered.
- The Backup Exec Shared Storage Option (SSO) is installed.
- The Backup Exec Central Administration Server (CAS) is installed.
- The Backup Exec Server Free Option is installed.
- The computer where Backup Exec is installed and the computer where it will be installed are running two different versions of the Windows Operating System.
- If planning to move Backup Exec to a different drive/directory on the server.
1. Confirm BE is working in its current database first.
2. Stop the all Backup Exec services (including the SQL(BKUPEXEC) service).
3. Open the \Program Files\Symantec\Backup Exec Directory. Copy the Data folder and paste it in the same location. Rename the "Copy of Data" to "Data-'TodaysDate' or "Data-Version#-New"
4. Copy the saved Database from the previous BE version into the Backup Exec\Data folder(or the entire folder).
This will be bedb_dat.mdf and bedb_log.ldf files.
5. If the Catalogs have been saved also, rename the Catalogs to Catalogs.old, then copy/move the saved catalogs under Backup Exec.
6. Start the SQL service.
7. Set the registry keys for BEMIG.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
7a. Launch the Registry Editor (Start, Run, Regedt32).
Navigate to HKLM | Software | Symantec | Backup Exec for Windows | Backup Exec | "VersionNumber" | Install
7b. Modify the value of "Upgrade" to 1.
(Create as a Dword if it is not present)
7c. Modify the value of "Upgrade Version" to the version of the DB being imported from. See chart.
(Create as a String value if not present)
Please refer the following Table while setting the value for Upgrade version Key.
X indicates BE versions that can be upgraded from
|Upgrade Version||11||12.0||12.5||2010||2010 R2||2010 R3||2012||2014||15||16||20|
|10.0 revision 5484||10.0.5484.0||X|
|10.0 revision 5520||10.0.5520.0||X|
|11 revision 6235||11.0.6235.0||X||X||X||X||X|
|11 (11d) revision 7170||11.0.7170.0||X||X||X||X||X||
|2010 R3||13.0.5204.0||X||X||X (1)||X (1)|
(1) To upgrade to Backup Exec 15 or Backup Exec 16 from BE2010 R3, SP4 or later has to be installed
Do not upgrade to Backup Exec 15 or Backup Exec 16 from an earlier versions of Backup Exec that run on a 32-bit operating system because the installation of Backup Exec 15 or Backup Exec 16 on 32-bit operating systems is no longer supported.
8.Open a CMD command prompt to \Program Files\Symantec\Backup Exec
- Run BEMIG
1>C:\cd C:\program files\Symantec\backup exec
2>C:\Program files\Symantec\Backup Exec >bemig
- Wait for it to fully complete and return to a new prompt.
9. Start BE services and open the BE console.
Note 1 : If the services fail to start, you may need to do additional steps of:-
- Stop the SQL(BKUPEXEC) service .
- Copy the BEDB database files from the Data folder to the desktop .
- Start the SQL(BKUPEXEC) service .
- Run BEutility Copy Database to import the desktop BEDB files. This will correct any Environmental changes effecting the database.
- Copy Database Document - https://www.veritas.com/docs/000032463
Note 2 : Job Logs (for jobs run prior to the migration) are not maintained inside the Backup Exec Database. If older jobs logs need to be accessible after the migration, then they have to be copied separately, however if Backup Exec is installed in a different path on the new server then you will not be able to open the copied job logs from within the Backup Exec Console itself (and will have to directly open the XML files to review them). Job Histories (which are kept inside the database) should still be accessible.
Note 3 : Due to how volumes are given new identifiers on new servers and how plug-n-play on the operating system will detect storage devices such as tape libraries, any storage devices used as targets for the backups will be seen as new devices after the migration. This does mean you may have to adjust the storage configuration within Backup Exec and also reconfigure the job definitions so that the jobs use the newly configured devices.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):