US20260023658
2026-01-22
Physics
G06F11/1464
The disclosed framework addresses the challenge of enforcing an aggressive Recovery Point Objective (RPO) for production databases without generating secondary copies during each backup operation. This approach overcomes bottlenecks associated with traditional storage management systems by minimizing the involvement of the storage manager computer in operations that could impact RPO. Key components are enhanced to autonomously capture and securely store database transaction logs away from the database management system (DBMS). Secondary copies are created less frequently, reducing the load on the system while temporary backup files facilitate restore operations.
A critical enhancement involves a database data agent that captures transaction logs and packages them into temporary backup files in a proprietary format, which includes compression and encryption for security. These files are transmitted to a media agent via a secure, proprietary data pipeline. This setup allows the media agent to store the files in a designated "dump repository," which can be located in local or cloud storage. The data pipeline ensures secure transmission and storage, enabling flexibility in system configurations while maintaining data integrity and security.
The system performs "sweep jobs" at intervals longer than the RPO to convert temporary backup files into secondary copies, which are then indexed and tracked. This process reduces the processing demand on the storage manager, as it only engages with the temporary files during these less frequent jobs. The media agent purges converted files from the dump repository, while continuously accumulating new temporary files. This approach allows for efficient data management and minimizes the risk of data loss, aligning with the aggressive RPO requirements.
For restoration, the media agent checks the dump repository for suitable temporary backup files, allowing for immediate restore operations without waiting for conversion into secondary copies. This capability ensures that data can be restored promptly, maintaining system reliability and meeting business continuity requirements. The system's architecture supports both cloud and non-cloud environments, providing flexibility and adaptability to various deployment scenarios.
The system's components, including the DBMS, database data agent, media agent, and storage manager, can be deployed across traditional data centers, cloud environments, or a combination of both. This flexibility allows organizations to tailor their data management infrastructure to their specific needs, ensuring that they can effectively manage data growth and protect their critical business information. The architecture supports diverse configurations, making it a versatile solution for modern data management challenges.