Storage Node Power Conservation Logic for Emergency Shutdown
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data storage systems face challenges in emergency shutdown procedures due to the large, costly, and regulated lithium ion batteries required for SAN and NAS nodes, which are necessary to prevent data loss but impose logistical and financial burdens.
Innovation Solution
Implementing a method and apparatus with parallel processes for emergency shutdown and power conservation, where data and metadata are destaged from volatile memory to non-volatile storage using an emergency power source, and power conservation actions are serially applied until enough reserve power is available, including reducing processor power, depowering unused components, and adjusting clock speeds, with logic to estimate and order power savings for efficient shutdown.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If large lithium ion batteries are used for emergency shutdown, then data loss prevention is improved, but cost and shipping regulation compliance worsen
Solution Approach 1:
The system performs preliminary actions by identifying and executing power conservation measures immediately upon detecting power loss. The controller serially implements conservation actions (depowering components, reducing processor speed, parking processor cores) before the battery is fully engaged, reducing the peak power demand and allowing smaller batteries to suffice for the remaining data protection task.
Solution Approach 2:
The system dynamically changes operational parameters by adjusting processor speed, memory speed, and component power states in response to power loss. These parameter changes reduce power consumption during the critical shutdown period, enabling the use of smaller batteries that comply with shipping regulations while still protecting data.
2Ease of manufacture
If battery capacity is reduced to comply with regulations, then shipping compliance is improved, but emergency shutdown capability worsens
Solution Approach 1:
The controller executes preliminary power conservation actions immediately upon detecting power loss, reducing the power consumption burden before the battery takes over. By serially implementing conservation measures (depowering unused components, reducing processor and memory speeds, parking processor cores), the system prepares the hardware to require less battery capacity for completing the shutdown sequence, thus enabling regulatory compliance without sacrificing shutdown capability.
Solution Approach 2:
The system dynamically adjusts its power consumption profile during the emergency shutdown sequence. The controller continuously monitors power availability and adaptively implements or adjusts power conservation actions based on real-time conditions, allowing the system to optimize battery usage and achieve reliable shutdown with smaller, compliant battery capacities.
3Use of energy by moving object
If power conservation actions are implemented serially, then power consumption is reduced, but shutdown time increases
Solution Approach 1:
The controller performs preliminary power conservation actions immediately upon detecting power loss, before the battery is fully engaged. By serially implementing conservation measures in advance (depowering unused components, reducing processor and memory speeds, parking processor cores), the system reduces the overall power consumption requirement, allowing smaller batteries to suffice for the remaining shutdown task without significantly extending total shutdown time.
Data Source
AI summary
Power conservation logic for a storage node operates in parallel with an emergency shutdown process in which an emergency power source is engaged and data and metadata are destaged from volatile memory to non-volatile managed drives. The power conservation logic serially implements power conservation actions until enough reserve power is available to complete the emergency shutdown process. The power conservation logic may learn how much power savings are realized from each conservation action and adjust the order in which the conservation actions are serially implemented, e.g. in order from greatest to least power consumption reduction.