File Interleaving on Netware - Anyone used this option before?

[BillHicks]

Hi, <br><br>We have a host backup server running Arcserve for Netware 6.10 (SP2) which backs up itself and 8 others which use the Push Agent for Netware 6.60 running on Netware v3.12. Currently we've split the workload between 2 jobs running concurrently on the same host server writing to 2 seperate DLT drives. A full backup takes 14 hours so we only backup incrementally during the week which is totally unacceptable for us but we have to do it to meet SLA's. There is currently about 90gig of data to be backed up across these servers. Does anyone know if adopting File Interleaving would &quot;dramatically increase the speed of remote backups&quot;? Or can anyone advise a better method? <br><br>There must be a reason why we haven't adopted this before if it's so good. What am I missing folks? How is the restore process affected if 4 server's files are on 1 DLT tape? <br><br>A lot of questions, I know. Thanks for any and all information. <br><br>

 

[BobT]

Push agent works well, IF you have cache buffers and file cache buffers,10% disk space on the client. If not you lose. I get 30% increase on speed by interleaving.<br>Bob T.

 

[TonyP1234]

I used the Interleaving option a few years back on the Netware server with 4 other Netware servers using push agents.

All 4 Push Agent boxes sent data at the same time, with the main server maintaing seperate buffers for each box sending data. When the buffer is full it gets written to tape.

Advantages: Quicker backups, if you have one slow box it does not affect the overall backup speed as the other boxes take up the spare network bandwidth.

Disadvantages: Restores take longer as the info can be scatterred along the tape. With several boxes sending data, pretty much all the network bandwidth is used.