How to revert to Backup Exec 2010 R3 (revision 5204) from Backup Exec 2012 (revision 1798)

Article:TECH200344  |  Created: 2012-11-30  |  Updated: 2014-02-04  |  Article URL http://www.symantec.com/docs/TECH200344
Article Type
Technical Solution

Product(s)

Issue



How to downgrade, revert, rollback to Backup Exec 2010 R3 (revision 5204) from Backup Exec 2012 (revision 1798)


Environment



Backup Exec 2012

 


Solution



Warning: The instructions provided in this document pertain only to Backup Exec 2010 R3 revision 5204 and Backup Exec 2012 revision 1798. This document is not intended for any other versions or revisions of Backup Exec.
 

Known Limitations
 
  • If an application/file system/operating system is supported in Backup Exec 2012 but not in Backup Exec 2010 R3, there is no expectation that these items can be backed up or restored  in Backup Exec 2010 R3 after reverting back.
  • Exchange incremental/differential backups that were performed in Backup Exec 2012 cannot be cataloged or restored in Backup Exec 2010 R3.
  • Backup Exec 2012 catalog information is written in UTC time/date format.  Cataloging Backup Exec 2012 media in Backup Exec 2010 R3 will result in restore selections displaying UTC times/dates.  Restoring this data will result in UTC time/date format.
  • Backup Exec 3600 appliances cannot be downgraded.
  • Retain the Backup Exec 2012 \Data and \Catalog folders for any future restore from media that is not compatible with Backup Exec 2010 R3.
  • Any job configuration or media retention information that was created in Backup Exec 2012 will not be retained after downgrading to Backup Exec 2010 R3.
  • Any job configuration or media retention information that existed in Backup Exec 2010 R3 prior to the upgrade to Backup Exec 2012 will be available after the downgrade only if the backup of the Backup Exec database for 2010 R3 (mentioned in the table in step 5 below) is still available for recovery. If this backup is missing, all jobs will have to be recreated and existing media will have to be managed manually.
  • Any BKF files that were created in Backup Exec 2012 will be placed in the Imported media set. If you use the default media protection settings, any time that a job needs to use that media, Backup Exec will prompt you to verify that it can be used. Since you may want the ability to restore from some of that media, you must cancel the jobs. Do not allow jobs to use that media. You may want to move the media to a temporary media set and then manually move them to the Scratch media set as required.
  • If email alerts are enabled in Backup Exec 2010 R3, you should notify email recipients that they will receive multiple alert messages as jobs are missed or canceled.
  • Backups of Microsoft SQL Server default instances that were made with Backup Exec 2012 cannot be restored with Backup Exec 2010 R3.
  • After the Backup Exec database files are copied, jobs may start to run and use existing media. Some of these jobs will be reported as missed and will be put back into the queue. You may have to cancel those jobs if you do not want them to run.

 

To downgrade from Backup Exec 2012 revision 1798 to Backup Exec 2010 R3 revision 5204:

  1. Ensure that you have a license key for Backup Exec 2010 R3.
    You can send a request to license@symantec.com to obtain a license key or you can find a telephone number for Symantec Customer Care at: http://www.symantec.com/support/techsupp_contact_phone.jsp
  2. Close Backup Exec.
  3. Stop all the Backup Exec services.
  4. Stop the SQL Server service that Backup Exec is using for the Backup Exec database.  By default, the SQL Server service name is “SQL Server (BKUPEXEC)”.
  5. Copy the following folders to a temporary location (for example, C:\BE-Revert): 


Folder Description

Source Folder (Default Locations)

Catalog folder

C:\Program Files\Symantec\Backup Exec\Catalogs

Data folder

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

Backup Exec database (from Backup Exec 2010 R3)

C:\Program Files\Symantec\Backup Exec\DataBackup2012-XX-XX-XX-XX-XX\Data


 

 

 

 

 

 

 

  1. Start all the Backup Exec services. The SQL Server service will start automatically..
  2. If the Deduplication Option is installed, follow these steps:
    1. Start Backup Exec.
    2. On the Storage tab, right-click the deduplication storage folder,  and then click  Details.
    3. Write down the storage path and the logon account information.
    4. Close Backup Exec.
  3. Uninstall Backup Exec 2012. Select the option to remove Backup Exec and all of its associated files.
    Note:  Uninstalling Backup Exec will not remove data that has been backed up to storage devices (such as tape drives, backup-to-disk folders, deduplication storage, etc).   In most cases, data backed up in Backup Exec 2012 can be restored in Backup Exec 2010 R3, so do not delete the storage devices.
  4. Reboot the computer.
  5. Install Backup Exec 2010 R3.   A file containing your Backup Exec 2010 R3 license information should still be on your computer.  When prompted to enter license keys, select Import, and then import the file “besernum.xml” from one of the following folders:
    • Windows 2003 - C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec\
    • Windows 2008 - C:\ProgramData\Symantec\Backup Exec\
      Note: If the license file "besernum.xml" does not exist, contact Symantec Customer Care to obtain your Backup Exec 2010 R3 license keys. You can send a request to license@symantec.com to obtain a license key or you can find a telephone number for Symantec Customer Care at: www.symantec.com/support/techsupp_contact_phone.jsp
      Note: If you do not have the installation files for Backup Exec 2010 R3, you can download them from the following location. You must have a license key for Backup Exec 2010 R3 to download the files.
      fileconnect.symantec.com
  6. After the Backup Exec installation completes, reboot the computer if necessary
  7. Run LiveUpdate to install Backup Exec service packs and patches.

    Note:  After installing service packs and patches, it might be necessary to reboot the computer.  After rebooting the computer, run LiveUpdate again to install any remaining service packs or patches..

    Note: Perform steps 13 through 16 only if you want to import your previous Backup Exec 2010 R3 jobs, policies, job history, alerts, etc.  Otherwise skip to Step 17.
     
  8. Stop all the Backup Exec services.
  9. Stop the SQL Server service that Backup Exec is using for the Backup Exec database.  By default, the SQL Server service name is “SQL Server (BKUPEXEC)”.
  10. Copy the Backup Exec data from the temporary folder from step 5 to the folders listed below.  The default locations are listed.

    Warning: After the Backup Exec database files are copied, jobs may start to run and use existing media. Precautions should be made to protect existing media. 
    Some of these jobs will be reported as missed and will be put back into the queue. You may have to cancel those jobs if you do not want them to run.


    Folder Description

    Target Folder

    Catalog folder

    C:\Program Files\Symantec\Backup Exec\Catalogs                                     

    Data folder
    Important Note:  The BEDB_dat.MDF and BEDB_log.LDF files from this temporary folder  should not be copied since these files (database files) are from Backup Exec 2012.

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

    Backup Exec 2010 R3  database files BEDB_dat.MDF and BEDB_log.LDF (As found in the DataBackup2012-XX-XX-XX-XX-XX\Data folder).

    If you are prompted to replace the existing files, click Yes.

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


     

 

 

 

 

 

 

 
    

  1. Start all the Backup Exec services. The SQL Server service will start automatically.
  2. Start Backup Exec, and then go to the Devices view.
    Note:  You may see double entries for your server and devices.  Restarting the Backup Exec services should resolve this issue.
     
  3. If the Backup Exec Deduplication Option is installed, follow these steps to bring the deduplication storage folder online:
    1. Right-click the deduplication storage folder (the device should show up as Offline).
    2. Click Delete, and then click Yes to confirm. This does not delete your backed up data. This only deletes the reference to the storage device in the Backup Exec database.
    3. When prompted to retarget your backup jobs, select a device. This is temporary until another deduplication storage folder is created.
    4. On the Tools menu, select Configure Devices >  New Deduplication Storage Folder.
    5. In the Storage path field, type the path to the deduplication folder that you wrote down in step 7c.
    6. In the Logon account field, select the same logon account that you wrote down in step 7c.
    7. Proceed though the rest of the wizard, and then restart the Backup Exec services when prompted.
    8. For those backup jobs that were targeting  your old deduplication storage folder, retarget these backup jobs to the new deduplication storage folder.
  4. Inventory tape drives, tape libraries, backup-to-disk folders, and deduplication folders.
  5. If you skipped steps 13 to 16, catalog ALL media in tape drives, tape libraries, backup-to-disk folders, and deduplication folders. This step is not necessary if you performed steps 13 to 16.
  6. Uninstall the Backup Exec  2012 Agent for Windows/Mac/Linux on all remote servers and reboot if prompted.
  7. Install the Backup Exec 2010 R3 Agent for Windows/Mac/Linux on all remote servers and reboot if prompted.
  8. In Backup Exec, select Backup, and then browse to each of the remote servers with the Backup Exec 2010 R3 Agent for Windows installed to verify that a certificate trust exists between the Backup Exec server and each remote server.  If prompted to create a certificate trust, do so. 
     



Article URL http://www.symantec.com/docs/TECH200344


Terms of use for this information are found in Legal Notices