CMS Data Archive Migration via Export and Restore
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Central management server (CMS) migration does not effectively transfer management functionality data, requiring manual regeneration and performance hits during hardware upgrades, as existing systems fail to seamlessly migrate management-related data across CMS instances.
Innovation Solution
A data-replacing archive operation system that facilitates migration by performing backup and restore operations, using tools to replace and transform management data, including identifiers, performance, and utilization data, reducing manual intervention and performance impacts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If CMS hardware is upgraded without data transfer, then hardware capability is improved, but management data is lost and must be regenerated
Solution Approach 1:
The system performs preliminary actions by exporting and archiving management data from the source CMS before hardware upgrade, then restores this data to the new CMS. This ensures management data is preserved and transferred proactively rather than lost during the upgrade process.
Solution Approach 2:
The system creates a copy of the management data from the source CMS through export operations, stores this copy in an archive file, and then restores it to the target CMS. This copying mechanism preserves the original data while enabling transfer to new hardware.
2Power
If management data is regenerated after CMS upgrade, then hardware is optimized, but time is lost and performance hits occur
Solution Approach 1:
The system performs the data collection and preparation actions in advance by exporting management data from the source CMS before the upgrade. This preliminary action eliminates the need for time-consuming data regeneration after the upgrade, as the data is already prepared and archived.
Solution Approach 2:
The system maintains continuity of useful action by seamlessly transferring management data from source to target CMS through archive operations. This continuous process eliminates interruptions and performance hits that would occur if data had to be regenerated after upgrade.
3Manufacturing precision
If manual data transfer is performed, then data accuracy is maintained, but operational complexity increases
Solution Approach 1:
The system performs self-service by automatically exporting, archiving, and restoring management data without requiring manual intervention. The archive tools autonomously complete the data transfer process, eliminating manual operations while maintaining data accuracy through structured export and restore procedures.
Solution Approach 2:
The system introduces an intermediary archive file as a mediator between source and target CMS. This intermediary structure standardizes the data format and enables automatic, accurate transfer without manual intervention, as the archive file serves as a reliable intermediate storage that preserves data integrity.
4Manufacturing precision
If performance data is reclected after upgrade, then system optimization is achieved, but productivity decreases
Solution Approach 1:
The system performs preliminary data collection by exporting performance and utilization data from the source CMS before the upgrade. This preliminary action ensures that optimization data is already collected and archived, eliminating the need for slow post-upgrade data recollection and maintaining high productivity.
Data Source
AI summary
An archive operation selected from a set comprising: an export operation, an import operation, and a combination export and import operation is initiated. The archive operation involves a transfer of data. During the archiving operation, some of the data is replaced.