0

What should be the ideal roll back plan for WSP (Farm) Solutions deployments? What backups should be taken? Before taking the backups what are the prerequisites that should be performed like, databases to static, stopping timer jobs etc.

1

For roll back or complete uninstall you have to do 3 things.

  1. Deactivate the features on site collections.
  2. Retract / Uninstall the Solutions. You can do it via central admin or powershell.
  3. Remove the solutions from farm. you can do it via power-shell or central admin.

    Disable-SPFeature -identity "MyCustom" -URL http://somesite

    Uninstall-SPSolution –Identity Solution.wsp –WebApplication http://webapplicatio

    Remove-SPSolution –Identity Solution.wsp

Useful link: https://msdn.microsoft.com/en-us/library/office/aa543958(v=office.14).aspx

  • What if it has to be a DR effort for failure of deploying solutions. – Achiever SP Jun 15 '17 at 17:09
  • If deployment failed, right? In that case same steps followed – Waqas Sarwar MVP Jun 15 '17 at 17:12
  • Ok, we tried to deploy new solution, be retracted, removed old solutions and tried to deploy new solutions. It failed to deploy. We tried deploying old solutions but those failed as well. Since we are approaching the downtime window, we just restored the VM backups. What could be the ideal thing to plan for such situations? What backups we should take? During the backups, does the Farm should go read only mode to make sure that no production data is lost? – Achiever SP Jun 15 '17 at 17:17
  • what the error you are facing? i think solution not retracted properly. You may need to recycle timer service, Admin service as well as reset IIS on servers. Also check from central admin if it is still displaying anything related to removed solution? – Waqas Sarwar MVP Jun 15 '17 at 18:17
  • When we deployed the solution, from central admin it shows the wsp is deployed, but when we check in the 15 hive folder, the latest files are not visible on all the servers in the farm. When we tried to access the site, we got a correlation id - which says the files were missing. Hence we tried to redeploy the old WSP`s, and the same problem occurred. So what should we do in such cases? how should be our roll back plan. – Achiever SP Jun 15 '17 at 19:25
1

For a WSP rollback, you would simply disable the Features deployed by the WSP (be they farm, Web App, Site, or Web), then retract the WSP. You don't need to do anything with databases nor timer jobs.

  • Ok, we tried to deploy new solution, be retracted, removed old solutions and tried to deploy new solutions. It failed to deploy. We tried deploying old solutions but those failed as well. Since we are approaching the downtime window, we just restored the VM backups. What could be the ideal thing to plan for such situations? What backups we should take? During the backups, does the Farm should go read only mode to make sure that no production data is lost? – Achiever SP Jun 15 '17 at 17:25
  • You need to look at your solutions; perhaps there is an issue with the retraction. Perhaps you need to recycle the timer service (e.g. you're implementing a timer job), etc. Also, online VM backups for SharePoint are not supported. – Trevor Seward Jun 15 '17 at 17:26
  • When we deployed the solution, from central admin it shows the wsp is deployed, but when we check in the 15 hive folder, the latest files are not visible on all the servers in the farm. When we tried to access the site, we got a correlation id - which says the files were missing. Hence we tried to redeploy the old WSP`s, and the same problem occurred. So what should we do in such cases? how should be our roll back plan. – Achiever SP Jun 15 '17 at 19:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.