Defining your storage management process

Defining your storage management process

Are there any 'process and procedure' templates in place for those companies that do not have a dedicated Storage Dept? We will be sharing a new SAN across Unix, NT/Wintel and eventually Novell. How do we divide up responsibilites and create a policy?

    Requires Free Membership to View

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

One could write a book on this issue. The short answer is that there is no real template you can use -- it varies based on each site. The way I have seen other enterprises handle this is by assigning responsibility for the SAN to a specific OS/System administrator group (either UNIX or Windows). Generally, server connectivity and volume management might be handled by specific OS administrators, and the administrative group in charge of the SAN handles SAN operations from the HBAs through the storage arrays themselves.


Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .bphAaR2qhqA^0@/searchstorage>discussion forums.


This was first published in October 2003