Forum Discussion

bobS432's avatar
bobS432
Level 3
8 years ago

Migrate BEDB without using BEUTIL

Hi,

I need to migrate the BEDB from one SQL server to another, however using the BEUTIL program is unfortunately out of the question due to the service restart it performs on SQL (the SQL server is shared by several other applications).

Now in terms of doing this, the course of action would I assume be:

  1. Stop BE services.
  2. Backup and restore BEDB using native SQL backup from one db server to the next.
  3. ??? change connection strings for BE somehow ???
  4. Restart BE services and verify it works as expected.

How can I accomplish step 3, I can't seem to find anywhere the SQL database connection is set with BE?

Thanks in advance,


Bob.

15
Windows Server 2012 R2

9 Replies

Sort By
    • bobS432's avatar
      bobS432
      Level 3
      8 years ago

      Thanks for your reply.

      The first article is about BEUTILITY, which is unfortunately what I explicitly can't use.

      For the second, I tried manually migrating the SQL database and amending the connection string settings as specified in the second article, and the services start and the client loads seemlingly correctly, showing the correct jobs etc. However, one big issue was this made my entire job history disappear, whether trying to restore a file or otherwise. As doing this basically invalidates all my existing backups, its not really workable so I have reverted and the job history came back.

      Is there an additional bit of configuration somewhere, or something that is dependant on that old instance that needs to be changed beyond what is mentioned in that article (that article does say it is for BE 2010, and I'm running 15).

      Thanks in advance,

       

      Bob.

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    8 years ago

    It is bad practice to install the Backup Exec database in the same instance as production databases for other business critical applications. As such I recommend you re-think your idea and keep it in a separate instance (or at very least limit the types of databses in the instance to IT systems such as Insight Manager etc that are less critical to business operations)

     

    You have already found one of the reasons for why it is bad practice - i.e. there might be a need for a service restart against the instance that runs the BEDB. Other reasons relate to how you DR restore the environment with all your databases in the same instance.

    • bobS432's avatar
      bobS432
      Level 3
      8 years ago

      Its not really my decision to make, it is what it is.

      So what we're basically saying is that fundamentally the BEUTILITY tool does some auto-magical things in the background while transferring databases that no one know's how to replicate manually? I mean if true thats quite an astonishingly scary proposition for a tool focused around backup and recovery. 

      Or is there something additional that needs to be done to recover my job histories once the db has been moved?

       

      • Colin_Weaver's avatar
        Colin_Weaver
        Moderator
        8 years ago

        Do you mean job histories or job logs? Job Histories are contained inside the BEDB but job logs are held in a path on the BE server itself