Everywhere I look shows a lowend of 40-50MB/s as the minimum speed of an LTO5, depending on the vendor. I'm sure compression will also mess with that number. This is probably just classic tape shoe-shining.
Regards, Shawn ________________________________ Shawn Drew > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Friday, August 23, 2013 3:23 PM > To: [email protected] > Subject: Re: [ADSM-L] TDP SQL backup performance > > I have a question about the target device, can an LTO-5 write at 20MB/sec? > Perhaps an intermediate landing zone that can write that slow might help. > > Andy Huebner > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[email protected]] On > Behalf Of Håkon Phillip Tønder-Keul > Sent: Friday, August 23, 2013 12:08 PM > To: [email protected] > Subject: Re: [ADSM-L] TDP SQL backup performance > > On 08/23/2013 04:07 PM, Sven Seefeld wrote: > > Hi, > > > > we're experiencing slow performance while backing up a 1,5 TByte MS > > SQL 2008R2 database with the TDP SQL Agent 6.3. As for DR-scenarios, > > we're doing legacy backups only. The actual speed is usually around 20 > > MByte/s, backups go to > > LTO-5 tape directly. The backup stream has to pass through 3 different > > firewalls, so we're not quite sure where the bottle neck is located, > > MS SQL API, TDP Agent or IP-firewall (SAN-Storage and TSM-Server > > should outperform everything else). > > > > Maybe someone can share his performance values with me. Any hints are > welcome. > > > > > > Regards, > > > > > > Sven > > Hi, > > Can you pos tyour dsm.opt and tdpsql.cfg? > > There is a lot of tuning that can boost your perfomance. > > -- > Mvh/Rgds > Håkon Phillip Tønder-Keul > Senior Consultant This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
