NetApp SnapMirror Monitor Script – Part 3 with DataONTAP PowerShell Toolkit v1.0

By | June 15, 2010

My second attempt also worked out pretty well, but the DataONTAP PowerShell Toolkit, has been released, and I wanted to update my script to leverage a supported toolkit. If you have a NetApp, and are getting deeper into using Powershell, this toolkit is for you.

I’m not going to go deep into the details of how this script works, as most of that is covered in the previous post.

What I am going to detail is the difference between the old and new scripts.

The Old Script

#Load the PoshOnTap Module
Import-Module PoshOnTap

#Connect to the Filer
Connect-NaServer -Filer netapp2

#Pull The Data
$body = Get-NaSnapMirror|Select Source,Destination,Status,State,Lag,LastTransferSize,LastTransferDurration|Out-String

#Send e-mail
Send-MailMessage -From "" -To "user@yourdomain" -Subject "NetApp Replication Script" -SmtpServer -Body $body

The New Script

#Load the DataONTAP Module
Import-Module DataONTAP

#Connect to the Filer
Connect-NaController netapp2

#Pull The Data
$body = Get-NaSnapmirror|Select SourceLocation,DestinationLocation,Status,State,LagTime,LastTransferSize,LastTransferDuration|Out-String

#Send e-mail
Send-MailMessage -From "" -To "user@yourdomain" -Subject "NetApp Replication Script" -SmtpServer -Body $body

The only differences between the 2 scripts are at lines 5 and 8.

Line 5:

  • Connect-NaServer -Filer becomes Connect-NaController

Line 8:

  • Source becomes SourceLocation
  • Destination becomes DestinationLocation
  • Lag becomes LagTime
  • LastTransferDurration becomes LastTransferDuration (obvious typo in PoshOnTap)

Other than those 2 lines, the scripts are identical.

I’d like to give a shout out to Glenn Sizemore for leading the way with PoshOnTap and NetApp for following his lead with the DataONTAP PowerShell Toolkit.

Update to this post
I was digging a little deeper on this post, and apparently dates are returned as INT64 Integers.  Makes things a little messy, and requires some data manipulation.

There’s a post about it on the NetApp Communities that details a workaround (again, kind of messy).  PoshOnTap handles dates better, so maybe NetApp will see the issue, and quickly release a v1.1 of the toolkit to correct the problem.  Nevertheless, I’ll continue using the supported (albeit a little more clunky with regard to dates) toolkit.

As soon as I find a clean/optimized way to address the situation, I will update this post.

Using Powershell I can execute the same command, and actually get more information.

5 thoughts on “NetApp SnapMirror Monitor Script – Part 3 with DataONTAP PowerShell Toolkit v1.0

  1. Pingback: Jase's Place » NetApp SnapMirror Monitor Script – Part 3 with … : : monitor

  2. Don

    Jase – this got it working in windows time format. grabbed the snippet from fjohn here:

    #Pull The Data
    $body = Get-NaSnapmirror|Select SourceLocation,DestinationLocation,Status,State,

    hope this pastes well


    1. Jase Post author

      Thanks for the extra legwork!

      I’ve been a little too busy to push it over the edge.

  3. Terry

    Thanks Jase for the fantastic starting ground here. Excellent work, nice of you to make my life easier.

    I would like to point out a couple tweaks that will make the time output human readable.

    According to Clinton Knight at the below discussion, we can use the LagTimeTS and LastTransferDurationTS to give us a more human readable output.

    Output will look like this:
    SourceLocation : Filer1:NFS1
    DestinationLocation : Filer2:NFS1_Mirror
    Status : idle
    State : snapmirrored
    LagTimeTS : 11:26:28
    LastTransferSize : 13794803712
    LastTransferDurationTS : 00:57:05

    My next step is to convert the transfer size to MB rather than just bytes.

    1. Jase Post author

      Good code there. I haven’t really had any need for NetApp code lately, given that I work for EMC.



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.