Help Urgent - Viewing old job reports in upgraded version

[JulesA]

Hi,

We have recently upgraded up system from version 10 to 2010 and have been successfully running jobs.

We have the old jobs which used to appear in the job monitor for version 10 saved and I need to somehow import or view them in our current version.

How can I do this?

Thanks

[Dev_T]

Did you uninstall 10d and install BE2010? Upgrade from BE10 to BE2010 is not possible........

[pkh]

We have the old jobs which used to appear in the job monitor for version 10 saved

How did you save these jobs?  Did you save the jobs themselves or the joblogs?

[Nimish_Patel]

You can not do that as Backup Exec stores all job logs in a .xml file under DATA folder and creates a link for the same in the Backup Exec database and keeping in mind that direct upgrade to 2010 from BE 10d is not possible, you must have had to uninstall BE 10d and install 2010. In that case, the contents of the DATA folder of your 10d got wiped out.

The only way to bring back those job logs would be possible only if you still have the copy of BE 10d database and all .xml files located in the data folder. If you have these things then we can bring your job logs back by first upgrading your BE 10d database to BE 11d or 12d and then upgrading the same to 2010.

If this answers your query, please mark this as the solution.

[JulesA]

Hi,  thanks for your replies.

I thought it would be easier to install 10d on a different server so we can use this to view the old records.  Just not sure now how I go about restoring the old db so we can view the old xml files which I have.  Do they have to go in that Data folder or can I point the job monitor to another location?

Thanks

[Nimish_Patel]

If you are planning to install BE 10d on a different server and has the data folder of the old 10d installation handy, then you can follow

1. stop all BE and SQL services on you 10d server.
2. rename the existing data folder on the server and copy the old data folder in its place.
3. Start just the SQL service.
3. opend command prompt and run following
   a. osql -E -S servername\BKUPEXEC  (Server name would be the name of your current server on which you have installed 10d).
       1>use bedb
       2>go
       1>SELECT partitionname FROM datapartition
       2>go  (After presseing enter the command prompt will show you the name of your old server with 10d)
       1>UPDATE DataPartition SET PartitionName='<this server name>' WHERE PartitionID =0            (<this server name> = Your New Server Name)
       2>Go
       1>SELECT partitionname FROM datapartition
       2>Go (After hitting enter, it will show you the name of the current server).
  b. Opened a new command prompt window and navigate to X:\Program Files\Symantec\Backup Exec  (X is the drive where you have installed 10d) and then run bemig.exe.
  c.  Reboot the server and you should be able to see your job history and job logs.


If this answers your query, please mark this as the solution.
      

[sksujeet]

If you want to see the old jobs then you should have the data and catalog folder from 10d otherwise it is not possible.

If you have it then follow the below steps:

1>You can install 10d on the other server
2> Once installed stop all the BE service and sql(bkupexec) service and rename the data and catalog folder from c:\program files\symantec\backup exec\ to data.old and catalog.old
3> Copy the backed up data and catalog folder to that location
4> If it is same server then go to step 5 otherwise you have to follow point 5 in this article to change the server name http://seer.entsupport.symantec.com/docs/319367.htm
Start all Backup Exec services.
you said you have upgraded from 10d to 2010, how was the upgrade done. Did you install 11d or 12.0 and then upgraded to 2010, as direct upgrade from 10d to 2010 is not possible.

[Nimish_Patel]

Duplicate answer sazz.

[JulesA]

bemig failed. The files in my data files are BE_DLO.mdf.bak and BE_DLO_log.ldf.bak obviously as well as the xml and dat file.



Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\JAnnetts>d:

D:\>cd d:\program files\veritas\backup exec

D:\Program Files\VERITAS\Backup Exec>bemig.exe
'bemig.exe' is not recognized as an internal or external command,
operable program or batch file.

D:\Program Files\VERITAS\Backup Exec>cd d:\program files\veritas\backup exec\nt

D:\Program Files\VERITAS\Backup Exec\NT>bemig.exe
Executing migration of data from 8.x
SetRange: from=0 to=500
Status Message: DriverConnect:DRIVER=SQL Server;SERVER=lonpsqldb01;DATABASE=BEDB

Status Message: Querying version data
Status Message: AdammUpgradeView::Initialize() = 0
Status Message: Install Key=Software\VERITAS\Backup Exec\Install
Status Message: NSE Migration: NSEMigration Internal Registry Key=0x0
Status Message: ADAMM upgrade started
Status Message: Backup Exec Device & Media Service Database, version 10.000001 i
s up to date. No changes are required.
Status Message: ADAMM upgrade ended
Status Message: Install Key=Software\VERITAS\Backup Exec\Install
Status Message: Job Migration: JobMigration Internal Registry Key=0x0
Status Message: m_sExePathName=D:\Program Files\VERITAS\Backup Exec\NT\ m_sPathN
ame=D:\Program Files\VERITAS\Backup Exec\NT\Data\
Status Message: Unable to open or query registry key Upgrade Version.
Status Message: Unable to migrate data.  Cannot determine previous version of Ba
ckup Exec.
Status Message: Unable to migrate data.  Cannot determine previous version of Ba
ckup Exec.
Status Message: Job Migration Failed
Status Message: Job Migration Failed
Summary Entry: Type=UPGSUMERR
 title=Job Migration
 message=

Unable to open or query registry key Upgrade Version.

Unable to migrate data.  Cannot determine previous version of Backup Exec.

Job Migration Failed
Upgrade state set to -1342160891

[Nimish_Patel]

can you confirm if your old DATA folder has BEDB_DAT.mdf and BEDB_log. ldf files ??? as these are the actual database of Backup Exec where your job history and links to your job logs are stored.

If these two files are not present then there is no way to recover the old database.

BE_DLO.mdf.bak and BE_DLO_log.ldf.bak are just a blank copy of the DLO databases.