I think one think to take into consideration is that the project prior to becoming a deployment unit is stored in the artifact repository which based on GIT. This can then be shared on a artifactory cluster amongst the servers hence appearing on all the participating nodes without the need to download/re-upload the project, some resources can be found here [1][2].

To share execution engine & session/log data in the cluster the engine (suite) and database needs further clustering/replication.

On the other hand you could  also import from the GIT repository the projects into eclipse (make if any necessary changes) and upload the new project to the second server as a new project of the 2nd server's repository (in the case that you are not interested in clustering)

[1] http://mswiderski.blogspot.com.br/2013/06/clustering-in-jbpm-v6.html

[2] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6/html-single/Installation_Guide/index.html#c…