Configuring FAST VP FAST VP is either enabled or disabled
{"Image DocumentName": "Configuring FAST VP FAST VP is either enabled or disabled", "Image ImageDescription": "Data Movement should be set to automatic. Relocation Rate controls aggressiveness of FAST. New Feature Allocate- by-Policy simplifies capacity management of thin Provisioned environments. Depicted here are the main FAST VP configuration settings. These are: State: Either ON or Off. FAST is either on or off. Movement Mode: Either automatic or Off. There is no user interaction once FAST VP is turned on, FAST VP moves at a granular level approximately 8 MB chunks, there is no way a user can identify each chunk being moved. Relocation Rate: This controls how aggressive FAST VP will be in its data movements. The lower the value, the more aggressive FAST VP will be. The minimum value is 1, the maximum value is 10, and the default value is 5. For the testing in our environment we used a value of 2. This setting affects the amount of data that will be moved at any given time, and the priority given to moving the data between pools \u2013 it does not affect the speed of the data movement. Reserved Capacity Limit: A percentage of the capacity of each virtual pool that is reserved for non-FAST activities. If the free space in a given virtual pool (as a percentage of pool-enabled capacity) falls below this value, the FAST controller does not move any more data into that pool. To further simplify the management and capacity planning of FAST VP environments, Enginuity 5876 and Solutions Enabler 7.4 provides FAST VP allocation by policy. This system-wide setting ensures that new allocations for thin devices associated with FAST VP policies no longer only come from the pool to which a thin device is bound but from any one of the tiers associated with the FAST policy. In the event that one tier can\u2019t service a new allocation because it is full, the tracks will be allocated from one of the remaining tiers. Allocate-by-Policy greatly simplifies the capacity management as tier demand reports can easily be generated via command line or visually through Unisphere to ascertain how storage is being utilized and plan for future needs. As a recommended practice, it is recommended that the VP allocation by FAST policy be enabled. Time windows. Create time windows to specify when data can be collected for performance analysis and when data movements can be executed. Recommend to have windows always open so FAST VP can use most recent analysis to optimize data placement.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}