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

ONTAP Recipes: Do you know you can...?   Easily add 6 SSDs to a 8-SSD AFF-A200 HA-Pair   An AFF-A200 HA pair ordered with 8x SSDs uses the root-data-data partitioning scheme.  Typically, the SSDs are provisioned into aggregates such that each controller uses 7 data partitions for filesystem data, and one data partition remains as a spare.   This recipes highlights the steps to add 6x SSDs to such a system.    1. Install the SSDs. They should be the same capacity as the existing SSDs.    2. Go to System Manager and select Hardware and Diagnostics -> Disks    3. Choose the Inventory tab, then Assign.    4. Assign all 6 SSDs to one of the two controllers in the HA pair. Let’s call it Node A.    5. Go to the Hardware and Diagnostics -> Aggregates screen, choose the data aggregate owned by Node A,  then Actions -> Add Capacity.    6. At this point, you will see one small SSD partition, and 6 whole SSDs.     7. Add the smaller disk/partition to the aggregate. This is the spare partition from the original 8-drive configuration.   8. Repeat the Actions -> Add Capacity operation for 5 of the 6 remaining disks. As you provision the whole SSDs into the data aggregate, they will be partitioned to match the rest of the SSDs.  One data partition per SSD will be used on this aggregate, and another spare data partition will be created and assigned to the partner node.   9. Return to the Aggregates screen and repeat the Actions -> Add Capacity operation for the data aggregate on the second node in the HA pair. If System Manager gives an error saying you have insufficient spare disks, you can resolve this by returning to the Disks-> Inventory screen and assign the remaining spare disk back to the second node.   For more information, see the ONTAP 9 documentation center ... View more