Steve The upgrade section may help, see the following link pay particular attention to the "Space requirements for the V6 server system" section.
On my win systems (2008x64) I used 3-4 volumes (located on separate SAN luns) for the DB, and separate volumes/luns for each the Active log, Archive, log, log mirror, and Fail-over log. Obviously, the better the faster the disks, the better the server will perform. Originally I was forced to set them up on an EMC Clariion but performance was dismal to say the least. After convincing the powers-to-be that disk performance was a problem they approved a move to an EMC Vmax, the difference was phenomenal. http://pic.dhe.ibm.com/infocenter/tsminfo/v6r3/index.jsp?topic=%2Fcom.ib m.itsm.srv.upgrd.doc%2Ft_srv_upgrd_plandb.html (IBM Tivoli Storage Manager servers > installing and upgrading the server > upgrading from v5 to v6 > planning the upgrade > planning space for the upgrade process and the upgraded server > space requirements for the V6 server system) ~Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Steven Harris Sent: Sunday, September 09, 2012 8:30 PM To: [email protected] Subject: [ADSM-L] Disk/Volume/mountpoint access for TSM 6.3 on Windows Hi All The TSM Documentation is, compared to much I have seen, wonderful. It covers system functions and facilities marvellously, but what it doesn't do well is spell out best practices from the numerous options available. I am installing TSM 6.3 on windows. Long term readers will recall my travails with NDMP and linux. The solution is to locate the widows client on this new server box and back up using a proxy node thta resides on the server. On Linux, AIX the layout is simple, one volume for DB another for active log, a third for archive log. Windows does not in general work this way. Looking at the DB2 doc for windows it seems that the DB is allocated as a number of files of a given size, but the examples place the archive log in its own windows drive letter, without explicitly stating why. Does anyone have experience of how to layout the TSM 6 database on Windows that they would be willing to share? RTFM is a valid response if you tell me which manual to read. I've already tried the obvious without finding what I'm looking for, but may have overlooked some clue. Thanks Steve Steven Harris TSM Admin Canberra Australia.
