Migrating to a new server

[digitlman77]

Currently I have a Windows 2003 x64 server.  We are running BE 2010 R2 4164.  In the near future, we plan to backing up data, paving this server and installing Windows 2008 R2 SP1.  What's the best way to back up the catalog and job info and then restore it? 

As part of this, we will be going from a 2005 SQL server local install to a SQL 2008 R2 local SQL install.

[VJware]

try this - http://www.symantec.com/docs/TECH129826

[digitlman77]

Will this work for different BE versions?  And SQL versions?

[VJware]

If different version, then use this - http://www.symantec.com/docs/TECH67296

[digitlman77]

Ahh...this requires both servers be online at the same time....since I plan to format the single server with a diff OS this would not apply....

[VJware]

In that case, would suggest to grap a copy of your Data & Catalog folders & re-install the same version after rebuilding the server...Replace the Data & the Catalogs folders & then do in-place upgrade to 2010 R3

[digitlman77]

Or, I can set up a temp vm with the trial version, transfer everything to that using the diff version move notes, rebuild, then transfer back using the same version notes?

[digitlman77]

I have BE installed on the VM, and I am trying to test copy jobs over, but they keey timing out.

Can you copy jobs from an older version of BE to a newer version?  I mean, via the GUI, not via any of the migration methods listed above?

[AmolB]

You can copy jobs between same versions of BE only else migration through BEMIG will help you 

to migrate BEDB from old version to new version

[digitlman77]

Ok..that would be my issue...thanks!

[digitlman77]

I rebuilt the vm by installing from the same 2010 R2 install DVD, then ran SP1 and a few other hotfixes.

The old server still cannot copy anything over.  It times out with no other useful error message.

Using the same bkexec AD account on both of them...no firewalls....WTF?

[pkh]

Symantec does not recommend using a VM as media server as it will have problems accessing physical devices like tape drives.

[digitlman77]

Well, I backed up the old sever, formatted, installed BE 2010 R2 4164, stopped BE and SQl and copied in the Catalog and Data folders, started everything, and then did an upgrade to R3.

Everything seems to be working fine, except that when I run the Support util, it complains:

Database is missing records for the PartitionName, PartitionID and PartitionGUID.
Use the link above to access the instructions for correcting this error.

I used http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH136210

to fix it, but the GUID in the SQl server and the registry are still different.

I tried to fix the schema using this:  http://www.symantec.com/business/support/index?page=content&id=TECH50537

But i gen an error when running the BEMIG.

Are these things I need to worry about?  So far, the backups and restores seem to be working.

[digitlman77]

Thoughts on this?

[digitlman77]

Anybody?

[Striker_303]

(1)-Stop SQL backup(bkupexec) service and

-Go to the installation Directory of Backup Exec,
  [default path: C:\Program Files\Symantec\Backup Exec]
-copy bedb_dat.mdf and bedb_log.ldf from Data folder to some another location
- copy complete Catalogs folder

(2)- Uninstall\ reboot \Re-install Backup Exec 2010 R3
 
(3)-Using Be-utility only - copy database -import those database .mdf and .ldf files
and replace catalog folder

Refer: http://www.symantec.com/docs/TECH49757

Note: do not copy and replace complete data folder as before.

[digitlman77]

Am I at risk of data loss if I do not do this ASAP?

[Striker_303]

Not really..as long as your backups and restores are working properly. :)

[digitlman77]

Ok, trying that now.

[digitlman77]

Ok, I just did ALLof that, re-ran the BEST, and I get the same errors about schema and datapartition info.

And I'm getting an error that the bkexec user privs acconut does not have "Manage auditing and security" set, but it may have not have before.