Your DB and Log shold be RAW as well, and in small vols. (ie 12GB log should be in 2-3GB VOls, DB, vols, depengin on size of db should be 5-10GB vols. Also try to make sure the raw logical vols are evenly spread accross as many LUNs as possible.
Charles Hart "Stapleton, Mark" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 07/29/2007 07:03 AM Please respond to "ADSM: Dist Stor Manager" <[email protected]> To [email protected] cc Subject Re: [ADSM-L] TSM performance very poor, Recovery log is being pinned From: ADSM: Dist Stor Manager on behalf of Craig Ross >TSM is installed on Solaris 10 This is something that popped right out for me. Do you have your storage pools located on raw logical volumes or mounted filesystems? If the latter, that might be your problem. Solaris has traditionally had incredibly poor throughput performance on mounted filesystems. You might give thought to rebuilding those storage pools on raw logical volumes. Of course, that will require that you completely flush all data from your disk storage pools to tape storage pools first, so as not to lose client data. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks (a CDW company) This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
