VanDyke Software Forums

Go Back   VanDyke Software Forums > File Transfer
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
Thread Tools Display Modes
  #1  
Old 08-27-2009, 04:34 PM
pulberg pulberg is offline
Registered User
 
Join Date: Aug 2009
Posts: 2
Vshell cluster?

Are all setups of vshell isolated instances or is there a clustering mechanism of some kind? (MS cluster svcs, load balanced with an F5, etc)

TIA,

Phillip
Reply With Quote
  #2  
Old 08-28-2009, 06:41 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,307
Hi Phillip,

To ensure that I understand your question, are you looking to install VShell within a clustered environment?

If not, would you be able to provide more details regarding your goal?

With this information I should be able to answer your questions.
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
  #3  
Old 08-28-2009, 09:23 AM
pulberg pulberg is offline
Registered User
 
Join Date: Aug 2009
Posts: 2
I would like to know if I can achieve failover via implementing vshell in a clustered environment or if vshell contains it's own clustering mechanism.
Reply With Quote
  #4  
Old 08-28-2009, 10:42 AM
rtb rtb is offline
VanDyke Technical Support
 
Join Date: Aug 2008
Posts: 4,307
Hi Phillip,

Currently, VShell is not cluster aware.

I have added this forum thread #3798 to a feature request in our VShell development database to release a cluster aware version of VShell.

Should a cluster aware version of VShell be released, we will post to this forum thread.

If you would like to be notified directly, please send an email to support@vandyke.com with a subject of "Feature Request in Forum Thread #3798".

In the meantime, although VShell has not been officially tested in a cluster environment and is not cluster-aware, we have received reports from customers who have VShell successfully installed and running within a cluster environment.

A VShell license will need to be purchased for each node within a cluster environment as explained in section 4 of the VShell license agreement ("MULTI-SERVER LICENSES").

There are several factors to be considered in regards to the installation of VShell within a cluster configuration:
  • Installation footprint
  • Location of the Host key files
  • Location of the PublicKey folder
  • Log file location
When using VShell on a cluster, it must be installed on each node. The installation directory can be located either on the local hard drive of the individual nodes, or in a shared location. In order for the cluster to be transparent to the end user, the following items must be common to each node:
  • Hostkey and Hostkey.pub files
  • PublicKey folder
  • SFTP virtual directory structure and files
  • User accounts
  • IP Address (usually inherent with the cluster config)
If you install VShell onto each node's local drive, you may want to create directories on the shared drive that will hold the Hostkey and Hostkey.pub files, as well as a common PublicKey folder. All of the nodes should have an identical configuration.

If you choose to install VShell onto a shared drive, you will be able to use the same directory as the installation point for all of the nodes. By default, VShell uses the installation directory as the base location for the Hostkey and Hostkey.pub files as well as the PublicKey folder. If you install VShell on a shared drive, it would be beneficial to configure each VShell node to store its log information in a separate directory, or on each node's local drive (e.g., C:\VShell\logs). This will prevent multiple VShell instances attempting to write to the same log file. By using the same drive letter mappings for the log files on the individual nodes, you will be able to replicate the VShell server registry key without having to modify each node's configuration to re-point to the proper logging location after a replicating.

Any changes made to a VShell configuration on one cluster node will need to be replicated to all remaining nodes.

VShell 3.0 and later versions provide an enhanced configuration export/import tool called "vshellconfig" that can be used to simplify the export/import process among nodes within a cluster. For example, on a "master" node within the cluster, the VShell configuration from the registry and related files such as Hostkey and Hostkey.pub can be exported to an XML file with the following command:
vshellconfig export VShellConfig.xml
Once the VShell configuration from the "master" node has been exported to an XML file, you should be able to copy the configuration to each remaining node within the cluster. Assuming VShell has already been installed on the remaining nodes and the .xml file has been copied to the target node, the following command can be used to import the configuration that was exported from the master node:
vshellconfig import VShellConfig.xml
__________________
--Todd

VanDyke Software
Technical Support
support@vandyke.com
505-332-5730
Reply With Quote
  #5  
Old 02-21-2017, 12:49 PM
andrewbaker andrewbaker is offline
Registered User
 
Join Date: Feb 2017
Posts: 2
Quote:
Originally Posted by rtb View Post
Hi Phillip,

Currently, VShell is not cluster aware.

I have added this forum thread #3798 to a feature request in our VShell development database to release a cluster aware version of VShell.

Should a cluster aware version of VShell be released, we will post to this forum thread.

If you would like to be notified directly, please send an email to support@vandyke.com with a subject of "Feature Request in Forum Thread #3798".

In the meantime, although VShell has not been officially tested in a cluster environment and is not cluster-aware, we have received reports from customers who have VShell successfully installed and running within a cluster environment.

A VShell license will need to be purchased for each node within a cluster environment as explained in section 4 of the VShell license agreement ("MULTI-SERVER LICENSES").

There are several factors to be considered in regards to the installation of VShell within a cluster configuration:
  • Installation footprint
  • Location of the Host key files
  • Location of the PublicKey folder
  • Log file location
When using VShell on a cluster, it must be installed on each node. The installation directory can be located either on the local hard drive of the individual nodes, or in a shared location. In order for the cluster to be transparent to the end user, the following items must be common to each node:
  • Hostkey and Hostkey.pub files
  • PublicKey folder
  • SFTP virtual directory structure and files
  • User accounts
  • IP Address (usually inherent with the cluster config)
If you install VShell onto each node's local drive, you may want to create directories on the shared drive that will hold the Hostkey and Hostkey.pub files, as well as a common PublicKey folder. All of the nodes should have an identical configuration.

If you choose to install VShell onto a shared drive, you will be able to use the same directory as the installation point for all of the nodes. By default, VShell uses the installation directory as the base location for the Hostkey and Hostkey.pub files as well as the PublicKey folder. If you install VShell on a shared drive, it would be beneficial to configure each VShell node to store its log information in a separate directory, or on each node's local drive (e.g., C:\VShell\logs). This will prevent multiple VShell instances attempting to write to the same log file. By using the same drive letter mappings for the log files on the individual nodes, you will be able to replicate the VShell server registry key without having to modify each node's configuration to re-point to the proper logging location after a replicating.

Any changes made to a VShell configuration on one cluster node will need to be replicated to all remaining nodes.

VShell 3.0 and later versions provide an enhanced configuration export/import tool called "vshellconfig" that can be used to simplify the export/import process among nodes within a cluster. For example, on a "master" node within the cluster, the VShell configuration from the registry and related files such as Hostkey and Hostkey.pub can be exported to an XML file with the following command:
vshellconfig export VShellConfig.xml
Once the VShell configuration from the "master" node has been exported to an XML file, you should be able to copy the configuration to each remaining node within the cluster. Assuming VShell has already been installed on the remaining nodes and the .xml file has been copied to the target node, the following command can be used to import the configuration that was exported from the master node:
vshellconfig import VShellConfig.xml
Resurrecting a really old thread - any chance VShell is now cluster aware?
Reply With Quote
  #6  
Old 02-21-2017, 01:36 PM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 3,004
Hi andrewbaker,

Sorry, no, VShell is still not cluster aware. However, what differs from the prior post is that it has been tested in a Server 2008 Failover Cluster environment and we have a document we can share if you would like to receive it. I have +1'ed the feature request to release a cluster aware version of VShell.

For direct notification about the status of that feature request should it change or if you would like to receive the Failover Cluster document, please send email to support@vandyke.com and reference "Feature Request - Forum Thread #3798" or "Failover Cluster document request - Forum Thread #3798" in the subject line.
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
  #7  
Old 02-21-2017, 01:58 PM
andrewbaker andrewbaker is offline
Registered User
 
Join Date: Feb 2017
Posts: 2
Appreciate the quick response Brenda! I'll email support.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:48 PM.


copyright 1995-2017 VanDyke Software, Inc.