VMAX3 and Locked Devices

I have an application that writes to its Device then  inside the array that Device is mirrored to an BCV.  When it is time for a backup a script will kick off that will break the mirror.
Then the backup application reads the data from that mirrored BCV.  Sometimes things will go wrong and that script will never resync the mirror.  That then results in broken backups.  To fix this I had to go into the VMAX3 SYMCLI and run these few commands.

  1.  symdev -lock list
  2. symdev release “Then confirm yes for each lock”

Looks really simple doesn’t it?  It took me a while to figure out.  It is not often I have to touch the VMAX and when I do it is usually with the GUI.  I also have a thick book of all the long complicated SYMCLI commands.  Thankfully through trial and error it ended up just being two simple commands.

Delete a SRDF pair on VMAX3

Recently I have had some issues with SRDF on the VMAX3 that I manage.  I was having issues trying to resolve it using the Unisphere GUI, which can be very limited in its capabilities, so I had to switch to command line.  First you create a text file and put in it something like “00001 00002” (No quotation marks in file).  Listing the two devices that need there pair broken.  Then you run this command.

symrdf -sid 123 -rdfg 1 -file rdf.txt deletepair -force

 

Using Solution Enabler to Delete a Storage Group

Recently I have been working on cleaning up storage on a EMC VMAX3.  You can do a lot using the GUI for most of the day to day maintenance, but using the CLI is a lot more efficient when it comes to removing storage groups.

symsg -sid 1234 delete storgegroup_SG -force

Using that command is a simpler and quicker way to remove storage groups than to use the Unisphere GUI.

Network, Meditech, and a VMAX3 failed backup

Recently the backup server rebooted itself in the middle of Networker running Meditech Magic backups.

Then all the Meditech backups would fail after 2 minutes.  This was caused by locked volumes with the VMAX3.  Backups with Meditech use BCV (Business Continuity Volumes) which are synced with TDEV volumes (Thin Devices).  These two volumes stay synced up at all times.  Then when a backup starts this connection is broken, and the backup is pulled from the BCV.  When the backup finishes the BCV reconnects to the production TDEV and syncs again.

Here are the commands I used with Solutions Enabler to unlock the volumes.

symdg -sid 1234 list (This will give you a list of all the LUNs on your server in the Device Group

symdev -lock list (This will give you a list of all LUN that are in locked mode)

symdev -lost # release (This will release the lock on the volumes)

Now you should be able to run the Meditech Magic backup.

Blog at WordPress.com.

Up ↑