Unified Replication Management for Automated Data Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IT organizations face challenges in maintaining data application and availability while satisfying service level agreements and compliance requirements, due to unprecedented data growth straining IT resources and increasing complexity in storage management, which traditional replication methods are inadequate to address.
Innovation Solution
The implementation of Unified Replication Management (URM) that automates application-level policy management and configuration of data protection and disaster recovery through a policy engine with a common user interface, enabling automation of protection tasks, risk management, and compliance monitoring across various replication technologies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If traditional replication methods are used for data protection, then data copying functionality is provided, but IT resource utilization is inefficient and system complexity increases due to manual management
Solution Approach 1:
The system enables self-service automation where the data protection system automatically discovers application components, determines dependencies, and executes protection workflows without manual intervention. The affinity module autonomously groups application components based on dependency analysis, and the workflow component automatically orchestrates protection operations across multiple systems.
Solution Approach 2:
The affinity module serves multiple functions: it discovers application components, analyzes dependencies between them, groups components into affinity groups, and provides this grouping information to the workflow component. This multi-functional approach consolidates what would otherwise require separate tools and processes, reducing overall system complexity while increasing automation.
2Productivity
If manual processes are used for application protection configuration, then flexibility in customization is maintained, but productivity and time efficiency decrease
Solution Approach 1:
The affinity module performs preliminary actions by discovering application components and determining their dependencies before the actual data protection workflow executes. This advance analysis and grouping of components prepares the system for rapid automated execution, eliminating the need for manual configuration during the protection process.
Solution Approach 2:
The system implements feedback mechanisms where the affinity module continuously monitors application components and their dependencies, and the workflow component adjusts protection operations based on this information. This feedback loop enables the system to adapt to changes in the protected environment automatically, maintaining high productivity without manual reconfiguration.
3Reliability
If comprehensive data protection coverage is implemented across all application components, then data reliability is improved, but device complexity and management overhead increase
Solution Approach 1:
The affinity module segments application components into distinct affinity groups based on their dependency relationships. This segmentation allows the workflow component to manage protection operations at the group level rather than individually for each component, reducing management complexity while maintaining comprehensive protection coverage across all components.
Solution Approach 2:
The system introduces a new dimension of organization by grouping application components based on affinity relationships rather than traditional hierarchical or physical structures. This dimensional change in how components are organized and managed simplifies the complexity of handling large numbers of protected components while ensuring comprehensive coverage.
Data Source
AI summary
In one aspect, a method includes validating application components, a set of operations and a flow of the operations. The application components, the operations and the flow of the operations are determined from a service plan. The flow of the operations enables protection and reuse of application components. The method also includes executing an operation of the set of operations, collecting status of the executing of the operation, determining dependent operations that are dependent on the operation, performing an affinity process based on a set of rules to determine which application components to group under a single dependent operation and which application components to separate into different dependent operations, and repeating the validating, executing, collecting, and determining for each dependent operation.