How to expand strip meta in vmax

1) Create devices to add to the meta -
symconfigure -sid 000 -cmd "create dev count=2, size=64gb cyl, emulation=FBA, config=TDEV;" prepare / commit
Consider AAAA and BBBB are newley created devices

2) Create devices to use for the BCV -
symconfigure -sid 000 -cmd "create dev count=2, size=64gb cyl, config=BCV+TDEV, emulation=FBA;" prepare / commit
Consider XXXX and YYYY are newley created devices
      
3) Form a meta from the BCV devices -
symconfigure -sid 000 -cmd "form meta from dev XXXX, config=striped, stripe_size=1920; add dev YYYY to meta XXXX;" prepare / commit

4) Bind this meta to a pool -
symconfigure -sid 000 -cmd "bind tdev XXXX to Pool <Pool_Name> preallocate size=ALL allocate_type = persistent;" prepare / commit

5) Expand the meta -
symconfigure -sid 000 -cmd "add dev AAAA:BBBB to meta ZZZZ, protect_data=TRUE, bcv_meta_head=XXXX;" prepare / commit

How to add device to existing srdf 

Here is what you do:
- SRDF/A remains active at all times.
- Create an RDF group for the purposes of initial synch up.
- Do the create pair to the synch-up RDF group.
- Synch the device in Adaptive copy mode.
- suspend the device with the -cons_exempt option
- perform a symrdf MOVEPAIR to move the new device into the SRDF/A group
- <set mode async> on the new device (not sure if this step is required from memory)
- symrdf resume the device
- The consistency exempt flag will go away automatically once the device is in srdf/a mode with no invalid tracks (in lock step with all other devices)
- now you can add the device into the device group.

Storage area network

A storage area network (SAN) is a dedicated network that provides access to consolidated, block level data storage. SANs are primarily used to enhance storage devices, such as disk arrays, tape libraries, and optical jukeboxes, accessible to servers so that the devices appear like locally attached devices to the operating system. A SAN typically has its own network of storage devices that are generally not accessible through the local area network (LAN) by other devices. The cost and complexity of SANs dropped in the early 2000s to levels allowing wider adoption across both enterprise and small to medium sized business environments.

A SAN does not provide file abstraction, only block-level operations. However, file systems built on top of SANs do provide file-level access, and are known as SAN filesystems or shared disk file systems.

Historically, data centers first created "islands" of SCSI disk arrays as direct-attached storage (DAS), each dedicated to an application, and visible as a number of "virtual hard drives" (i.e. LUNs).^[1] Essentially, a SAN consolidates such storage islands together using a high-speed network.

Operating systems maintain their own file systems on their own dedicated, non-shared LUNs, as though they were local to themselves. If multiple systems were simply to attempt to share a LUN, these would interfere with each other and quickly corrupt the data. Any planned sharing of data on different computers within a LUN requires advanced solutions, such as SAN file systems or clustered computing.

Despite such issues, SANs help to increase storage capacity utilization, since multiple servers consolidate their private storage space onto the disk arrays.

Common uses of a SAN include provision of transactionally accessed data that require high-speed block-level access to the hard drives such as email servers, databases, and high usage file servers.

Welcome To Storage F1

I am starting blog for all my storage friends.
Come and share your knowledge with others.