Transcript Slide 1

Site Maintenance
Site Maintenance
May 2010
1
M3 Maintenance Management
System
System Upgrade 2009/10
Kevin Farish
M3 Technical Manager
May 2010
Site Maintenance
Introduction
• The M3 system hardware & software were upgraded at
the start of 2009
• Included upgrade to M3 7.1 Tech, Workplace 5.3.3, and
Streamserve v4
• The M3 development system was upgraded at the start
of 2010
• New development system uses virtualised Wintel
servers
Site Maintenance
May 2010
3
Reasons for the upgrade
• System installed in 2004 to replace obsolete maintenance
management system with a single Sun V480 running the
M3 application and the Oracle database
• Dedicated Oracle database server (Sun V480) added in
2006 with additional storage capacity
• This upgrade designed for a significant increase in user
base from ≈ 700 to ≈ 2000; integration into M3 of other
obsolete systems; and improved system performance
• SAN storage added to cope with increasing data volumes
(approx. 2% per month = doubling every 3 years)
Site Maintenance
May 2010
4
M3 System Upgrade
• All M3 system servers were replaced (with the exception
of the M3 Output Manager) to provide significantly
increased computing power
• The upgrade added a dedicated SQL database server
• Application and Database servers upgraded to Solaris 10
• The core M3 system application software was upgraded to
Version 7.1 (Tech). M3 Workplace upgraded to v5.3.3
• M3 databases moved to a SAN (Storage Area Network)
for increased performance and reliability
• The Oracle database was upgraded from v9 to v10g
Site Maintenance
May 2010
5
M3 System Diagram
End Users
Data Centre
Site Maintenance
May 2010
6
M3 Production Servers
M3 Application Server
Sun V490 (4x 1.8GHz UltraSparc IV+, 16GB)
M3 Database Server
Sun T5120 (T2 8-core cpu, 64 threads, 32GB)
M3 Workplace
HP Proliant DL380 G5 (1x 2.66GHz Quad-core Xeon)
M3 SQL Server
HP Proliant DL580 G5 (2x 2.4GHz Quad-core Xeon)
M3 Output Manager
HP Proliant DL380 G3 (2x 2.8GHz Xeon)
M3 BPW1
HP Proliant DL380 G5 (1x 2.66GHz Quad-core Xeon)
M3 LBI2
HP Proliant DL380 G5 (1x 2.66GHz Quad-core Xeon)
SAN3
Hitachi HDS 9570V
1. Business Performance Warehouse
2. Lawson Business Intelligence
3. Storage Area Network
Site Maintenance
May 2010
7
Remote
Data Centre
B151
Sellafield
1x New LTO-3 Tape Drive to be
added to Existing Centralised IBM
3584 Tape Library
B910
Sellafield
M3
New UNIX Media Server
(Netbackup Media Server)
BCAN
1
2
3
4
5
6
7
8
6
7
8
ONLINE
SPARE
POWER
SUPPLY
POWER
SUPPLY
MIRROR
PCI
RISER
CAGE
HP
ProLiant
DL380G5
PPM
DIMMS
PPM
HDS 9570v
SAN Attached
Array
PROC PROC
INTER
LOCK
FANS
OVER
TEMP
1
UID
2
BVERBCKUP1
(Netbackup
Master Server)
1
2
3
4
5
ONLINE
SPARE
POWER
SUPPLY
POWER
SUPPLY
MIRROR
PCI
RISER
CAGE
PPM
PPM
DIMMS
PROC PROC
INTER
LOCK
FANS
HP
ProLiant
DL380G5
2Gps Fibre Channel
Production
Existing
Centralised IBM
3584 Tape
Library (8x LTO-2
Drives)
OVER
TEMP
UID
Brocade 4100
(redundant
switch fabric)
1
2
BNSTSBCK1
(Netbackup
Media Server)
2Gps Fibre Channel
MIRROR
PCI
RISER
CAGE
2
3
4
5
6
UID
7
8
1
HP DL380 G5 (New LBI
Front-End Server)
HP
ProLiant
DL580
2
1
HP
ProLiant
DL380G5
ONLINE
SPARE
POWER
SUPPLY
POWER
SUPPLY
PCI
RISER
CAGE
2
3
4
5
6
7
8
1
ONLINE
SPARE
POWER
SUPPLY
POWER
SUPPLY
PROC PROC
INTER
LOCK
FANS
OVER
TEMP
2
3
4
5
6
7
8
1
2
3
4
5
6
7
PCI
RISER
CAGE
2
3
4
5
6
7
8
HP
ProLiant
DL380G5
1
POWER
SUPPLY
3
4
5
6
7
8
MIRROR
PCI
RISER
CAGE
HP
ProLiant
DL380G5
PROC PROC
INTER
LOCK
FANS
OVER
TEMP
8
2
ONLINE
SPARE
POWER
SUPPLY
DIMMS
PROC PROC
INTER
LOCK
FANS
1
MIRROR
PPM
PPM
PROC PROC
HP DL380 G3 (Reused MOM Server)
HP DL380 G5 (New
BPW Server)
HP
ProLiant
DL380G5
DIMMS
PPM
PPM
MIRROR
DIMMS
PPM
DIMMS
PPM
POWER
SUPPLY
PPM
1
ONLINE
SPARE
POWER
SUPPLY
HP ProLiant DL580 G5 (New
Dedicated SQL Server for
Workplace, BPW & LBI)
PPM
HP ProLiant DL380
G5 (New Workplace
IIS Websphere
Server)
INTER
LOCK
FANS
OVER
TEMP
OVER
TEMP
G5
UID
1
2
UID
Sun T5120 (New
M3 Oracle DB
Server)
1
2
UID
1
2
UID
1
2
Sun v490 (New M3
Application Server)
BCAN
Production LAN
Database Server
Re-Used Infrastructure
Backup / Storage (BCAN) LAN
Sellafield Ltd Production Restricted LAN (Also used
for iLO, iLOM and ALOM Management)
Fibre Channel SAN
End
Users
New Infrastructure
Site Maintenance
May 2010
8
How the upgrade was managed
• New production system installed, commissioned & tested
in a separate (on-site) data centre
• Two test runs completed for database upgrade (v9 to 10g)
prior to final cutover
• Cutover completed during a 2 day outage
• Previous system left running (but unused) for 1 week as a
fallback position in case of unforeseen problems
• New development system re-used the previous production
M3 Application and M3 Database servers
• Original development system software also upgraded as
an interim measure whilst new development system built
Site Maintenance
May 2010
9
SQL
Server
2005
Workplace
1
App
Workplace
2
App
MOM 1
App
MOM 2
App
BPW 1 /
E-Coll 1
App
BPW 2 /
E-Coll 2
App
LBI 1
App
LBI 2
App
Guest OS
Guest OS
Guest OS
Guest OS
Guest OS
Guest OS
Guest OS
Guest OS
Guest OS
Virtual
Centre /
VMotion
HDS 9570v SAN
Attached Array
Service
Console
Brocade 4100
(redundant switch
fabric)
VMware Virtualisation Layer
UID
2Gbps Fibre Channel SAN
1
HP
ProLiant
DL580
2
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
G5
UID
1
HP
ProLiant
DL580
2
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
Sun
Sun
SUN v480 –
BM3DEVDB1
SUN v480 –
BM3DEVAPP1
2*UltraSparc III
1.2GHz CPU,
10GB
2x VMware ESX Servers
Sellafield Ltd Backup LAN (BCAN) 1000Mbps
Sellafield Ltd Restricted LAN 1000Mbps
FAS3070C
Sellafield Ltd Production Restricted LAN (Also used for ALOM)
activity
status
Storage vLAN (NFS) 1000Mbps
SunFire V 480
vMotion vLAN 1000Mbps
4*UltraSparc III
1.2GHz CPU,
16GB
SunFire V 480
Service Console vLAN 1000Mbps
G5
Re-used Infrastructure
power
FAS3070C
activity
Sellafield Ltd Backup LAN (BCAN)
status
power
NetApp
FAS3020c
Fibre Channel SAN
Vmware ESX Service Console
Storage vLAN (NFS)
VMotion vLAN
M3 Dev DB Server
B151
Vmware
ESX
Servers
VMware
ESX
Servers
End Users
M3
B151
Development
Sellafield
Site Maintenance
May 2010
10
Creating new VMware development environment
• New development system Wintel servers all implemented
on existing ESX infrastructure
• Servers created using a Physical to Virtual (P2V) tool,
VMware vCentre Converter, which created a Virtual
Machine from an Image of the corresponding Production
Servers.
• Each VM configured with new IP addresses and servernames.
Site Maintenance
May 2010
11
M3 Application & Database
• M3 Application and M3 Database servers re-used the
previous production Sun servers
• Both servers were cleared down completely and O/S reinstalled.
• Oracle version 10g installed on database server by DBA
• M3 application installed by copying folder structure from
production server
• System configuration files updated manually by Lawson
prior to starting the application
Site Maintenance
May 2010
12
Send in the Clones
• The Physical to Virtual (P2V) process produces an exact
clone of the real server
• This includes embedded server names, IP addresses, port
numbers, usernames, passwords etc.
• This is ideal for Business Continuity purposes, but
problematic if servers are to be in addition to the original
• Great care is needed to ensure all relevant parameters are
changed prior to application start up to prevent unintended
consequences.
Site Maintenance
May 2010
13
And finally . . .
Any questions?
Site Maintenance
May 2010
14