If it is the same server, you can mount the raid partition and issue a cp -a to move all the data.
If it is a new server, you can use a cross-over-cable to join the 2 servers {faster data transfer, secure}, and run NFS or rsync to copy all data from the one disk system to the raid system.

If the new raid server is up and running, and if the linux is the same version in both, you can simply do rsync and copy everything .. even the binaries if you wish.

If the linux version is different, you can safely copy passwords, group and shadow files and the associated home directories and other entries.

Since you mean a RAID controller then you'll have nothing special to do in terms of prep... that's why I asked.

The contents of /home, /etc/passwd, /etc/group and /etc/shadow should be transportable except 1 caveat: Different distros use different user names for different purposes. So if distro A (where you're coming from) has user "foo", but distro B (where you're going to) doesn't, then you'll have problems if you just replace one passwd/shadow file with another. What I usually do is compare the passwd files between the source and target system, them add the missing entries on the target system. You can simply cut-and-paste from one to another if you like. Be careful that you ensure that users who appear on both systems have the same UID/GID or you'll be in for some fun!

Also, be careful moving bulk moving directories over. Once again, you can run into problems replacing all of /var on the new system from the old system.

What I typically do is move over /home (relatively safe, assuming that I've not created any new users on the new system) and re-establish my users and groups. Once they are successfully restored, I then move over /usr/local and /opt, which should be simple since they are supposed to be used only by the local admin for custom software.

Having taken care of the light work I then compare the '/var' directories, moving over what is missing. Finally, I get my configurations moved over, carefully inspecting the differences between configurations on the old and new.

BTW, when you do this do yourself a favor and keep track of what you had to do. I keep notebooks on all of my systems in which I make notations to what I did to them so that when I upgrade I can quickly do what I need to do.

Sure! admino...here we go.
The old server is really just a desktop PC running Fedora Core 1. It has three users, runs apache web server, Mysql server, PHP, Perl, Webmin, and some custom scripts. Some stuff in the /etc directory has been modified, so I will need to get that info transfered also.
If you need more, please ask. I appreciate all the help everyone is giving.
I am currently installing Fedora Core 1 to the new server, and I will need it to do the same thing the old server is doing...which is why I am here. LOL

Since you are running fedora core1 on both the systems, it is safe to copy the files from one server to another .. including the binaries.

Since you have just 3 users, there are 3 ways how you can do this.

first, you need to copy the /etc/passwd. /etc/shadow and /etc/group
then tar/copy or rsync the /home files to the new server..

so far so good.. the users can login with their same username and password and also, the permissions on the home directory and their files will be the exact same.

Now, you can stop mysql on the old server, and then either use mysqldump to backup and move the mysql databases to the new server, or you can just simly copy the mysql files and it will start working.

you can then copy the apache conf files and your other custom files.

way 2:

since both servers are on fedora, you can rsync everything frol the old server to the new server.

way 3:

since you have just a few users in the system, you can just add users like you add first, ,, useradd and manually copy the files using tar and then fix and chmod and chown in the new server.
mysql also using mysqldump

for apache conf, you can check the difference in the conf files and just add the entry manually.

If you are not using a custom kernel or some specific hardware specific drivers to load, it will work without errors.
Since you are using hardware raid, and not software raid, the kernel will just see it as sda.

Can you paste the specific error that u are getting?

0

Featured Post

An important part of learning any new piece of software is understanding the terminology it uses. Thankfully WordPress uses fairly simple names for everything that make it easy to start using the software.

I am a long time windows user and for me it is normal to have spaces in directory and file names. Changing to Linux I found myself frustrated when I moved my windows data over to my new Linux computer.
The problem occurs when at the command line.…

Learn how to get help with Linux/Unix bash shell commands.
Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…