On Wed, 24 Apr 2002, Ilja G. Coolen wrote: > Hi, > > I'd suggest to move it to it's own filesystem placed on an redundant disk > array, enjoying high performance and recoverability. > We placed our database volumes on an ESS subsystem. Where you place it is > your own choice. Just try to achieve redundancy.
Did you put all primary/copy db volumes on the ESS? What kind of db cache hit are you getting? How are you talking to the ESS and how much other stuff is talking to the ESS while TSM is running? I am considering using the 2nd/3rd copy of the db for DRM purposes on an ESS. > > > Have fun. > > > > Ilja G. Coolen > > > _____ > > ABP / USZO > CIS / BS / TB / Storage Management > Telefoon : +31(0)45 579 7938 > Fax : +31(0)45 579 3990 > Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Intranet > : Storage Web > <http://intranet/cis_bstb/html_content/sm/index_sm.htm> > > _____ > > - Everybody has a photographic memory, some just don't have film. - > > > -----Oorspronkelijk bericht----- > Van: Brenda Collins [mailto:[EMAIL PROTECTED]] > Verzonden: woensdag 24 april 2002 13:37 > Aan: [EMAIL PROTECTED] > Onderwerp: TSM Database Location > > > We are just setting up a new TSM server. It appears to load the default > database under /opt/tivoli/tsm/server/bin. Is it common practice to leave > it there or to move it to it's own separate location? Any recommendations? > > Thanks, > Brenda > Jonathan Siegle Center for Academic Computing [EMAIL PROTECTED] Penn State University 814-865-5840 University Park, Pa 16802
