Trex distributed installation to Centralised Storage (SAN)

[Former Member]

Hi

We are planning to install a distributed TREX system comprising master and backup instances. We need to install these to centralised storage and as stated in the TREX 7.10 multi hosts install guide:

"The data can be located on a server that is optimized for file sharing, in a storage area network (SAN), or on a network attached storage server (NAS server)."

Our SAN storage is HDS

TREX 7.10 will be installed to Windows Server 2003 EE 64 bit servers.

We are limited to two physical servers, hence the decision to configure as master and backup for High Availability.

Note 1107725 states that "TREX 6.1, TREX 7.0, and TREX 7.1 currently does not support installations based on Microsoft® Windows Clustering / Microsoft® Cluster Service (MSCS), Solaris Cluster or other Cluster environment."

If we cannot cluster the windows servers, how can we use SAN storage to present centralised storage to both Windows Servers?

Thanks

Graham

[sam_venkat]

Hi Graham, Were you able to find an answer to your issue?  Are you presenting SAN to both hosts?

[sunny_pahuja2]

Hi,

You need not to use MSCS cluster solution for TREX distributed installation. You can have all data on central storage that can be NFS mounted or on SAN that can be access by both master and slave servers. Check installation guide. Please find an extract from the guide:

Centralized Data Storage

With centralized data storage, the data is stored so that all TREX hosts can access it.

Centralized data storage can be realized with different hardware solutions: The data can be located on a server that is optimized for file sharing, in a storage area network (SAN), or on a network attached storage server (NAS server). It is important that the connection between the TREX hosts and the data is sufficiently fast. In the following documentation, a central storage location is referred to as a file server regardless of the underlying hardware.

Centralized data storage is necessary if you want indexing to be highly available. You can only move from a master index or queue server to a backup index or queue server if you are using centralized data storage. You can use standard solutions such as the RAID system to make data highly available.

Centralized data storage also has the following advantages if you are only using master and slave hosts:

● Index replication generates less of a network load because the replicated files do not have to be copied onto every slave host.

● Index replication is quicker.

● Less disk space is required for the replicated indexes because all slave hosts share an index copy.

Thanks

Sunny