1 / 35

Anatomy of a Archiving Project Basic Principles To Consider

Anatomy of a Archiving Project Basic Principles To Consider. Bruce Fischer, Princeton Softech. Princeton Softech. Proven leader in Enterprise Data Management Solving complex data management issues since 1989

Melvin
Télécharger la présentation

Anatomy of a Archiving Project Basic Principles To Consider

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Anatomy of a Archiving ProjectBasic Principles To Consider Bruce Fischer, Princeton Softech

  2. Princeton Softech • Proven leader in Enterprise Data Management • Solving complex data management issues since 1989 • In-depth functional knowledge of mission-critical applications and the business rules that govern them • Over 2,400 customers worldwide, Including nearly half of the Fortune 500 • At each level of the management organization (CIO, business executives), we appeal to the most universal, broadest business issues • Simplification of Infrastructure • Information Governance • Business Continuity • Business Value

  3. Addressing The Challenges • Key challenges for sites with Custom Applications • Managing Application Performance • Controlling Costs - Mitigating Risks Associated with Data Retention and E-Discovery Requirements How can archiving help?

  4. Explosive Database Growth • Mergers & acquisitions • Organic business growth • eCommerce • ERP/CRM • Records retention: • Healthcare – HIPAA • Pharmaceutical – 21 CFR 11 • Financial – IRS and SEC Rule 17a-4 • Data multiplier effect • According to industry analysts, annual compound growth rates for databases will exceed 125%

  5. The Ongoing Problem Risk Compliance $ Downtime IT Resources How many copies?

  6. The Data Multiplier Effect 1200GB Test Production Total Development Backup 200GB DisasterRecovery 200GB 200GB 200GB 200GB 200 GB Quality Control Data Multiplier Effect Actual Data Burden = Size of production database + all replicated clones

  7. Who is Impacted and how they benefit • Data Growth • Retention and Compliance • Portfolio Optimization • CEO • CIO • Applications • DBAs • Quality Assurance • Business Users • Capacity Planners

  8. Analysts Projections • A new ESG report, "Digital Archiving: End User Survey and Market Forecast 2006-2010," regarding their purchasing intentions for archiving solutions. • 48% of organizations say they will purchase and deploy a database archiving application within the next 24 months • An additional 35% say they expect to purchase a database archiving application at some point beyond 24 months. • Database-resident information will be the fastest growing type of archived information between now and 2010, growing at a CAGR of 79%. Over 4000 Petabytes of database archives will exist in 2010. • The database archiving market will grow at a CAGR of 38.5 percent through 2009- Gartner

  9. Basic Principles for Archiving Data

  10. Assess • Determine application types • Mission critical • Business critical • Targeted for sunset • Decide where to locate the archive • Which storage devices • When to deploy each type • Determine access requirements • Who, what, how, when?

  11. Classify • Identify “Business Objects” to archive • Historical reference snapshot • Examples: Activities, Service Requests • Determine retention requirements • Cross functional consensus • Time value of business object • Deletion requirements • Identify post-archive use cases • Customer service inquiries, audit, e-discovery, trend analysis • SLA for access • Retrieve from archive • Reload to temporary DBMS

  12. Functional Requirements for Archive

  13. Archive • Determine operational practices • Frequency of archive • Automated or manual operations • Online or offline • Define file management • Across storage tiers • Manual or integrated (Tivoli, Symantec, etc.)

  14. Active Data Inactive Data Historical Data Evolving Business Value Value Access Frequency Time

  15. Active Data Tier 1 Inactive Data Historical Data Tier 2 Define Storage Strategies Value Access Historical Data Tier 3 Time

  16. CLOSE_DATE > 01-JAN-2005 CLOSE_DATE > 01-JAN-2001& < 31-DEC-2005 CLOSE_DATE < 31-DEC-2000 Set Migration Policies Tier 1 Value Access Tier 2 Tier 3 Time

  17. Ledgers Archiving a Complete Business Object

  18. Store • Determine format of archives • Archive file system • Define hardware targets • Number of tiers • Types of devices • Establish security parameters • Integration with existing framework • Database, application, network

  19. Cost-Effective Tiered Storage Off-LineArchive Online Archive Current History/Reporting Production Database ArchiveDatabase SAN / NAS Production Database Tape WORM Flat Files Files Time

  20. Access • Analyze use cases vs. cost of access • Goal: match SLA to value to cost • Application independent access • Native application access • Communicate access terms & conditions • SLAs • Resource provisioning • Training on access paths

  21. Dispose • Build cross-functional team • Business, legal, audit, IT • Business owns data, IT manages supporting infrastructure • Determine data deletion policies • Signoff by stakeholders • Which records to delete, and when • Ensure orderly disposal • Automated or manual delete • Audit trails

  22. Getting Started with Archiving Data

  23. Step 1: Business Policies Drive Archiving • Identify applications that manage regulated data • Build consensus among stakeholders on retention and retrieval: • Business owners, application developers, storage • Include CFO, legal, compliance, security • Document your business policies: • Types of data (Active, Inactive/Historical, Reference) • Processes for Archiving, Viewing, Retrieving Objects • Processes for Compliance and Disposal

  24. Define Retention Policies at Business Layer

  25. Step 2: Define the Storage Architecture • Technical Safeguards (Security) • Data integrity safeguards • Access controls – authentication, authorization • Recording media (WORM media or subsystems) • Secure audit trails, duplicate copies, etc. • Data privacy safeguards • Access controls – authentication, authorization • Data encryption • Access logs, audits and reports *Exact requirements depend on regulatory environment

  26. Storage Goals and Criteria Goals: • Cost effective • Easy to manage and scale • Ensure accessibility for many years Selection Criteria: • Storage capacity • Availability • Manageability • Performance • Cost Existing storage technology to be combined with new storage technology (e.g. ATA disk storage) to help reduce cost.

  27. Step 3: Don’t Forget About Process • Important regulatory requirements specify that the data must remain unaltered and accessed only by the proper individuals. • Accessibility, storage and audit policies each result in a specific set of processes that govern their maintenance and education. • Consistent, repeatable, controlled, documented archive and access methods and tools

  28. Possible Alternatives to Archiving • Tune or partition the database • Add capacity • Processors, storage • Back up the database • Purge data • Alleviate symptoms temporarily, but… • Inflate costs • Do not address underlying data growth

  29. Archiving Solution Technical Requirements • Basic Requirements • Support archive, purge and retrieve operations, including selective retrieve • Ensure referential integrity of archived data • Increase database performance and minimize batch windows • Ensure security and maintain access control of archived data • Archive data stored in database as well as the File System, and maintained linkage • Archival Definition • Allow scope of archive and cascading purge to be controlled • Maintain schema information in addition to archive data • Provide pre-defined archival configurations for key objects • Allow pre-defined archival configurations to be modified to reflect configurations made to applications

  30. Archiving Solution Technical Requirements (2) • Archive Data Storage and Access • Provide access to archived data from within the application • Allow data to be archived to another database and offline storage, and integrate with hierarchical storage management • Example – Archive to IBM DR550, long term retention • Archive Management • If there is an interruption in the archive, purge and retrieve processes, be able to recover from the point of the interruption • Report on what data is archived • Provide administrative tools to manage the archives

  31. Identify the data to archive Define the data to delete Select Archive File storage Create the archive Research, report, retrieve Creating and Managing Archived Data

  32. Choosing the Best Access Method • Native application access • Convenient for functional users • Can slow down online transaction processing • “Self-Help” access (Canned Reports, Query Tools) • Convenient for functional users • No IT services required • Application independent access • Preserves a complete view of historical business records regardless of originating application or version • Facilitates decommissioning, upgrade and migration paths

  33. Summary of Advice • Recognize that IT owns Infrastructure, but the Business owns the data • Improve functional processes by tiering services by functional need • Higher service levels on current transactions • Lower-cost, lower service levels on historical transactions • Limit liability by ensuring real-time compliance controls are sustained and documented in your historical retention processes and tools • Respond quickly and accurately to audit requests • Reduce costs of discovery

  34. Questions

More Related