Hi Bill,

Thanks for the feedback.

I fully agree with what you write HOWEVER, in my case the server is a
simple email server with almost all POP accounts and also a SAMBA file
server (again most of the data is static) so a "little" bit of loss is
acceptable. I have used this "Disaster Recovery" method successfully on
several of my customer sites (running Linux) and it is really a 30
second (no kidding!!) reboot to get the system going in the event of a
disk failure. BTW I have also implemented a Microlite BackupEdge backup
as well. If you use the Disaster Recovery of Microlite, it takes
approximately 2-4 hours to fully recover (hence the 30 second recovery
for a mail server) is required by my customer. I really did now want to
get into the merits or lack thereof of the method used - just a reason
or fix as to why the "dd" command works fine under same conditions with
LINUX and not woth SO 5.0.5. I will probably try Bela suggestion and
try with SCO 5.0.7 and see whether it is indeed a kernel problem or
not. Again much thanks for your time and suggestions. Rgds. Otto.



Bill Vermillion wrote:
> In article <1136729079.655900.309730@g14g2000cwa.googlegroups .com>,
> Otto <otto@applied.com.sg> wrote:
>
> >Thanks for the reply. Indeed I tried it with both the old wd driver (as
> >originally delivered in 5.0.5) as well as the newer wd driver as found
> >in 5.0.7. The timing is DRASTICALLY diff (the old wd driver took almost
> >4 hrs to complete, the new wd driver finished in under 25 minutes for a
> >20Gb clone!!). However, the result seems to be the same - the new
> >clone is badly corrupted. As I mentioned previously this only happens
> >on a "live" running booted system. If I boot from say a CD and clone
> >drive 1 to drive 2 it works just fine. Again, any help or ideas to try
> >would be much appreciated. Rgds. Otto.
>
> Just an observation here.
>
> Running dd on a live drive could be problematic as many things are
> being continually run and updated on an Unix system.
>
> From my POV the best way to ensure you are OK is to put the OS on
> the other drive for starters, and then do updates through the
> filesystem and NOT dd via a tool such as rsync.
>
> Bill
> --
> Bill Vermillion - bv @ wjv . com