- #Upgrade backup exec install#
- #Upgrade backup exec update#
- #Upgrade backup exec upgrade#
- #Upgrade backup exec software#
- #Upgrade backup exec download#
This does mean you may have to adjust the storage configuration within Backup Exec and also reconfigure the job definitions so that the jobs use the newly configured devices.Veritas Backup Exec (formerly Symantec Backup Exec System Recovery) combines the speed and reliability of disk-based, bare-metal Windows system recovery with revolutionary technologies for hardware-independent restoration and lights-out operation. Note 3 : Due to how volumes are given new identifiers on new servers and how plug-n-play on the operating system will detect storage devices such as tape libraries, any storage devices used as targets for the backups will be seen as new devices after the migration. Job Histories (which are kept inside the database) should still be accessible. If older jobs logs need to be accessible after the migration, then they have to be copied separately, however if Backup Exec is installed in a different path on the new server then you will not be able to open the copied job logs from within the Backup Exec Console itself (and will have to directly open the XML files to review them).
#Upgrade backup exec upgrade#
(1) To upgrade to Backup Exec 15 or Backup Exec 16 from BE2010 R3, SP4 or later has to be installedĭo not upgrade to Backup Exec 15 or Backup Exec 16 from an earlier versions of Backup Exec that run on a 32-bit operating system. X indicates BE versions that can be upgraded from Please refer the following Table while setting the value for Upgrade version Key. Note: (Create as a STRING value "Upgrade Version" if not present in the registry) Modify the value of "Upgrade Version" to the version of the database DB being imported or migrated from.
#Upgrade backup exec software#
HKLM | Software | Veritas | Backup Exec for Windows | Backup Exec | "VersionNumber" | Installħc.
#Upgrade backup exec install#
HKLM | Software | Symantec | Backup Exec for Windows | Backup Exec | "VersionNumber" | Install Launch the Registry Editor (Start, Run, Regedt32). It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.ħa. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. Great care should be taken when making changes to a Windows registry. Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. If the Catalogs have been saved also, rename the Catalogs to Catalogs.old, then copy/move the saved catalogs under Backup Exec. This will be bedb_dat.mdf and bedb_log.ldf files.ĥ. Copy the saved Database from the previous BE version into the \Backup Exec\Data folder(or the entire folder). Rename the "Copy of Data" to "Data-'TodaysDate' or "Data-Version#-New"Ĥ. Copy the Data folder and paste it in the same location. Open \Program Files\Symantec or Veritas \Backup Exec Directory.
Stop the all Backup Exec services (including the SQL (BKUPEXEC) service).ģ.
#Upgrade backup exec download#
Obtain patches from the Veritas Download CenterĢ.
#Upgrade backup exec update#
Update Backup Exec to the latest Service Pack, Feature Pack, or Hotfix. Confirm Backup Exec is working in its current database.
The Backup Exec Central Administration Server (CAS) is installed.The Backup Exec Shared Storage Option (SSO) is installed.ldf files are from an older version of Backup Exec installed on a different server then please do not follow the procedure below if any of the following are true: This tool follows the same upgrade version rules that the BE installer has. If that fails to occur or a saved database from a previous BE version needs to be added to a newer BE version, the BEMIG tool can be used. The recommended upgrade method is to allow the Backup Exec (BE) installer upgrade BE and its database during the installation. Need to manually upgrade Backup Exec from a previous version.