Generally, tapes are streaming, so it is possible that if the transfer rate across the network is slow then more tape may be required for the same amount of data.
Really - you need to determine the bottleneck - can you tar from one machine to the HDD on another and see how long it takes - and then locally tar this data to the tape drive. That should give you some good ideas of where the performance bottleneck is. At Tuesday, 09-04-02 16:42 (+1000), Gonzalo Servat wrote: >Hi All > >I was performing backups across the network using Arkeia until one day >the wrong tape was inserted and the whole tape cycle went haywire (as it >requires you enter the right tape with the right label or you get a nice >email in the morning asking you to insert the right tape - when infact, >I DID enter the right tape) and so I got pretty p@#@ed off at Arkeia and >decided to switch to using tar (as I can insert any tape and it will >write, plus tar is pretty universal accross *nix systems so I can >restore on any system) > >Aaaanyway, the point of my story is... it would normally take ~2.5hours >to backup 33GB across the network using Arkeia to tape. >With tar, it takes over 8 hours at which point it gives me a nice "no >space left on device" message on the screen. > >I'm not using gzip compression. I've tried this and it doesn't help the >speed problem (or capacity problem) > >The backup unit is an Ecrix VXA-1 using V17 tapes. > >Any ideas?? > >Thanks in advance! > >Regards, > >Gonzalo. > > >-- >SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ >More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
