1. © 2005 Princeton Softech, Inc. Princeton Softech Anatomy of an Archive Project Let’s Talk About Data!! April 18, 2007 Alan Schneider

2. © 2005 Princeton Softech, Inc. 2 Archiving Impact  Archiving solves a variety of problems  Today’s focus: Information Lifecycle Management (“ILM”)  Components  Issues to consider

3. © 2005 Princeton Softech, Inc. 3 5 Reasons Why Company’s Don’t Archive  Organizational Alignment  Priority  Funding  Timing  Knowledge of what archiving is and how to do it

4. © 2005 Princeton Softech, Inc. 4 What is ILM?  Information has a ‘lifecycle’  Over time, the value of data decreases  Data should be stored and managed according to its evolving value

5. © 2005 Princeton Softech, Inc. 5 ILM Quiz Q Product or concept? Q Storage vendor solution? Q Function of frequency of data access? Q Fast and easy to implement? Q Crucial to substantial infrastructure savings? A ILM is about managing data from cradle to grave A Archiving is the key enabler of ILM

6. © 2005 Princeton Softech, Inc. 6 Components of an Archive Project

7. © 2005 Princeton Softech, Inc. 7 Assess  Determine application types or modules -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?  Build archive server, or utilize existing application server(s)?

8. © 2005 Princeton Softech, Inc. 8 One Example of an ILM Infrastructure DATA Tier I Custom Tier IITier IIICAS Tape DATA Disposal Database Server With Optim Database Server With Optim

9. © 2005 Princeton Softech, Inc. 9 One Example of an ILM Infrastructure DATA Tier I Custom Tier IITier IIICAS Tape DATA Disposal Archive Server

10. © 2005 Princeton Softech, Inc. 10 Classify  Identify “Business Objects” to archive -Database and application constraints -Retention requirements  Identify time parameters -Time value of business object -SLA for access  Specify deletion requirements  Identify post-archive use cases -Customer service inquiries -Audit / e-discovery -Retrieve from archive -Reload to temporary DBMS -SLA for access

11. © 2005 Princeton Softech, Inc. 11 One Example of Classifications ApplicationTier Deployments Deletion> 2 Year Access SLA > 5 year Access SLA Mission Critical3 Years 7 Years No3 Hours1 Day Business Critical2 Years 4 Years Yes, after 78 Hours3 Days Important6 months 3 years Yes, after 33 days30 days DecommissionTier III OnlyYes, after 1014 days30 days

12. © 2005 Princeton Softech, Inc. 12 Subset and Privatize Data  Eliminate cloning and related problems -Unproductive wait time -Expensive storage requirements  Speed creation / refresh of test databases -Improve test coverage, quality -Accelerate application deployment  Eliminate disclosure risks -Mask, transform, de-identify -Protect data privacy

13. © 2005 Princeton Softech, Inc. 13 Privacy News – The US Government is Involved US Senate Bill Holds IT Managers Responsible for Privacy Breaches By Scott M. Fulton, III, BetaNewsScott M. Fulton, III February 8, 2007, 8:09 PM A bill introduced in the US Senate on Tuesday by Judiciary Committee Chairman Patrick Leahy (D - Vermont), along with one independent and one Republican backer, aims to strengthen security requirements for all private databases accessible online that may hold personal information. Reintroducing language that had been stalled since 2005, if passed, the bill could hold IT managers accountable and responsible for security breaches where personal information is pilfered.

14. © 2005 Princeton Softech, Inc. 14 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.)  Establish processes -Backup -Archive -Reorg

15. © 2005 Princeton Softech, Inc. 15 Store  Determine format of archives -DBMS vs. File  Define hardware targets -Number of tiers -Types of devices  Establish security parameters -Integration with existing framework  Database, application, network -Additional Archive security requirements  Functional security  Data, Object and File security

16. © 2005 Princeton Softech, Inc. 16 Access  Analyze use cases vs. cost of access -Goal: match SLA to value to cost -Native, application based access -Application independent access  Communicate access terms & conditions -SLAs -Resource provisioning -Training on access

17. © 2005 Princeton Softech, Inc. 17 Tune  Deletes are expensive  Evaluate indexing and partitioning strategies  Tune SQL to match constraints

18. © 2005 Princeton Softech, Inc. 18 Dispose  Determine data deletion policies -Sign off by stakeholders -Which data to delete, and when -Automated or manual delete

19. © 2005 Princeton Softech, Inc. 19 Princeton Softech Inc.  Provider of a single solution for managing enterprise application data throughout every stage of the information lifecycle  In business since 1989; 2400 customers; 50% of Fortune 500; profitable with no debt  Supports multiple applications, databases, operating systems and hardware platforms  Optim capabilities -Migrate, Archive and Vault Data -Test Data Management and Data Privacy -Application Retirement

20. © 2005 Princeton Softech, Inc.