File Director appliance clustering

Version 5

    Verified Product Versions

    AppSense DataNow 3.6AppSense DataNow 3.5AppSense DataNow 3.0AppSense DataNow 4.0AppSense DataNow 4.1AppSense DataNow 4.2AppSense File Director 4.3

    Introduction

    Describing the configuration and further information around File Director Appliance clustering

    Detail

    There are a number of items which need to configured before clustering can be enabled.

    A blank Microsoft SQL database must be created for the cluster. The SQL instance hosting the database must support SQL authentication. You will require an SQL logon that has dbo access to the new database. It is recommended that a highly available SQL solution is used, such as SQL always-on availability groups (be aware that File Director does not support multi-subnet failover)

    Please ensure any new nodes being added to a cluster are first licensed and patched (This limitation will be addressed in a subsequent release)

    All appliances that you wish to cluster should be located on the same network. Multicast (V3.x) / Broadcast (V4.x) traffic between the appliances should not be blocked.

    When pointing the configuration to the SQL database, the local appliance configuration is not automatically seeded to the database. A backup of the config prior to configuring the shared database setting should be taken if you wish to retain the settings already configured on your appliance (this will need to be restored into the admin console once the config has been switched to use the SQL database).

    To enable clustering on the first appliance:

     

    1. Logon to your hypervisor and connect to your File Director appliance Console
    2. Logon to the Appliance and select cluster configuration and hit returnSelect a name for this new cluster (You will need this later when adding additional appliances)
    3. Press F10 to save the configuration
    4. Log out of the appliance console
    5. Logon to the Web Admin console for this File Director appliance
    6. Navigate to Configuration –>Database and click Edit
    7. Change the Database Type to “Microsoft SQL Server” and populate the fields as follows:
      • Host: DNS name or IP address of your SQL server
      • Instance Name: This should be left blank for the default instance, or populated with the instance name
      • Database Port: Leave the Database port as default, unless you have changed this on your SQL server
      • Database User: The user name for the SQL logon that was configured on the SQL server earlier
      • Database Password: Populate the password for your database user
    8. Click Save
    9. *Optionally at this point, if you wish to restore an appliance backup, you should do so now

    You have now successfully created the first node in the cluster. The process for adding additional nodes to a cluster is very similar to the initial configuration:

    1. From the hypervisor, connect to the appliance console for the appliance which you wish to add to the cluster
    2. Once logged in, select cluster configuration and hit return
    3. Type the cluster name which you specified for your initial node
    4. Press F10 to save the configuration
    5. Log out

    Logging back on to the Web Admin console for this appliance, you will see that the changes have all populated from the initial node.

    If you are using a load balance to direct traffic between your cluster nodes. You should configure it monitor the status page:

    http://[appliance ip]:8001/status

     

    NOTE: It is possible to see real-time events relating to the cluster; when logged on to the appliance console for any of the cluster nodes, press alt + F2 (alt+F3 in 4.3+).

     

    Please be aware of the following KB if adding clustering to an existing configuration, or adding a preconfigured node to an existing cluster

    DataNow clustered fields not propagating

    If troubleshooting clustering, please refer to the acs.log in the appliance diagnostic bundle for debug output