Forum Discussion

pj483's avatar
pj483
Level 3
7 years ago

Issue migrating EV databases to new SQL server

I am moving the EV databases between SQL servers and have hit an issue at the store reconfiguration stage. When entering the new SQL instance name I get the error:

Could not get service status
Enterprise Vault Storage Service

This service is not running at the moment as the migration instructions indicate shutting down all of the services except the Directory Service (which consequently starts the Admin Service).

Any ideas?

Thanks.
Enterprise Vault 9
  • GertjanA's avatar
    GertjanA
    Moderator
    7 years ago

    Hello,

    I assume you followed the documentation, and have updated the directory database and the fingerprint database already. To reconfigure the Vault Store database(s), you should be able to do just the below. If that fails, then run Deployment Scanner, and enter only the NEW sql information. See if all SQL checks are green.

    Stop the Enterprise Vault Storage service.

    Move the vault store database to the new SQL Server.

    Make sure that the Vault Service account has the correct permissions to access the new database.

    In the Administration Console, right-click the vault store whose database you have moved, and click Properties.

    Click the Database tab.

    In the SQL Server box, enter the name of the new SQL Server.

    Click OK.

    Restart the Enterprise Vault Storage service.

    • pj483's avatar
      pj483
      Level 3
      7 years ago
      Hi.

      Yes I’ve followed all the instructions to this point and there are active connections in the fingerprint database on the new server. I have also done exactly as you say for the update of the store’s location but that’s when I get the error I reported.

      I’ll give the Deployment Scanner a try, though.

      Thanks.
    • pj483's avatar
      pj483
      Level 3
      7 years ago

      Deployment Scanner reports issues with collation and the absence of SQLXML. The collation of the EV databases are consistent with each other but different from that of the instance.

      Would either of these cause the issues we're seeing?

      Thanks again.

      • GertjanA's avatar
        GertjanA
        Moderator
        7 years ago

        absence of sqlxml is no issue if you do not use FSA Collation issue is going to be problematic! do not continue if the collation mismatch is indeed existing!

        But, it might be a false alarm. Can you paste the exact lines for a database pls?

        I just ran it on an EV I know has collation issues. If you have a red cross with SQL Collation, and the lines show:

        sqlserver, port: Unmatched default SQL collation: Server: Latin1_General_CI_AI; 

        databasename database: SQL_Latin1_General_CP1_CI_AS.

        then you have to make sure that the collection of the NEW server matches the collation of the OLD server, or at least the collation of the databases. If you do not have the same collation, you WILL run into trouble. Upgrading for instance will not be possible.

  • OldEmployee's avatar
    OldEmployee
    Level 5
    7 years ago

    I saw a similar error during the mgiration.

    I had to login to the server which holds the Vault store and make this change. Ofcourse the directory services had to be started fully (8192 event) on that server.

    My servers are on EV 11.

    • pj483's avatar
      pj483
      Level 3
      7 years ago

      Hi. Sorry when you say "make this change", what change do you mean?

  • pj483's avatar
    pj483
    Level 3
    7 years ago

    Would it be possible to make the connection updates via ODBC and/or registry changes to circumvent whatever issue appears to be causing this alert?

    • GertjanA's avatar
      GertjanA
      Moderator
      7 years ago

      If you moved all databases to the new server:

      edit registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\Directory\DirectoryService, value SQLSErverName to read the servername+ the instance+portnumber (server\instance,port)

      then use C:\Windows\SysWOW64\odbcad32.exe, system dsn. Verify all are correct. Here wyou will see portnumber.

      • pj483's avatar
        pj483
        Level 3
        7 years ago

        Thanks for that. Tried it but unfortunately the original value is still reported inside the Administration Console. I presume it must be stored elsewhere which is why the AC is the documented way to update it.