β07-24-2014 07:02 AM
Hi All,
I'm trying to upgrade our BE2012 server to BE2014 and am getting an error during the migration phase of the upgrade stating that the database cannot be upgraded. In the error log I can see errors as below:
The only KB article I can find relating to this is here:
http://www.symantec.com/business/support/index?pag...
This is for BE2012 however and does not seem to match my logs.
Anyone else had this issue before and able to resolve?
Thanks
β07-24-2014 08:04 AM
Hi Dunfraggin,
Before the upgrade ensure that Backup Exec 2012 is uptodate with all patches and hotfixes installed, then reboot the media server and run the upgrade.
β07-24-2014 08:13 AM
Thanks Imosla.
I had originally ran the upgrade against the media server without doing this and then after the first failure I found a hotfix was missing on the BE2012 server so applied this.
After rebooting the upgrade again failed at the same point and with the same error. I have mamaged to also find this warning in the install logs now too (which was also in the previous attempts tried):
The account used to perform the upgrade has full rights to the SQL server (this is on a different server, not on the backup exec server) as well as SQL rights too to be able to perform the upgrade.
β07-24-2014 10:47 PM
It is failing over here ~
dbutil RunSQLScript: execute sql cmd failed. sql statement: UPDATE JHD Set JHD.ResourceDisplayName = RES.ResourceName FROM dbo.[JobHistoryDetail] JHD INNER JOIN dbo.[Resource] RES ON JHD.ResourceID = RES.ResourceID WHERE JHD.ResourceDisplayName = ''
Is JHD/RES a name of a resource/job ?
β07-25-2014 01:07 AM
Hi VJ,
No JHD/RES is not the name of any resources or jobs within this backup environment. I'm at a loss to see where this comes from?
β07-25-2014 01:36 AM
I currently do not have access to a machine, but i am guessing JHD stands for Job History Details and RES stands for Resource. Probably, there is a job or a job history log preventing the migration.
I would recommend you to log a formal support case for assistance with the migration.
β07-25-2014 01:39 AM
β07-25-2014 01:49 AM
Thanks guys.
The BEUtility repair on the DB might be a good shot to try first before logging a call. Will give that a try and update with the results - It won't be today as I'll need a new change window now :(