4 4 3:Migrate Sesam Server to New Hardware

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2019. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

SEP Warning.png Warning

This manual is intended for advanced SEP sesam administrators only. Customers are not supposed to migrate the SEP sesam Server by this manual. Executing such an action is at your own risk! For a supported system migration, contact SEP sesam support for remote consulting. Customers migrating by these steps will lose support by SEP for the server installation!

Introduction

To migrate the SEP sesam server installation to new hardware without changing the host name and IP address (only possible with the same OS on both installations), there are three main components that need to be moved. The SEP sesam software itself, the SEP sesam database, backups, license and configuration files. In case you have to change the hostname and IP address follow the notes at the end of the article.

Before the move

First be sure to have a good and current Sesam_Backup and a Sesam bootstrap file that should be emailed by the sm_disaster script every new day. The new hardware should have the OS installed and networking functioning.

The Sesam Database

The Sesam database contains all the configuration of Sesam, including client configuration and tracking the backup savesets. The bootstrap file mentioned above is a copy of this database but here is how to create an additional copy through the command line.

  • first source the profile in a terminal.
   * In linux systems that command is source /var/opt/sesam/var/ini/sesam2000.profile
   * In windows systems: C:\"program files"\sepsesam\var\ini\sm_prof.bat
  • next export the database to a file
   * in the terminal 
          sm_db export -f <path to file>/<name of file>.sql
          for example, if we wanted to export the database to /home/root/ in linux the command would be 
          sm_db export -f /home/root/sesamdb.sql
  • Open the exported file and be sure that the database exported correctly.
  • Copy that file to the new hardware.

Install on the new hardware

  • Install sesam on the new hardware. Use the same version installed on the old hardware to prevent database mismatches.

Other files needed from the old hardware

  • /var/opt/sesam/var/directory (or C:\program files\sepsesam\var\ - do not copy the whole var-directory!)
    • Copy the complete /lis directory to the new server
    • Copy the /ini/sm_lic.ini to the new server
    • Copy the /ini/sm_ssh to the new server
    • Copy the /times to the new server
    • Copy the /ini/sm_java.policy to the new server
    • Just in case of an update issue, copy the complete /db directory to the new server
  • From the /opt/sesam/bin/sesam directory (C:\program files\sepsesam\bin\sesam) Copy the sm_alarm, sm_disaster and sm_notify scripts. To a safe location on the new hardware. this will preserve any customization done to these scripts.
  • Copy the path of any datastores that are stored on the old hardware to the exact same path on the new hardware. for example. if the datastore was at the path /Backups on the old hardware it will need to be copied to /Backups on the new hardware. Otherwise Sesam will not be able to find the backups stored on the new hardware. This copy can take a long time depending on the amount of backups saved in the datastore.

Import Sql file to new hardware database

  • First open a terminal and source the Sesam profile as before.
  • import a empty Database from the directory <SESAM_ROOT>/skel/db/(sqlite)or(postgres)/sesam_db.sql
    • Windows
sm_db import -n -f "c:\Program Files\SEPsesam\skel\db\sqlite\sesam_db.sql"


    • Linux
sm_db import -n -f /opt/sesam/skel/db/postgres/sesam_db.sql
  • import the the sql file form the old hardware.
  sm_db import -n -f /<path to file>/<file>.sql 

in our example assuming the file was copied to /home/root/ on the new server

  sm_db import -n -f /home/root/sesamdb.sql

at the end, this is very important for Linux, import the sesam_insert_start.sql because triggers are set and other important adjustments are made with it

  sm_db import -n -f /opt/sesam/skel/db/postgres/sesam_insert_start.sql

restart Sesam service

In the same terminal enter

  sm_main restart
to restart the service

finally, check that the configuration and backups have imported successfully. Open a restore window and be sure that backups are seen in the wizard.


Notes

  • if the new SEP sesam Server has a different ip address or hostname you have to work with the command sm_setup change_servername new-server-name
  • if the new SEP sesam Server has a different ip address or hostname a new license will need to be acquired. please contact Sesam Sales.
  • if the server hostname or ip address has changed all clients hosts, files will need to be updated with the new entry.
  • also each client will need to have this command entered in a terminal first source the sesam profile
 sm_setup set_client <server fully qualified domain name> 

where <server fully qualified domain name> is the FQDN of the new sesam server.