Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/How_to_change_and_stagger_the_deduplication_schedule_in_ONTAP_9
      Applies to ONTAP 9 Description A common task for a system under resource contention is to stagger the schedules of a background task. This article provides the steps of creating a schedule and a dedup...Applies to ONTAP 9 Description A common task for a system under resource contention is to stagger the schedules of a background task. This article provides the steps of creating a schedule and a dedupe policy to stagger the volumes as needed.
    • https://kb.netapp.com/Cloud/Astra/Trident/Trident_pods_can_t_be_properly_scheduled_in_kubernetes_nodes_in_a_new_installation
      NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes...NetApp Astra Trident RedHat Openshift cluster (OCP) After installing Trident in a kubernetes cluster, the Trident pods do not reach running status and getting issues to be assigned to kubernetes nodes: Warning FailedScheduling xmys (x155 over 13h) default-scheduler 0/9 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/9 nodes are available: 1 Preemption is not helpful for scheduling, 8 node(s) didn't match Pod's node affinity/selector
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/A_SnapCenter_backup_fails_with_the_error_snapshot_already_exists
      Applies to SnapCenter Server Issue Occassionally, the same snapshot is attempted to be created twice in a row, as visible from the mlog/audit.log from the ONTAP storage, showing the error: A snapshot ...Applies to SnapCenter Server Issue Occassionally, the same snapshot is attempted to be created twice in a row, as visible from the mlog/audit.log from the ONTAP storage, showing the error: A snapshot copy with that name already exists. Note: this is usually the only snapshot attempt in the SAL/SCW log of the failed Job