Re: Advanced question: How to copy files from one server to the other?



On Fri, 26 Sep 2008 18:42:05 +0300, Tom wrote:

Hello folks!

Here is my situation:
***************
I am administering a samba fileserver with 1 Terrabyte of user data. The
data is stored on a RAID5. The partition uses raiserfs as a filesystem and
is 1 Terrabyte big. The disk uses a MBR disklabel. The OS is SuSE-Linux
8.2-32bit with kernel 2.4.20. I am using Samba 2.2.a-SuSE

Now I have a new linux box as a replacement for the old server. It has a
RAID6, the partition is 10 Terrabyte and formated with XFS filesystem. The
disk uses a GPT disklabel. The OS is openSUSE 11-64bit with kernel
2.6.25.16-0.1. I am using Samba 3.2.3-0.1.

That's a pretty big jump. I am presently running Samba 3.2.3 on kernel
2.6.24.x (on an XFS filesystem). My setup is also more simple than your
setup, because I use Samba in standalone server mode. If I were in your
place, I'd plan on some downtime where this can be tested and verified.
There are always minor differences, and you are making a pretty big leap.
The last upgrade I made to my servers was a lot easier (from Slackware
11.0 to Slackware 12.0), but it took more than 5 minutes to make sure that
it was working and all accounts were properly migrated, etc.

What I want to do:
***************
I want to safely and correctly copy the files from the old server to the
new server and replace the old machine by the new one. After this the
new machine should function again as a samba-PDC and serve the files to
the windows clients, exactly as it's predecessor did all the years.

QUESTION:
***********
How should I copy the files from old server to new server in the best
and most secured way, so that everything is exactly as before,
concerning also e.g. file permissions, attributes, etc? Also there
should be a CRC check when files are copied so that I am sure that
everything is ok 100% My idea was to use RSYNC. Is that the best
solution?

I would use tar over a nc network transport (on gigabit ethernet). Other
fixups may be required when the files are in place. For example, are you
using extended attributes and file access control lists?
getfattr, setfattr
getfacl, setfacl

The benefit of nc is the raw transport, using no encryption etc. This is
appropriate on trusted local network. In the simplest case, a crossover
cable can be used to create a trusted network between the source and
destination computer. Use ifconfig if necessary to set addresses.

Since the old server has only a 100MBit NIC i was thinking about to
install the old RAID controller with it's disks into the new server and
make a local copy from controller old to controller new, instead of
using the network. Is that a good idea?

I would _guess_ that it may be more trouble than it's worth. If you want
to do something quick to speed up network transfer, install a gigabit
network card in the old server temporarily. It is generally easier to
reconfigure network cards than disk drives (and disk arrays).

Gererally: Is there anything that you could warn me off or that I should
keep in mind? E.g. the different operating system bitsizes (64bit vs.
32bit)? Or the different filesystems (raiserfs vs. XFS)? Is it maybe
better not to do the local approach but to use the network approach
instead because of some problems that may occure?

I have no experience with 64bit OSs.

Thank you for any hint or peace of advice!!!

Best regards
Tom

Note: some comments inline.

I think you should run some simple tests first to verify your new box
will actually work as the PDC. Once you know that the new box is working
correctly using the desired access modes (network shares, ssh, etc.),
then you can make the final transfer of the bulk of your data.

After the data is in place, you can run verification checks to
double-check that everything was transferred as intended.

Minimal checks:
Overall file count
Overall file sizes
Overall directory listing with timestamp and size info

Detailed check:
At source, generate md5sum for all files which were transferred, then
at destination verify md5sums are correct.

When you're sure that everything is ready, start samba and begin sharing
the files.

This sounds like a challenging job. Be careful.

--
Douglas Mayne
.



Relevant Pages

  • [HPADM] RE: Mapping Samba Share to XP
    ... "The mapped network drive could not be created because the following error occurred: The remote computer is not available." ... Is there anything I need to change in the configuration on the CIFS server? ... I am unable to map to the Windows XP clients on the 158 subnet still, but this is due to the firewall, so if someone knows how I can make that happen, please let me know? ... Mapping Samba Share to XP ...
    (HP-UX-Admin)
  • Re: [Full-Disclosure] Re: Microsoft Security, baby steps ?[Scanned] [Scanned]
    ... disk *every day*, just due to hard drive failures and the like. ... via the SMS server or for companies not running SMS they may use RIS or ... another image multicast server. ... network) They would of course have to keep RIS images up to date. ...
    (Full-Disclosure)
  • Solved: FreeBSD as print server w/CUPS + samba + apsfilter
    ... CUPS and Samba so that local (connected to server) printers print ... as network printer amongst Windows 2k/XP clients. ... samba over Win2k network" contained what I had accomplished, ...
    (freebsd-questions)
  • Re: Have I destroyed the Exchange 2003 active directory and can it be repaired
    ... After you've replaced the disk you might consider creating a new mailbox ... Took the disk out and put it in another server, ran chkdsk on it there, ... I then put the disk back in the exchange ... Had a look at the usual suspects (network settings etc) and all seems ...
    (microsoft.public.exchange.admin)
  • Samba, please help (newbie)
    ... I am trying to configure linux to operate in my win2000 network. ... Samba has a huge number of configurable options most ... # server string is the equivalent of the NT Description field ... user logon script ...
    (alt.os.linux)