Presentation is loading. Please wait.

Presentation is loading. Please wait.

Page 1JSOC Review – 17 March 2005 Database Servers Challenges A very large database on the order of a few TB -- We can't copy the whole database in real.

Similar presentations


Presentation on theme: "Page 1JSOC Review – 17 March 2005 Database Servers Challenges A very large database on the order of a few TB -- We can't copy the whole database in real."— Presentation transcript:

1 Page 1JSOC Review – 17 March 2005 Database Servers Challenges A very large database on the order of a few TB -- We can't copy the whole database in real time Transactions-intensive applications -- We can't hope to catch up a day's transactions in a hour's time. Therefore replaying transaction log on the replica is not practicable. Requirements Need a primary JSOC database server Need backup server for our Primary -- Require backup to be ready to take over for Primary at any time, with a reasonable latency, say 30 minutes Need a web server, or a way to provide service to web users. -- Requires hourly update time constraint, 95% up time, maintenance may need to be propagated from the primary server -- Must hold a big database (basically whole JSOC database) -- Front-end software can control data access. * Private user data can remain private via front-end access control Must support remote DRMS systems -- Need a replication database server because remote sites want only selected table sets -- More relaxed time requirement than web users

2 Page 2JSOC Review – 17 March 2005 DRMS DRMS/SUMS A/B system –We will have at minimum two physical servers: a Primary (A) and a Warm-Stanbdy (B) –These machines will be physically identical, or as near as possible. One must be ready to take over for the other in the event of catastrophe or maintenance. –We will create procedures and practice the switch-over between A & B Web Support –Web site data should reflect JSOC data within an approximate latency of one hour –Users such as solar weather and LMSAL will be supported via a direct connection with the Primary DRMS, not the web site. Remote DRMS Support –We anticipate at least eight remote DRMS sites, up to a dozen –Users need subsets of JSOC data; recommend a replication server to supply this data to their DRMS database. Best candidate is SLONY-1 software. Procurement Plan –Procurement planned for approximately the same time as overall hardware procurement for JSOC

3 Page 3JSOC Review – 17 March 2005 Layouts - Basic

4 Page 4JSOC Review – 17 March 2005 Layouts – Disk Snapshot

5 Page 5JSOC Review – 17 March 2005 Layouts – ZFS Solaris file server


Download ppt "Page 1JSOC Review – 17 March 2005 Database Servers Challenges A very large database on the order of a few TB -- We can't copy the whole database in real."

Similar presentations


Ads by Google