IN2P3 HPSS Migration report V 5.1 6.2.2.2

IN2P3 HPSS Migration reportIN2P3 HPSS Migration reportV 5.1 V 5.1 6.2.2.2 6.2.2.2Pierre-Emmanuel Brinette

IN2P3 Computing Center (Lyon – France)

[email protected]

Overview

Context of the migration What’s new in HPSS 6.2 IN2P3 HPSS Configuration Migration Planning Metadata Migration Conclusion

Friday, April 21, 2023Pierre-Emmanuel Brinette 2

Context of migration

IN2P3 use HPSS as main MSS since 1999. The last major upgrade (to v 5.1) has been made

in 2005. Migration to HPSS 6.2 planned since 2007:

– HPSS 6.2.1 test platform setup in mid 2007. IN2P3 HPSS staff has changed in 2008.

– The engineers that manage HPSS leave the center.– The new team has no experience in HPSS.

In 2009 upgrade to HPSS 6.2 is necessary – Support for T10k-B drives.– Remove End-Of-Life equipments.


Overview



What’s new in HPSS 6.2.2.2

Major changes:– DCE is no longer used as security mechanism.– Some changes in the HPSS API.

New Authentication/Authorization mechanisms: – Unix/Unix : /etc/passwd or NIS – Kerberos/LDAP.

Officially supported platform: – AIX 5.3 and RHEL 4.7. – DB2 v 9.1.


Overview



IN2P3 HPSS Configuration (early 2009)

25 M files / 6 Pb + 2000 users Main access protocol is RFIO HPSS is used as tape

backend for others storage systems:– xrootd: 1 M files /1 Pb– SRB used for files transfers– dcache 2 M files / 2 Pb for grid


HPSS-API

HPSS

xrootd dcache

RFIOSRB

Local users only

Grid users (SRM)

Local and remote users

IN2P3 HPSS Configuration (early 2009)

HPSS 5.1– 42 disk movers

– 2600 disk volumes

– 28 tape movers

– 66 drives

– Gbits LAN


SAN2/4 gbits

FASt 90012 Tb

HPSS MASTERCore Server

AIX 5.1DB2 8DCE

DS8300120 Tb

DDN240 Tb

HPSS SLAVE Core Server

AIX 5.2DCE

6 Disk Movers AIX 5.1

(incl. 3 DCE mover)

4 Tape Movers AIX 5.1

32/64 x 64Gb LUN per mover


(incl. 2 DCE mover)

32 x 64Gb LUN per mover

12 Disk Movers RHEL 4.7

80x64Gb20x256Gb LUN per mover

SCSI Disk arrayDB2 metadata


SRB serversSolaris 10HPSS API

20 drives 9940

12 drives 9840

34 drives T10k-A

3x SL8500 / 10000 slots

1x STK9310 / 6000 slots

Gbit LAN

RFIO serversAIX 5.1/5.2DCE ClientHPSS API

Overview



Migration Planning

SAN2/4 gbits

FASt 90012 Tb

HPSS MASTERCore Server

AIX 5.1DB2 8DCE

DS8300120 Tb

DDN240 Tb

HPSS SLAVE Core Server

AIX 5.2DCE


(incl. 3 DCE mover)


32/64 x 64Gb LUN per mover


(incl. 2 DCE mover)

32 x 64Gb LUN per mover


80x64Gb20x256Gb LUN per mover

SCSI Disk arrayDB2 metadata



20 drives 9940

12 drives 9840

34 drives T10k-A

3x SL8500 / 10000 slots

1x STK9310 / 6000 slots

Gbit LAN

RFIO serversAIX 5.1/5.2DCE ClientHPSS API


Migration to HPSS 6Migrate to HPSS

6.2

Migrate to HPSS

6.2

Migrate to HPSS

6.2

Migrate to HPSS

6.2

Migration goal– Clean-up

configuration

– Remove EOL hardware

– Decrease the number of volumes

Migration Planning


Migration goal– Introduce new

hardware– Use 10 Gbits for

mover

SAN2/4 gbits

New Core serverAIX 5.3DB2 9.1

DDN480 Tb


10 Gb LAN

40 x 1To LUN per mover



20 drives 9940

12 drives 9840

34 drives T10k-A

3x SL8500 / 10000 slots

1x STK9310 / 6000 slots

1/10 Gbit LAN

RFIO serversAIX 5.3

HPSS API30 drives T10k-B6 Tape Movers

AIX 5.34Gbit FC / 10 Gb LAN

DS8300DB2 Metadata

NIS

New

New

10 Gb

New

New

Migration Planning

IBM Migration requirements– Migration procedure applied on the production

server.– Metadata migration procedure assume a 1 core

server and a 1 subsystem.– Empty Disk volumes.– UID/GID in DCE consistent with new auth/authz

system (ie NIS).


Migration Planning

IN2P3 CC constraints – Change the HPSS Core server and remove

secondary server (EOL) – Use NIS for Auth/Authz– Modify metadata of 4 subsystems– Drastically reduce the number of Disk

Volumes/hpss mover/servers– Introduce the new tape movers


Migration Planning


Feb 09 Apr 09 May 1, 09 May 15, 09

Jun 1, 09 Jun 5, 09

HPSS 6.2 Test platform setup

Migration case study with IBM Support

Dec 08

Writing migration procedure

HPSS 6.2 metadata migration platform setup

Setup new production server

Migration

(Non linear time line)

Clean-up production config

Migration Planning


May 31

Jun 1 Jun 2 Jun 3 Jun 4 Jun 5

Stop HPSS access

Purge disk

Reduce disk volume

May 25

Shutdown HPSS

Export & Convert DB2 metadata

Import in new server Configure new

server

RFIO Installation

(Non linear time line)

HPSS mover installation

Tests

Overview



Metadata migration

HPSS 6.2 introduce new DB2 Tablespace containers scheme Use a production metadata backup after HPSS shutdown On a temporary HPSS systems:

– Create exactly the same raw devices than the ones used on the production server

– Restore the backup, run metadata conversion script, and export DB content

On the new production system:– Create the databases with HPSS install procedure (mkhpss)– Populate the databases with the DB content just exported


# DB2 BACKUP FULL OFFLINE

1. # DB2 RESTORE …2. # hpss_md_convert …3. # db2move export …

1. # mkhpss subsysx …2. # db2move import …

HPSS 5.1 PRODDB2 8

HPSS 6.2 TestDB2 9

Same TS containersThan HPSS 5.1 prod

HPSS 6.2 new PRODDB2 9.1

New TS containers

Overview



Conclusion


Migration issues– Even with a good preparation we have encountered

(small) issues during the migration. – Details available on demand.

Benefits– Supported HPSS version.– Stability improved.– Configuration simplified.– Metadata queries now runs faster.– Gain lot of experience for the new staff !

Conclusion


After migration– Repack of remaining 9940 tapes– Remove of last PowderHorn library– Repack of T10k-A T10kB (Big files SC)– Repack 9840 T10k-A Sport

Future – HPSS 7.1 migration in 2010– 4th SL8500 with T10K-B– Add more disk (probably DDN)


Thanks for your attention

Date post:	26-Jan-2016
Category:	Documents
Upload:	oihane
View:	42 times
Download:	2 times

IN2P3 HPSS Migration report V 5.1 6.2.2.2

Documents