Differences

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

--- migration_guide_from_v3_to_v4 [2019/02/02 05:14] – [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 =====
@@ Line 22: / Line 36: @@
   - sudo /usr/local/sbin/EFA-Backup -backup
   - sudo chmod -R 775 /var/spool/MailScanner/quarantine (to loosen permissions for copy)
-  - sudo chmod -R 775 /etc/opendkim/* (only if you are using opendkim)
+  - 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
+  - sudo chmod -R 775 /etc/opendkim/*
 ===== v4 Appliance Preparation =====
-  - Build a v4 testing using any means
+  - Build a v4 testing using any means with sufficient storage
-  - (Recommended) Do not set it up yet, this uses DHCP (if no DHCP, set a temporary static IP in /etc/sysconfig/network-scripts)
+  - Do not set it up yet (if no DHCP, set a temporary static IP in /etc/sysconfig/network-scripts)
   - Start eFa first-time configure (Y/n) -> n
   - yum install sshfs
   - 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)
+  - 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
   - cp -ra /mnt/var/spool/MailScanner/quarantine/* /var/spool/MailScanner/quarantine (transfers entire quarantine to new appliance, if prompted for overwrite, answer no)
   - chmod -R 750 /var/spool/MailScanner/quarantine/*
   - chown -R postfix:mtagroup /var/spool/MailScanner/quarantine/*
-  - cp /mnt/var/EFA/backup/<nameofbackup> /var/eFa/backup (where <nameofbackup> is the name of the backup you generated during v3 preparation)
 The following steps apply if you are using opendkim
@@ Line 59: / Line 84: @@
   * Let system reboot
   * Log into console and drop to shell
-  * /etc/postfix/main.cf:
+  * 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.
-      * smtpd_milters = inet:127.0.0.1:8891 inet:127.0.0.1:33333 (if using dkim)
+     * /etc/mail/spamassassin
-      * non_smtpd_milters: inet:127.0.0.1:8891 (if using dkim)
+     * /etc/MailScanner
-  * sudo systemctl enable opendkim (if using dkim)
+     * /etc/MailScanner/rules
-  * sudo systemctl start opendkim (if using dkim)
+     * /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
+  * /etc/postfix/main.cf:
+      * smtpd_milters = inet:127.0.0.1:8891 inet:127.0.0.1:33333
+      * non_smtpd_milters = inet:127.0.0.1:8891
+  * sudo systemctl enable 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.