Conditions Snapshots
[
BaBar-Conditions
]
- What is a snapshot
- Load a snapshot
- Available Snapshots
- Snapshot Table in ORACLE
Available Snapshots
Below is a list of "offical available snapshots:
| Name | From | Content | Where | Updated |
| analysis |
MASTER | only CDB dbs |
/nfs/objyserv03/objy/databases/snapshot2/master/analysis/current |
daily |
| full |
MASTER | all dbs |
/nfs/objyserv03/objy/databases/snapshots/master/full/current |
every Monday |
| betaMini |
MASTER | only const for Mini analysis |
|
|
Snapshot for Analysis Conditions FDBs
Every day a snapshot from the MASTER is taken containing only the CDB databases
and is imported into the current analysis conditions federation
(as of this writing: cond18boot). This snapshot can be used to update an existing
conditions federation. If a new federation is created this snapshot is not sufficinet
as the legacy databases are also needed. The legacy databases are part of a full snapshot described
below.
Full MASTER Snapshot
A full MASTER snapshot is taken once a week, every Monday. It contains all the
CDB databases and the legacy databases. This snapshot is needed if a new conditions
feederation is created.
BetaMini Snapshot
The beta mini snapshot is a consistent snapshot that contains only those
conditions needed for a BetaMini analysis job. The snapshot is significantly smaller
then a full snapshot. It is in the order of 1.5-2 GB.
Automatic Snapshots
MASTER CDB snapshot
A full CDB snapshot is taken from the MASTER daily (during production). The snapshot contains all CDB databases
but not the legacy databases.
MASTER Full snapshot
A full conditions snapshot is taken once a month. It contains all CDB and legacy databases. This snapshot can
be used to establish a new federation.
IR2 to AMBIENTBOOT
Once a data a snapshot from IR2 is taken. This snapshot contains the IR2 origins from the the
Conditions, Configurations and Ambient domains. The Ambient snapshot is an incremental one.
The snapshot is loaded to AMBIENTBOOT.
snapshot script = BdbIR2ToAMBIENTSnapshot.tcsh
snapshot dir = /nfs/objyserv10/objy/databases/snapshots/ir2/forAmbient
log file = /afs/slac.stanford.edu/g/babar/Bdb/log2/cronlogs/IR2ToAmbientSnapshot_<abbr. weekday name>.log
IR2 to PC1
Every hour a snapshot is taken from IR2 containing the ir2 conditions and
configuration. It runs always 15 minutes past the hour not to interfer with loading of
constants to IR2.
The snapshot is transfered to PC1 but not loaded automaically. Loading the
snapshot to PC1 is controlled by the OPR-controll system. Only if a snapshot is needed
it is loaded.
snapshot script = BdbIR2ToAMBIENTSnapshot.tcsh
snapshot dir = /nfs/objyserv03/objy/databases/snapshot2/ir2/concfg/current
log file = /afs/slac.stanford.edu/g/babar/Bdb/log2/cronlogs/IR2ToAmbientSnapshot_<abbr. weekday name>.log
PC1 (PCn) to MASTER
The new rolling calibration produced in PC1,PC2 and PC3 are loaded to the MASTER.
The following table shows which origins are extract from a PC federation and loaded to the MASTER:
| PC FDB | Origins in snapshot |
| PC1 | pc1, ir2, cfg |
| PC2 | pc2 |
| PC3 | pc3 |
PC1 is used to propagate the ir2 and configuration conditions to the MASTER.
Last modified: Tue Jul 11 17:29:13 PDT 2006
|
