Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 1 subscriber
  • Views 23371 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

Sophos Enterprise 5.2 migration

svdb

Hello,

We have:

Server1: (windows 2003) Database service (5.2)

Server2: (windows 2003) Sophos management server (5.2)

we want to migrate the Server 2 installation (w2k3) to a new server (Server3: W2K8), en i will keep the Server 1 installation.

I read the article "http://www.sophos.com/en-us/support/knowledgebase/28276.aspx" but the first note tells me:

  • These instructions apply only to installations that used the default settings. In particular, it does not apply to installations where the database and/or the management service are located on a different server to the console.  For further information on installing or upgrading a management server with a remote database see article 33980.

The article 33980 isn't in my opinion not the right one.

can anybody tell me how to migrate the Windows 2003 (Server 2) installation to Windows 2008 (server 3) ?

:38093


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

    Hello Vikas,

    the database has almost all the information, endpoints and their grouping, policies, events. You don't have to restore the database (as long as its and SEC's version match), you continue to use the existing (remote) database with a newly installed management server.

    The difference between method 1 and 2 is that the latter keeps the identity of the management server. The identity is not IP or name but kinda ID card the server presents to the endpoints. When the software is installed the endpoints make note of this ID and from then on they only talk (that is communicate via RMS) to a server presenting this very ID.

    Method 1 is simpler but (arguably) less elegant and requires that all endpoints are reprotected.

    What's not working? When installing the management server the old database (whether it has been pointed to in the dialog or imported after installation of the database component) must be present so that the entry for the old management server can be updated to reflect the new one. If you restore the database after the management server has been installed it won't be consistent.

    Christian

    :56116
Reply
  • 0

    Hello Vikas,

    the database has almost all the information, endpoints and their grouping, policies, events. You don't have to restore the database (as long as its and SEC's version match), you continue to use the existing (remote) database with a newly installed management server.

    The difference between method 1 and 2 is that the latter keeps the identity of the management server. The identity is not IP or name but kinda ID card the server presents to the endpoints. When the software is installed the endpoints make note of this ID and from then on they only talk (that is communicate via RMS) to a server presenting this very ID.

    Method 1 is simpler but (arguably) less elegant and requires that all endpoints are reprotected.

    What's not working? When installing the management server the old database (whether it has been pointed to in the dialog or imported after installation of the database component) must be present so that the entry for the old management server can be updated to reflect the new one. If you restore the database after the management server has been installed it won't be consistent.

    Christian

    :56116
Children
No Data