the read only snapshots are not updating from storage side

[ParBOSS]

Hi Guru's,

I need urgent help on the following:

The 3PAR T 800 3.1.2 MU1 is not updating the read only volumes and hence failing the script as well.

Here is the details this information according to last scheduled backup

On script if we mention like “-ro” its create the snapshots like below … and Job will failed at this stage

############################################################################################################
Running "/usr/bin/ssh -q odc3par2607 updatevv -ro -f set:CG_ODMORAPRD02_TSM"
Started: Tue Apr 14 10:01:27 CDT 2015
############################################################################################################

Updating VVs odmoraprd02_01.copy.tsm odmoraprd02_02.copy.tsm odmoraprd02_03.copy.tsm odmoraprd02_04.copy.tsm odmoraprd02_05.copy.tsm odmoraprd02_06.copy.tsm odmoraprd02_07.copy.tsm odmoraprd02_08.copy.tsm odmoraprd02_09.copy.tsm odmoraprd02_10.copy.tsm odmoraprd02_11.copy.tsm odmoraprd02_12.copy.tsm odmoraprd02_13.copy.tsm odmoraprd02_14.copy.tsm odmoraprd02_15.copy.tsm odmoraprd02_16.copy.tsm odmoraprd02_17.copy.tsm odmoraprd02_18.copy.tsm odmoraprd02_19.copy.tsm odmoraprd02_20.copy.tsm odmoraprd02_21.copy.tsm odmoraprd02_22.copy.tsm odmoraprd02_23.copy.tsm odmoraprd02_24.copy.tsm odmoraprd02_25.copy.tsm odmoraprd02_26.copy.tsm odmoraprd02_27.copy.tsm odmoraprd02_28.copy.tsm odmoraprd02_29.copy.tsm odmoraprd02_30.copy.tsm odmoraprd02_31.copy.tsm odmoraprd02_32.copy.tsm odmoraprd02_33.copy.tsm odmoraprd02_34.copy.tsm odmoraprd02_35.copy.tsm odmoraprd02_36.copy.tsm odmoraprd02_37.copy.tsm odmoraprd02_38.copy.tsm odmoraprd02_39.copy.tsm odmoraprd02_40.copy.tsm odmoraprd02_41.copy.tsm odmoraprd02_42.copy.tsm odmoraprd02_43.copy.tsm odmoraprd02_44.copy.tsm Parent volumes are VV set members: odmoraprd02_01.copy odmoraprd02_02.copy odmoraprd02_03.copy odmoraprd02_04.copy odmoraprd02_05.copy odmoraprd02_06.copy odmoraprd02_07.copy odmoraprd02_08.copy odmoraprd02_09.copy odmoraprd02_10.copy odmoraprd02_11.copy odmoraprd02_12.copy odmoraprd02_13.copy odmoraprd02_14.copy odmoraprd02_15.copy odmoraprd02_16.copy odmoraprd02_17.copy odmoraprd02_18.copy odmoraprd02_19.copy odmoraprd02_20.copy odmoraprd02_21.copy odmoraprd02_22.copy odmoraprd02_23.copy odmoraprd02_24.copy odmoraprd02_25.copy odmoraprd02_26.copy odmoraprd02_27.copy odmoraprd02_28.copy odmoraprd02_29.copy odmoraprd02_30.copy odmoraprd02_31.copy odmoraprd02_32.copy odmoraprd02_33.copy odmoraprd02_34.copy odmoraprd02_35.copy odmoraprd02_36.copy odmoraprd02_37.copy odmoraprd02_38.copy odmoraprd02_39.copy odmoraprd02_40.copy odmoraprd02_41.copy odmoraprd02_42.copy odmoraprd02_43.copy odmoraprd02_44.copy


On script if won’t mention like “-ro” its create the snapshots like below …

############################################################################################################
Running "/usr/bin/ssh -q odc3par2607 updatevv -f set:CG_ODMORAPRD02_TSM"
Started: Tue Apr 14 14:43:18 CDT 2015
############################################################################################################

Updating VVs odmoraprd02_01.copy.tsm odmoraprd02_02.copy.tsm odmoraprd02_03.copy.tsm odmoraprd02_04.copy.tsm odmoraprd02_05.copy.tsm odmoraprd02_06.copy.tsm odmoraprd02_07.copy.tsm odmoraprd02_08.copy.tsm odmoraprd02_09.copy.tsm odmoraprd02_10.copy.tsm odmoraprd02_11.copy.tsm odmoraprd02_12.copy.tsm odmoraprd02_13.copy.tsm odmoraprd02_14.copy.tsm odmoraprd02_15.copy.tsm odmoraprd02_16.copy.tsm odmoraprd02_17.copy.tsm odmoraprd02_18.copy.tsm odmoraprd02_19.copy.tsm odmoraprd02_20.copy.tsm odmoraprd02_21.copy.tsm odmoraprd02_22.copy.tsm odmoraprd02_23.copy.tsm odmoraprd02_24.copy.tsm odmoraprd02_25.copy.tsm odmoraprd02_26.copy.tsm odmoraprd02_27.copy.tsm odmoraprd02_28.copy.tsm odmoraprd02_29.copy.tsm odmoraprd02_30.copy.tsm odmoraprd02_31.copy.tsm odmoraprd02_32.copy.tsm odmoraprd02_33.copy.tsm odmoraprd02_34.copy.tsm odmoraprd02_35.copy.tsm odmoraprd02_36.copy.tsm odmoraprd02_37.copy.tsm odmoraprd02_38.copy.tsm odmoraprd02_39.copy.tsm odmoraprd02_40.copy.tsm odmoraprd02_41.copy.tsm odmoraprd02_42.copy.tsm odmoraprd02_43.copy.tsm odmoraprd02_44.copy.tsm


Any quick help will be much appreaciated.

Thanks
Dave

[Richard Siemers]

Hello Dave,

from the cli help - note the clause "if not a VV set member"

Code: Select all

OPTIONS
    -ro
        Specifies that if the specified virtual volume (<VV_name>) is a read-
        write snapshot the snapshot's read-only parent volume is also updated
        with a new snapshot [b][u]if the parent volume is not a member of a virtual
        volume set. [/u][/b]If this option is not specified, the virtual volumes, as
        indicated with the <VV_name> specifier, are replaced by a new snapshot.
        See Notes for additional information.

Code: Select all

    After the updatevv command is executed, all VLUNs associated with the
    specified virtual volume name are removed. The command then updates the
    snapshots as follows:

        If the -ro option is not specified, or if the specified virtual volume
        name is a read-only snapshot, the command removes the snapshot, and
        creates a new snapshot of the same name and of the same parent.

        If the -ro option is specified and the specified virtual volume name is
        a read-write snapshot, the virtual volume is removed and its read-only
        parent is replaced by a new read-only snapshot of the same name. Then,
        a new read-write snapshot is created of the new read-only snapshot. If
        the read-only parent has multiple read-write snapshots, the updatevv
        operation will fail because the read-only parent volume cannot be
        removed.

[Richard Siemers]

We've implemented a daily refresh of a dev DB from production and have this exact same issue. Our RW snaps refresh everyday, but it does not update the parent RO snap, even though the -ro parameter is used. I have verified that we are not using any "VV sets" in the literal term as it

I have opened a case with HP, but I suspect that ay say that specifying more than one vv on the command line is the equivalent of a VV set, and will skip updating the RO parents.

If that is the case, its going to force us to rewrite our scripts from the single "updatevv" line into larger batch jobs that remove vlun, delete the rw snaps, update the ro snaps, then create rw snaps, then re-create vluns... since we are snapping a production SQL db, we need the ro snap to be crash-consistent, getting data and logs at the same time.

Anyone else have experience with this issue?

[Richard Siemers]

Update:

The parent VV has to be RO snap... by default a snapshot created is as RW. So by default, a snapshot of a snapshot is RW to RW which does not work for updatevv.

So to fix my situation, I need to recreate the parent snap as RO or, skip the extra layer of snaps.