Steps needs to be taken before moving the luns from one storage group to other without any data loss or server panics

what server OS /application ?

we are moving data on the old server that is on clariion to the new server on Vblock. Linux team is making a test to move this data. New server has some other applications that are not on the old server.

Server is Linux. not sure about the application. can you provide the best practices for all the OS that you know?

so if you are moving between an old clariion to a vBlock (assuming EMC array as the backend). Don't you need to replicate the LUNs to the vBLock first ?  I was assuming you are trying to move LUNs between storage groups on the same array.

Moving a LUN from one storage group to another is disruptive. On Unix/Linux you will first need to determine if that LUN is part of a volume group. If it is you can't just move an individual LUN, you would need to move all LUNs that comprise that volume group. What is the purpose of this move ?

Linux team is not copying any data to the Vblock. They just wanted to map the luns from the clariion array(old server) to the new server. Data still sits on the clarrion array.so we need to create a new storage group and add the required luns to the new storage group. we are not migrating any data. I am sorry for not explaining this in my previous post.

Thanks for the help. what if we need to move on a windows sql box? is the procedure same?

pretty much minus the volume manager (hopefully you are not using Veritas Storage Foundation for Windows or spanning disk volumes)

Do you have a command to find the storage groups a lun belongs to on a clariion?

for symmetrix we have symaccess -sid xxxx list -type storage -dev xxxx 

you will need to do some scripting, naviseccli is more than a decade old and still is as crappy as it was 10 years ago.

naviseccli -address   storagegroup -list

This may be a late answer , the below Navicli command will give the storagegroup membership of any LUN

#naviseccli -h ip getlun #lunno | grep -i "lu storagegroup\:"

This may be a late answer to your post,

The LUNs can be shared across multiple storage groups and in your case your existing server LUNS can be added in to new server storage group.

Curious to know how it went.
Ramnav , can you update us with the outcome of this?

We have created new storage group and added luns to the new storage group bringing down the databases. Linux team rescanned the devices on new server.

Thanks all for the help.