Link to home
Start Free TrialLog in
Avatar of Lizandro Diaz
Lizandro DiazFlag for United States of America

asked on

Power Vault MD 3000

The company I work for used to have a clustered exchange server, now we have a Power Vault MD 3000 which we would like to use as a NAS regular storage where we can use \\itsIP and just use it as a simple storage, do you know if this is possible.User generated imageUser generated imageUser generated imageUser generated imageUser generated imageUser generated imageHere I'm attaching some pics of it.
Avatar of Member_2_231077
Member_2_231077

Dell MD3000 (and MD3000i) have no ability to work as fileservers, you will have to attach it to a server and use it as additional storage. Assuming the Exchange cluster is being decommissioned you can use one of those servers as a NAS head for it.
Avatar of Lizandro Diaz

ASKER

Andyalder, thanks for help, but how do I do what you say? Do you have a guide I can take a look at?
Assuming you still have the old Exchange servers then either leave the HBA in it that's currently connected to the MD3000 or move the HBA to another server. Create a logical drive on it (or erase the old Exchange one) and then put your data on it and create shares on the server.

Do you have the IP address of the MD3000? You'll need that to manage it, without it you won't know when disks fail.
We removed everything off the server rack, so we have to do this from scratch. Any idea where I can get kinda step by step process?
User generated image
This is how it used to be, any ideas about cabling?
ASKER CERTIFIED SOLUTION
Avatar of Member_2_231077
Member_2_231077

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
OK, I will figure out how this is done with the information you have given me.
One more thing, once this is done, how do I access the storage \\IPadd or how's that done?
Once you have attached a server to it you just access the shares same as if they were on local disks, e.g \\servername\sharename. The MD3000 appears to the server as a large SAS disk, just like those inside the server itself.
Got it, will try to get it done.
andyalder

I'm stuck here, wondering what to do next. User generated imageUser generated image
MDSM looks good, you need to add support for MD3000 under windows MPIO. Then assuming you are using one of the original HBAs it should see one new big disk.

There's no need to change the management network properties, you already have access to MDSM.
How do I do this?
"MDSM looks good, you need to add support for MD3000 under windows MPIO. "
On the MPIO properties page select MD3000 and click add.
User generated image
Where do I get that info?
Oh, hang on. You don't need to add support for the MD3000, it's already in the list. If it's cabled up via SAS you should see it in disk administrator.

There's a windows (and linux) post configuration guide at http://ftp.respmech.com/pub/MD3000/en/MD3000_Install_Guide/postinst.htm#wp999119 for configuring MPIO but first you should see it (twice) in disk administrator.
Yes, it is " If it's cabled up via SAS you should see it in disk administrator."

For some reason I can't see it. User generated image
What could I been doing wrong?
Check the host to virtual disk mappings link in MDSM to make sure your host is listed (it should already be there because you are re-using one of the original SAS HBAs.
Not sure if this matters, but we put the HBA on an IBM server.
Finally I was able to figure this out with all the hints you provided me.

User generated image
User generated image
Thanks for your guidance andyalder. Really appreciate it.
I picked this as a solution since there are multiple inputs on the MD3000 seems like it has to be specific to use In0 for it to work, even though this doesn't show how it is done or the full solution, this tip lead me to work on other things.