After migrating Backup Exec or chaning the Backup Exec installation path unable to open the older job logs.

book

Article ID: 100039693

calendar_today

Updated On:

Description

Error Message

 “The job log could not be loaded x:\Program Files\Symantec\Backup Exec\Data\JOB LOG NAME.xml”.

 “The job log could not be loaded x:\Program Files\Veritas\Backup Exec\Data\JOB LOG NAME.xml”.

 

User-added image

Resolution

 

1)  Manually copy old job log xml file to current Backup Exec \Data path folder. 

Copy Job Log *.xml files in the old \Backup Exec\DATA folder and pathl ocation to the current Backup Exec installation path \Backup Exec\Data folder path.  Default C:\Program Files\Veritas\Backup Exec\Data.

Example:

Current Backup Exec \Data folder location: D:\Program Files\Veritas\Backup Exec\Data

Old Backup Exec \Data folder location: C:\Program Files\Symantec\Backup Exec\Data

Create directory C:\Program Files\Symantec\Backup Exec\Data and copy all the old job logs to the directory.

 


 

2) To prevent having job log files in multiple location OR if the new server does not have a drive letter to match the old server drive/pth a SQL script can be executed ot update the Backup Exec Database.  The SQL script will update the path in the Backup Exec database and all the job logs can be centrally located in the current Backup Exec installation \Data folder.

 

CAUTION: Before proceeding, please Stop the Backup Exec services and SQL BKUPEXEC or SQL BKUPEXEC64 and copy the Backup Exec database files to a safe location.  Copy \Backup Exec\Data\bedb_log.ldf, bedb_dat.mdf, and BEDB.bak to a safe location.  Start the SQL BKUPEXEC or BKUPEXEC64 service and then the Backup Exec services.

 

 

A) Perform a Backup aka "dump" of the Backup Exec database using BEUTILITY.

 

How to run a dump database with the Backup Exec for Windows Servers Utility (BEUtility) to back up the database file to hard disk

https://www.veritas.com/support/en_US/article.100022872

 

Locate the BEDB.bak file in \Program Files\Veritas\Backup Exec\data folder and copy it to a safe location.

 

B) The following SQL query assumes the same drive letter is used but the product path is now "Veritas" vs "Symantec".

 

Old Path:         C:\Program Files\Symantec\Backup Exec\Data

Current Path: C:\Program Files\Veritas\Backup Exec\Data

 

 

USE BEDB;

update JobHistorySummary

set JobLogFilename = replace (JobLogFilename , 'Symantec' ,'Veritas')

where JobLogFilename like '%Symantec%'

 

 

C) The following SQL query assumes the same path of the Backup Exec installation but drive letters have changed from "C:" to "D:".

 

Old Path:         C:\Program Files\Veritas\Backup Exec\Data

Current Path: D:\Program Files\Veritas\Backup Exec\Data

 

 

USE BEDB;

update JobHistorySummary

set JobLogFilename = replace (JobLogFilename , 'C:\' ,'D:\')

where JobLogFilename like '%C:\%'

 

 

 

Note: If the outcome of the SQL query or script produces unintended results, please immediately restore the Backup Exec database (BEDB.bak) using BEUTILITY.

 

How to drop the existing Backup Exec Database and reload from backup

https://www.veritas.com/support/en_US/article.100020245

 


 

Issue/Introduction

After migrating from older version of Backup Exec to a new server , unable to open the older job logs. This issue can occur if Backup Exec is uninstalled and installed to a new drive or folder path keeping the exisitng Backup Exec Configuraiton (Database or Data folder). “The job log could not be loaded c:\Program Files\Symantec\Backup Exec\Data\JOB LOG NAME.xml”.