You run the 4.7 installer on the new database server, and choose to just add the database. If you don't have an existing SQL instance to use it will create you one called Sophos again. I assume however you're moving this to an existing SQL server?
Either way, say this SQL server is a member server for your domain, you'll end up with a new local group on that computer called "Sophos DB Admins". You will then need to create an account, domain account is fine and call it "SophosManagement" for example and add it to the local "SOphos DB admins" group on the new database server.
Note: This account needs to be able to log on to the existing manageemnt server and will be used by the management service to access the database.
You'll also end up with the SOPHOS47 database but it will be blank at this stage.
I would then Close SEC on your existing management server and stop the services: "Sophos management server" "Sophos Message Router" Then take a backup of SOPHOS47 using backupdb.bat (http://www.sophos.com/en-us/support/knowledgebase/110380.aspx). So essentially you are going to be running:
You then need to copy this database backup file: "sophos47db.bak" to the new SQL server (C:\windows\temp\) and then restore it to the database on there using restoredb.bat:. E.g.
You now have the database restored and corrected on the new SQL server , you just need to point the existing management server at it.
Then you modify the install on the existing managament server to remove the database component, this will then prompt for where the database is, you then choose the new SQL server and instance name, you then chose the "SophosManagement" account as this has access to the database.
You can remove the local SQL instance as requried once happy it's all working.
You run the 4.7 installer on the new database server, and choose to just add the database. If you don't have an existing SQL instance to use it will create you one called Sophos again. I assume however you're moving this to an existing SQL server?
Either way, say this SQL server is a member server for your domain, you'll end up with a new local group on that computer called "Sophos DB Admins". You will then need to create an account, domain account is fine and call it "SophosManagement" for example and add it to the local "SOphos DB admins" group on the new database server.
Note: This account needs to be able to log on to the existing manageemnt server and will be used by the management service to access the database.
You'll also end up with the SOPHOS47 database but it will be blank at this stage.
I would then Close SEC on your existing management server and stop the services: "Sophos management server" "Sophos Message Router" Then take a backup of SOPHOS47 using backupdb.bat (http://www.sophos.com/en-us/support/knowledgebase/110380.aspx). So essentially you are going to be running:
You then need to copy this database backup file: "sophos47db.bak" to the new SQL server (C:\windows\temp\) and then restore it to the database on there using restoredb.bat:. E.g.
You now have the database restored and corrected on the new SQL server , you just need to point the existing management server at it.
Then you modify the install on the existing managament server to remove the database component, this will then prompt for where the database is, you then choose the new SQL server and instance name, you then chose the "SophosManagement" account as this has access to the database.
You can remove the local SQL instance as requried once happy it's all working.
