DataCore Hyperconverged Infrastructure

Explore this Page

Overview

This section explains how to deploy and configure DataCore SANsymphony in hyperconverged setups. It includes supported deployment options, key configuration notes, service dependency settings for startup/shutdown, and best practices for integrating with Hyper-V or ESXi environments.

Deployment Options for Hyperconverged Infrastructure Configurations

Option 1:

SANsymphony software is installed directly on a Windows Server-based host which is running an application or Hyper-V

The host (also known as Hyperconverged Infrastructure (HCI) node) is added to the server group as a DataCore Server. The HCI node creates one or more disk pools and adds local disks. The HCI node can create highly-available mirrored virtual disks using the local pool as the primary storage source and a pool from another DataCore Server as the secondary storage source. Mirrored virtual disks are then directly served to the HCI node to use as storage resources for applications running on that host. The best practice for automating this process, refer to the DataCore Deployment Wizard.

Option 2:

SANsymphony is installed on one or more Windows Server-based virtual machines that are running on Hyper-V, an ESXi host or other non-Windows-based hypervisors

In this case, the virtual machine also known as the HCI node) is added to the server group as a DataCore Server. The ESXi host or Hyper-V host must be registered as a host in the server group.

The HCI node creates one or more disk pools and adds local disks made available through physical hard disks (Hyper-V) or Raw Device Mappings (ESXi or non-Windows-based hypervisors) from the local host. The HCI node can create mirrored virtual disks using the local pool as the primary storage source and a pool from another DataCore Server as the secondary storage source. Mirrored virtual disks are then served to the hypervisor host or other registered hosts.

The best practice for automating this process, refer to the DataCore Installation Manager for vSphere and DataCore Installation Manager for Hyper-V

Generally, each HCI node contributes its locally-attached storage to pools in the server group. All uninitialized block storage devices attached to the HCI node can be used as storage resources for pools. Multiple disk pools can be created on a single HCI node. Their storage resources can be combined with other HCI nodes, integrated into a central DataCore SANsymphony SAN, or Cloud storage. Internal storage resources may be shared in a highly-available configuration with multiple HCI nodes or across a cluster of servers. A DataCore SANsymphony SAN can consist of from one to 64 HCI nodes. The HCI node does not need to be configured to contribute storage, but instead can be configured to host applications that access storage directly from the pools.

This graphic shows a deployment of DataCore SANsymphony software into multiple virtual machines on each ESXi host of a VMware cluster.

Each HCI node must be properly licensed according to the Capacity license activated on the node.

Configuration and Operational Notes for DataCore SANsymphony as a Hyperconverged Infrastructure Node

Some steps may have been performed by the Automated Installation and Upgrade Wizard during software installation, in which case skip those steps. Those steps depend on the template selected during installation.

Most configuration and operations performed for Hyperconverged Infrastructure (HCI) nodes are the same as that for any standard DataCore Server. However, some special notes apply when performing configuration or operations from an HCI node, as noted below. (Refer to the associated Help topics below for more information and instructions.)

Once configured, the HCI node can perform operations and management activities in the same manner as any standard DataCore Server in the server group.

Special Configuration Notes:

  • Refer to the SANsymphony Best Practices Guide for important configuration information.

    The guide can be found on the DataCore Technical Support Portal in FAQ 838 (All Best Practices Guidelines). Also see these other applicable FAQs on the DataCore Technical Support Portal for running the software on virtual machines: FAQ 1155 (Best Practices-Installing a DataCore Server within a Virtual Machine), FAQ 1348 (Best Practice Guideline for DataCore SANsymphony), and FAQ 1626 (iSCSI Best Practices, Network Settings for DataCore SANsymphony in a VM). (These FAQs can be viewed by registered customers with a login to the DataCore Technical Support Portal.)

  • Add DataCore Server operation: When adding the HCI node as a DataCore Server to an existing server group, the Add DataCore Server operation must be performed from one of the DataCore Servers in the existing server group, not from the HCI node. See Establishing Server Groups.
  • Port roles assignments: Port roles should be configured to provide dedicated network ports for use with the software. Remove port roles for all other ports not dedicated to running the software in order to prohibit access. See Assigning Port Roles and Groups.
  • System startup and shutdown: The software runs as a system service called DataCore Executive (Dcsx); only when the service is started can the virtual disk be accessed. Properly configuring service dependencies is essential to ensure the proper start and/or stop order of the software and application services. See Configuring Service Dependencies for Proper System Startup and Shutdown for instructions. (Also see Removing the DCSX Service Dependency in a System Startup to remove the DCSX service as a dependency.)

Important Operational Notes:

  • Creating virtual disks: When creating mirrored virtual disks, use a local disk pool of the HCI node as the primary storage source (top selection) and a pool from another DataCore Server in the server group as the secondary storage source. See Creating Virtual Disks.
  • Serving virtual disks: When serving virtual disks, allow the front-end paths to be auto-selected, which is the default setting. See Serving Virtual Disks.
  • Discovering served virtual disks: Virtual disks can be discovered and prepared for use in the same manner as any physical disk.

    The software will protect devices that are being managed, as well as internal devices that were created when virtual disks are served back to the server that created it. Those protected devices will appear in Disk Manager as Not Initialized. Attempting to initialize those protected devices will result in an error message "The device is not ready." This is normal behavior.

Configuring Service Dependencies for Proper System Startup and Shutdown

The DataCore SANsymphony software runs as a system service called DataCore Executive (Dcsx); only when this service is started can virtual disks be accessed. The proper start and/or stop order of DataCore SANsymphony software and application services is essential, in particular during startup or shutdown of the Windows operating system.

  • On startup, an application may start incorrectly or fail if the disk resources used by the application are not available. Ensure that DataCore SANsymphony software is running before the application starts by configuring service dependencies. See Ensure Successful Startup.
  • On shutdown, an application may shutdown incorrectly or lose data if the disk resources used by the application become unavailable before the application has properly stopped. Ensure that the DataCore SANsymphony software keeps running until the application has stopped. See Ensure Proper Shutdown.

Ensure Successful Startup

The following instructions are an example of how to configure service dependencies. In this example we use Microsoft Hyper-V Server to illustrate how to set the service dependencies correctly. Depending on your specific SANsymphony Hyperconverged Infrastructure (HCI) configuration, different and/or additional configuration steps may be necessary to achieve the same result.

In this example, we will make the Hyper-V Virtual Machine Management service dependent on the DataCore SANsymphony service, so that the Hyper-V service will only start if the service is already running. The service name for the software is DataCore Executive (DCSX).

  1. On the HCI node, find the service name of the application. The service name is typically found in the Properties dialog box of the service in Computer Management > Services. The service name of the Hyper-V service is VMMS.

  2. Open a command window and query the current service configuration by entering this command:SC QC VMMS

    Make a note of the services listed in the DEPENDENCIES section. In this case, the current service dependencies are: RPCSS and WINMGMT. Ensure proper spelling.

  3. The service name for the software is DataCore Executive (DCSX). In order to extend the list of service dependencies to include DCSX, enter:

    SC CONFIG VMMS DEPEND=RPCSS/WINMGMT/DCSX

    The following success message should be displayed:

    [SC] ChangeServiceConfig SUCCESS

  4. To confirm that DCSX was correctly added, enter the command SC QC VMMS again. The list of dependencies should have the original dependencies, as well as DCSX.

Ensure Proper Shutdown

During system shutdown, by default, the Service Control Manager does not take service dependencies into consideration. As a result, DataCore SANsymphony software may be stopped after a shutdown or restart has been initiated and before dependent applications.

In order to prevent potential problems or data loss, an HCI node running the software should not be shut down or restarted without taking pre-emptive steps.

All applications must be stopped on the HCI node before initiating a restart or shutdown. Dependent services should be stopped before stopping the DataCore Executive service. Provided that the service dependencies have been set up correctly, this can be done by stopping the DataCore Executive service. Initiating a Stop command to the DataCore Executive service will first stop any dependent services before the DataCore SANsymphony software is stopped.

Stopping the DataCore Executive service can be done either from Computer Management>Services or from the command prompt. Instructions are provided for both methods.

To stop the service from Computer Management>Services:

  1. Right-click on DataCore Executive and select Stop from the context menu.
  2. Confirm the Stop Other Services message in order to proceed with stopping DataCore SANsymphony software as well as dependent applications.

  3. After the DataCore Executive service has successfully stopped, the HCI node can be safely shut down or restarted.

To stop the service from a command prompt:

  1. Enter NET STOP DCSX. A message will appear that the dependent services will also stop. Confirm to continue by entering Y.

  2. After the DataCore Executive service has successfully stopped, the HCI node can be safely shut down or restarted.

Removing the DCSX Service Dependency in a System Startup

Under certain circumstances, it may be necessary to remove the DCSX service dependency in a system startup.

In the following example, the DCSX service is removed by reconfiguring the existing dependencies without DCSX; therefore, the Hyper-V service will start without the DCSX service. Depending on your specific SANsymphony HCI configuration, different and/or additional configuration steps may be necessary to achieve the same result.

  1. Open a command window. The currently configured service dependencies for the Hyper-V service can be queried by entering this command:

    SC QC VMMS

    The services are listed in the DEPENDENCIES section.

  2. In this case, the DCSX service is omitted and the other dependencies RPCSS and WINMGMT are reconfigured.

    SC CONFIG VMMS DEPEND=RPCSS/WINMGMT

Learn More