User Tools

Site Tools


migration_guide_from_v3_to_v4

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
migration_guide_from_v3_to_v4 [2019/02/02 16:35] – [v4 Appliance Preparation] spammymigration_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 /usr/local/sbin/EFA-Backup -backup   - sudo /usr/local/sbin/EFA-Backup -backup
   - sudo chmod -R 775 /var/spool/MailScanner/quarantine (to loosen permissions for copy)   - sudo chmod -R 775 /var/spool/MailScanner/quarantine (to loosen permissions for copy)
 +  - sudo chmod -R 775 /var/EFA/backup/* (to loosen permissions for copy)
 +  - sudo sa-learn --backup > /root/backup.txt
  
 If you are using opendkim, do the following If you are using opendkim, do the following
  
-  - sudo chmod -R 775 /etc/opendkim/(only if you are using opendkim)+  - sudo chmod -R 775 /etc/opendkim/*
  
 ===== v4 Appliance Preparation ===== ===== v4 Appliance Preparation =====
Line 35: Line 51:
   - sshfs <nameofv3user>@<ipaddress>:/ /mnt   - sshfs <nameofv3user>@<ipaddress>:/ /mnt
   - cp /mnt/var/EFA/backup/<nameofbackup> /var/eFa/backup (where <nameofbackup> is the name of the backup you generated during v3 preparation)   - cp /mnt/var/EFA/backup/<nameofbackup> /var/eFa/backup (where <nameofbackup> is the name of the backup you generated during v3 preparation)
 +  - chmod 600 /var/eFa/backup/<nameofbackup>     (secure the backup file)
 +  - chown root:root /var/eFa/backup/<nameofbackup>  (secure the backup file)
 +  - cp /mnt/root/backup.txt /root/backup.txt
  
 The following steps apply if you want to keep your quarantine The following steps apply if you want to keep your quarantine
Line 65: 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 "v3" or "v4" extension for any settings you may want to use.  Restore attempts pick the best settings but generates these files for further review.
 +     * /etc/mail/spamassassin
 +     * /etc/MailScanner
 +     * /etc/MailScanner/rules
 +     * /var/www/html/mailscanner/
 +     * /etc/postfix
 +
 +If your bayes database is blank in the MailWatch GUI after migration, run this:
 +
 +  * sudo sa-learn --clear
 +  * sudo sa-learn --restore /root/backup.txt
  
 The following steps apply if you are using opendkim The following steps apply if you are using opendkim
Line 70: Line 100:
   * /etc/postfix/main.cf:     * /etc/postfix/main.cf:  
       * smtpd_milters = inet:127.0.0.1:8891 inet:127.0.0.1:33333       * smtpd_milters = inet:127.0.0.1:8891 inet:127.0.0.1:33333
-      * non_smtpd_miltersinet:127.0.0.1:8891+      * non_smtpd_milters inet:127.0.0.1:8891
   * sudo systemctl enable opendkim   * sudo systemctl enable opendkim
   * sudo systemctl start opendkim   * sudo systemctl start opendkim
   * sudo systemctl reload postfix   * 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.1549125349.txt.gz · Last modified: 2019/02/02 16:35 by spammy