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.

Slides:



Advertisements
Similar presentations
Test test Please press the F5 key to begin. (Then, press the Page Up or Page Down keys to move through the following 3 slides.)
Advertisements

Big Data Working with Terabytes in SQL Server Andrew Novick
Transaction.
Shared File Service VM Forum January, SFS Topics Targeted Usage Security Accessing CIFS Shares Availability & Protection Monitoring Pricing.
Oracle Data Guard Ensuring Disaster Recovery for Enterprise Data
1 © Copyright 2010 EMC Corporation. All rights reserved. EMC RecoverPoint/Cluster Enabler for Microsoft Failover Cluster.
Toolbox Mirror -Overview Effective Distributed Learning.
Page 1JSOC Review – 17 March 2005 Database Maintenance Karen Tian
Page 1JSOC Review – 17 March 2005 DRMS Core System Karen Tian
1 Choosing Disaster Recovery Solution for Database Systems EECS711 : Security Management and Audit Spring 2010 Presenter : Amit Dandekar Instructor : Dr.
DePaul Bears Try Your Luck!. Why buy this product? Approximately 1,000,000 cell phone users Approximately 2,000,000 or more people play the lottery New.
1© Copyright 2011 EMC Corporation. All rights reserved. EMC RECOVERPOINT/ CLUSTER ENABLER FOR MICROSOFT FAILOVER CLUSTER.
DATABASE MANAGEMENT SYSTEMS 2 ANGELITO I. CUNANAN JR.
1 Figure 10-9: Business Continuity Planning Business Continuity Planning  A business continuity plan specifies how a company plans to restore core business.
1 Disaster Recovery Planning & Cross-Border Backup of Data among AMEDA Members Vipin Mahabirsingh Managing Director, CDS Mauritius For Workgroup on Cross-Border.
Distributed Databases
Disaster RTO SLAYearlyMonthly 99%3.65 days7.20 hours 99.5%1.83 days3.60 hours 99.9%8.76 hours43.8 minutes 99.95%4.38 hours21.56.
SQL Server 2008 Implementation and Maintenance Chapter 7: Performing Backups and Restores.
10/26/00Splitting Access Databases...1 Preparing for Access 2000 Windows 2000/Office 2000 Roll-out.
Business Continuity and Disaster Recovery Chapter 8 Part 2 Pages 914 to 945.
Consistency And Replication
Sofia, Bulgaria | 9-10 October SQL Server 2005 High Availability for developers Vladimir Tchalkov Crossroad Ltd. Vladimir Tchalkov Crossroad Ltd.
CH2 System models.
Chapter 16 Designing Effective Output. E – 2 Before H000 Produce Hardware Investment Report HI000 Produce Hardware Investment Lines H100 Read Hardware.
CSU - DCE Internet Security... Privacy Overview - Fort Collins, CO Copyright © XTR Systems, LLC Setting Up & Using a Site Security Policy Instructor:
Database Management System Module 5 DeSiaMorewww.desiamore.com/ifm1.
Information Availability Brett Paulson Sr. VP and Chief Information Officer Board of Trade Clearing Corporation FIA – November 7, 2002.
©2006 Merge eMed. All Rights Reserved. Energize Your Workflow 2006 User Group Meeting May 7-9, 2006 Disaster Recovery Michael Leonard.
ICT Standards and Guidelines The Structure of the Project Akram Najjar CNSI – Senior Consultant Director of InfoConsult.
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 12 Distributed Database Management Systems.
Types of Electronic Infection
1 Data Guard. 2 Data Guard Reasons for Deployment  Site Failures  Power failure  Air conditioning failure  Flooding  Fire  Storm damage  Hurricane.
Module 1: Exploring Replication. Overview Understanding SQL Server Replication Setting Up Replication Understanding Agents in Replication Securing Replication.
Module 11: Introducing Replication. Overview Introduction to Distributed Data Introduction to SQL Server Replication SQL Server Replication Agents SQL.
Hands-On Microsoft Windows Server Implementing Microsoft Internet Information Services Microsoft Internet Information Services (IIS) –Software included.
7. Replication & HA Objectives –Understand Replication and HA Contents –Standby server –Failover clustering –Virtual server –Cluster –Replication Practicals.
Chapter 15: Achieving High Availability Through Replication.
© Wiley Inc All Rights Reserved. MCSE: Windows Server 2003 Active Directory Planning, Implementation, and Maintenance Study Guide, Second Edition.
ALMA Archive Operations Impact on the ARC Facilities.
1 Bill Hayden Director, Data Services Edward Jones.
Fast Crash Recovery in RAMCloud. Motivation The role of DRAM has been increasing – Facebook used 150TB of DRAM For 200TB of disk storage However, there.
Eduardo Gutarra Velez. Outline Distributed Filesystems Motivation Google Filesystem Architecture The Metadata Consistency Model File Mutation.
 Replication is the process of copying database information  Replication is used for:  Backing up your database  Migrating to a new server  Mirroring.
SQL Server 2005 Implementation and Maintenance Chapter 12: Achieving High Availability Through Replication.
Ing. Erick López Ch. M.R.I. Replicación Oracle. What is Replication  Replication is the process of copying and maintaining schema objects in multiple.
High Availability in DB2 Nishant Sinha
Module 9 Planning and Implementing Monitoring and Maintenance.
Database technology Introduction ER Modeling Database objects (intro) SQL.
KCIUG 30 January, 2004Raw Tables for Improved Load Performance1 Christopher Coleman Database Analyst Mediware Information Systems.
Business Continuity Planning for OPEN OPEN Development Conference September 18, 2008 Ravi Rajaram IT Development Manager.
Oracle Architecture - Structure. Oracle Architecture - Structure The Oracle Server architecture 1. Structures are well-defined objects that store the.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Mario Reale – GARR NetJobs: Network Monitoring Using Grid Jobs.
Log Shipping, Mirroring, Replication and Clustering Which should I use? That depends on a few questions we must ask the user. We will go over these questions.
 Computer hardware refers to the physical parts of a computer and related devices. Internal hardware devices include motherboards, hard drives,
Click to edit Master title style Sytel’s High Availability Strategy © 2012 Sytel Limited. All rights reservedVersion 2.5.
Cofax Scalability Document Version Scaling Cofax in General The scalability of Cofax is directly related to the system software, hardware and network.
Step-by-Step Guide to Asynchronous Data (File) Replication (File Based) over a WAN Supported by Open-E ® DSS™ Software Version: DSS ver up85 Presentation.
9 Copyright © 2004, Oracle. All rights reserved. Getting Started with Oracle Migration Workbench.
Veeam Availability Suite v9. Availability for the Always-On Enterprise.
Backups for Azure SQL Databases and SQL Server instances running on Azure Virtual Machines Session on backup to Azure feature (manual and managed) in SQL.
Distributed Database Management Systems
Lead SQL BankofAmerica Blog: SQLHarry.com
AlwaysOn Mirroring, Clustering
Maximum Availability Architecture Enterprise Technology Centre.
Introduction to Replication
Gluondb1 (online) Resides on gluon25, own IP address
Windows Azure Migrating SQL Server Workloads
AlwaysOn Availability Groups
LO3 – Understand Business IT Systems
Designing Database Solutions for SQL Server
Presentation transcript:

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

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

Page 3JSOC Review – 17 March 2005 Layouts - Basic

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

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