What 3par should provide for RC monitoring....

[hdtvguy]

OK after 3 years of running blind on RC and being recently burned we finally started our script to monitor RC groups and RPO violations.

First and foremost this is a WORK IN PROGRESS!!!

I figured I would get this out there now rather than wait until ti is all done to help other people that may be in the same jam with being blind to RC delays.

The script will enumerate RC Groups and volumes and based on the period the RC group is set to determine if any volumes in the RC group are past their calculated RPO. Calculated RPO is determined by looking at the last time the volume synced and adds the period interval and compares that to the current time. If it is past the RPO it will export the data into a csv that can be used to see how far behind it is. There is still improved logic to come on this as the way showrc command exports data and what fields can be counted as reliable is a work in progress.

There is a parameter to bypass (default) any RC groups that are stopped.

Futures will include ability to write the data into a MS SQL DB and also to alert on stopped RC groups.

[hdtvguy]

Updated to fix a few bugs. Note the alertonstopped parameter is not yet implemented.

[Richard Siemers]

Thanks for sharing. Good stuff.

[dardan]

Updated to fix a few bugs. Note the alertonstopped parameter is not yet implemented.

Wow, this looks very nice. Especially as we're having some issues with RC link time-outs (with as consequence RC groups failing - and VVs deadlocked).
Any progress on this script?

Regards,

[hdtvguy]

I hear this script will break with 3.2.2, but am waiting for our lab system to be upgraded so I can check it.

[nsnidanko]

I've designed solution to monitor RC Groups for RPO violation via WSAPI and Powershell. You can find all required info and sample script.
http://blog.gptnet.net/?p=304

You can create loop and go through each volume, but I only cared about specific once, thus kept it simple.