Getting installation right for storage management

Symantec product slightly easier to get up and running than HP SRM wares.

To measure the products' overall ease of installation, we installed both in Windows and Linux/Unix environments. Ironically, both products we tested are simpler to install on Linux/Unix than on Windows servers. With Windows install, both have requirements like installing Windows Server options such as SNMP, using a static IP addresses, manually creating special accounts, physically changing starting parameters of installed services or granting exotic rights (software restriction policies, for example).

Installation of the Storage Essentials suite requires a fair amount of planning - for instance, if you don't support fully qualified domain names for internal servers, which is common for organizations that use network address translation schemes and only expose a few systems directly to the Internet, you'll need to reconfigure your DNS server to support fully qualified host names for internal hosts. This can be avoided, but only by using HTTP rather than Secure-HTTP for the management application.

You'll also need to install optional Windows components including SNMP Trap Service and Microsoft Data Access Component v 2.7, disable the Internet Information Server service if installed, and get the included Oracle software installed, updated and patched before you begin with the software install. If you want to use the deployment tool for agents, you'll need to install Secure Shell and ensure that permissions for the Storage Essentials service account are such that you can remotely install software on the target systems.

Once you get the database and Storage Essentials and SIM software installed, you'll need to install a connector piece that joins the two pieces, which only accepts a fully qualified domain name (not a Windows hostname or IP address) to find the SIM server - even if it's on the same system as the Storage Essentials server. You'll also need to import a license file, and install agents on any servers that you want to manage.

Symantec's Veritas Command Central Storage is more monolithic than the HP application. There is a single software install rather than three or four, although there are still a number of prerequisites that need to be dealt with before the install. These include setting a local security policy if you're using Windows 2003, making sure that the Veritas Authentication Service is working properly, and ensuring fully qualified domain names for local host resolve properly (which can also be accomplished by editing the \windows\system32\etc\drivers\hosts file, which doesn't work for the HP product). You'll also need to enter license information, or leave the field blank for a 60-day evaluation license.


Return to main test story

Learn more about this topic

TK

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.
Related:

Copyright © 2006 IDG Communications, Inc.

SD-WAN buyers guide: Key questions to ask vendors (and yourself)