Schedule and monitor data migration
-
PDF of this doc site
- Install and maintain appliance hardware
- Install and upgrade software
- Perform system administration
-
Monitor and maintain StorageGRID
-
Recover and maintain
- Grid node recovery procedures
-
Recover and maintain
Collection of separate PDF docs
Creating your file...
Data migration must be scheduled and monitored as necessary to ensure data is placed according to the ILM policy within the required timeframe.
Schedule data migration
Avoid migrating data during core operational hours. Limit data migration to evenings, weekends, and other times when system usage is low.
If possible, do not schedule data migration during periods of high activity. However, if it is not practical to completely avoid the high activity period, it is safe to proceed as long as you closely monitor the relevant attributes and take action if they exceed acceptable values.
Monitor data migration
This table lists the attributes you must monitor during data migration, and the issues that they represent.
If you use traffic classification policies with rate limits to throttle ingest, you can monitor the observed rate in conjunction with the statistics described in the following table and reduce the limits if necessary.
Monitor | Description |
---|---|
Number of objects waiting for ILM evaluation |
|
Targeted archival system's storage capacity |
If the ILM policy saves a copy of the migrated data to a targeted archival storage system (tape or the cloud), monitor the capacity of the targeted archival storage system to ensure that there is sufficient capacity for the migrated data. |
Archive Node > ARC > Store |
If an alarm for the Store Failures (ARVF) attribute is triggered, the targeted archival storage system might have reached capacity. Check the targeted archival storage system and resolve any issues that triggered an alarm. |