Topic: How to export db configuration to shell script

[Jáder]

I'm planning an upgrade on a SME6.01 (running for 5 years... without updates GOD knows how long!) so I'd like to export all db configuration to a shell script.
That would allow me to select parts of script to be updated on new SME7.4 (White lists, ...)

I know I can show the config and redirect output to a file... but that will force a lot of manual edit before re submit it to new server.

BTW: I'll put a new HDD and install on same machine... later copy data and use old HDD to RAID1.

Have someone already done this and have a tip ?

Thanks

Jáder

[janet]

jader

This is probably the most straightforward approach

http://wiki.contribs.org/UpgradeDisk

[Jáder]

Mary

jader

This is probably the most straightforward approach

http://wiki.contribs.org/UpgradeDisk

Thanks by your tip.
I'll remove old HDD with 6.01 and everything else and put aside.
Install a new HDD and 7.4 on it... standard install.
Later I'll move data from old HDD to new one... after restart basic functionality on server.
I just wanna a way to create a .sh file with configuration as an easy way to restore db config (or affa) data.

I'll look into pre-backup and pre-restore events to see if I can find anything.

Jáder

[Igi2003]

You must not expand db configuration. Just copy all files from /home/e-smith/db to an external HDD

[CharlieBrady]

You must not expand db configuration. Just copy all files from /home/e-smith/db to an external HDD

No, that is not good advice. The wiki article already referenced is the best approach.

[janet]

jader

That "tip" is a method created by one of the leading developers of sme server and is the recommended way of upgrading from sme6.x to sme7.x

There is no recommended "configuration only" option, as configuration details are contained in many different files. Were it as simple as you ask, a routine would have been developed years ago.

It really depends on what you mean by "configuration".
Perhaps you are just referring to the basic setup details that could be saved to a floppy disk in some older version of sme (was it 4.x or 5.x or 6.x that still had that option ?).

You can get a similar result using the backup server config method referred to here
http://wiki.contribs.org/Backup_server_config

There is also the Lazy Admin Tools (LAT) contrib.

As I said before and Charlie agrees, the UpgradeDisk method will be perhaps the easiest approach. It will transfer all your config and users and shared data and mysql databases, but not the installed rpms (some of which could be incompatible with sme 7 anyway, and there are quite a few additions to sme7 base code, which did away with the need for contribs eg spam & antivirus & RBL lists etc, so you do not really want to transfer data associated with those old contribs.
You must remove the custom templates referred to and generally follow the steps carefully.

Also the backup server config article has many other specific tips for doing partial upgrades manually and with care & understanding should be successful.
There is also other info in that same article about backup and restore inclusions and the important signal events.

If your current server is a domain controller and you do not use one of the recommended restore approaches, then you will lose the machine accounts, which means all windows workstations will have to rejoin the domain, and  you may lose the User Profiles on the workstations.

[mmccarn]

I have posted a script I use to transfer SME servers to new hardware as an attachment to NFR Bug 5701.

Alternatively, I *love* Affa.  The Affa wiki page includes a description of how to use Affa to upgrade a SME 6 server to SME 7 on new hardware: http://wiki.contribs.org/Moving_SME_to_new_Hardware#SME_6_Server

Be aware that SME 6 add-ons that kept their data in the config db may not translate directly to the format/db used in SME 7.  I seem to remember needing to play with my spam whitelists to get them working in SME 7.  Having said that, since SME 7.1 (or 7.2?) I try to avoid whitelists altogether; I use Bayesian autolearning and 'LearnAsSpam/LearnAsHam' to train the spamassassin to handle email without using whitelists.

[Jáder]

jader

That "tip" is a method created by one of the leading developers of sme server and is the recommended way of upgrading from sme6.x to sme7.x

Sorry... no offenses meant.
I see the upgrade method and think it´s good.
I´m just a little anxious about to put server to do all work without a lot of control.
I´m a old guy... used to command line... used to make 2 or even 3 backup copies and move things step by step.

There is no recommended "configuration only" option, as configuration details are contained in many different files. Were it as simple as you ask, a routine would have been developed years ago.

It really depends on what you mean by "configuration".
Perhaps you are just referring to the basic setup details that could be saved to a floppy disk in some older version of sme (was it 4.x or 5.x or 6.x that still had that option ?).

That would be wonderful... a copy of all info on db databases + a mysql dumpall... and other things I cannot remember right now (that´s because I´d like to have a tip about what to copy!)
I can remember to save /etc/motd where I put all update I do on server, with date... to be able to track them down later.
but what else ?

There is also the Lazy Admin Tools (LAT) contrib.

As I said before and Charlie agrees, the UpgradeDisk method will be perhaps the easiest approach. It will transfer all your config and users and shared data and mysql databases, but not the installed rpms (some of which could be incompatible with sme 7 anyway, and there are quite a few additions to sme7 base code, which did away with the need for contribs eg spam & antivirus & RBL lists etc, so you do not really want to transfer data associated with those old contribs.
You must remove the custom templates referred to and generally follow the steps carefully.

Also the backup server config article has many other specific tips for doing partial upgrades manually and with care & understanding should be successful.
There is also other info in that same article about backup and restore inclusions and the important signal events.

If your current server is a domain controller and you do not use one of the recommended restore approaches, then you will lose the machine accounts, which means all windows workstations will have to rejoin the domain, and  you may lose the User Profiles on the workstations.

Will use LAT as needed.

Jáder

[Stefano]

Jader:

in my experience the best way to migrate SME from different hw/sw release is Affa.. works flawlessy in many situations..

all you need is to read carefully the Wiki page, in particular this part

HTH

[janet]

jader

Trust the developers, they put a lot of effort in getting upgrades from 6.x to 7.x to work. The users mail folder naming structure was altered from 6 to 7 and the upgrade routines take this into account. If you just copy user mail then you have a command line job ahead of you to fix it all up. Also the partition arrangement was changed, a new install of 7.x is required to get the advantages of this, so you then need to do a backup & restore. The restore from disk is easier than any other method.

The script you want has already been created for you, it's called the built in backup and restore routines which are really just a series of command line commands all put together as a cohesive routine.

....a copy of all info on db databases + a mysql dumpall...
I´d like to have a tip about what to copy!

Well it appears you glossed over this article which covers everything including alternative methods.
You can get a similar result (ie config minus data) using the backup server config method referred to here
http://wiki.contribs.org/Backup_server_config

There is much additional info, ie the "list" you want, in that article.

.....but what else ?

What else do you want ?
Use the UpgradeDisk method. The instructions tell you what to do and these steps remove the "bits" of sme 6 that are inappropriate to have on sme7.
All behind the scenes version change issues are taken care of, and all system configuration, mysql dbs, users and user data, and shared data (ibays) etc, is transferred.
You do not need to spend time creating a backup as you restore directly from the "data" on the original disk. You also get to retain your original disk still in original working order that you can revert to if anything goes wrong.

[Jáder]

Mary

Thanks by your time trying help me.
I'm a little anxious because this is a VERY old installation... on a factory...with no space to errors.

It's been for 3 years without updates... and now they FINALLY decided to upgrade.
But this is a highly modificated SME601 installation... with a lot of extra rpms.

I'm planning to work a entire saturday to upgrade software (linux) on a server with just 30GB data... but I MUST to be sure that everything works. Otherwise monday morning (7:30am) I must to be there to help them... and I'd HATE this.

I'll follow the DiskUpgrade path... and will post here results.

Thanks

Jáder

[janet]

jader

I suggest you do a trial run, as there might be unforseen issues  due to the old versions of base rpms on the system. Sort out any hiccups. If that goes OK you can follow up with the real switchover.
In a worst case scenario, you can just reconnect the original drive and you should have the still functional original server.

But this is a highly modificated SME601 installation... with a lot of extra rpms.

Well you should tell us what they are. There was a long forum thread (5 or 6 pgs) re  upgrading from 6.x a few years ago. I think it is linked in that UpgradeDisk article. There are many contrib rpms on 6.x that were incompatible with sme 7 due to major system improvements and additions. You will need to locate the new compatible rpms, but mostly they are available using yum. You should do this homework and be ready with the contrib upgrade steps before you start. I'd even suggest a trial run of upgrading the system AND installing any new contribs you require. There are bound to be some time consuming gotchas that may take longer than one Saturday to sort out. Given the age, lack of system upgrades and high customisation, I think a trial run is almost obligatory, unless of course you like living on tte edge, but you sound very conservative to me.

I know that "must be ready" Monday morning feeling, it's the cause of many a long nights work.

[Jáder]

Mary

I´m not sure how to run the trial... I´m 60km away from server... and do not willing to do anything more than ABSOLUTLY necessary on SME601+customs ( I think in 6.01 there was script with a lot of custom rpms... and I had run that on this server)

I think I´ll believe UpgradeDisk and hope for the best!

Jáder

[Jáder]

Just to let anyone to know: The upgrade using Mary ( http://wiki.contribs.org/UpgradeDisk ) tip was sucefull.
Just as easy as ANY upgrade should be.

It takes almost one hour of work to upgrade the SME 6.01 with lots of hacks (using old 80GB IDE HDD) to SME 7.4 with other NEW 80GB IDE.

Thank you for all who help to create that procedure.   
Thank you MARY!