Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 29 replies
  • Subscribers 1 subscriber
  • Views 25683 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Transfer SophosDB to remote server

tedz

Hi,

Need advice to transfer my sophosDB in a central console to remote server. 

Running SEC 4.7 

updrage to SEC 5.1 

what is the steps to do this? 

Regards,

tedz

:28377


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    The fact that you could see the SOPHOS47 database when you created a UDL test file (I assume this UDL test file looks similar to the connection string registry key the management service uses) to test connectivity to the SQL database from the management server the error would suggest permissions problems of the user SophosManagement.

    That UDL test was run as you, where as the management service is trying to connect as the SophosManagement account.

    A good test now would be... on the SQL server create a command prompt running as SophosManagement user.
    E.g in a command prompt type:
    runas /user:[domain]\SophosManagement cmd
    In this new CMD window running as SophosManagement , then execute a SQL command against the SQL server.

    SQLCMD -E -S .\sophos -d SOPHOS47 -Q "exec dbo.SDDMBootstrapDataGet"

    This should return some XML rather than an error. If it errors, what is shown?


    Note: Ideally you would run this SQLCMD test on the management server to connect to the remote SQL instance but as the management server probably doesn't have sqlcmd, testing permssions on the SQL server is ok.


    Otherwise:

    Can you:
    1. Check that "SophosManagement" user can log onto the SQL server (The above test does this)

    2. DROP the Sophos DB Admins Login. To do so, on the SQL Server run:
    sqlcmd -E -S .\sophos -Q "DROP LOGIN [SERVERNAME\Sophos DB Admins]"

    Where:
    SERVERNAME should be replaced with the NetBIOS form of the computer name of the SQL server.
    I assume the SQL instance is called SOPHOS.

    3. Re-create the Login. On the SQL Server run:
    sqlcmd -E -S .\sophos -Q "CREATE LOGIN [SERVERNAME\Sophos DB Admins] FROM WINDOWS"

    Where:
    SERVERNAME should be replaced with the NetBIOS form of the computer name of the SQL server.
    I assume the SQL instance is called SOPHOS.

    4. On the SQL server run:
    sqlcmd -E -S .\SOPHOS -d SOPHOS47 -i C:\ResetUserMappings.sql

    Where:
    I assume the SQL instance is called SOPHOS.
    the SQL file can be obtained from here: http://sophserv.sophos.com/repo_kb/111898/file/ResetUserMappings.sql.txt

    5. Ensure that "SophosManagement " is a member of the "Sophos DB Admins" group on the SQL Server.

    6. Start the management service.

    Regards,
    Jak


    Note:
    As for the errors with running SQLcmd, sqlcmd -E -S .\sophos -Q "SOPHOS47" is wrong it should be:
    sqlcmd -E -S .\sophos -Q "select name from sysdatabases"
    But as the UDL test from the management server to the SQL server listed the database it's a bit mute.

    :28895
Reply
  • 0

    Hi,

    The fact that you could see the SOPHOS47 database when you created a UDL test file (I assume this UDL test file looks similar to the connection string registry key the management service uses) to test connectivity to the SQL database from the management server the error would suggest permissions problems of the user SophosManagement.

    That UDL test was run as you, where as the management service is trying to connect as the SophosManagement account.

    A good test now would be... on the SQL server create a command prompt running as SophosManagement user.
    E.g in a command prompt type:
    runas /user:[domain]\SophosManagement cmd
    In this new CMD window running as SophosManagement , then execute a SQL command against the SQL server.

    SQLCMD -E -S .\sophos -d SOPHOS47 -Q "exec dbo.SDDMBootstrapDataGet"

    This should return some XML rather than an error. If it errors, what is shown?


    Note: Ideally you would run this SQLCMD test on the management server to connect to the remote SQL instance but as the management server probably doesn't have sqlcmd, testing permssions on the SQL server is ok.


    Otherwise:

    Can you:
    1. Check that "SophosManagement" user can log onto the SQL server (The above test does this)

    2. DROP the Sophos DB Admins Login. To do so, on the SQL Server run:
    sqlcmd -E -S .\sophos -Q "DROP LOGIN [SERVERNAME\Sophos DB Admins]"

    Where:
    SERVERNAME should be replaced with the NetBIOS form of the computer name of the SQL server.
    I assume the SQL instance is called SOPHOS.

    3. Re-create the Login. On the SQL Server run:
    sqlcmd -E -S .\sophos -Q "CREATE LOGIN [SERVERNAME\Sophos DB Admins] FROM WINDOWS"

    Where:
    SERVERNAME should be replaced with the NetBIOS form of the computer name of the SQL server.
    I assume the SQL instance is called SOPHOS.

    4. On the SQL server run:
    sqlcmd -E -S .\SOPHOS -d SOPHOS47 -i C:\ResetUserMappings.sql

    Where:
    I assume the SQL instance is called SOPHOS.
    the SQL file can be obtained from here: http://sophserv.sophos.com/repo_kb/111898/file/ResetUserMappings.sql.txt

    5. Ensure that "SophosManagement " is a member of the "Sophos DB Admins" group on the SQL Server.

    6. Start the management service.

    Regards,
    Jak


    Note:
    As for the errors with running SQLcmd, sqlcmd -E -S .\sophos -Q "SOPHOS47" is wrong it should be:
    sqlcmd -E -S .\sophos -Q "select name from sysdatabases"
    But as the UDL test from the management server to the SQL server listed the database it's a bit mute.

    :28895
Children
No Data