I understand it from the TSM side, it's the Linux side that I'm not sure about. What does it take(ie hardware, software) to get to a SAN, so that we can use the disk for a storage pool?
We are running a Z/890 with an IFL, and SuSE Linux running under VM 5.1. Gene Walters System Programmer WV Dept of Administration - OT 304-558-5914 ext 8902 Fax 304-558-1351 >>> [EMAIL PROTECTED] 5/31/2007 3:40 PM >>> > Where is it documented? The description is in the TSM Administrators Guide in the "Using Magnetic Disk Devices with TSM" chapter (my manuals are old, but this hasn't changed since the ADSM days). The important stuff is in the description of DEVTYPE=FILE and DEVTYPE=DISK options for device classes and storage pools. With DEVTYPE=FILE, you essentially define the SAN storage as a bunch of files emulating tapes, and have TSM spool directly to them. TSM doesn't care about what kind of disk storage the files live on as long as the operating system can access it. DEVTYPE=FILE volumes can also be used for database dumps and export/import processing, so if you're tape-constrained on the Linux guest or you want to use normal 390 tape drives, this is a partial way to cheat on the TSM stupidity of not supporting channel-attached tape. With DEVTYPE=DISK, you use DEFINE VOLUME, and add the volumes to a storage group as normal. DEVTYPE=DISK volumes are better suited for random-access work, but can't be used for database dumps, etc. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
