Adding or Extending SAN Disk(s)

to Existing Windows Servers

Enterprise Hosting Services

Operating Systems Engineering

Version 1.0

June 21, 2005

 Adding or Extending SAN Disk(s)
to Existing Windows Servers
Overview

Statement of This document contains proprietary and confidential information. All data
Confidentiality submitted is provided in reliance upon the recipients agreement not to use or
disclose except in connection with its business dealings with Wells Fargo.
The recipient of this document agrees to inform its present and future
employees who receive or have access to the information contained in this
document of its confidential nature, and to instruct each employee that he/she
must not disclose any information concerning this document to others except
to the extent that such matters are generally known to, and are available for
use by, the public. The recipient of this document agrees that it will not
duplicate or permit others to duplicate any material contained herein except
for its own internal use.

BY ACCEPTANCE OF THIS DOCUMENT, RECIPIENT AGEES TO

BE BOUND BY THE FOREGOING STATEMENT.

Introduction This image installation is to be used in conjunction with the manual server
build document. The steps to follow are listed below. The intention of this
process is to significantly reduce the number of manual steps required.

It must be noted that the quality assurance procedure should be followed post-
installation as the end result of the server build must remain the same
regardless of the procedure followed.

This document is intended for OSE engineers, the EHS Level 2 Intel Support
Team and ESM engineers.

Contents This publication contains the following topic.

Topic See Page

Procedure 3

2
Procedures

Step Action
1 A Change Request is needed. Please confirm that the Change
Request is submitted by the business unit and is approved.
2 Send a notification prior to your action to all concerned groups and
individuals.
3 Complete a full backup successfully.
4 Reboot the server and ensure that the server comes back up healthy
without changes. If the server has another issue, you should stop
here.
5 Contact ESM to disconnect secondary path to the LUN.
6 Verify that a path has been disconnected with the HDLM software
on the server.
7 Reboot the server and ensure that the server comes back up healthy
without changes. If server has another issue, you should stop here.
8 Uninstall HDLM 5.2 and reboot the server.
9 Install HDLM 5.5 and reboot the server to ensure that disks on a
Hitachi 9980 and the TagmaStore storage devices are visible to the
operating system.
10 Verify that you have only one path using HDLM 5.5.
11 Contact ESM engineer to add new LUN or extend the existing
LUN and then reboot the server.
12 Verify that you can see additional allocated disk space, but do not
format or extend.
13 Contact ESM engineer to enable secondary path and then reboot
the server.
14 Verify that you see only one set of disks from both paths, If not,
you need to troubleshoot.
15 Format or extend additional allocated space.
16 Reboot one time to ensure that the server is still healthy.
17 Send a notification of completion to all concerned parties.
18 Send an email to Chris Shearman using subject of upgrading
HDLM from 5.2 to 5.5 with details of Change Request number and
server name(s).