Hello Amit
if am not wrong,hope you just require the Device ID of the Quorum disk?

It's easy to find if you have powerpath installed on the host.Right click on that particular Quoram disk,You will gt the device ID 7 then you can get the complete details of it from the following command

"symdev -sid xxx show device id"

as Quorum disks are spaced use cluster nodes, how do i find the same on unix?

On Unix .. as usual .. it depends

HPUX uses a small slice of any existing disk as quorum device. You have to dig the cluster configuration if you want to find what disk is used.
Veritas uses some "fence devices" .. They area fancy and tiny .. .. And usually comes 3 by 3
Suncluster AFAIK (but I may be wrong) don't use quorum disks .. but I had little if no experience with the beast.
Legato Autostart relies on the network .. no quorum disks (again I played very little with this beast).

Suresh,

Thanks for your response... I have managed to fetch the details of the quorum volumes on the old symm5 array using the output of the syminq comand.
My application consists of 3 clustered pairs(6 hosts) with each cluster allocated 146GB space from this symm5 array and I am required to migrate the entire setup on the new DMX, as the symm5 is going to be decommissioned shortly.
From my findings, I have observed that the first 2 pairs of clustered W2K hosts have 1.05GB quorum volumes each and the last clustered pair of hosts have a .509GB quorum volume.
I need to know whether there are any standard procedures and specifications to be considered while creating the new quorum volumes on the new DMX array or is it ok if I just create the new quorum volumes on the DMX using the same specs as that on the older symm5 arrray ??

Usually "quorum" devices are small disks where the cluster stores its stuff. I hope you have Solution Enabler on your host. Issue a "syminq" command and look for small disks. They can range from 500mb to 4gb .. however there are rules from M$. Hopefully you can ask the guy who installed the cluster. Or if you can open the "cluster manager" (I don't really remember the name of the application, however it's in "Administrative Tools") you'll easily identify the quorum disk.

are you going to migrating using SRDF or simple copy ? Since cluster relies on disk signature to identify its disk resources if you migrate using SRDF ..you are good as disk signature will remain on the DMX3 device ..if you are going to be copying data via host tools ..you will need to use cluster recovery tools to either write new signature to cluster configuration or the other way around ..write signature currently in the registry to the DMX disks.

Unfortunately, it has been decided to have a filesystem migration on the new DMX. As I understand, this would mean apart from the application space, I would have to configure 3 new quorum devices of .509 GB for each clustered pair of hosts.
As I said earlier, currently on the old symm5 array, there are 3 quorum devices, of which 2 are 1.09 GB and for one cluster it is .509GB.
I am just wondering whether there must be any specific reason for this ??
Is it ok if I just go ahead and have 3 new quorums on the DMX of .509 GB each or do I replicate the same setup as is currently on the old symm5 array ??

dynamox hit it right on the head - if you aren't migrating at the LUN level (i.e. using SRDF, Open Replicator, SAN Copy, etc.) then you will need to plan on doing some reconfiguration work within the cluster. If you do a SAN based copy then you should not need to do anything other than gracefully shutdown the cluster at the start of the migration, make sure everything is setup access wise the same, and then gracefully start your cluster nodes after the migration.

If you plan on doing a simple host based disk-to-disk copy then the simplest plan would be to simply reconfigure the whole cluster and swapping-out the quorum disk on the old array for the new similar sized drive on the new array. There is nothing special from a storage stand-point for a Windows quorum drive and technically it could be any physical size you like. The only requirement is that every node in the cluster has access to the quorum drive.

Looks like something I already said