Add SnapMirror data protection relationship tools

[ebarron]

Summary

Add MCP tools for managing SnapMirror data protection relationships between volumes/SVMs.

Background

Per SPSPM-2247, the ONTAP MCP server should support data protection. SnapMirror is the primary mechanism for replicating data between ONTAP clusters for disaster recovery and backup. No SnapMirror tools currently exist.

Proposed Tools

• create_snapmirror — Create a SnapMirror relationship (async, sync, or mirror-vault)
• update_snapmirror — Update relationship policy or schedule
• delete_snapmirror — Delete a SnapMirror relationship
• initialize_snapmirror — Start initial baseline transfer
• update_snapmirror_transfer — Trigger an on-demand transfer/update
• break_snapmirror — Break relationship (make destination writable)
• resync_snapmirror — Resynchronize a broken relationship

ONTAP REST API Endpoints

• POST /api/snapmirror/relationships
• PATCH /api/snapmirror/relationships/{uuid}
• DELETE /api/snapmirror/relationships/{uuid}
• POST /api/snapmirror/relationships/{uuid}/transfers

Priority

Low — Important for data protection but complex; read-only queries can use ontap_get in the interim.

Related

• Jira: SPSPM-2247