FAQ

Archiv

NEED

From time to time there is a need to migrate the Safend Management Server to a different machine while maintaining the communication with all the Clients.

SOLUTION

Basically, the Safend Management Server migration is straight forward and simple.This goal of this procedure is to verify the integrity of the various Safend components in the environment following the migration. This is mainly important for large environments with many Clients.

1. Before the migration, make sure you have relevant backups.
   It is recommended to backup manually just prior to the migration, even if you do have scheduled backups.

   From the Console backup the Safend System file (SYB) or the Safend Keys and Configuration files (SKB+SCB), depending on the version you have (SYB from version 3.3 SP3 and above).
   If using an MSSQL DB, you should also take a DB backup, and if using a virtual machine you should also take a machine snapshot.

2. Keep the old Server running until the migration process is finished correctly.Important Note!
   The Server installation file you use for the next step must be from the exact same version as your original Server.
3. On the new Server machine run a Server installation and choose the Restore option.* In case you are using an external MSSQL DB:
   Choose to restore from an existing DB and direct the Server to the existing MSSQL DB.
   Make sure the DB user you use is the same one that performed the original installation.

   * In case you are using an embedded MySQL DB:
   Choose to restore using the backup files and point to the relevant files and enter the password when asked for during the installation.

4. Test basic Server functionality
   Open all tabs, create a new policy, modify an existing policy, query on some logs, run a report (if Reporter module exists), etc.
5. Once the Server functionality is verified you can migrate the Clients from the old Server to the new one.Clients communicate with the Server according to its name, and you have two options to maintain the communication between the Clients and the new Server:
   1. Change the old Server machine name and rename the new Server to the original Server name.
      If this is done, you will have to update the new Server certificate as explained in the solution "Generate a new certificate and replace it on the Safend Server".
      No action will be required on the Clients side.
   2. If you did not rename the new Server name to the original name:
      In the new Server machine save and publish all policies and from the Clients tab send an Update Policy command to all the Clients.
      This will notify the Clients of the new Server (which has the same keys as the original one).
6. Verify you are able to update a policy and that it gets updated on a Client machine.
7. Verify you are able to receive logs from a Client in the Console.
8. Once all the above is done and verified, you should uninstall the old Server.

*Note that the steps are the same regardless of the platforms (32/64 bit), as long as both operating systems are supported for your specific version.