ppt

musicincurableData Management

Jan 31, 2013 (3 years and 10 months ago)

82 views

Minerva DB Taking Stock

Lee Lueking

June 23, 2009

June 23, 2009

MINERvA DB Taking Stock

2

Outline


Status/plan for the SAM catalog


All the other DB’s


Moving ahead w/ the databases

June 23, 2009

MINERvA DB Taking Stock

3

Data File Catalog w/ SAM


Oracle instance on
Minosora3 (minos dev
machine): minerdev


SAM server on minos
-
sam02: minerva_dev


SAM client installed on
minerva05 +
minervadaq02


Web: http://neutrino
-
dev.fnal.gov/computing/fin
drun_sam.html

SAM

ORACLE

Sam

server

SAM client

(on minerva05)

Web interface

(ala MINOS)

June 23, 2009

MINERvA DB Taking Stock

4

SAM Status and Plan


All DAQ files since April are being catalogued in sam
minerva
-
dev.


File Count: 2287


Average File Size: 105.84MB


Total File Size: 236.39GB


Total Event Count: 2816045


Need Minerva to gain some experience using this


Create production instance, and re
-
load all files. Options:


Share Minos production DB server


Use new Minerva DB server (discussed next)


Begin adding merged and processed data into catalog


June 23, 2009

MINERvA DB Taking Stock

5

Other (possible) DB Information Inventory


FEB (Front End Board) Cal, Gain Cal are in COOL


Alignment is currently in XML format


PLEX is in XML format


Geometry is in XML format


Hardware Database is in relational format on MySQL
server. This has been ported to PostgreSQL in the past.


Run conditions, Beam info, Detector Control System
(DCS), are in data stream.


Detector configuration is in a file in CVS.

June 23, 2009

MINERvA DB Taking Stock

6

Ideas for Moving Ahead


Could store XML files as blobs in COOL
with appropriate IOV info.


Or store their CVS version/tags
information for the XML files in COOL

June 23, 2009

MINERvA DB Taking Stock

7

In Progress + Issues


In Progress


Minerva DB machine has been on site for +6
months.


Install RHEL on Maurine’s list (ETA=soon).


Need Oracle instance installed there.


Issues


Can we share instance for SAM and other apps
(COOL, etc. )?


Minerva does NOT have machine for Dev or Int.



June 23, 2009

MINERvA DB Taking Stock

8

DB Requirements (proposal)


Considerations

1.
What service level is required (including hardware support):
24x7
, 8x5,
8x7
(open to discussion)

2.
Transaction support:
y
/n

3.
Referential integrity:
y
/n

4.
Backup and recovery and tolerance for data loss:
hot

or cold backups ,
snapshots, point in time recovery

5.
Free space recovery features: y/n

6.
Client software support and distribution: ups/upd, is there support for
the database client? y/n

7.
Performance analysis, tuning and recommendations:
y
/n

8.
Security, authentication level: ldap, krb,
pwd

or mix

9.
Time to recover from hardware failure:
8 hours (?)


10.
Expectation level for planned/unplanned downtimes:
2/8 hours (?)



Requirements and list and support levels described at:

http://www
-
css.fnal.gov/dsg/external/database_tier_explanation.htm

finis

discussion