Pre-Install Steps

To ensure a smooth installation, please take a few moments to ready the systems that will be included in the SAN. This includes reviewing the release notes, ensuring the necessary required software is installed and current, and that you have your user accounts, passwords, and storage server licenses in order.

Before beginning the installation:

  • Physically connect one or two (for High Availability) storage servers to a network and ensure they are accessible. All network adapter cards, HBAs, hubs, or switches should be in place and operational.

  • Physically connect any storage devices to be managed directly to the storage server or via hub or switch.

  • Ensure your application servers are ready to become members of the SAN:

    • It is very important to refer to our Technical Support Web site (http://www.datacore.com/index_frame.asp?frame_subnav_content=7) for detailed FAQs about special configuration instructions pertaining to the specific operating system and your high availability products. Perform any configuration necessary for the specific operating system and the software installed.

    • Perform any upgrades or install any service packs to application server operating system software.

    • Physically configure Fibre Channel and iSCSI connections to storage servers.

    • If using iSCSI, install iSCSI Initiator software on application servers. (If using Microsoft iSCSI Initiator software, during installation do not enable the Microsoft MPIO Multipathing Support for iSCSI option— even if intending to use MPIO.)

    • Install optional application server software (such as DataCore MPIO, DataCore VSS, AIM Client) on application servers and install any software updates.

    • If using High Availability (HA), install Multipath Drivers on application servers  that will require HA access to mirrored disk resources being provided by the storage servers. Multipath drives can be either DataCore or other high availability drivers (e.g., DataCore AP, DataCore MPIO,  or Veritas DMP). Install them using recommended procedures. See the DataCore SANmelody Technical Support Web site (http://datacore.com/index_frame.asp?frame_subnav_content=7) for qualified DataCore products and Application Server High Availability Products.  

  • Read the Release Notes provided with our software for important information.

  • Verify that your storage servers meet the system requirements as defined on our Web site (http://www.datacore.com/products/prod_SANmel_prerequisites.asp). Microsoft .NET Framework 3.5 must be installed on the storage servers or the installation will terminate. (This software can be downloaded from Microsoft Download Center: http://www.microsoft.com/downloads/.) Ensure that the appropriate Microsoft Windows 2008 service packs are installed on storage servers.

  • Refer to the Windows Security Settings Disclosure topic for a disclosure of the changes to security-related settings which will be made to the Windows operating system during the installation of SANmelody software.

  • Choose the computer name of the storage server carefully. See Warnings below.

  • Create a local user account to be used exclusively for SANmelody software. This account should be assigned with Administrator privileges and allow the setting of Log On as Service privilege. This account will be used with the Domain Communication Service (DcsSDS). If your configuration will consist of two storage servers, both storage servers must use the same account name and password.

  • If you have purchased a DataCore Support Plan, please fill out the Support Registration form on the Technical Support Web site (http://www.datacore.com/index_frame.asp?frame_subnav_content=2). Your license number is required to submit the form. After submitting this form, you will receive a logon and password to access the SANmelody Technical Support database and other important product information, and will be able to download any software updates for this product.   

  • Review Licensing Information and ensure you have a valid license file. Copy the appropriate license file to the storage servers or make sure that it is accessible via a network. These files are unique to each server. Configurations are governed by license parameters.

  • If using iSCSI:

    • For Windows Server 2008, Microsoft iSCSI Initiator is included with the operating system and does not need to be installed, but the Microsoft iSCSI Initiator Service must be started in order to mirror over iSCSI because storage servers will act as both initiator and target.
      (The service can be started from Windows Services. When you start the service, you will receive a message to unblock the service so it can communicate through the Windows Firewall. Click Yes on the message.)

WARNING:  In Microsoft iSCSI Initiator software, do not enable the Microsoft MPIO Multipathing Support for iSCSI option— even if you intend to use MPIO.   

    • The installation and configuration of Microsoft iSNS Server software simplifies the configuration of iSCSI channels. If you are planning to use an iSNS server, physically attach the iSNS server to the SAN and install the software. Microsoft iSNS Server software can be downloaded from the Download Center on the Microsoft Web site.  
      CAUTION:  Do not use your storage server as an iSNS server.

  • If using AIM:

    • TCP/IP connections are required between the AIM source and AIM destination servers. (Only IPV4 addressing is supported.)

    • Transfer Mode Utilities can be either FTP Transfer Mode (FTP) or SMB Transfer Mode (SMB).

      • If using FTP:

        • The Windows firewall on the server must be configured to allow out-going FTP connections from the AIM source server and incoming FTP connections from the AIM destination server. (Please refer to Microsoft or Internet Information Services (IIS) Websites for more information and instructions on configuring FTP firewall settings.)

        • Add a server role for Web Server (IIS) with the FTP Publishing Service option on the AIM destination server.

      • If using SMB:

        • The AIM source server must have the ability to access a defined network share on the AIM destination server.

        • The AIM destination server must allow incoming LAN connections from the AIM source server from a user defined in the Administrators group.

      • Other configuration steps necessary will be performed after installation, as outlined in the Getting Started with AIM topic in the on-line Help.

    • The Administrator may want to set up another user account for AIM. A new account must have Administrator Privilege (with password) and Log On as Service Privilege set. AIM source and destination servers must use the same account.

  • If using two storage servers in the configuration for High Availability (HA):

    • Requires two storage servers physically connected to each other over a LAN in order to exchange configuration information and exist in a partnership.

    • Both servers must use the same logon account and password.

    • If using Fibre Channel, the servers must have one or more Fibre Channel connections (direct or indirect) between them to facilitate the mirroring of data from one server to the other.

    • If using iSCSI, the servers must have at least one NIC (for iSCSI use) that is connected either directly or indirectly to the other storage server.

WARNINGS:

  • Because a local user account cannot be created on a Domain Controller, do not install SANmelody software on a Primary Domain or Backup Domain Controller.

  • Do not install SANmelody software on a Microsoft Cluster Node.

  • Do not enable Microsoft MPIO Multipathing Support on the storage server.

  • Do not change the computer name of a storage server after SANmelody software has been installed.

  • Do not use underscores in computer names.

Pre-Installation Steps