At the moment I'm doing some performance tests with ADSM NT in a
     standalone configuration hooked up with a (for the time being) single
     DLT drive.
     I'm specifically using a standalone ADSM configuration as a solution
     to those NT environments requiring a very short backup/restore window
     (< 4 hours) with loads of data (> 100gb).

     My primary question is, why does it look like that even though there
     should be no network involved I only see backup/restore speeds of less
     than 1mb/sec, something you would expect when doing a backup over
     token ring (which happens to be the network card I have in my server).
     You would expect all communications to be internal and that speeds of
     up to 8-10mb/sec (to disk storage) should be possible !

     Second, when doing media moves (512 mb, 340 large files) from tape to
     disk ADSM is pushing the DLT drive at a slow 1.5 mb/sec, less than
     half the DLT's speed capacity (I did a some verifying with Arcserve to
     see what speed the DLT could be operated at, backup hit a max of 3.6
     mb/sec).

     The tests were done using an IBM520 with 5 disks in a RAID-5 with an
     HP Surestore DLT70 attached to the system. Backup/restore went
     straight to/from tape.
     ADSM client and server were configured to use TCP/IP (also tried
     namedpipes, but made no difference) as communications protocol
     (TCPBUFFSIZE 31, TCPWINDOWSIZE 64, TXNBYTELIMIT 25600),
     the client is configured to backup/restore through localhost. The test
     data used was 270mb devided over 170 (mostly large 5-20mb) files.
     Version of ADSM server is V3.1.2, client is V3.1.05L.

     Any input is welcome,


     Regards, groeten,

     Walter Ridderhof

     Mainland Sequoia