Know about the version, list of symcli commands ect.. This will make the traget devices in ReadWrite RW mode. If the session created with a "-copy" option default create option is copy , this will start the background copy from source to target device. By default this will create a differentail session.
|Published (Last):||21 November 2004|
|PDF File Size:||17.86 Mb|
|ePub File Size:||13.48 Mb|
|Price:||Free* [*Free Regsitration Required]|
The information here is not a substitute for the product guides which have been consolidated into a single downloadable PDF documentation set please download and refer to the documentation set for full feature descriptions. FAST has been enhanced to work on a more granular level KB track level and we have abstracted a lot of the internals so that the end user need not be so concerned about the mechanics of the array they can simply provision capacity and set a performance expectation which the array will work to achieve.
VMAX3 supports 64K storage groups so there is no reason not to configure 1 per app. Create and add your devices, here I am creating 5 x GB devices and adding to my storage group.
Note I can just create GB devices, no meta is created. At present we can create devs up to 16TB soon to be increased further. Present to the host via a masking view, no change from VMAX here. SLO compliance is reported at every level when looking at storage group components in Unisphere. The output shows the approximate response time for each.
Additionally you can see consumption on an individual device level on the application storage group. This is useful as you can now create devices and automatically add to storage group from CLI, so a staging group may exist. Needless to say, taking snapshots on VMAX3 is quicker, more efficient and easier than it has been on any previous generations.
See the technote for full details. Like most features in the VMAX to access the functionality simply put the word sym in front of the feature name. SnapVX is controlled with the symsnapvx command set. Really the only command you should need is symsnapvx —h, this will get you the full set of options.
Creating Snapshots SnapVX is simplest when your storage has been designed with an application per storage group, you can still use device groups or files if you want but VMAX3 supports 64K storage groups, that is enough for one per application in most environments and means only managing a single entity for each application for provisioning as well as local replication and remote replication.
You can snap multiple applications together using a cascaded storage group containing all of the child storage groups for each application. SnapVX snapshots are consistent by design so no need to specify any additional flags to obtain a point in time image of a live system.
To create a snapshot simply grab the storagegroup name which contains all the devices for your application and execute the establish command, the example below will create a snapshot hourly snapshot and will automatically terminate the same snapshot 24 hours after it was created: symsnapvx —sg test—snapshotname hourlysnapshot establish —ttl —delta 1 —nop You could run the command above in a cron job or batch file every hour and snapvx will create a new generation each time gen 0. Listing SnapVX Snapshots And Capacity Consumed In order to see which storage groups are consuming the most space we can run the following cmd: symcfg list —srp —demand —type sg The output lists the storage groups showing their subscribed capacity how much potential space they can consume as well as their actual allocated capacity.
A Particulary useful output here is the SnapShot Allocated GB Column, if you are in a bind for space you can quickly identify which storage group has consumed the most snapshot space and terminate some snapshots to return space to the SRP. Note your storage group will only show up in this command output if it is FAST managed. Shown below SourceSG1 has a large capacity of snapshot allocated storage.
For deeper dive and more on the internals please see the Technote on EMC. Can also be used to view Symmetrix device locks. Mapping and Masking of devices symacl — Administer Symmetrix access control information. Older Symmetrix Pre symmigrate — Migrates the physical disk space associated with a Symmetrix device to a different data protection scheme, or to disks with different performance characteristics. Share this:.
EMC VMAX3 – CLI Cheat Sheet