NDMPCopy is a little bit creaky but allows you to control explicitly which directories get copied. It's very useful. When I say it's a bit creaky I mean I've observed some strange and uneven behaviours from it performance wise. It's never threatened our data though and so we still use it without qualms.
We've also used the prototype technology Dave alluded to and that goes like the proverbial off a shovel! I think we were seeing 20+GB/hr between a F330 and an F520. It makes a full copy of a filer (ie we had to be careful to boot with the right OS floppy and such, one of the few times you have to care which CPU you're using) no more, no less.
NDMPCopy has gone as fast as 2.5MB here, over FDDI, the prototype software boosted that to almost 5MB/s and we basically had a full filer copy in an hour and a half!
Sorry this mail isn't very timely, but I hope it's useful to someone.
+--- In a previous state of mind, "Mark D Simmons" mds@gbnet.net wrote: | | NDMPCopy is a little bit creaky but allows you to control explicitly which directories get | copied. It's very useful. When I say it's a bit creaky I mean I've observed some strange | and uneven behaviours from it performance wise. It's never threatened our data though and | so we still use it without qualms.
Once I got it built, the tool seemed quite nice. The speeds I was seeing were about 500K/sec (at best). But, the source filer is quite busy. There were some very odd problems with the ndmpcopy. It simply stopped once (that sucked). This was after having spent 3 hours getting to that point (and 10 hours left, according to the program). Not very happy when that occured.
| We've also used the prototype technology Dave alluded to and that goes like the proverbial | off a shovel! I think we were seeing 20+GB/hr between a F330 and an F520. It makes a full | copy of a filer (ie we had to be careful to boot with the right OS floppy and such, one of | the few times you have to care which CPU you're using) no more, no less.
Sounds great. My only question (which I think was answered by Beepy) was if you can run the tool while still serving data? The only reason I did not pursue the BMM was that I could not afford any downtime. I hope that future migrations will be less painful. (well, at least faster).
| Sorry this mail isn't very timely, but I hope it's useful to someone.
Thanks for the reply. I have found it quite interesting.
Alexei