Backup Operation Status Tracking via Transaction Logs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information management systems provide only an 'all-or-nothing' job status reporting, failing to offer users timely updates on backup operations until the entire backup job is completed, leading to user dissatisfaction and inefficiency.
Innovation Solution
Implementing a storage manager that collects granular information about data storage operations at client devices, allowing for real-time reporting of backup status through transaction log files and an indexing server, independent of the overall job completion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the system waits for the entire backup job to complete before reporting status, then the job status reporting is simple and reliable, but the user receives no timely updates on intermediate backup operations
Solution Approach 1:
The patent segments the backup job status reporting into two independent components: (1) overall job status tracking maintained by the storage manager, and (2) granular operation-level status reporting collected directly from client devices via transaction logs. This segmentation allows the system to provide detailed intermediate status information without waiting for complete job completion, while maintaining reliable overall job status tracking.
Solution Approach 2:
The patent introduces an indexing server as an intermediary component that collects transaction log files directly from client devices and makes them accessible to the storage manager. This intermediary enables the storage manager to retrieve granular backup operation status information without waiting for the overall job to complete, effectively decoupling the status reporting timeline from the job completion timeline.
2Loss of information
If the storage manager queries each computing resource for backup status, then comprehensive status information can be obtained, but the system complexity and communication overhead increase
Solution Approach 1:
The patent extracts the status reporting function from the distributed computing resources and centralizes it in transaction log files generated by client devices. Instead of requiring the storage manager to query multiple computing resources (media agents, backup proxies, secondary storage devices), the system only needs to access the indexing server and read the pre-generated transaction logs, dramatically simplifying the architecture.
Solution Approach 2:
Client devices autonomously generate and maintain their own transaction log files that record backup operation status, eliminating the need for external querying mechanisms. Each client device serves its own status reporting needs by maintaining local transaction logs that can be independently accessed by the indexing server and storage manager.
3Productivity
If backup jobs span multiple days with autonomous operations, then productivity is improved, but the user receives prolonged 'job pending' status with no granular updates
Solution Approach 1:
The system performs preliminary actions by having client devices generate and store transaction log files during backup operations as they occur. These logs are prepared in advance and made available in the indexing server before the overall backup job completes, enabling the storage manager to retrieve and display granular status information immediately when queried, even during multi-day autonomous backup operations.
Data Source
AI summary
Systems and methods disclosed herein provide users with granular current information about backup operations that completed at their user devices, regardless of whether a backup job as a whole, which comprises a plurality of backup operations across multiple computing devices, is presently complete or incomplete. Accordingly, an illustrative information management system comprises feature enhancements that collect granular information about data storage operations occurring at a client device, so that up-to-date status thereof may be provided to querying users on demand. Thus, the illustrative system need not wait for the completion of the backup job to answer status queries about backup operations occurring before the full completion of the backup job. Moreover, data backed up in one of these backup operations may be restored on demand independently of whether the backup job as a whole is presently complete or incomplete.