Tag Archives: application retirement
As part of their cost cutting program, organizations are consolidating data centers and the applications within them. Federal and state agencies in the public sector are among those where IT consolidation and moving applications to the cloud are top priorities as part of an overall goal to increase efficiencies and eliminate costs. In other industries, many consolidations are also under way due to mergers and acquisitions and other cost cutting initiatives. As you plan or undergo a consolidation project, you also need to plan for the retirement of legacy, redundant applications that are left behind.
Eliminating Up To 95% Of Legacy Costs As Part Of Your Journey To The Cloud, With Application Decommissioning And Archiving
We’re all familiar with those legacy applications that no longer add value, but still absorb significant costs. These redundant applications may be left due to mergers and acquisitions, IT consolidation, business modernization, application migration, or moving to a cloud-based or software as a service environment. If you are an EMC customer, many of you may be undertaking projects to consolidate your IT stack to increase efficiency, and moving gradually towards a private or hybrid cloud environment. As you are virtualizing, re-platforming, and migrating your hardware and software, what do you do with the old applications that are left behind? (more…)
Applications are retired (sunset or decommissioned) when they become dormant or read-only. This occurs as a result of mergers and acquisitions or through modernization efforts and is a natural part of Application Information Lifecycle Management. While the applications may be no longer needed, the data they contain cannot be discarded. As a result, many organizations have hundreds, even thousands, of defunct applications that are consuming budget dollars, taking up data center space, complicating IT management, and generally just getting in the way. The challenge is getting rid of applications without getting rid of the data which is tightly coupled to them. (more…)
ROI Tool To Help Make The Business Case For Database Archiving, Application Retirement, Test Data Management, And Data Masking
Though the benefits of containing the size of your databases by archiving seems obvious in terms of saving costs and improving performance, quantifying those benefits in terms of dollar savings requires more thought. The same is true when it comes to the costs that can be eliminated by retiring redundant legacy applications. Some of the savings may come from hard dollar costs such as:
– Backup devices
– Maintenance contracts
– Software licenses (more…)
Following a Merger and Acquisition (M&A), there is usually a focus on consolidating the two companies’ IT systems, leaving behind many redundant legacy applications. Until those legacy applications are shut down, you haven’t realized the cost savings of the consolidation. However, those old applications may contain data that’s no longer used for daily operations, but need to be retained for regulatory compliance. Keeping those applications up and running, just to retain the data within them introduces operational, business and legal risks. It is likely that the IT staff who have the expertise about those applications are no longer with the company, and without them it may be difficult to impossible to access the data in a meaningful way, in the time required, for an audit or eDiscovery request.
As a final part of our series, Architecting A Database Archiving Solution, we will review a process I use to assess a client’s existing Total Cost of Ownership of their database application and how to justify a database archiving solution. The key metrics I begin with are listed below and explained:
During this series of “Architecting a Database Archiving Solution”, we discussed the Anatomy of A Database Archiving Solution and End User Access Requirements. In this post we will review the archive repository options at a very high level. Each option has its pros and cons and needs to be evaluated in more detail to determine which will be the best fit for your situation.
Series: Architecting A Database Archiving Solution Part 3: End User Access & Performance Expectations
In my previous blog as part of the series, architecting a database archiving solution, we discussed the major architecture components. In this session, we will focus on how end user access requirements and expected performance service levels drive the core of an architecture discussion.
End user access requirements can be determined by answering the following questions. When data is archived from a source database:
- How long does the archived data need to be retained? The longer the retention period, the more the solution architecture needs to account for potentially significant data volumes and technology upgrades or obsolescence. This will determine cost factors of keeping data online in a database or an archive file, versus nearline or offline on other media such as tape. (more…)
Before we can go into more details on how to architect a database archiving solution, let’s review at a high level the major components of a database archiving solution. In general, a database archiving solution is comprised of four key pieces – application metadata, a policy engine, an archive repository and an archive access layer.
Application Metadata – This component contains information that is used to define what tables will participate in a database archiving activity. It stores the relationships between those tables, including database or application level constraints and any criteria that needs to be considered when selecting data that will be archived. The metadata for packaged applications, such as Oracle E-Business Suite, PeopleSoft, or SAP can usually be purchased in pre-populated repositories, such as Informatica’s Application Accelerators for Data Archive to speed implementation times.
Policy Engine – This component is where business users define their retention policies in terms of time durations and possibly other related rules (i.e. keep all financial data for current quarter plus seven years and the general and sub ledgers must have a status of “Closed”). The policy engine is also responsible for executing the policy within the database, and moving data to a configured archive repository. This involves translating the policy and metadata into structured query language that the database understands (SELECT * from TABLE A where COLUMN 1 > 2 years and COLUMN 2 = “Closed”). Depending on the policy, users may want to move the data to an archive (meaning it is removed from the source application) or just create a copy in the archive. The policy engine takes care of all those steps.
Archive Repository – This stores the database archive records. The choices for the repository vary and will be determined based on a number of factors typically driven from end user archive access requirements (we will discuss this in the next blog). Some of these choices include another archive database, highly compressed query-able archive files, XML files to name a few.
Archive Access Layer – This is the mechanism that makes the database archive accessible either to a native application, a standard business reporting tool, or a data discovery portal. Again, these options vary and will be determined based on the end user access requirements and the technology standards in the organizations data center.
In the next series, we will discuss how End User Access and Performance Requirements impact the selection of these components in further detail.
Julie Lockner, Founder, www.CentricInfo.com
Classifying databases data for an ILM project requires a process for categorizing and classifying that involves the business owners, Records Management, Security, IT, DBA’s and developers. In an ideal scenario, a company has documented every single business process down to data flows and database tables. IT can map database tables to the underlying infrastructure. Since most of us work in realistic scenarios, here is one approach you can take to classify information without knowing all the interrelations.�