Since the release of RES HyperDrive, we’ve been contacted by lots of enthusiastic people who are using RES HyperDrive. The most questions we received were about the configuration. In this article I will describe some guidelines for configuring the RES HyperDrive appliance.
Configuration of the RES HyperDrive appliance
After starting the RES HyperDrive appliance and changing the password of the ‘root’ account, you have to setup the network configuration.
Don’t change the name of the device name! Leave this as pre-configured.
Use the FQDN of the appliance in the Hostname field.
Configure the domain name in the Search field.
If you need to edit this configuration afterwards, use the command:
system-config-network on the command line interface of the appliance.
Create a DNS record in the Forward and Reverse Lookup Zones for the RES HyperDrive virtual appliance before continuing with the VA setup. Create a Reverse Lookup Zone if none is configured in your DNS environment for the subnet in which the appliance resides.
The rest of the configuration can be done by starting the webpage: https://<hostname>/va
Connect to the local or the iSCSI storage of your environment.
Make sure you are using the FQDN of the DB server in the Hostname field.
Use an SQL account which has enough rights to create the database and SQL login (e.g. ‘sa’ account).
Use port 1433 as the standard port for SQL connection.
Make sure you are using the FQDN of the appliance in the FQDN field.
Active Directory Configuration:
Always use a domain controller which holds the Global Catalog, in the ‘AD Host’ and ‘LDAP Host’ fields.
Make sure you use the FQDN of these server(s).
The Base CN should point to the location in the Active Directory where the user accounts will reside.
Use the [Domain\username] in the ‘User’ field, otherwise the
‘The LDAP bind failed, are your credentials correct? ‘ error message could occur after clicking the Test button.
Use the FQDN of your e-mail server in the ‘SMTP Server’ field.
Use the full e-mail address in the ‘email’ fields.
RES Automation Manager:
When you don’t use RES Automation Manager in your environment, the ‘Dispatcher host’ field does not need to be configured.
The option ‘Allow users to create their own RES HyperDrive account’ is disabled by default. If disabled, user accounts can only be created by using RES Automation Manager.
Make sure that the RES HyperDrive appliance is able to connect to the Internet by using HTTPS. A proxy server cannot be used (yet), direct access to the Internet is required.
Don’t forget to click ‘get license info’. Otherwise it’s not possible to commit the configuration.
Commit your configuration and the RES HyperDrive appliance will be configured. In the browser window, the progress will be shown.
The above screen will be shown when the configuration was successful. Before closing the browser window, download the PuTTY key or OpenSSH key for the ‘hyperdrive‘ account to access the RES HyperDrive appliance remotely.
These keys will be deleted after a reboot of the appliance and can be downloaded afterwards by using the following URL’s:
If there is any error reported during the configuration of the appliance, this will be shown in the browser. Make sure to save the log file by clicking on the ‘setup log’ link. This log is needed for further troubleshooting.
Common error messages
- ‘Could not connect to Active Directory’
- ‘Error 3802: Unknown error occurred. Please try again or contact support.’
- ‘This link is not valid. Contact RES HyperDrive support if you keep having this problem.’
Re-configure the Active Directory – LDAP configuration in the RES HyperDrive Virtual Appliance. Check the configured Base CN.
Check the KB article:
‘This link is not valid’
- Create an account for the user.
- Enable the option ‘Allow users to create their own RES HyperDrive account’ in the ‘RES Automation Manager’ part of the configuration.
More information is available in the RES HyperDrive Administration Guide. This document can be accessed by using the following link: RES HyperDrive Administration Guide