Post reply

Database Infrastructure

  • May 28, 2004 at 3:20 am

    #82911

    Hi, I need to design a database infrastructure for a project that iam involved with.

    The main point is to come up with a diagram showing all components that are required to satisfy the client requirements. I will not discuss the actual project but this is a similar situation. How do I come up with a structure?

     

    Recently due to the recent spate of terrorist activities around the world, the US government has decided to set up a new database that is to record the activities of all US.  This will involve having all their personal details, photographs, relations and so on.  They are required to have an identity chip and transmitter attached to them at all times that will record the coordinates of where they are every few minutes.  All of this will need to be logged in the database.  This database needs to be constantly updated and thus is a 24/7 operation with very little downtime.  If there is maintenance that needs to be done then there will need to be some sort of replacement database to go online during the down time.  This replacement database thus needs to be kept up to date with the latest changes and also needs to have the changes made to it during downtime transferred over to the primary database when it becomes operational again.  (Consider log shipping, remember, you only have a window of opportunity for updating database images of only a few minutes).

    Facilities are required for offline analysis of the database on a 24 hour basis.

     

    Governmental Policies on Security, Disaster Recovery and Availability:

     

    1. There will need to be downtime for maintenance every month for a maximum of 1 hour.
    2. There maximum database size for the operational database is around 100 Terabytes
    3. Peak hours would be around 6-10 am and 4-7pm, both weekdays and weekends.
    4. Allowable downtime would be only 5 minutes if a database fails.
    5. Able to recover all data 2 minutes before recovery.
    6. There is no limit set on the size of the budget.
    7. There should be backups stored at several different locations, these locations would be dotted around the country to avoid sensitive data being lost, the closest one would used as the offsite backup, plus there would be one warm backup on standby and one hot spare.
    8. Some pieces of the database must be available at remote disconnected locations
    9. The required minimum bandwidth is 1 Gigabyte per second on the network path between the primary server and the backup servers (This is the network path that will be used for backup and restore operations).
    10. Must be secure from external intrusion
    11. Access to data must be based on user roles
    12. All data access must be auditable

    What components do I need ? Please help

     

  • May 31, 2004 at 8:00 am

    This was removed by the editor as SPAM

  • May 31, 2004 at 9:33 am

    #508418

    You need to talk to people that do this sort of thing, like NasDaq, Dell, etc. People that need to handle high volumes with high uptimes on MS technology. It can be done, but you don't want to repeat mistakes. Talk to people that make it happen and then find consultants that HAVE ALREADY DONE IT.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply