Database Archive Architecture With Threshold-Based Repository Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data archiving systems face inefficiencies in managing large volumes of data records, leading to increased processing power requirements, downtime, and slow data retrieval, especially during backup processes.

Innovation Solution

Implementing an A/B repository architecture with threshold-based data migration, utilizing fast retrieval repositories for recent data and an archive repository for stored data, along with an index file for efficient retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data records are archived in a single repository, then storage capacity is sufficient, but data retrieval speed decreases and system downtime increases

Engineering Contradiction:
Improvedata retrieval speedVSAvoidrepository architecture complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system divides the repository into multiple segments: a first repository for recently modified data records and a second repository for archived data records. This segmentation allows the system to maintain fast retrieval for recent data while efficiently archiving older data, resolving the contradiction between retrieval speed and storage capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a temporal dimension to the repository architecture by implementing an A/B switching mechanism that alternates between active and archived repositories based on time-based thresholds. This dimensional approach enables simultaneous optimization of both retrieval speed (through active repository access) and storage efficiency (through archived repository usage).

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Productivity

If all data records are kept in active repositories, then data accessibility is maximized, but processing power requirements increase

Engineering Contradiction:
Improvearchiving efficiencyVSAvoidprocessing power consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The system extracts older, less frequently accessed data records from the active repository and moves them to the archived repository based on modification time thresholds. This extraction reduces the volume of data that requires high-speed processing and storage, thereby lowering processing power requirements while maintaining productivity through efficient archiving operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements dynamic parameter changes by adjusting the threshold for data archiving based on system load, repository capacity, and access patterns. This allows the system to optimize the balance between productivity (archiving efficiency) and energy consumption (processing power) by adapting archiving parameters to current operational conditions.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If data archiving is performed frequently, then storage management is improved, but system downtime increases

Engineering Contradiction:
Improvedata management reliabilityVSAvoidsystem downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system employs periodic archiving actions triggered by thresholds such as repository capacity limits or time-based criteria rather than continuous archiving. This periodic approach allows the system to maintain reliability through regular data management while minimizing downtime by performing archiving operations only when necessary, rather than continuously interrupting system operations.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent implements preliminary archiving actions by proactively moving data to archived repositories before the active repository reaches full capacity or before data becomes truly obsolete. This preliminary action prevents critical downtime by ensuring smooth transitions between repositories and maintaining system availability during archiving operations.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If multiple repositories are used for data archiving, then data retrieval efficiency improves, but system complexity increases

Engineering Contradiction:
Improvedata retrieval easeVSAvoidrepository management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces an intermediary archiving manager that automatically handles the complexity of managing multiple repositories. This intermediary component mediates between the active and archived repositories, managing data transitions, threshold monitoring, and repository switching based on predefined criteria, thereby improving data retrieval ease while masking the underlying complexity through automated management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements self-service mechanisms where the repository system automatically monitors its own capacity, performs archiving operations based on predetermined thresholds, and manages data transitions without requiring complex external management. This self-service approach simplifies operation by allowing the system to autonomously handle repository management tasks while maintaining ease of data retrieval for users.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12443578B1Systems and methods for a database archive
Publication Date: 2025.10.14 VEEVA SYSTEMS INC
  • US12443578B1 patent drawing
  • US12443578B1 patent drawing
  • US12443578B1 patent drawing

AI summary

A method for archiving data records in an archive repository includes retrieving, in response to: the first multiple of change data records of a first repository including at least the first threshold number of change data records and a second repository including the second multiple of change data records including at least the second threshold number of change data records, the second multiple of change data records of the second repository. The first repository and the second repository are configured to store data records. The method further includes generating multiple change files and storing the multiple change files in the archive repository. The archive repository is configured to store data files. The method further includes storing a second change data record in the second repository.