Using Tivoli Storage Manager w/SAN

2007-05-31 Thread Gene Walters
Hello,

Has anyone here setup TSM on Linux using a SAN as their main storage
pool?  Is it possible?



Gene Walters
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8902
Fax 304-558-1351

--
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


Betr.: Using Tivoli Storage Manager w/SAN

2007-05-31 Thread Pieter Harder
Hello Gene,

yes, it is possible. We have all disk pools for TSM for Linux on zSeries on an 
IBM DS8300.

Best regards,
Pieter Harder

[EMAIL PROTECTED]
tel  +31-73-6837133 / +31-6-47272537

>>> Gene Walters <[EMAIL PROTECTED]> 05/31/07 3:23  >>>
Hello,

Has anyone here setup TSM on Linux using a SAN as their main storage
pool?  Is it possible?



Gene Walters
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8902
Fax 304-558-1351

--
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

Brabant Water N.V.
Postbus 1068
5200 BC  's-Hertogenbosch
http://www.brabantwater.nl
Handelsregister: 16005077

--
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


Re: Using Tivoli Storage Manager w/SAN

2007-05-31 Thread David Boyes
> Has anyone here setup TSM on Linux using a SAN as their main storage
> pool?  Is it possible?

Yes, it works as documented although you should use the DASDtape (disk
emulates tape) approach, and ensure you have defined a high number of
"devices" for that pool. 

--
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


Re: Using Tivoli Storage Manager w/SAN

2007-05-31 Thread Gene Walters
Where is it documented?

Gene Walters
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8902
Fax 304-558-1351

>>> [EMAIL PROTECTED] 5/31/2007 9:42 AM >>>
> Has anyone here setup TSM on Linux using a SAN as their main storage
> pool?  Is it possible?

Yes, it works as documented although you should use the DASDtape (disk
emulates tape) approach, and ensure you have defined a high number of
"devices" for that pool.

--
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


Re: Using Tivoli Storage Manager w/SAN

2007-05-31 Thread David Boyes
> 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


Re: Using Tivoli Storage Manager w/SAN

2007-06-01 Thread Gene Walters
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


Re: Using Tivoli Storage Manager w/SAN

2007-06-01 Thread David Boyes
> 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?

On the hardware front, you need a FICON adapter with the FCP microcode
feature, and whatever jumper cables you need to connect to your SAN
switch. 

You have the software support in your VM and in Linux already. Your SAN
admin will need to define a volume for you, and will give you the WWPN
information you need to feed CP and Linux to get access to the device.
Once that's done, format it, partition it, and mkfs it like normal,
mount it in your Linux guest, add it to /etc/fstab, and start defining
TSM volumes on it. 

--
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


Betr.: Re: Using Tivoli Storage Manager w/SAN

2007-06-01 Thread Pieter Harder
If you have z/VM, SLES and TSM for Linux on zSeries you are all set from the 
software side. On the hardware side you need two FC ports  configured for chpid 
type=FCP (assuming you want failover/load balancing, otherwise you can scrape 
by on 1 port) out of a Ficon card and connected to a SAN switch.
If you have all that it is a matter of doing it.

Best regards,
Pieter Harder

[EMAIL PROTECTED]
tel  +31-73-6837133 / +31-6-47272537

>>> Gene Walters <[EMAIL PROTECTED]> 06/01/07 5:02  >>>
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

Brabant Water N.V.
Postbus 1068
5200 BC  's-Hertogenbosch
http://www.brabantwater.nl
Handelsregister: 16005077

--
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