Did you know… You can use inactive data reporting on non-FabricPool aggregates?   First available in ONTAP 9.4, inactive data reporting (IDR) is an excellent tool for determining the amount of existing inactive (cold) data that can be tiered from a high-performance SSD aggregate to low-cost object storage. IDR uses a 31-day cooling period to determine which data is considered inactive. IDR is displayed on the Storage Tiers page in OnCommand System Manager. IDR is enabled by default on FabricPool aggregates, but more importantly, especially for those considering taking advantage of FabricPool for the first time, you can enable IDR on non-FabricPool aggregates. Note: IDR cannot be enabled on aggregates where FabricPool cannot be enabled (for example, root, HDD aggregates, NetApp MetroCluster, and so on).   From the ONTAP CLI, complete the following steps: To enable IDR on a non-FabricPool aggregate, run the following command: storage aggregate modify -aggregate <name> -is-inactive-data-reporting-enabled true As an alternative to viewing the amount of inactive data on an aggregate in OnCommand System Manager, you can view the amount of inactive data by running the following command: storage aggregate show-space -fields performance-tier-inactive-user-data, performance-tier-inactive-user-data-percent   For more information about FabricPool, see TR-4598: FabricPool Best Practices . For more information about ONTAP, see the ONTAP 9 Documentation Center .   ... View more

Did you know that… You can easily test the SVM-DR destination disaster recovery without breaking the SnapMirror relationship?   Note: In an existing SnapMirror relationship, these steps will help you test the disaster recovery solution without breaking the SnapMirror relationship. In a SnapMirror relationship, select the volumes to be tested. destination::> snapmirror show -expand Create a default subtype vserver on the destination cluster. destination::> vserver create -vserver <clone_vserver> -subtype default Note: Create LIFs and export polices to enable NFS traffic. Create a clone on the destination cluster. Select the parent volume and parent Snapshot copy from the SnapMirror destination vserver as parent vserver. destination::> vol clone create -vserver <clone_vserver> -flexclone <flex_cone_volume> -type RW -parent-vserver <SVM-DR Destination vserver> -parent-volume <parent_volume> -junction-active true -foreground true -parent-snapshot <parent_snapshot> Mount the FlexClone volumes on the junction path. destination::> vol mount -vserver <clone_vserver>  -volume <flex_cone_volume> -junction-path /<flex_cone_volume_mountpath> Mount through NFS on the desired test client. FlexClone volumes should be visible on the client. For more information about ONTAP, see the ONTAP 9 Documentation Center. ... View more

Did you know you can…? Calculate your round-trip time (RTT) for SnapMirror Synchronous   Run the cluster peer ping command, where the originating-node is the node that hosts the source volume of the relationship and the destination-node is the node that hosts the destination volume of the relationship. cluster::> cluster peer ping -originating-node sti8080-475 -destination-node sti8080-477 Node: sti8080-475 Destination Cluster: C2_sti8080-477_cluster Destination Node IP Address Count TTL RTT(ms) Status ---------------- ----------- ----- ---- ------- ------------------------- sti8080-477   172.26.145.10 1     64   0.452   interface_reachable sti8080-477   172.26.145.12 1     64   0.352   interface_reachable   For intracluster relationships, you can run the network ping command in a similar way. cluster::> network ping -node sti8080-477 -destination sti8080-475 -show-detail   For more information about ONTAP, see the ONTAP 9 Documentation Center. ... View more

Did you know you can…? Easily convert a SnapMirror relationship to zero recovery point objective (RPO)   Verify the network round-trip time (RTT) between the two nodes is less than 10ms. Add a SnapMirror synchronous license to the source node. Delete the asynchronous SnapMirror relationship: destination::> snapmirror delete -destination-path vs1:vol1 Release the asynchronous SnapMirror relationship on the source side with the option to retain the Snapshot copies: source::> snapmirror release -destination-path vs1:vol1 -relationship-info-only true Note: The default release operation (without setting relationship-info-only to true) deletes the Snapshot copies created by this relationship. This process does not allow a resync operation for a new relationship created for these volumes. Create the synchronous SnapMirror relationship by specifying a policy of type sync-mirror or strict-sync-mirror: destination::> snapmirror create -source-path vs0:vol1 -destination-path vs1:vol1 -policy Sync Note: To create a strict synchronous relationship, use the StrictSync policy instead. Resync the synchronous SnapMirror relationship: destination::> snapmirror resync -destination-path vs1:vol1 For more information about ONTAP, see the ONTAP 9 Documentation Center ... View more

Did you know you can…? Easily convert a synchronous SnapMirror relationship to asynchronous   Quiesce the synchronous SnapMirror relationship: destination::> snapmirror quiesce -destination-path vs1:vol1 Delete the synchronous SnapMirror relationship: destination::> snapmirror delete -destination-path vs1:vol1 Release the synchronous SnapMirror relationship on the source side with the option to retain the Snapshot copies: source::> snapmirror release -destination-path vs1:vol1 -relationship-info-only true Note: The default release operation (without setting relationship-info-only to true) deletes the Snapshot copies created by this relationship. This process does not allow a resync operation for a new relationship created for these volumes. Create the asynchronous SnapMirror relationship by specifying the required policy: destination::> snapmirror create -source-path vs0:vol1 -destination-path vs1:vol1 -policy MirrorAllSnapshot Resync the asynchronous SnapMirror relationship: destination::> snapmirror resync -destination-path vs1:vol1 For more information about ONTAP, see the ONTAP 9 Documentation Center ... View more