maxing out a DMX1000

yeah that's sort of what I had been thinking, the big problem is the "temp storage" :P we do have another DMX1000 but it only has about 8TB free. does it make sense for me to start finding out how many devices were created using hypers on the 146GB drives? Great tip about the cache, I haven't thought about that. just checked out all the V-max presentation yesterday...man, if only that came out a few years back, we won't have this problem to deal with now :P Thanks stefano!

Funny, I just said the same thing about the V-Max in another thread. I've got DMX3 on the floor, but still running into issues similar (but different) to yours. If only those DMX3s were V-Max we wouldn't have a problem!

You are welcome

Thus your issue is with temp storage ?? Go ask your sales rep a quote .. you can always ask EMC to lease you a storage while moving data around ..

The easier way to find devices on 146Gb drives is to obtain a list of drives in different disk groups and later use symdev filtering its output by diskgroup.

# symdisk -sid xxx list -by_diskgroup

# symdev -sid xxx -diskgroup Y list

V-MAX for president

Thanks man, yup you read my mind, I used those commands yesterday to generate the following numbers

SYMM A (7.3 TB free)
# of 146GB drives = 72

Configured/used space across those drives = 6 TB (got this by subtracting the unconfigured space on the drive from it's formated size then added everything together, also subtracted available mapped/unmapped devices)

planning to replace them with 500GB drives so that comes out to be 72 x 500GB = 35TB additional RAW storage

SYMM B (9.4TB free)
# of 146GB drives = 84

Configured/used space across those drives = 5.5 TB
84 x 500 = 41TB additional RAW storage

unfortunately due to facility constraints we won't be able to put any more racks and borrow temp storage

so if we were to use something like OR, would it be something like this?

-copy 146GB luns from SYMM B to SYMM A
-swap the drives out on SYMM A, copy the data back from SYMM B (this time it would include both SYMM A and SYMM B data since there would be plenty of space now)
-swap out the drive on SYMM B, copy its data back from SYMM A

we also have static SRDF devices on those 146GB drives which will add to the headaches. So I have read some of OR documentation, as I understand it, it copies the data over the SAN fabric. But out of curiosity, could this be used to copy devices on the same symm or does it have to go to a remote symm.


Splodge
thanks for the comment are you referring to symmreix Optimizer? please direct me to some relevant documentation on how you did your manual swap, Thanks!

jliu2

Yes - Symmetrix Optimizer.
There are some white papers on Powerlink to do with Symmetrix Optimizer.
Also if you read the Symmetrix Optimizer Manuals (either under Solutions Enabler or ControlCenter) that will help.
The sections on the "migrate" option explain it, but I don't think the migrate option will work on the DMX1000 (wrong code level).
You can do it 4 ways. (in no particular order)
1 - CLI
2 - ControlCenter
3 - SMC
4 - Optimizer on the Service Processor.
Not all Hypers can be "swapped" (e.g BCV,DRV,SFS,VCMDB, anything unprotected)

I'll check it out, thanks man