poplacook.blogg.se - Backup exec 16 migration to another server

Backup exec 16 migration to another server update#
Backup exec 16 migration to another server upgrade#

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).ģ. Obtain patches from the Veritas Download CenterĢ.

Backup exec 16 migration to another server update#

Update Backup Exec to the latest Service Pack, Feature Pack, or Hotfix. Confirm Backup Exec is working in its current database.

If planning to move Backup Exec to a different drive/directory on the server.ġ.

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.

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:

Backup exec 16 migration to another server upgrade#

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.