Moving to a new server

[ggggus]

I'm running CentOS 4.3 on an older server and I just bought a nice new server that I want to move my stuff over too. I'm looking for a good tutorial/guide on the subject that would cover things like copying the user information/passwords of all the existing users on the server over to the new one.

New new server has 64 bit processors, where as the old server did not have that, any suggestions on keeping my configurations the same there, while utilizing 64 bit versions of software if they are available.

In case it matters, the server is used as a web hosting server.

***************************************
J. Jacobs

http://www.piercedmedia.com

 

[zeland]

Configurations should be independent of CPU architecture.
User information is in /etc/passwd.
Group information in /etc/group.
Passwords in /etc/shadow
and of course, user files /home.


--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

 

[ggggus]

Is there a complete listing of the default config files for other common server programs?

I'm familiar with httpd.conf and my.conf since I've manually edited those, but I have to admit that I've gone the easy route with sendmail, iptables firewall, bind dns, and others and I've used webmin to set these up.

I can figure out what all these config files are all named on my own, but why re-invent the wheel if someone has already compiled a list of these common config files.

***************************************
J. Jacobs

http://www.piercedmedia.com

 

[QatQat]

For sendmail copy the /etc/mail/ directory

for iptables run the following

iptables-save > /tmp/my_iptables_setup

and on the new machine restore the setup

iptables-restore < /tmp/my_iptables_setup
Obviously adjust the paths and filenames to whatever wuits you.
The command is not distribution dependant and should work in CentOS (which I think is Debian based but I stand correction) as well as any other. Should CentOS be rpm based distro (therefore redhat child) you may copy the file /etc/sysconfig/iptables and restart iptables on the new machine.



For bind you need the /etc/named.conf file and probably you need to copy all your zone files.


Concerning your CPU architecture, yes most daemons will be cpu independant.
Running a /etc tar backup and restoring it on the new machine may be a quicker way but you may have problems if servers' versions have changed.

Out of the servers you mentioned above, I do not think you will have any problems in copying config scripts, restarting daemons and get running again.

QatQat



Life is what happens when you are making other plans.