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

SEC 5.1 Migration

Hello,

I'm planning the migration of a SEC 5.1 installation to a new server according to the documentation found here:

http://www.sophos.com/en-us/medialibrary/PDFs/migration/sec_51_mgeng.pdf

I just want to make sure that I didn't overlook anything.

Old and new server are both Windows 2003 32Bit, so I suppose there won't be much trouble here.

At the end, the new server is supposed to have the same identity as the old one. Apart from the fact that I have to take done the old server before setting up the new one, I don't see any issues here, either.

All clients are currently offline and are meant to stay that way until the end of the migration. This means that there will be no way of pushing out updating policies before migration.

I do not have the password for the SophosUpdateMgr user, but from my understanding I don't need it.

I'm not using Sophos Encryption.

So my idea was to do all the necessary steps on the old server, copy the files, take it down, install the new server with the same identity and then perform the steps described in the documentation on the new server. Is it correct that after that the clients will get a new update policy from the new server which of course includes the new password for the SophosUpdateMgr?

:38963


This thread was automatically locked due to age.
Parents
  • you don't expect me to dissent from the official documentation and suggest otherwise, do you

    Of course not. It has always been my intention to stick to the official documentation. All I'm asking is: Which one?

    We have the server migration guide http://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_51_mgeng.pdf dated June 2012. Since what I was doing was a very special case of a server migration, using that seems to be a good idea. (I went through it without any errors and I'm very optimistic that when the clients come back on, everything will work as expected.) The downside of this documentation is, that it's quite a lot of work.

    Then there is the backup/restore guide http://www.sophos.com/en-us/support/knowledgebase/114299.aspx which seems to exactly describe my use case and is much simpler. It was last updated two weeks ago. It does, however, at one point refer to the migration guide, though not in a way that explicitly suggests that all the steps described there are to be applied. ;-)

    To make it short:

    I consider creating a scheduled task based on what's written in the backup/restore guide and copy that data to an external device. After that I'd like to be fairly confident to be able to make a DR using that data on a fresh install. ;-)

    :38999
Reply
  • you don't expect me to dissent from the official documentation and suggest otherwise, do you

    Of course not. It has always been my intention to stick to the official documentation. All I'm asking is: Which one?

    We have the server migration guide http://www.sophos.com/en-us/medialibrary/PDFs/documentation/sec_51_mgeng.pdf dated June 2012. Since what I was doing was a very special case of a server migration, using that seems to be a good idea. (I went through it without any errors and I'm very optimistic that when the clients come back on, everything will work as expected.) The downside of this documentation is, that it's quite a lot of work.

    Then there is the backup/restore guide http://www.sophos.com/en-us/support/knowledgebase/114299.aspx which seems to exactly describe my use case and is much simpler. It was last updated two weeks ago. It does, however, at one point refer to the migration guide, though not in a way that explicitly suggests that all the steps described there are to be applied. ;-)

    To make it short:

    I consider creating a scheduled task based on what's written in the backup/restore guide and copy that data to an external device. After that I'd like to be fairly confident to be able to make a DR using that data on a fresh install. ;-)

    :38999
Children
No Data