We want to move the complete Backup Exec 12 installation to an other server - How do we preserve all settings

[fredrikp]

We want to move the complete Backup Exec 12 installation from one server to another preserving all settings (jobs, medias etc).

How do we do it?

Current server uses Windows Server 2003, 32 bit. New server Windows Server 2008, 64 bit. We could adjust the OS on the new one if required, but we would prefer to use the one specified.

[CraigV]

Backup everything in the Symantec\Back Exec installation directory...specifically the Data and Catalog folders.

[Colin_Weaver]

There's a few issues with this - firsly assuming BE is already installed and patched on the new server - you start by copying the Data and Catalog folders (as per CraigV answer) with the BE services on the servers (including the SQL instance) stopped

Assuming that the name of the Windows 2008 Server is not the same as on the 2003 server - before you start the BEWS services, you need to sort out the name inside the BEDB - so you need to start the SQL Instance (but not the other BEWS servcies) and then change the name on the new server as follows:
Open a command prompt and type
osql -E -S newservername\BKUPEXEC
at the 1> prompt type
use bedb
at the >2 prompt type
go

at the 1> prompt type
UPDATE DataPartition SET PartitionName='newservername' WHERE PartitionID =0   
at the >2 prompt type
go

at the 1> prompt type
quit

Assuming you have kept the version of Backup Exec the same between the two servers (extra steps required if not) you should then be able to start the Backup Exec Services

What you will find is that there are disconnected tape devices in the devices screen (referencing the old server) along with whatever devices are connected to the new server - you will need to change every job and policy template so that it points at the connected devices before you will be able to delete the devices that show against the old server.

 

[fredrikp]

I can't find any data there at all, just a directory called "License Assessment Tool".

Is the data stored elsewhere? How do I find it?

[Colin_Weaver]

You may have a custom install location

If you check the registry key
HKLM\SOFTWARE\Symantec\Backup Exec for Windows\Backup Exec\12.0\Install\Path

It should tell you where Backup Exec is installed - the Catalogs and Data Folder would normally be located under that location

[fredrikp]

It just says:

2> go
The Service Broker in database "BEDB" will be disabled because the Service
Broker GUID in the database (...) does not
match the one in sys.databases (...).

[Colin_Weaver · Accepted solution]

OK that means there is an inconsistency between the database content and the sys tables which can be resolved by doing a SQL Dump of the database to a backup file - slightly more difficult to explain how to do it - easiest method is to use the SQL Studio  Manager (or SQL Studio Manager Express) to connect to the BKUPEXEC instance and then locate the BEDB Database right click on it select Tasks --> Back Up...

Add a new desitination file into the Destination Pane (or if the BEDB.BAK is already listed there use it) and click OK

You should get a sucess returned. Then you will be able to repeat the origional commands provided earlier.

Note if you don't already have SQL Studio Manager (or the express version) on a system in your environment then you may have to download it from Microsoft - if you have a member of staff who is a SQL admin then they should be able to help if you are unfamiliar with SQL

[Ken_Putnam]

Here is the Symantec recommended procedure

http://seer.entsupport.symantec.com/docs/319367.htm

[Colin_Weaver]

More detailed version of same information - as it also uses the OSQL method to change the server name - you will still run into the problem with the SQL Inconsistency on the Sys tables. Note sqlcmd and osql provide the same functionality