hardcard copy

hello,
need to make a hardcard copy (qnx2 System) to another hardcard (1to1) for
Backup, if the hard card crashes ore something
heard about a unix “dd” - does it work ?
and how,
is a linux boot disk ok for that ??
thanks
Roland

In article <b04fcm$378$1@inn.qnx.com>, Roland Schreiner wrote:

hello,
need to make a hardcard copy (qnx2 System) to another hardcard (1to1) for
Backup, if the hard card crashes ore something
heard about a unix “dd” - does it work ?
and how,
is a linux boot disk ok for that ??
thanks
Roland

dd is a unix ditty, “device to device” copy program that copies
bit for bit what’s given as input to wnat’s given as output.

It’s a standard, but usually not installed, part of most
Linux as well as QNX 6.x.
You could do it from the NC Momentics CD for that matter…


Cowboy

I have a very good DENTAL PLAN. Thank you.

If you want to do that, make sure that your destination hardcard is either
capable of mapping bad blocks in a manner that is invisible to the OS, or
has perfect media. I recall that old drives generally both lacked that
capability, and did tend to have bad blocks. That could mean that the
filesystem data that resides in a particular block on your source drive
might need to be copied to a block that is unavailable (because it’s bad) on
the backup drive. If you do a read/write/verify dcheck on your destination
drive and get any bad blocks at all, the dd approach will almost certainly
not work.

“Cowboy” <curt@gwis.com> wrote in message
news:slrnb2e3aq.qha.curt@desktop.cowboy.loc

In article <b04fcm$378$> 1@inn.qnx.com> >, Roland Schreiner wrote:
hello,
need to make a hardcard copy (qnx2 System) to another hardcard (1to1) for
Backup, if the hard card crashes ore something
heard about a unix “dd” - does it work ?
and how,
is a linux boot disk ok for that ??
thanks
Roland

dd is a unix ditty, “device to device” copy program that copies
bit for bit what’s given as input to wnat’s given as output.

It’s a standard, but usually not installed, part of most
Linux as well as QNX 6.x.
You could do it from the NC Momentics CD for that matter…


Cowboy

I have a very good DENTAL PLAN. Thank you.

OK,

Thanks for your info, so if dd is not the best way, any other idea ??

Greetings
Roland

“Eric Johnson” <eric@qnx.com> schrieb im Newsbeitrag
news:b078ln$b9m$1@nntp.qnx.com

If you want to do that, make sure that your destination hardcard is either
capable of mapping bad blocks in a manner that is invisible to the OS, or
has perfect media. I recall that old drives generally both lacked that
capability, and did tend to have bad blocks. That could mean that the
filesystem data that resides in a particular block on your source drive
might need to be copied to a block that is unavailable (because it’s bad)
on
the backup drive. If you do a read/write/verify dcheck on your destination
drive and get any bad blocks at all, the dd approach will almost certainly
not work.

“Cowboy” <> curt@gwis.com> > wrote in message
news:> slrnb2e3aq.qha.curt@desktop.cowboy.loc> …
In article <b04fcm$378$> 1@inn.qnx.com> >, Roland Schreiner wrote:
hello,
need to make a hardcard copy (qnx2 System) to another hardcard (1to1)
for
Backup, if the hard card crashes ore something
heard about a unix “dd” - does it work ?
and how,
is a linux boot disk ok for that ??
thanks
Roland

dd is a unix ditty, “device to device” copy program that copies
bit for bit what’s given as input to wnat’s given as output.

It’s a standard, but usually not installed, part of most
Linux as well as QNX 6.x.
You could do it from the NC Momentics CD for that matter…


Cowboy

I have a very good DENTAL PLAN. Thank you.

In article <b0a5d1$hdl$1@inn.qnx.com>, Roland Schreiner wrote:

OK,

Thanks for your info, so if dd is not the best way, any other idea ??

In light of that info…
Can you mount it as a block device, and do a file by file copy ?
cp /fs/sourcedevice/* /fs/destinationdevice/


Cowboy

People who go to conferences are the ones who shouldn’t.

Can you mount it as a block device

I think no, cause the hard cards I copy to are used ones with Fat.

Greetings
Roland

“Cowboy” <curt@gwis.com> schrieb im Newsbeitrag
news:slrnb38eel.r0p.curt@desktop.cowboy.loc

In article <b0a5d1$hdl$> 1@inn.qnx.com> >, Roland Schreiner wrote:
OK,

Thanks for your info, so if dd is not the best way, any other idea ??

In light of that info…
Can you mount it as a block device, and do a file by file copy ?
cp /fs/sourcedevice/* /fs/destinationdevice/


Cowboy

People who go to conferences are the ones who shouldn’t.

Copying data from one block device to the other is doing essentially the
same thing as ‘dd’, and would have the same vunerabilities. In QNX 2, the
dcopy utility will perform that sort of copying. Assuming the second drive
is appropriately mounted, the dcopy utility would be worth a try since by
default will verify that the copy worked by reading back the data on the
destination drive.

QNX 2 has a utility called ‘backup’ that is intended to copy files from one
filesystem to another. That should be a safe way to transfer data even if
the second drive has bad blocks (you’d need to mount, partition, remount,
dinit, dcheck the new hardcard first before you could copy to it).

You might have some difficulty getting both hardcards working simultaneously
(two controllers)… you might need to specify the controller address and the
interrupt in your mount command. If you can’t make that work, doing the copy
across the network between two QNX 2 machines might be an option also.


“Roland Schreiner” <diver@cvmx.de> wrote in message
news:b1einq$sej$1@inn.qnx.com

Can you mount it as a block device

I think no, cause the hard cards I copy to are used ones with Fat.

Greetings
Roland

“Cowboy” <> curt@gwis.com> > schrieb im Newsbeitrag
news:> slrnb38eel.r0p.curt@desktop.cowboy.loc> …
In article <b0a5d1$hdl$> 1@inn.qnx.com> >, Roland Schreiner wrote:
OK,

Thanks for your info, so if dd is not the best way, any other idea ??

In light of that info…
Can you mount it as a block device, and do a file by file copy ?
cp /fs/sourcedevice/* /fs/destinationdevice/


Cowboy

People who go to conferences are the ones who shouldn’t.

Thanks for your help, but the whole thing sounds difficult.
The problem is, that i have to be sure that:

The original hard card will not crash.
I am able to do this copies at customers (one is in Slowakia) for example
with a Laptop…

Did somebody try image progs like drive image ore something ?

greeting
Roland
“Eric Johnson” <eric@qnx.com> schrieb im Newsbeitrag
news:b1en39$d4t$1@nntp.qnx.com

Copying data from one block device to the other is doing essentially the
same thing as ‘dd’, and would have the same vunerabilities. In QNX 2, the
dcopy utility will perform that sort of copying. Assuming the second drive
is appropriately mounted, the dcopy utility would be worth a try since by
default will verify that the copy worked by reading back the data on the
destination drive.

QNX 2 has a utility called ‘backup’ that is intended to copy files from
one
filesystem to another. That should be a safe way to transfer data even if
the second drive has bad blocks (you’d need to mount, partition, remount,
dinit, dcheck the new hardcard first before you could copy to it).

You might have some difficulty getting both hardcards working
simultaneously
(two controllers)… you might need to specify the controller address and
the
interrupt in your mount command. If you can’t make that work, doing the
copy
across the network between two QNX 2 machines might be an option also.


“Roland Schreiner” <> diver@cvmx.de> > wrote in message
news:b1einq$sej$> 1@inn.qnx.com> …
Can you mount it as a block device

I think no, cause the hard cards I copy to are used ones with Fat.

Greetings
Roland

“Cowboy” <> curt@gwis.com> > schrieb im Newsbeitrag
news:> slrnb38eel.r0p.curt@desktop.cowboy.loc> …
In article <b0a5d1$hdl$> 1@inn.qnx.com> >, Roland Schreiner wrote:
OK,

Thanks for your info, so if dd is not the best way, any other idea
??

In light of that info…
Can you mount it as a block device, and do a file by file copy ?
cp /fs/sourcedevice/* /fs/destinationdevice/


Cowboy

People who go to conferences are the ones who shouldn’t.