INACTIVE DATA IS SLOWING DOWN YOUR SYSTEM
Let GlueData help you speed things up and save you money
WHY YOU NEED TO ARCHIVE
The rise in data’s availability, volume and importance is daunting for most organisations. Given the rapid growth in access to information, unchecked data can quickly overwhelm your system and compromise its ability to function optimally. It can also result in an unnecessary cost and compliance burden.
A key component to effective management of your data and SAP system is identifying data that is no longer active and moving it into long-term storage systems. This is known as data archiving and it’s a crucial element of your business’s data strategy.
THE VALUE IN ARCHIVING
Improve analytics and business intelligence insights
Significantly improve SAP system performance
Reduce backup time and downtime during upgrades
Reduce hardware and cloud storage costs
Align with data-related statutory regulations
Access archived information when you require it
GLUEDATA’S ARCHIVING METHODOLOGY
STEP 1: Client Requirement
We begin with a discovery process to assess the reason behind the archiving request. Typically, this falls into one, or a combination, of three concerns: the client’s system is too slow, the database is getting too big or the cloud strategy requires reduced space.
STEP 2: Technical Assessment
We define the archiving scope through a technical assessment that identifies which information can and cannot be archived. This enables GlueData to confirm the project scope and provide the client with a proposal for consideration.
STEP 3: Preparation
The project is prepared and planned, with defined scope, objectives and schedule. The detailed concept (technical concept) is created, detailing the top archive objects,
their sequences, dependencies, and proposed residence times
for archiving.
STEP 4: Testing + Training
User tests are performed and releases obtained before the go-live. The business and process requirements are configured in the SAP system. The project team members also receive the required training during this phase. Planning and setup of an archive calendar for go-live scheduling is compiled.
STEP 5: Go-Live Execution + Support
Archiving goes live in the SAP productions systems in this phase for historical data. GlueData provides ongoing support to the project team to ensure limited downtime and seamless archiving of data.
STEP 6: Continuous Archiving
All the preparation work would have been concluded in the previous phases and these configurations can be transported to Production, whereafter the actual production data archiving can commence. Archiving
is carried out on a regular basis going forward.
GLUEDATA’S ARCHIVING METHODOLOGY
STEP 1: Client Requirement
We begin with a discovery process to assess the reason behind the archiving request. Typically, this falls into one, or a combination, of three concerns: the client’s system is too slow, the database is getting too big or the cloud strategy requires reduced space.
STEP 2: Technical Assessment
We define the archiving scope through a technical assessment that identifies which information can and cannot be archived. This enables GlueData to confirm the project scope and provide the client with a proposal for consideration.
STEP 3: Preparation
The project is prepared and planned, with defined scope, objectives and schedule. The detailed concept (technical concept) is created, detailing the top archive objects,
their sequences, dependencies, and proposed residence times
for archiving.
STEP 4: Testing + Training
User tests are performed and releases obtained before the go-live. The business and process requirements are configured in the SAP system. The project team members also receive the required training during this phase. Planning and setup of an archive calendar for go-live scheduling is compiled.
STEP 5: Go-Live Execution + Support
Archiving goes live in the SAP productions systems in this phase for historical data. GlueData provides ongoing support to the project team to ensure limited downtime and seamless archiving of data.
STEP 6: Continuous Archiving
All the preparation work would have been concluded in the previous phases and these configurations can be transported to Production, whereafter the actual production data archiving can commence. Archiving
is carried out on a regular basis going forward.
Do these
questions
sound familiar?
- Should we archive prior to migrating to SAP S/4 HANA?
- What should we archive and what should we delete?
- Where should archived data be stored?
- Are there any license fees required?