We have a situation where users are allowed to upload content, and then separately make some changes, then submit a form based on those changes.
我们的情况是允许用户上传内容,然后单独进行一些更改,然后根据这些更改提交表单。
This works fine in a single-server, non-failover environment, however we would like some sort of solution for sharing the files between servers that supports failover.
这在单服务器,非故障转移环境中工作正常,但我们希望某种解决方案在支持故障转移的服务器之间共享文件。
Has anyone run into this in the past? And what kind of solutions were you able to develop? Obviously persisting to the database is one option, but we'd prefer to avoid that.
过去有没有人碰到这个?你能开发出什么样的解决方案?显然坚持使用数据库是一种选择,但我们宁愿避免这种情况。
4 个解决方案
#1
1
At a former job we had a cluster of web servers with an F5 load balancer in front of them. We had a very similar problem in that our applications allowed users to upload content which might include photo's and such. These were legacy applications and we did not want to edit them to use a database and a SAN solution was too expensive for our situation.
在以前的工作中,我们有一组Web服务器,前面有一个F5负载均衡器。我们遇到了一个非常类似的问题,我们的应用程序允许用户上传可能包含照片等的内容。这些是遗留应用程序,我们不想编辑它们以使用数据库,而SAN解决方案对我们的情况来说太昂贵了。
We ended up using a file replication service on the two clustered servers. This ran as a service on both machines using an account that had network access to paths on the opposite server. When a file was uploaded, this backend service sync'd the data in the file system folders making it available to be served from either web server.
我们最终在两个群集服务器上使用文件复制服务。这在两台计算机上使用一个帐户运行,该帐户具有对相对服务器上的路径的网络访问权限。上传文件后,此后端服务会同步文件系统文件夹中的数据,使其可从任一Web服务器提供。
Two of the products we reviewed were ViceVersa and PeerSync. I think we ended up using PeerSync.
我们审查的两个产品是ViceVersa和PeerSync。我想我们最终使用了PeerSync。
#2
1
In our scenario, we have a separate file server that both of our front end app servers write to, that way you either server has access to the same sets of files.
在我们的场景中,我们有一个单独的文件服务器,我们的两个前端应用服务器都写入,这样您就可以访问相同的文件集。
#3
0
The best solution for this is usually to provide the shared area on some form of SAN, which will be accessible from all servers and contain failover.
对此的最佳解决方案通常是在某种形式的SAN上提供共享区域,该区域可从所有服务器访问并包含故障转移。
This also has the benefit that you don't have to provide sticky load balancing, the upload can be handled by one server, and the edit by another.
这也有一个好处,您不必提供粘性负载平衡,上传可以由一个服务器处理,另一个服务器编辑。
#4
0
A shared SAN with failover is a great solution with a great (high) cost. Are there any similar solutions with failover at a reasonable cost? Perhaps something like DRBD for windows?
具有故障转移功能的共享SAN是一个很好的(高成本)解决方案。是否有任何类似的解决方案以合理的成本进行故障转移?或许类似于DRBD for windows?
The problem with a simple shared filesystem is the lack of redundancy (what if the fileserver goes down)?
简单的共享文件系统的问题是缺少冗余(如果文件服务器出现故障怎么办?)?
#1
1
At a former job we had a cluster of web servers with an F5 load balancer in front of them. We had a very similar problem in that our applications allowed users to upload content which might include photo's and such. These were legacy applications and we did not want to edit them to use a database and a SAN solution was too expensive for our situation.
在以前的工作中,我们有一组Web服务器,前面有一个F5负载均衡器。我们遇到了一个非常类似的问题,我们的应用程序允许用户上传可能包含照片等的内容。这些是遗留应用程序,我们不想编辑它们以使用数据库,而SAN解决方案对我们的情况来说太昂贵了。
We ended up using a file replication service on the two clustered servers. This ran as a service on both machines using an account that had network access to paths on the opposite server. When a file was uploaded, this backend service sync'd the data in the file system folders making it available to be served from either web server.
我们最终在两个群集服务器上使用文件复制服务。这在两台计算机上使用一个帐户运行,该帐户具有对相对服务器上的路径的网络访问权限。上传文件后,此后端服务会同步文件系统文件夹中的数据,使其可从任一Web服务器提供。
Two of the products we reviewed were ViceVersa and PeerSync. I think we ended up using PeerSync.
我们审查的两个产品是ViceVersa和PeerSync。我想我们最终使用了PeerSync。
#2
1
In our scenario, we have a separate file server that both of our front end app servers write to, that way you either server has access to the same sets of files.
在我们的场景中,我们有一个单独的文件服务器,我们的两个前端应用服务器都写入,这样您就可以访问相同的文件集。
#3
0
The best solution for this is usually to provide the shared area on some form of SAN, which will be accessible from all servers and contain failover.
对此的最佳解决方案通常是在某种形式的SAN上提供共享区域,该区域可从所有服务器访问并包含故障转移。
This also has the benefit that you don't have to provide sticky load balancing, the upload can be handled by one server, and the edit by another.
这也有一个好处,您不必提供粘性负载平衡,上传可以由一个服务器处理,另一个服务器编辑。
#4
0
A shared SAN with failover is a great solution with a great (high) cost. Are there any similar solutions with failover at a reasonable cost? Perhaps something like DRBD for windows?
具有故障转移功能的共享SAN是一个很好的(高成本)解决方案。是否有任何类似的解决方案以合理的成本进行故障转移?或许类似于DRBD for windows?
The problem with a simple shared filesystem is the lack of redundancy (what if the fileserver goes down)?
简单的共享文件系统的问题是缺少冗余(如果文件服务器出现故障怎么办?)?