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

SEC 5.1 Migration

tomerb

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
  • 0

    Hello Thomas,

    do I have to stick by the order mentioned in the migration documentation

    you don't expect me to dissent from the official documentation and suggest otherwise, do you :smileywink:? Last time I've actually migrated a whole production server was, IIRC, before 4.0 - so any experience from then does not apply. I did clone servers for Beta tests though, of course with a different name/IP but the same certificates (in order to be able to move the clients around without reprotecting them). I'd say just doing a full install and then restoring the database could work (on one occasion, think it was for 5.0, I've also imported the old (downlevel) database and manually upgraded it without problems). Please note that this is unsupported - but this might not scare you as you are DR-tested :smileyvery-happy:

    Christian 

    :38993
Reply
  • 0

    Hello Thomas,

    do I have to stick by the order mentioned in the migration documentation

    you don't expect me to dissent from the official documentation and suggest otherwise, do you :smileywink:? Last time I've actually migrated a whole production server was, IIRC, before 4.0 - so any experience from then does not apply. I did clone servers for Beta tests though, of course with a different name/IP but the same certificates (in order to be able to move the clients around without reprotecting them). I'd say just doing a full install and then restoring the database could work (on one occasion, think it was for 5.0, I've also imported the old (downlevel) database and manually upgraded it without problems). Please note that this is unsupported - but this might not scare you as you are DR-tested :smileyvery-happy:

    Christian 

    :38993
Children
No Data