Very Computer

I'm converting a client from D3/SCo to D3Linux/Redhat 5.2. I'm struggling to
read the SCO 4mm DAT tape & can get the account restore to bomb in such a
way that it overwrites DM with fatal results!!

Has anyone else had a similar problem whereby DM gets overwritten?

I managed to restore a filesave some weeks ago but when restoring the
account save last Friday I got the DM destruction problem.

I figure it's got something to do with SCO using quarter inch drivers to
create the tape & Linux using the 4mm drivers & me forgetting the mt -f
/dev/nst0 setblk 0 command. But I am intrigued as to how DM gets smacked
when restoring an account!

Any clever techies out ther with some ideas?

Thanks in advance

Tom power

        The rule of thumb is, all settings, and I do mean all, MUST
match on both the source and target machines.  If the Unix block size on
the SCO machine was 512 and the pick0 file read "16384 q l", so must the
Linux machine.  On the SCO machine, if you did a "t-att 512" prior to
reading from/writing to the tape drive, the same must be done on the
Linux machine prior to reading the tapes.

Do you have enough disk space on the SCO box to do the account-save to pseudo
floppy? If so, I would try that and then tar the file to the Linux box

.>'m converting a client from D3/SCo to D3Linux/Redhat 5.2. I'm struggling to

Quote:>read the SCO 4mm DAT tape & can get the account restore to bomb in such a
>way that it overwrites DM with fatal results!!