How to manually migrate the job definitions, hardware profiles, and media rotation information from Backup Exec 8.x - 10.x.

In Backup Exec (tm) 8.6 (as well as prior versions of Backup Exec), job definitions, hardware profiles, and media rotation data are stored in the following files:

Job Definitions:

Backup Exec\NT\Data\Jobs7.dat

Backup Exec\NT\Data\Scripts.uni

Backup Exec\NT\Data\Bewinui.uni

Backup Exec\NT\Data\Bewinnt7.sch

Backup Exec\NT\Data\Jobhist.dat

Hardware and Media Rotation information:

Backup Exec\NT\PVL.MDB

Notes:

1. Explanation of each of these files is given in the Related Documents section of this TechNote.

2. Catalogs are not part of these files and hence a different method is required in order to migrate catalogs. See Related Documents for assistance in migration of catalogs.

In Backup Exec 9.x and Backup Exec 10.x for Windows Servers, the same data is contained in the SQL 2000 database files.

Database and related files:

Backup Exec\NT\Data\BEDB_dat.mdf

Backup Exec\NT\Data\BEDB_log.ldf

Backup Exec\NT\Data\BEDB.bak

Backup Exec\NT\Data\BEDB_dat.bak

Note: The BEDB.bak and BEDB_dat.bak are not active database files. The BEDB.bak file contains the most recent internal backup of the active database while the BEDB_dat.bak is a 'blank' database in case the active database becomes corrupted and is unable to be repaired. Please see the Related Documents section below for further information on these files.

During an upgrade from Backup Exec 8.x, the data content is migrated from the individual data files to the SQL database of 9.x or 10.x. If it is necessary to migrate this content after the upgrade, use the following steps to migrate the data into a blank database using the bemig.exe utility. These steps may also be used to migrate 8.x data from a different media server with a different computer name. (This is limited to job definitions and media set information. Hardware profile information will need to be created.)

Notes:

1. If the Backup Exec 8.x installation was upgraded from a Backup Exec 7.x installation, install Hotfix 14 prior to the manual upgrade process (see Related Documents.)

2. If it has been determined that there was a failure on an initial migration attempt during the upgrade installation, then the 8.x files were corrupted prior to the upgrade and will not be able to be migrated manually (see Figure 1).

Figure 1

3. At this time, the merging of old data and current data in the same database is not supported. Migration will not be successful if the current database is not blank.

To perform the migration, perform the following steps:

1. Replacing the current database with a blank copy

Warning: This will remove all current job definitions and configurations from Backup Exec

a. Run the following: :\Program Files\Veritas\Backup Exec\NT\beutility.exe

b. If the media server is not already listed under All Media Servers, add the media server name to BEUtility:

i. Right-click All Media Servers

ii. Select New Media Server...

iii. Specify the local media server name and click Get Server Information

c. Right-click the media server: select from the Recover Database menu

d. At the Recover Database window, select Drop existing database and reload from base

Note: If the migration does not succeed, open Backup Exec for Windows Servers, step through the First Time Startup Wizard and reattempt the migration from step 2 onward.


2. Preparing the environment for the migration:

a. Stop the current Backup Exec Services (including MSSQL$BKUPEXEC)

b. Create a notepad document

c. Copy and paste the following content into the document:

-------------------------------------------------------------------------------------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Adamm]

"ODBC Driver Connection String (Migration)"="DRIVER=Microsoft Access Driver (*.mdb);DBQ=C:\\Program Files\\VERITAS\\Backup Exec\\NT\\pvl.mdb"

-------------------------------------------------------------------------------------------------------------------

Note: The path will refer to the location of the PVL.MDB file which will be migrated. Alter the path as necessary to direct it to the proper location.

d. Save the document as migration.reg

e. Double-click migration.reg and click OK to apply the change to the registry

f. Open the registry editor (regedt32.exe)

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.

Browse to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Server\HasStartedSuccessfully

Change the value to 0.

g. Close the Registry Editor

3. Preparing the old data and performing the migration:

a. Confirm the job definition files of 8.x are located in the current Backup Exec 9.x or Backup exec 10.x Data folder

b. Confirm PVL.MDB from 8.x is in the current Backup Exec\NT folder

(If only migrating the job definitions from 8.x, or if there are difficulties communicating with hardware or media sets after a migration attempt, ignore step "b")

c. Confirm BEMIG.EXE is present in the Backup Exec\NT folder

d. Start the BACKUPEXEC and MSSQL$BKUPEXEC services

Note:

If the MSSQL$BKUPEXEC service is not started , on executing the BEMIG.EXE command the migration would be unsuccessful and the output would generate the status as :

Upgrade state set to 536870915

e. Open the command prompt

f. Browse to the location of bemig.exe (default location: :\Program Files\Veritas\Backup Exec\NT)

g. Type bemig.exe and press

Given below is an example of a successful migration output of bemig.exe.

C:\Program Files\VERITAS\Backup Exec\NT>bemig.exe
Executing migration of data from 8.x
SetRange: from=0 to=300
Status Message: Querying version data

Starting copy...

1 rows copied.
Network packet size (bytes): 4096
Clock Time (ms.): total 1
Status Message: ADAMM upgrade started
Status Message: Backup Exec Device & Media Service Database, version 9.000001 is
up to date. No changes are required.
Status Message: ADAMM upgrade ended
Status Message: ADAMM migration started
Status Message: Querying source database
Status Message: Querying version data
Status Message: Querying device data
Status Message: Querying machine data
Status Message: Querying changer data
Status Message: Querying drive data
Status Message: Querying slot data
Status Message: Querying partition data
Status Message: Querying barcode rule data
Status Message: Querying backup to disk data
Status Message: Querying machine device data
Status Message: Querying device pool data
Status Message: Querying device pool device data
Status Message: Querying vault data
Status Message: Querying client data
Status Message: Querying media set data
Status Message: Querying media label data
Status Message: Querying destination database
Status Message: Querying device data
Status Message: Querying machine data
Status Message: Querying changer data
Status Message: Querying drive data
Status Message: Querying slot data
Status Message: Querying partition data
Status Message: Querying barcode rule data
Status Message: Querying backup to disk data
Status Message: Querying machine device data
Status Message: Querying device pool data
Status Message: Querying device pool device data
Status Message: Querying vault data
Status Message: Querying client data
Status Message: Querying media set data
Status Message: Querying media label data
Status Message: Migrating source database
Status Message: Migrating device data
Status Message: Migrating machine data
Status Message: Migrating changer data
Status Message: Migrating drive data
Status Message: Migrating slot data
Status Message: Migrating partition data
Status Message: Migrating barcode rule data
Status Message: Migrating backup to disk data
Status Message: Migrating machine device data
Status Message: Migrating device pool data
Status Message: Migrating device pool device data
Status Message: Migrating vault data
Status Message: Migrating client data
Status Message: Migrating registry data
Status Message: Migrating media set data
Status Message: Migrating media label data
Status Message: Querying media data
Status Message: Migrating media data
Status Message: Migrating media data
Status Message: ADAMM migration ended
Status Message: Reading Job Records
Status Message: Reading Schedule Records
Status Message: Reading Selection List Records
Status Message: Converting Job Records
Status Message: Converting Schedule Records
Status Message: Inserting Schedule Records
Status Message: Converting Selection List Records
Status Message: Converting Selection List Records 1
Status Message: Converting Selection List Records 2
Status Message: Converting Selection List Records 3
Status Message: Converting Selection List Records 4
Status Message: Converting Selection List Records 5
Status Message: Converting Selection List Records 6
Status Message: Converting Selection List Records 7
Status Message: Converting Selection List Records 8
Status Message: Inserting Selection List Records
Status Message: Inserting Job Records
Status Message: Reading Job History Data.
Status Message: Converting job history data.
Status Message: Migration of Job Data Complete
Status Message: Job Migration Success
Summary Entry: Type=UPGSUMINFO
title=Job Migration
message=Job Migration Success
Summary Entry: Type=UPGSUMWARN
title=Job Migration
message=

Some migrated jobs may have been placed on hold and should be reviewed. These jobs may have had schedule or selection list changes.

C:\Program Files\VERITAS\Backup Exec\NT>
-------------------------------------------------------------------------------------------------------------------------------------------------------------

Note: If errors occur in reference to duplicate devices in PVL.MDB, these can be safely ignored.

Once complete, confirm all job definitions have been migrated successfully.

If unsuccessful, then the old job definition files contain corruption or invalid data content that could not be translated during the migration. Backup Exec 8.x data files can contain corrupted data in locations where 8.x will not normally read. However, during the migration, the BEMIG utility attempts to move all the data from the 8.x files. There is currently no way to edit or repair the original job definition files to remove such corruption, and in such cases a manual recreation of the job definitions within Backup Exec 9.x and Backup Exec 10.x will be necessary.