Hi.
Some years ago (I think 2) I make a tests to boot Windows 2000 from ESS.
The configuration was as follow:
- IBM eServer xSeries 440
- Windows 2000 Advanced Server (machines was with 4 CPU/8 GB RAM)
- QLogic 2300 adapter (IBM FC2-133 Host Adapter)

The tests are successful, but there are some problems:
1. IBM Doesn't support boot for xSeries (Intel based servers) from SAN,
but the Qlogic does
2. There are some problems with updating SDD drivers (because I want to
use 2 paths to ESS for redundancy)
3. As the result test was successful, but the customer agrees to me that
unsupported solution for production environment is bad idea.


Best Regards,
Svetoslav Tolev






"Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
19.01.2005 23:46
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
SAN Booting






Hi all:



We are looking at booting servers from a SAN instead of local disks.



We are planning to use either TSM image or file backups of the OS drives
(Windows 2003) to make server deployment and bare metal restores
quicker:



Install Windows (and apps) on hardware

Run SYSPREP

Backup SAN disk from another system (either TSM image backup or TSM file
system backup)



To roll out new hardware or perform BMR:

Recover TSM image or file system backup (from another system)

Plug in new hardware to this system and run SYSPREP



My questions on this:



Is anyone booting from SAN?

What applications?

Is anyone booting a TSM server from a SAN?

Are there any issues (TSM and others) to look out for?



Is anyone using TSM as above for System Deployments?

Any issues?



I apologize that some of these questions may not be TSM related so
please reply directly to me rather than the list.



Thanks,



Tim Rushforth

City of Winnipeg

trushforth AT winnipeg DOT ca