Forum Discussion

Bakker's avatar
Bakker
Level 3
15 years ago
Solved

Unusual Upgrade Path

Hello All,

I'm faced with an unusual upgrade path required for our Backup Exec 12.0 server.
To support backups of 2008 R2 systems we need to upgrade this server to version 13.0 (2010).

The server itself is 64 bit capable but currently installed with Windows 2003 32 Bit Standard Edition. We'd like to upgrade this (reinstall the system) with Server 2008 R2 64 Bit standard edition while we're at it.

I've looked through the knowledge base and found a few articles that describe our required upgrade somewhat. Most notably this one:
http://seer.entsupport.symantec.com/docs/319367.htm

It however lists that this should not be done (upgrade from 32 bit to 64 bit with a reinstall) when you're switching between operating system versions (2003 to 2008 R2)

Does anyone have any idea how we can do this without losing our jobs/history/archives etc? It would really be a hassle to begin with a fresh installation.

Any input is very welcome!
12.x and Earlier
2010
Backup and Recovery
Backup Exec
Backup Exec (media server only)
  • Bakker's avatar
    Bakker
    15 years ago
    Well i think i was able to make it work. So far i've only done this in a test environment but the above advice did indeed help.

    Taking the following steps:

    1. Update BE 12.0 with the latest patches
    2. Upgrade BE 12.0 to 13.0
    3. Install BE 13.0 on the new server
    4. Update BE 13.0 on the new server with the latest patches
    5. Stop BE/SQL services on the old server.
    6. Stop BE/SQL service on the new server
    7. Copy over the Catalogs, Data and IDR folder to a temp location on the new server
    8. Set up the folders for the Logs and Catalogs on the proper drives (we had moved these a while ago).
    9. Start beutil.exe and import the old database (replacing the MDF and LDF files led to the same issues as posted above)
    10. In beutil.exe move the catalog and log folder locations to the newly created folders on the other drive.
    11. Copy the logs and catalogs into these new folders
    12. Start backup exec services.
    13. In backup exec go to tools - options - catalog and modify the path to point to the proper directory
    14. Restart BE services
    15. Delete old devices/servers

11 Replies

Sort By
  • Nimish_Patel's avatar
    Nimish_Patel
    Level 5
    15 years ago

    As you know from the TechNote, cross hardware paltform upgrade is not advised. However, if you want you can install BE 2010 on a 64 bit server and then follow the migration process mentioned in

    http://support.veritas.com/docs/287063      (How to use BEMIG to migrate/upgrade a previous Backup Exec (BE) Database to a newer Backup Exec Install version)
    http://support.veritas.com/docs/318321     (How to migrate from Backup Exec from one version to an another on different server with a different server name)


    If this answers your question, mark it as the sollution.

  • AmolB's avatar
    AmolB
    Moderator
    15 years ago

    Though the above link states "Do not follow this procedure if, 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" you may follow the article. It works fine.

    Note:  Make sure you take backup of data & catalogs folder from X:\Program Files\Symantec\backup Exec



     

  • Bakker's avatar
    Bakker
    Level 3
    15 years ago
    Hi,

    Thanks for the replies. Sorry for not responding earlier but i did not get around to it.

    I've completed the steps above and have come to the part just after running BEMIG.

    When i try to start the Backup Exec Server service it stops immediately stating:

    "The Backup Exec service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs"

    The eventlog shows the same error as listed here:
    http://seer.entsupport.symantec.com/docs/318577.htm

    Very odd as the old database server also came from a SQL express edition installed by backup exec

    Any idea where i should look?

    Thanks
  • AmolB's avatar
    AmolB
    Moderator
    15 years ago

    Hi Bakker

    Try Copy database.

    1) Stop the SQL service used by backup exec.

    2) Copy the BEDB_DAT.MDF  and BEDB_LOG.LDF from X:\Program Files\Symantec\Backup Exec\Data folder to the desktop

    3) Start the SQL service.

    4) Open BEUtility from X:\Program Files\Symantec\Backup Exec and perfrom copy database.

    5) For copy database refer to http://support.veritas.com/docs/286093

    Note: Please take a backup of DATA & CATALOGS folder from X:\Program Files\Symantec\Backup Exec before perfroming about steps.

  • Bakker's avatar
    Bakker
    Level 3
    15 years ago
    Hi,

    Thanks for the pointers,

    However the Device and Media service fails to start after doing this:

    The Backup Exec Device and Media Service cannot start because it detected a database schema version mismatch.

    Odd, no?
  • pkh's avatar
    pkh
    Moderator
    15 years ago
    What the previous advice is trying to do is to transfer your old BE database directly to BE 2010.  As you have found out, this will not work as the database schema is different.

    If I were you, I would do the following

    1) Upgrade to BE 2010 first.  This will upgrade your BEDB, thus preserving all your jobs.

    2) Stop all the BE services and the SQL service for the BE instance.

    3) Copy the Data and Catalog folders.

    4) Install your 64-bit OS

    5) Install BE 2010

    6) Stop all the BE services and the SQL service for the BE instance.

    6) Replace the Data and Catalog folder that you have copied in Step 3.

    7) Start the SQL service for the BE instance and then all the BE services.
  • Bakker's avatar
    Bakker
    Level 3
    15 years ago
    Hi pkh,

    Thanks for your reply. After yesterdays attempts that was exactly what i was thinking. I'm just waiting for the upgrade license to be finalised.

    I assume i can also copy over the Logs folder containing my Job logs? (just the .xml files).

  • pkh's avatar
    pkh
    Moderator
    15 years ago
    I an using BE 12.5 and my job logs are in the Data folder.
  • Bakker's avatar
    Bakker
    Level 3
    15 years ago
    Ah that is correct, we moved the Job Log folder location because of a lack of diskspace on the Backup Exec installation drive.
  • Bakker's avatar
    Bakker
    Level 3
    15 years ago
    Well i think i was able to make it work. So far i've only done this in a test environment but the above advice did indeed help.

    Taking the following steps:

    1. Update BE 12.0 with the latest patches
    2. Upgrade BE 12.0 to 13.0
    3. Install BE 13.0 on the new server
    4. Update BE 13.0 on the new server with the latest patches
    5. Stop BE/SQL services on the old server.
    6. Stop BE/SQL service on the new server
    7. Copy over the Catalogs, Data and IDR folder to a temp location on the new server
    8. Set up the folders for the Logs and Catalogs on the proper drives (we had moved these a while ago).
    9. Start beutil.exe and import the old database (replacing the MDF and LDF files led to the same issues as posted above)
    10. In beutil.exe move the catalog and log folder locations to the newly created folders on the other drive.
    11. Copy the logs and catalogs into these new folders
    12. Start backup exec services.
    13. In backup exec go to tools - options - catalog and modify the path to point to the proper directory
    14. Restart BE services
    15. Delete old devices/servers