==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this
link:http://bugs.contribs.org/show_bug.cgi?id=7633
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
--- Comment #55 from turandot <[email protected]> ---
All,
today I tested quite a bit. The summary is:
- affa 3 seems to work properly.
- There are a few pitfalls you need to avoid.
- Migration from SME 8.1 (32 Bit) to SME 9.0 (32 Bit) tested successfully.
Please regret that I had to translate the WebGUI back to English: I am working
with a German GUI. So don't trust blindly in the steps below. Actually the
information could be transferred to http://wiki.contribs.org/Affa if other
people confirm that all works as expected.
So here is the step by step procedure for migration from SME 8.1 to 9.0. This
should work with any other SME combination as well, but I haven't tested it
yet.
- Make a fresh install on new hardware using the SME 9.0 32 Bit CDROM. Example
settings:
-- Domain name: athome.xx (use your existing domain name)
-- Host name: smebackup (must not match to existing host)
-- IP address: 192.168.0.10 (must not match to existing IP address)
-- Subnet: 255.255.255.0
-- role: Server only
-- Gateway: 192.168.0.1 (use your existing gateway)
-- DHCP: DEactivate
-- DNS server: 192.168.0.1 (use your existing DNS server)
-- activate changes: yes
-- The fresh server will then restart with the above settings.
- Update your fresh server:
-- Login as user root on local console.
-- Use 'top' command to display running jobs. Wait until 'yum' stopped running.
-- yum clean all
-- yum update
-- The fresh server will be updated.
-- signal-event post-upgrade
-- signal-event reboot
-- The server will reboot.
- Basic configure of your fresh server
-- Login as admin through the WebGUI:
https://smebackup.athome.xx/server-manager/
-- click to "Security / Remote access", there activate:
--- Secure access by SSH: allow access limited to local network
--- Allow admin commands via secure SSH connection: yes
--- Allow secure SSH connection with standard password: yes
-- Click Save
- Install affa 3
-- Login as root on local or remote SSH console.
-- mkdir /root/affa3
-- cd /root/affa3
-- wget
http://pkgs.repoforge.org/perl-Config-IniFiles/perl-Config-IniFiles-2.56-1.el6.rf.noarch.rpm
--> Caveat: if you use a fresh SME 8.1, then use wget
http://pkgs.repoforge.org/perl-Config-IniFiles/perl-Config-IniFiles-2.56-1.el5.rf.noarch.rpm
-- wget
http://pkgs.repoforge.org/perl-Filesys-DiskFree/perl-Filesys-DiskFree-0.06-1.2.el6.rf.noarch.rpm
--> Caveat: if you use a fresh SME 8.1, then use wget
http://pkgs.repoforge.org/perl-Filesys-DiskFree/perl-Filesys-DiskFree-0.06-1.2.el5.rf.noarch.rpm
-- wget
http://pkgs.repoforge.org/perl-Proc-ProcessTable/perl-Proc-ProcessTable-0.45-1.el6.rf.i686.rpm
--> Caveat: if you use a fresh SME 8.1 32 Bit, then use wget
http://pkgs.repoforge.org/perl-Proc-ProcessTable/perl-Proc-ProcessTable-0.45-1.el5.rf.i386.rpm
--> Caveat: if you use a fresh SME 8.1 64 Bit, then use wget
http://pkgs.repoforge.org/perl-Proc-ProcessTable/perl-Proc-ProcessTable-0.45-1.el5.rf.x86_64.rpm
--> Caveat: if you use a fresh SME 9.0 64 Bit, then use wget
http://pkgs.repoforge.org/perl-Proc-ProcessTable/perl-Proc-ProcessTable-0.45-1.el6.rf.x86_64.rpm
-- wget
http://www.guedel.eu/phocadownload/uploads_AG/smeserver-affa-3.2.2.0-0.noarch.rpm
--> Caveat: the server http://www.guedel.eu/ seems to be down at the moment. I
will try to add the RPM to this bugtracker later.
-- yum localinstall --enablerepo=smecontribs
smeserver-affa-3.2.2.0-0.noarch.rpm
perl-Config-IniFiles-2.56-1.el6.rf.noarch.rpm
perl-Filesys-DiskFree-0.06-1.2.el6.rf.noarch.rpm
perl-Proc-ProcessTable-0.45-1.el6.rf.i686.rpm
--> Caveat: be careful to install correct packages for your fresh SME. Adapt
package names accordingly.
-- signal-event post-upgrade
-- signal-event reboot
-- The fresh server will reboot.
- Patch and configure affa 3
-- Login as root on local or remote SSH console.
-- cd /sbin
-- rm affa
-- Copy patched version 3.2.2-1 (see header of affa script) from
http://bugs.contribs.org/show_bug.cgi?id=7633#c41 to /sbin/affa using e.g. scp
or FileZilla to /sbin/affa
-- chmod 0750 affa
-- create /etc/affa/sme-backup.conf ('sme-backup' is the jobname in this
example; change to whatever you like). I will try to add my example job
separately.
-- mkdir /var/affa
-- affa --configcheck (should throw out no errors; this was the step where I
received errors when I made mistakes in the above configuration)
- Run affa for test purposes
-- Login as root on local or remote SSH console.
-- affa --send-key sme-backup
--- Job sme-backup: Generating DSA keys...
--- Successfully created DSA key pair.
--- [email protected]'s password: <Enter password>
--- Public key sent to 192.168.0.2
-- affa --run sme-backup
--- The authenticity of host 'sme-backup (192.168.0.2)' can't be established.
--- RSA key fingerprint is 3b..........65.
--- Are you sure you want ton continue connecting (yes/no)? <yes>
-- affa –-list-archives (check that your first archive is available)
-- affa --run sme-backup (note that you won't be asked for the password again)
-- affa –-list-archives (check that your second archive is available)
>From here you should be able to work with affa 3 as earlier with affa 2. Refer
to e.g. http://wiki.contribs.org/Affa .
- Rise fresh SME 9.0
-- Login as root on local or remote SSH console.
-- affa -–rise sme-backup
-- Once the rise command is finished, shut down your old server.
-- Then reboor the fresh hardware.
Test and enjoy your fresh hardware with SME 9.0!
Regards, turandot
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
