migration_guide_from_v3_to_v4
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| migration_guide_from_v3_to_v4 [2019/02/02 16:33] – [v4 Appliance Preparation] spammy | migration_guide_from_v3_to_v4 [2019/12/03 02:11] (current) – [v4 Commission] spammy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Migration Guide from eFa v3 to eFa v4 (Live Migration) | + | ====== Migration Guide from eFa v3 to eFa v4 ====== |
| + | |||
| + | ===== Overview ===== | ||
| + | |||
| + | Migrating from v3 to v4 is possible using the backup and restore functionality of eFa. | ||
| + | |||
| + | The process involves doing the following: | ||
| + | |||
| + | - Initial preparation (fact gathering) | ||
| + | - Preparing v3 appliance | ||
| + | - Preparing the v4 appliance | ||
| + | - Shutting down the v3 appliance | ||
| + | - Configuring the v4 appliance and running a restore | ||
| + | |||
| + | If successful, all databases will be transferred to v4 with upgraded schema and compatible settings will be transferred. | ||
| ===== Preparation ===== | ===== Preparation ===== | ||
| Line 22: | Line 36: | ||
| - sudo / | - sudo / | ||
| - sudo chmod -R 775 / | - sudo chmod -R 775 / | ||
| + | - sudo chmod -R 775 / | ||
| + | - sudo sa-learn --backup > / | ||
| If you are using opendkim, do the following | If you are using opendkim, do the following | ||
| - | - sudo chmod -R 775 / | + | - sudo chmod -R 775 / |
| ===== v4 Appliance Preparation ===== | ===== v4 Appliance Preparation ===== | ||
| Line 34: | Line 50: | ||
| - yum install sshfs | - yum install sshfs | ||
| - sshfs < | - sshfs < | ||
| + | - cp / | ||
| + | - chmod 600 / | ||
| + | - chown root:root / | ||
| + | - cp / | ||
| + | |||
| + | The following steps apply if you want to keep your quarantine | ||
| + | |||
| - cp -ra / | - cp -ra / | ||
| - chmod -R 750 / | - chmod -R 750 / | ||
| - chown -R postfix: | - chown -R postfix: | ||
| - | | + | |
| The following steps apply if you are using opendkim | The following steps apply if you are using opendkim | ||
| Line 62: | Line 84: | ||
| * Let system reboot | * Let system reboot | ||
| * Log into console and drop to shell | * Log into console and drop to shell | ||
| + | * Review files with a " | ||
| + | * / | ||
| + | * / | ||
| + | * / | ||
| + | * / | ||
| + | * / | ||
| + | |||
| + | If your bayes database is blank in the MailWatch GUI after migration, run this: | ||
| + | |||
| + | * sudo sa-learn --clear | ||
| + | * sudo sa-learn --restore / | ||
| The following steps apply if you are using opendkim | The following steps apply if you are using opendkim | ||
| Line 67: | Line 100: | ||
| * / | * / | ||
| * smtpd_milters = inet: | * smtpd_milters = inet: | ||
| - | * non_smtpd_milters: inet: | + | * non_smtpd_milters |
| * sudo systemctl enable opendkim | * sudo systemctl enable opendkim | ||
| * sudo systemctl start opendkim | * sudo systemctl start opendkim | ||
| + | * sudo systemctl reload postfix | ||
| - | + | If you use 3rd party virus scanners, those will need to be installed on the new appliance. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
migration_guide_from_v3_to_v4.1549125192.txt.gz · Last modified: 2019/02/02 16:33 by spammy
