FAQ

Migration der Safend Protector Datenbank

Bei diesem Knowledge Base Artikel handelt es sich um einen Archiveintrag, der 1:1 aus den FAQv1 Beiträgen übernommen wurde. Er dient dazu, auch Lösungen für ältere Versionen nach wie vor anzubieten und durchsuchbar zu machen.

Archiv

Sie haben Safend Protector 3.2 installiert und wollen auf die Version 3.3 aktualisieren.
Hierzu gibt der hersteller SAFEND folgende Hinweise:

We recommend upgrading the Server first and then migrating to the new database.

Server upgrade

Follow the Installation Guide. Use the Restore mode described in page 36.

Please note that the SKB file can be used for the upgrade from version 3.2 to 3.3 but the SCB file cannot.

Therefore you will be able to keep communicating with the clients using the old keys, but won't be able to maintain your configuration (policies, queries etc.)

During the upgrade choose using the embedded MySQL DB and not the new MSSQL (this will be done later in order to use the new SCB file).

DB migration

It is not possible migrate from a MySQL DB to a MsSQL DB while maintaining all of the data.

The recommended course of action in this case would be:

  • <!--> <!-[endif]->Backup the Safend keys (to an .skb file) and configuration (to an .scb file) from the console under
    Tools => Administration => Maintenance
  • <!-[endif]->Uninstall the Console & Server, restart and re-install them in Restore installation mode using the keys
    and config backups. (The restore installation mode is described in details in the Installation Guide).
  • <!-[endif]->During the Restore installation mode you'll have the option to connect to a SQL server instead of using a built-in MySQL server.
  • <!-[endif]->Following these steps, you'll maintain communication with the existing clients.
    However you will lose the logs currently stored in your DB and the policy associations.