>Write the same data to two drives simultaneously? ... It wasn't the intent :-), but you can do this with amanda-2.4.3 (now in beta) or amanda-242-tapeio (from CVS) by using the "rait" output driver and defining two drives. The "first" drive will contain the real data and the "last" (second) drive contains the checksum (exclusive or). But since there is only one drive, the checksum is identical to the data.
I think. You should test it. >Filling the tape might be >an issue, but I guess if you hit EOM on either drive you could restart the >current image on both. That's what will happen with the above code. >Leaving level 0s on the holding disk after a write so that something like >amflush could make another tape of it? I re-posted some changes recently that hook the unlinking of images from the holding disk. It was meant to do all images, but could be changed to do only level 0's. >Some of my backups are across a WAN and take several hours, dragging the data >across twice seems like a gross inefficiency. ... If you have enough holding disk space, you could set "reserve" to allow full dumps and set tapedev to "/no/such/device" to force amdump to run but leave everything in the holding disk. Then some clever hard linking (to prevent removal) and multiple amflush runs should be able to accomplish what you want. >Frank John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
