BaBar Database Environment
At SLAC, all BaBar members are in the Unix group bfactory. We created a special user objysrv that is in this group and that we use to run the lock and AMS servers. All Objy areas are group writable by bfactory. The software sits in an AFS area readable only by AFS group g-babar:com-obj, which includes those users who have signed the Objy agreement.
User test federations
User test federation are located on objyserv07, which has 1.5 TB of disk space, split in two file systems. Users with login names starting with A-H are using one file system, and one lock server. All others use the other file system and second lock server. User federations are accessed via NFS.
User test federations are not intended for production, and not meant to store important data, that needs to be kept for a long time and accessed by other users. If your data needs long term storage, consider putting in the production federation, in physics analysis groups, such as charmonium. If you need new groups, please contact computing management first for approval. For MC-related tests, another option is to use simulation test federations. Please contact the MC production coordinator about this.
There is a disk space saving policy for user test federations. Owners of test federations that are not used for two weeks are automatically warned every two weeks, and if their federations are still not active five days after warning (there was no access to those federations), they are automatically deleted.
Following are useful links related to user test federations:
- How do I create a test federation?
- How do I check whether lock server is running?
- How do I load conditions?
- Complete FAQ section
- FDID Allocation
Public analysis federations
Public analysis federations, such as simuboot or physboot contain data produced by Prompt Reconstruction farms and MC production farms (both at SLAC and at remote sites).
The data resides on data servers (datamoveXX, objydataXX machines) and catalogs, and other metadata are on special catalog servers. Journal files are on separate machines.
All access to public analysis federations data is done via AMS.
While the data may actually belong to different physical federations, users are using single access point to all collections of either physics or simulation data. From the user's view, all data resides in one federation, called bridge federations.
There are monitor jobs which check for AMS running on data servers and restart servers when they pass away.
Following are useful links about public analysis federations:
- Public Analysis Federations at SLAC
- I'm getting a database related error...what happened?
- Outage Schedule
- What Federations are Locked?
- Event Store Data Management
BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us
Page Owner: Jacek Becla
Last Update: June 13, 2002