Currently, my company is using DFS and robocopy to deploy web applications from a DFS server to production servers. That has been working fine. However, there are times where we'd need to roll back a release due to critical issues, and the way it's been done is to copy the previous release version back to the same location on the DFS server and push it to production servers again (using robocopy basically). This way has several issues, yet I do not personally think it's a good roll-back methodology.
Does anyone know of a better or right methodology to roll back releases regarding MS DFS and Robocopy? Thank you very much in advance for your information.
Regards,
~James