Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/It_is_possible_to_get_a_list_of_deleted_objects_after_wrongly_modifying_ILM_rule
      Applies to NetApp StorageGRID 11.3.x NetApp StorageGRID 11.4.x Answer Yes, under certain conditions. Please contact NetApp Technical Support and reference this article for further assistance on the mo...Applies to NetApp StorageGRID 11.3.x NetApp StorageGRID 11.4.x Answer Yes, under certain conditions. Please contact NetApp Technical Support and reference this article for further assistance on the modification. Additional Information additionalInformation_text
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/StorageGRID_erasure-coded_object_data_usage_weeks_after_changing_ILM_policy_to_dual_copy
      Applies to NetApp StorageGRID Software version: 11.4 StorageGRID Information Lifecycle Management (ILM) Issue User notice erasure-coded (EC) object data stored on the storage node object store (ranged...Applies to NetApp StorageGRID Software version: 11.4 StorageGRID Information Lifecycle Management (ILM) Issue User notice erasure-coded (EC) object data stored on the storage node object store (rangedb volumes) weeks after modifying ILM policy from EC to dual copy: Note: Above screenshot is taken from lab setup and does not contain a lot of object data.
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/StorageGRID_S3_client_large_data_sets_performance_issues_during_or_after_ILM_erasure_coding_policy_change
      Applies to NetApp StorageGRID Changing an information lifecycle management policy (ILM) to and from erasure coding for migration or GRID reconfiguration causes S3 clients to experience performance deg...Applies to NetApp StorageGRID Changing an information lifecycle management policy (ILM) to and from erasure coding for migration or GRID reconfiguration causes S3 clients to experience performance degradation Performance metrics to be extremely high ERROR 1419 S3RQ: S3 request error (Exception after bytes sent): connection=1234567890, Resource=/bucket_xyz/object_s3.jpg, HTTP Status Code=500, ErrorMsg=InternalError, ErrorType=Client CustomErrorMessage={ }, Details={Failed to enqueue data (DSTR)}