Currently a development team is attempting to use to the steps outlined below:
"We are trying to deploy files to a Microsoft file server cluster. Only one host is the owner and has access to the disk at a time. The second server is just standing there waiting incase the other server goes down. At which time then the stand by unit will own the disk. The servers are called fs01-prod.surepayroll.com and fs02-prod.surepayroll.com. Then there is a listener that is named prodfs.surepayroll.com. It floats between the 2 servers and is only on the active node. From my laptop I can connect to \\prodfs.surepayroll.com\c$ but in the Deploy tool it fails, I am guessing it is a name mis match. Right now we deploy not to prodfs.surepayroll.com but to fs01-prod.surepayroll.com and if it is the owner it works. But then on the next phase it deploys to fs02-prod.surepayroll.com it doesnt have the disk so it fails and you need to go in after all things fail and you have to click skip. We would prefer to deploy to prodfs.surepayroll.com if possible."
The current SmbHost CI does not work with a server cluster because the checkConnections fail to be able to copy or access the need folders for running the baseline task steps.
Ideally this request would update the functionality of the current SmbHost CI to allow connections and working with server cluster shares described above. If a new CI type is needed to make this work, that is also a viable alternative.
by: Bryan G. | 8 days ago | Integrations
Comments
Our field team will approach for the additional questions.