Topic: SME 6 => SME 7 migration.

[raem]

Probably requires a
/sbin/e-smith/signal-event pre-backup

See alternative method for restoring directly from disk

http://forums.contribs.org/index.php?topic=30745.msg144369#msg144369

see my original post of 19 Sept revised 24 Sept

[netspirit]

Hi Ray,
Sorry for late reply. So I did a lot of migration since my last message here and everytime I had to copy manually all databases from the old server to new one but it is working as per your idea. So thanks a lot !

An happy SME 7.0 user from France

[netspirit]

Hi all,
I found after few days of several migrations from 6.0.01 to 7.0 some big problem for us. In fact it is inside MySQL. Installing PHPmyadmin-multiuser (last release which is PHPMYADMIN 2.9.0.2) has shown us the problem. We can't connect with it properly, we are log-off after each refresh or action inside PHPMyAdmin and we need to set again the langage on the logon page before login again. It's returning always to UTF8 langage which is avoiding us to log-in with an error message saying :"#1045 - Access denied for user 'admin'@'localhost' (using password: YES)". But if we set the langage as ISO-8859-1, we can log in again.
Inside MySQL we found that all migrated databases are in collation : ISO-8859-1 and new ones are in UTF-8 like MYSQL.
So is this a normal consequence of our migration? If yes, is there a solution to solve this or not?
I do not know how to do today and searching, searching...

Regards

[raem]

netspirit

> Inside MySQL we found that all migrated databases are in collation :
> ISO-8859-1 and new ones are in UTF-8 like MYSQL.
> So is this a normal consequence of our migration?

That sounds like something you should be reporting to the bugtracker.
That approach may also be the quickest way to resolve your issues.

[actron]

Log in as root to the local (new) server, enter
cd /root/.ssh
ssh-keygen -t rsa
(choose a randomish name eg "keyname" and press enter twice when prompted for a passphrase)

chmod 600 keyname*
scp keyname.pub [ip of remote server]:/root/.ssh/
(enter root password)

- Now connect to the Old server (replace 192.168.1.1 with actual ip)
ssh 192.168.1.1
(log on as root)
cd /root/.ssh

if [ ! -f authorized_keys ]; then touch authorized_keys ; chmod 600 authorized_keys ; fi
(above "if" command should all be on one line)
cat keyname.pub >> authorized_keys
rm -f keyname.pub
exit

tried, but it does not work.

[byte]

Log in as root to the local (new) server, enter
cd /root/.ssh
ssh-keygen -t rsa
(choose a randomish name eg "keyname" and press enter twice when prompted for a passphrase)

chmod 600 keyname*
scp keyname.pub [ip of remote server]:/root/.ssh/
(enter root password)

- Now connect to the Old server (replace 192.168.1.1 with actual ip)
ssh 192.168.1.1
(log on as root)
cd /root/.ssh

if [ ! -f authorized_keys ]; then touch authorized_keys ; chmod 600 authorized_keys ; fi
(above "if" command should all be on one line)
cat keyname.pub >> authorized_keys
rm -f keyname.pub
exit

tried, but it does not work.

Can you tell us what you mean by it does not work? i.e which bit didnt work?

[actron]

Can you tell us what you mean by it does not work? i.e which bit didnt work?

Excuse, i was not clearly enough
want to say, all of this work. but password must always enter.

[jfarschman]

Brian,

  Thanks for this.  I read it over and saw the controls and logic immediately.  For those working through this script I have a couple of comments.

  1.  First you need to set up an SSH trust between the remote $RMH machine and the machine you are running the script on.  This is pretty easy.  Just do a  search for "ssh-keygen" and you'll find plenty of help.

  2.  Watch your disk space.  This script doesn't worry about disk space and copies the files to /root/tmp and then to appropriate destination.  Generally, this is a good idea, but if you are like me and have a pile of i-Tunes video dowloads you may run out of disk space.

      For disk space conscious people change line 55;

Code: [Select]

rsync -vPa -e ssh $RMH:/home/e-smith/ $LTD/home/e-smith/
       
      To write directly to your user and ibays directories.  Also comment out line 73 which copies the tmp ibays to the live location.

Code: [Select]

rsync -vPa -e ssh $RMH:/home/e-smith/ /home/e-smith/
     
I like the idea of having all the settings and templates in a /root/tmp directory, but my ibays are enormous.

  Thanks Brian.

[jfarschman]

About Key generation

I generally do not specify a key name.  My process goes like this:

ssh-keygen -trsa

# just hit return a few time and ignore the prompts

This will generate id_rsa.pub and the private key as well.  Copy the contents of this key into the authorized_keys file, that may or may not exist... and copy it to the authorized_keys of the other machine.