unable to creat BCV paring ?

Question

I have a strange problem with create TimeFInder BCV paring I have a symm device group that BCV was added via # for dev in `cat /tmp/BCVDeviceList`; do echo $dev; symbcv -g symCC2dg associate dev $dev; done now I check it now, and it shows BCV has been added #symdg show  symCC2dg Group Name:  symCC2dg     Group Type                                   : REGULAR      Device Group in GNS                          : No     Valid                                        : Yes    Symmetrix ID                                 : 00018xxxxxxx    Group Creation Time                          : Mon Jun 14 14:36:13 2010    Vendor ID                                    : EMC Corp    Application ID                               : SYMCLI     Number of STD Devices in Group               :    8    Number of Associated GK's                    :    0    Number of Locally-associated BCV's           :    8    Number of Locally-associated VDEV's          :    0    Number of Locally-associated TGT's           :    0    Number of Remotely-associated VDEV's(STD RDF):    0    Number of Remotely-associated BCV's (STD RDF):    0    Number of Remotely-associated TGT's(TGT RDF) :    0    Number of Remotely-associated BCV's (BCV RDF):    0    Number of Remotely-assoc'd RBCV's (RBCV RDF) :    0    Number of Remotely-assoc'd BCV's (Hop-2 BCV) :    0    Number of Remotely-assoc'd VDEV's(Hop-2 VDEV):    0    Number of Remotely-assoc'd TGT's (Hop-2 TGT) :    0     Standard (STD) Devices (8):        {         --------------------------------------------------------------------                                                      Sym               Cap         LdevName              PdevName                Dev  Att. Sts     (MB)        --------------------------------------------------------------------        DEV001                N/A                     00C3 (M)  RW    104414        DEV002                N/A                     00F1 (M)  RW    104414        DEV003                N/A                     00FC (M)  RW    104414        DEV004                N/A                     0107 (M)  RW    104414        DEV005                N/A                     0112 (M)  RW    104414        DEV006                N/A                     011D (M)  RW    104414        DEV007                N/A                     0133 (M)  RW    104414        DEV008                N/A                     0574 (M)  RW     56953        }     BCV Devices Locally-associated (8):        {         --------------------------------------------------------------------                                                      Sym               Cap         LdevName              PdevName                Dev  Att. Sts     (MB)        --------------------------------------------------------------------        BCV001                N/A                     05CF (M)  RW    104414        BCV002                N/A                     05DA (M)  RW    104414        BCV003                N/A                     062A (M)  RW    104414        BCV004                N/A                     0635 (M)  RW    104414        BCV005                N/A                     0640 (M)  RW    104414        BCV006                N/A                     064B (M)  RW    104414        BCV007                N/A                     068A (M)  RW    104414        BCV008                N/A                     05C9 (M)  RW     56953        } so it shows BCV has been added and assocaite in the symm device group. However, #symmir -g  symCC2dg query Cannot proceed because the device does not have any BCV pairing relationship Device group 'symCC2dg' does not have any standard devices that are BCV paired. #symmir -g  symCC2dg establish -full -nop 'Full Establish' operation execution is in progress fordevice group 'symCC2dg'. Please wait... The feature being requested is not currently licensed so it think ehrer is no BCV pairing relationship? what am missing  ? A command to create pairing? I was able to create a separate symmCCdg group months earlier without problem. Thanks

RobertDudley · Answer

The relationship between source device and BCV as it has not been established.  You can establish just those devices, I am assuming device 008, to build that relationship.  Another method would be to do an establish on the group with the -full option.

Uwe-Ud0Mk · Answer

'The feature being requested is not currently licensed' is a licensing issue, not a TF issue. Check your license file and try again.

jason2009 · Answer

I have Timefinder/mirror license installed. but not Timefinder/clone.

just find out from EMC sales it seems

Timefinder/mirrow would only allow create un-protected BCV

while

TImefinder/clone is need to create BCV with raid5. Huh?

so maybe this is a licence issue. will check when we got the clone license.

RobertDudley · Answer

correct if your BCV's are raid-5 then its actually using clone emulation even though you issue a symmir command.

Symmetrix

Was this post helpful?