Workflow to recover from a failure that does not require replacing journal volumes

Use the following workflow to recover from a failure on the UR delta resync pair due to a journal volume failure on the storage system at the GAD secondary site that does not require replacing the journal volume.

When a failure occurs on the UR delta resync pair, a SIM is displayed.

1. Increase the available capacity of the pool used by the journal at the GAD secondary storage system.
2. Resynchronize the UR delta resync pair to restore its status from the failure.

   Command example:

   pairresync -g oraDELTA -hold y

   If a failure occurs after the one volume capacity of a UR pair can be expanded, then the creation, resync, swap resync, horctakeover, and delta resync operations of the UR pair cannot be performed because the capacity of both the volumes is not the same. Make sure to expand the other volume capacity so that the capacity of both the volumes is the same, and then retry the operation.

3. Confirm that the status of the UR delta resync P-VOL is PSUS.

   Command example:

   pairdisplay -g oraDELTA -fxce -IH1
   Group PairVol(L/R) (Port#,TID, LU),Seq#, LDEV#.P/S,
   Status,Fence, %, P-LDEV# M CTG JID AP EM E-Seq# E-LDEV# R/W
   oraDELTA dev3(L) (CL1-A-1, 0, 1) 822222 4444. P-VOL
   PSUS ASYNC ,0 6666 - 0 0 - - - - -/-
   oraDELTA dev3(R) (CL1-A-1, 0, 1) 844444 6666. S-VOL
   SSUS ASYNC ,0 4444 - 0 0 - - - - -/-

4. Confirm that the mirror status of the journal of the UR delta resync pair is PJNS using the CCI instance for managing the GAD secondary storage system.

   Command example:

   pairdisplay -g oraDELTA -v jnl -IH1
   JID MU CTG JNLS AP U(%) Q-Marker Q-CNT D-SZ(BLK) Seq# Num LDEV#
   000 1 1 PJNS 4 21 43216fde 30 512345 62500 1 39321
   

5. Confirm that no failure SIMs are displayed.