I have recently been asked to consolidate our current three sophos server into one server (move everything to server #3). The configuration is below:
OS - Windows 2003 server R2, SP2
domain - one
servers - 3
Server #1 - manages computer group 1
Server #2 - manages computer group 2
Server # 3 - manages computer group 3
Each server has its own SEC
SEC version 3.11
SQL 2000 standard for each of the server
My questions are:
Can you merge the three databased into one? Since the data structure is the same for the three servers, can you use SQL import/export to add the addition data?
Assumming the database can and has been "merged" into one, what do I need to do to make sure clients from server #1 and server #2 will talk/report to the new (server #3).
I'll start with question 2. Iff the servers have been set up to use the same certificate (which is unfortunately rarely the case) then it's just putting a custom mrinit.conf in the CIDs and clients will "move" to the desired server.
Q1: the databases can't be merged for a number of reasons. First and foremost the pivotal table numbers the computers sequentially (with the server having ComputerID 1).
If the servers use different certificates you'd have to uninstall Sophos from the clients in two of the three groups.
The answer may depend on why you want to merge them. If it's for reporting purposes you could ask support about CMV; this is a product that can consolidate multiple management servers to a central server using SQL replication. It's quite a bit of work to set up but could be an option if that's the sole reason.
If it's for management purposes it would be extremely tricky to merge the data as said before and totally unsupported and probably leave a lot of doubt over the integrity of the system. So it looks like you may have to loose the historical data of two thirds of your machines, at least in a live system. You can always backup the databases and point a management server at them 'off-line' if you need to go back and check anything or run SQL queries at the databases for reporting on the old data.
To point the clients at the new server you might be best off just re-protecting them, however If the download bandwidth required to do this is unthinkable you could see if support have any RMS re-init scripts for clients to help them point to the new server and obtain new certificates.
Quote