Resolving lag issues

This workflow provides an example of how you might resolve a lag issue. In this scenario, you are an administrator or operator accessing the Unified Manager Dashboards/Overview page to see if there are any problems with your protection relationships and, if they exist, to find solutions.

Before you begin

You must have the OnCommand Administrator or Storage Administrator role.

About this task

In the Dashboards/Overview page, you look at the Unresolved Incidents and Risks area and see a SnapMirror Lag error in the Protection pane under Protection Risks.

Steps

  1. In the Protection pane on the Dashboards/Overview page, locate the SnapMirror relationship lag error and click it.
    The Event details page for the lag error event is displayed.
  2. From the Event details page you can perform one or more of the following tasks:
    • Review the error message in the Cause field of the Summary area to determine if there is any suggested corrective action.
    • Click the object name, in this case a volume, in the Source field of the Summary area to get details about the volume.
    • Look for notes that might have been added about this event.
    • Add a note to the event.
    • Assign the event to a specific user.
    • Acknowledge or resolve the event.
  3. In this scenario, you click the object name (in this case, a volume) in the Source field of the Summary area to get details about the volume.
    The Protection tab of the Health/Volume details page is displayed.
  4. In the Protection tab, you look at the topology diagram.
    You note that the volume with the lag error is the last volume in a three-volume SnapMirror cascade. The volume you selected is outlined in dark gray, and a double orange line from the source volume indicates a SnapMirror relationship error.
    SnapMirror lag cascade topology
  5. Click each of the volumes in the SnapMirror cascade.
    As you select each volume, the protection information in the Summary, Topology, History, Events, Related Devices, and Related Alerts areas changes to display details relevant to the selected volume.
  6. You look at the Summary area and position your cursor over the information icon in the Update Schedule field for each volume.
    In this scenario, you note that the SnapMirror policy is DPDefault, and the SnapMirror schedule updates hourly at five minutes after the hour. You realize that all of the volumes in the relationship are attempting to complete a SnapMirror transfer at the same time.
  7. To resolve the lag issue, you modify the schedules for two of the cascaded volumes so that each destination begins a SnapMirror transfer after its source has completed a transfer.