Transcript Exploit the Power of Enterprise Data Management

Princeton Softech
Anatomy of an Archive Project
Let’s Talk About Data!!
April 18, 2007
Alan Schneider
© 2005 Princeton Softech, Inc.
Archiving Impact
 Archiving solves a
variety of problems
 Today’s focus:
Information Lifecycle
Management (“ILM”)
 Components
 Issues to consider
© 2005 Princeton Softech, Inc.
2
5 Reasons Why Company’s Don’t Archive
 Organizational Alignment
 Priority
 Funding
 Timing
 Knowledge of what archiving is and how to do it
© 2005 Princeton Softech, Inc.
3
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
160
140
120
100
80
60
40
20
0
3
M
on
th
1
M
on
th
s
6
M
on
th
s
1
Y
ea
r
18
M
on
th
s
24
M
on
th
s
3
ye
ar
s
4
Y
ea
rs
5
Y
ea
rs
6
Y
ea
rs
Value
Time Value of Data
Tim e
Invoices
© 2005 Princeton Softech, Inc.
Purchase Orders
Inventory
4
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
© 2005 Princeton Softech, Inc.
5
Components of an Archive Project
© 2005 Princeton Softech, Inc.
6
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)?
© 2005 Princeton Softech, Inc.
7
One Example of an ILM Infrastructure
Tier I
Custom
DATA
DATA
Database Server
With Optim
DATA
DATA
Tier II
Tier III
© 2005 Princeton Softech, Inc.
CAS
Database Server
With Optim
Tape
Disposal
8
One Example of an ILM Infrastructure
Tier I
Custom
DATA
DATA
DATA
DATA
Archive Server
DATA
DATA
Tier II
Tier III
© 2005 Princeton Softech, Inc.
CAS
Tape
Disposal
9
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
© 2005 Princeton Softech, Inc.
10
One Example of Classifications
Application
Tier
Deployments
Deletion
> 2 Year
> 5 year
Access SLA Access SLA
Mission Critical
3 Years
7 Years
No
3 Hours
1 Day
Business Critical
2 Years
4 Years
Yes, after 7
8 Hours
3 Days
Important
6 months
3 years
Yes, after 3
3 days
30 days
Decommission
Tier III Only
Yes, after 10 14 days
© 2005 Princeton Softech, Inc.
30 days
11
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
© 2005 Princeton Softech, Inc.
12
Privacy News – The US Government is Involved
US Senate Bill Holds IT Managers Responsible for Privacy Breaches
By Scott M. Fulton, III, BetaNews
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.
© 2005 Princeton Softech, Inc.
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.)
 Establish processes
- Backup
- Archive
- Reorg
© 2005 Princeton Softech, Inc.
14
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
© 2005 Princeton Softech, Inc.
15
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
© 2005 Princeton Softech, Inc.
16
Tune
 Deletes are expensive
 Evaluate indexing and partitioning
strategies
 Tune SQL to match constraints
© 2005 Princeton Softech, Inc.
17
Dispose
 Determine data deletion policies
- Sign off by stakeholders
- Which data to delete, and when
- Automated or manual delete
© 2005 Princeton Softech, Inc.
18
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
© 2005 Princeton Softech, Inc.
19
© 2005 Princeton Softech, Inc.