Backup, Restore and Migrate Server Help

I also have not had any luck with restoring/migrating the management server to a server with a different name and IP address...is this even possible?

Keep in mind that when the server name changes the update locations must also be changed (unless you use a share "somewhere else")

Prerequisite: the key is imported before installing

Scenario 1:

Backup the database and restore it on the new server. Change the updating policies on the new server and reprotect the computers. This follows article 28276 which has an incomplete (IMO steps 7-9 of  Upgrading from Enterprise Console 2 to Enterprise Console 3.x must be done after step 8 of  Upgrading from Enterprise Console 3.x to Enterprise Console 4.0 ) description of a migration process. But this is probably not what you are looking for since reprotecting all computers might not be easy.

Scenario 2:

Backup and restore. Then create an alias in DNS with the old name pointing to the new server. Clients will then connect to the new server. Copy mrinit.conf to the rms subfolders as described in article 14635 steps 1.2.6 and 1.3. Clients will pick up the new RMS configuration with the next update. That's what we've done after the disaster I mentioned.

Scenario 3:

Similar to 2 but you change the RMS configuration in the old CIDs. You don't use the DNS alias but this procedure doesn't work for disaster recovery (unless your CIDs are "somewhere else"). 

It's also my humble opinion that the console should have the option built in to Backup and Restore instead of manually using batch files.

Now I'd guess that "big installations" use other products besides Sophos and that they have their own backup, restore and recovery strategy. So backing up a database and keeping important registry settings is not specific to Sophos. Still it'd be nice to have the option to make a backup of "all the important stuff" (the keys, policies and group structure).

Christian

I also have not had any luck with restoring/migrating the management server to a server with a different name and IP address...is this even possible?

Keep in mind that when the server name changes the update locations must also be changed (unless you use a share "somewhere else")

Prerequisite: the key is imported before installing

Scenario 1:

Backup the database and restore it on the new server. Change the updating policies on the new server and reprotect the computers. This follows article 28276 which has an incomplete (IMO steps 7-9 of  Upgrading from Enterprise Console 2 to Enterprise Console 3.x must be done after step 8 of  Upgrading from Enterprise Console 3.x to Enterprise Console 4.0 ) description of a migration process. But this is probably not what you are looking for since reprotecting all computers might not be easy.

Scenario 2:

Backup and restore. Then create an alias in DNS with the old name pointing to the new server. Clients will then connect to the new server. Copy mrinit.conf to the rms subfolders as described in article 14635 steps 1.2.6 and 1.3. Clients will pick up the new RMS configuration with the next update. That's what we've done after the disaster I mentioned.

Scenario 3:

Similar to 2 but you change the RMS configuration in the old CIDs. You don't use the DNS alias but this procedure doesn't work for disaster recovery (unless your CIDs are "somewhere else"). 

It's also my humble opinion that the console should have the option built in to Backup and Restore instead of manually using batch files.

Now I'd guess that "big installations" use other products besides Sophos and that they have their own backup, restore and recovery strategy. So backing up a database and keeping important registry settings is not specific to Sophos. Still it'd be nice to have the option to make a backup of "all the important stuff" (the keys, policies and group structure).

Christian