Also, backup requires alot of db interaction (insert, commit, calculate/build file aggregates, etc.), whereas migration just moves from disk pool to tape... so, migration of 350 MB should be much faster -- notwithstanding tape mount and positioning (which, for DLT, can be several minutes).
Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Zlatko Krastev Sent: Friday, May 17, 2002 1:11 AM To: [EMAIL PROTECTED] Subject: Re: Performance again!!! Backup direct to tape involves the communications. Migration is purely server process. So its check can eliminate some TCP bottlenecks (if any). For local client there should be no big difference. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Performance again!!! Hello, we didn't try that one ... Is there any reason for the migration from disk to tape to be faster than backup from disk to tape? thx Sandra --- Zlatko Krastev <[EMAIL PROTECTED]> wrote: > How long does the migration to tape take after > backup to disk? > > Zlatko Krastev > IT Consultant > > > > > Please respond to "ADSM: Dist Stor Manager" > <[EMAIL PROTECTED]> > Sent by: "ADSM: Dist Stor Manager" > <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > cc: > > Subject: Performance again!!! > > Hello everybody, > > It seems like TSM performance problems will neer > end!!! > > Here is the new problem: > > The customer is running TSM 4.2.1.0 on a Windows > 2000 > server machine . An IBM rack case 82XX which > contains > a Quantum DLT8000 tape drive is connected to the > server. > The driver version for the Quantum DLT drive is 1.5 > and > is installed on the W2K machine. We tried a backup > of > 350MB on the local server with the Windows 2000 > Backup > > utility and it took us approximately 75 seconds . > > Next , we tried the same Backup from TSM using its > Device Driver and it took us about 9 minutes . We > tried switching TSM to use the Native device driver > but still we got the same performance result . > > So we upgraded to 4.2.2 ; In the Device Manager for > TSM,we can see that TSMSCSI.exe is upgraded to > 4.2.2.25 and the ADSMSCSI.sys is 4.2.2.3 . The > server > has a version of 4.2.2.25 . Still , we obtained > poor > backup performance . > > We suspected that maybe it was a database bottleneck > ( eventhough it is still empty) ; so we tried the > same > Backup using TSM but the destination was on the > HardDisk. > The performance was good and the backup finished > within 75seconds . So, we can eliminate the > database > problem. > Also, we noticed with version 4.2.2.0 that it is > crashing frequently . It was exiting abnormally . > > On the site of tivoli, the latest version of TSM > server is 4.2.2 . We do not have the 5.1 release . > > does anyone have a suggestion? > > thx a lot > Sandra > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com
