Can I create a meta from non-meta dev on 5875?

Just be sure to verify the code is at 5875.  I believe in older code versions even forming a concatenated meta would wipe out the data on the TDEV.  It will definately wipe it out if you form a striped meta (regardless of code version). 

Also if you're at lower than 5875 only unmapped TDEVs can be formed into metas.  If at 5875 they can be bound and mapped (for concatenated).

For the convert (from concatenated to striped) step there are also some restrictions as to what can and can't be used for a BCV with the protect_data option.  It depends on the SE and Microcode levels.  Generally if you have SE 7.3.x and 5875 code you should be good to go, but I'd strongly recommend checking the Solutions Enabler Symmetrix Array Controls CLI Product Guide for details on expanding a thin meta.

You can do this in two steps with 5875 code. The TDEV must be turned into a concatenated meta first, you cannot non-disruptively form a striped meta directly. However you can convert the concat meta to striped after you formed the concat meta with the data_protect option.

Thank you both. Yes we are using SE 7.3.2.2 and Enginuity 5875.231.172.

I think I have the steps down now.

From the aforementioned guide, starting on p65:

Converting a metadevice

To convert a metadevice’s configuration from concatenated to striped, use the
following command:

convert meta SymDevName config=MetaOption
[, stripe_size=MetaStripeSize>[cyl]],
[, protect_data=[TRUE|FALSE],
[bcv_meta_head=SymDevName];

Where:

stripe_size— Specifies the stripe size in 512 byte blocks.

protect_data— Specifies whether the data needs to be protected. Possible
values are TRUE or FALSE. This option can only be used while converting a
metadevice from concatenated to striped.

bcv_meta_head— Specifies the Symmetrix device name (or thin device name).

Metadevices can be converted from concatenated metadevices to striped devices
using the convert meta command. The command can also be used to change the
stripe size of a striped metadevice.

When converting from concatenated metadevices to striped devices, use the
protect_data option to preserve data on the BCV metadevice during conversion.
The BCV metadevice must match the original standard meta in size, configuration,
and member count.

The bcv_meta_head option specifies which BCV metadevice to use.

Example

To convert a concatenated metadevice 0030 to a striped metadevice and preserve data
during the conversion using BCV metadevice 01F, enter:

convert meta 0030, config=striped, stripe_size=1920,
protect_data=TRUE, bcv_meta_head=01f

Note: The specified BCV metadevice must be identical to the original metadevice in capacity,
stripe count, and stripe size.

Thin metadevices The following thin metadevice conversions are supported:

? Convert thin concatenated metadevices to thin striped metadevices, without
protecting data.
? Convert thin concatenated metadevices to thin striped metadevices, while
protecting data using a regular BCV device.
? Convert a thin concatenated metadevice to a thin striped metadevice, while
protecting the data on the thin meta using a thin BCV device that is persistently
allocated.
? Convert a thin striped metadevice to a thin concatenated device, without
protecting the data.
Restrictions The following restrictions apply to converting thin metadevices:
? All existing rules for converting metadevices using BCV devices for data
protection apply to thin BCV devices. (such as size, number of members, and
member size).
? A thin BCV device used for data protection must be bound to a thin pool, and
must be fully allocated with persistent allocations.
66 EMC Solutions Enabler Symmetrix Array Controls Version 7.3 CLI Product Guide
Managing Configuration Changes
? RDF BCVs cannot be used for data protection.
? If a thin BCV metadevice is used for protecting data, the meta head and all
members must be bound to a thin pool.
? All the data on the BCV device used for protecting the data will be lost.

Hi,

Can you please let me know if you were able to do this? My concern is for the first step. Can we convert a non-meta device to a concatenated meta device online? Enginuity 5876?

mumshad, yes we were able to do this on 5875 code, steps we followed are listed below, some were precautionary

1) Clone the source TDEV to make a backup of it (precautionary - since this was our first time)

2) Make source TDEV not ready and unmap - (again precautionary)

3) Carve TDEV to add as a new meta member to source tdev - In our case 25GB TDEV to add to another 25GB TDEV

4) Form concatenated meta as you would normally, adding the new TDEV (meta member) to the source TDEV (meta head)

5) Mask the new "expanded" meta back to host, you should have no data loss.

Rermember, this process is for concatenated only. To create a striped meta from a standard non-meta TDEV, more of a 2 step process. Convert to a concat meta, and then from concat to striped, but you need to use a BCV save device for that process, which is well documented and also can be found in the Symmetrix Procedure Generator.

Good luck