Timeline for Sharepoint 2013 3-tier farm architecture to have zero down time in deployments
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 5, 2016 at 7:42 | comment | added | user25351 | Okie i will check this when our setup is ready. Also instead of opening each server and deploying from RDC is there any way to automate above steps from one server itself to deploy in all servers? | |
| Feb 4, 2016 at 11:08 | comment | added | Paul Strupeikis | I was recycling app pools in a loop on my test APP server and WFEs kept working fine. Maybe you've got something configured in a wrong way? | |
| Feb 4, 2016 at 10:32 | comment | added | user25351 | Yes here my Questions but when we follow 2-5 steps in APP server App pools are recycled in and it will not be able to serve any requests coming from WFE as it gives 503 error?? Thats what my understanding. | |
| Feb 4, 2016 at 10:11 | comment | added | Paul Strupeikis | I am pretty sure that IIS Reset doesn't affect service applications - just tested this with 2 WFEs and 1 APP server - iisreset being run in a loop on APP server while uploading documents and setting user/managed metadata fields - everything worked like a charm. You can Add/Install/Update solutions on APP server whenever you want. Keep in mind, that if you are doing Update-SPSolution you will need to install new SPFeatures manually by running Install-SPFeature (just a note). | |
| Feb 4, 2016 at 7:22 | comment | added | user25351 | Thanks for you reply Paul. So if i understand correctly even if we are just updating the solution using Update-SPSolution your steps 2- 5 should be valid? Also correct me if am wrong, when this activity is done on App server WFE will not be able to serve the request so still there will be a down time i suppose? | |
| Feb 3, 2016 at 16:16 | history | edited | Paul Strupeikis | CC BY-SA 3.0 |
added 240 characters in body
|
| Feb 3, 2016 at 16:02 | history | answered | Paul Strupeikis | CC BY-SA 3.0 |