Tblucky

I have used this procedure to successfully migrate an installation of BUE 2015 ver. 14.2 to a new server, with a different machine name. If you are moving things from the old machine to the new machine and they both have the same names, see my post here and use that instead.

I used this procedure for a client who was ONLY using local disk based backups, but this will also work for tape/other device backups as well.

Symantec Backup Exec 2016 Server Error

First, download this document. It contains most of the steps, with the additions/changes below.

Using the PDF document from above:

Veritas Backup Exec 16, which became generally available in November 2016, expanded its support to include the Microsoft Azure cloud, Windows Server 2016 and Hyper-V Server 2016. Previous product versions already supported Amazon Web Services and the Google Cloud Platform, as well as third-party clouds that support the Amazon Simple Storage Service protocol. Veritas Backup Exec 16 helps you migrate to the cloud, gives you immediate protection for Windows Server 2016 and Hyper-V 2016, and enables time, cost and resource savings across your entire infrastructure.

Symantec Backup Exec 2012 Windows Server 2016

1. Setup the new server. Patch it up to date through Windows updates. Join it to the domain. Make sure the machine name is correct (what you want it to be going forward)
2. Install BUE onto the new server.
   1. This is SECTION 3 of the PDF, “Install Backup Exec on the Destination Computer”
3. Make sure both the old BUE server and the new BUE server have the exact same
   1. Software version, BUE 2015 / 14.2 (etc.)
   2. Patches.
      1. Run live update on both machines and make 100% sure both have the same version and hotfixes
4. Perform step #1 in the PDF, “Obtain information about the current Backup Exec installation”
5. Perform step #2 in the PDF, “Move Backup Exec data to a temporary location”
   1. Note: it’s up to you if you want to copy directly from the old server to the new server. I directly copied things over the lan from the old machine to the new machine and left the old machine intact.
6. Skip step #3 (already done above)
7. Start step #4 “Move Backup Exec data from temporary location to the destination…” NOTE: Stop after 4.3. Do not proceed yet.
   1. Complete steps 4.1, 4.2 and 4.3
8. In our case, this client was using a disk based backup strategy. At this point, we shut down the old server, shut down the new server, and installed the 3tb hard drive from the old server into the new server.
   1. we also made sure the DRIVE LETTER was the same on the new server for this drive as it was on the old server (after startup)
9. On the new server, go to the BUE path:
   1. C:Program FilesSymantecBackup ExecCatalogs
   2. You will see the copied over files from your old server.
   3. You need to make a COPY of the folder name from your old server and copy that folder (and contents) into the same “Catalogs” directory, but renamed for the new BUE server name.
      1. For example, if your catalogs folder contains a folder BACKUPSERVER1 (and within that folder are many files), create a new folder named for the NEW server name (whatever that is) and copy all the FILES and FOLDERS from within the BACKUPSERVER1 folder, to the new folder.
      2. You will now have to folders now, one named for the old machine and one for the new machine, each with identical contents
10. On the new server, do this procedure:
11. At this point, RESTART the new server
12. When it boots back up, login and launch BUE
13. if all went well you should be ready to go.