hey We have a sharepoint farm in production envirornement ( 9 servers), in our portal, we have lot of lists, custom webparts, and infopath form. but no transactional applications and the farm is in a virtual environement ESX+VMWare. What are the best partices to complete a rollback when the deployement fails ? Is a farm snaphot is not supported by microsoft ? why ? Thanks.

Which version of SharePoint ? ModeratorSP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters

SharePoint 2007 SP2 on windows server 2008 R2 Thanks.

Hello Claude25, Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.

Rollback · There is really no way to rollback SharePoint updates back after a failure. · It depends on what updates you were doing. http://technet.microsoft.com/en-us/library/cc263467(office.12).aspx . You will have to rebuild. · You need to do a backup and restore of the farm’s content as well as configuration data. Please review the articles below for rollback http://technet.microsoft.com/en-us/library/ff806338.aspx#handlingfailures http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/5a1ad9e9-e734-499c-bcdc-0227499ce905 Virtual Environment · With a virtual environment, you are able to roll back from a failed upgrade, only under certain conditions. · In preparation for an upgrade, all SharePoint servers should be gracefully shut down. Once all SharePoint servers are turned off, then do the same for SQL. Once all machines are shut down, take a snapshot, that way there will be no lingering connections · The snapshots all have to be taken at the same time for all farms in the production environment including SQL if its on a different server ( SQL and SharePoint have to be at the same version/time of the snapshot.) · The easiest approach is to have SharePoint and SQL on the same server, however when a farm is as large as you have it, that is most likely not an option due to performance · When reverting you have to revert all 9 servers including SQL · I am not aware of any public documentation regarding this Review the articles below for snapshots http://technet.microsoft.com/en-us/library/ee748594.aspx http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/e5abf633-9023-4f24-a707-2680cced28e8 http://blogs.msdn.com/b/jjameson/archive/2011/03/23/virtual-machine-snapshots-and-sharepoint-development-part-2.aspx These are some sites for the best practices for SharePoint: http://technet.microsoft.com/en-us/office/sharepointserver/bb736746.aspx http://www.microsoft.com/downloads/en/details.aspx?familyid=3d1fa469-0064-4054-9c1a-a6d8c8afce2b&displaylang=en Thanks Manas

Rollback · There is really no way to rollback SharePoint updates back after a failure. · It depends on what updates you were doing. http://technet.microsoft.com/en-us/library/cc263467(office.12).aspx . You will have to rebuild. · You need to do a backup and restore of the farm’s content as well as configuration data. Please review the articles below for rollback http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/5a1ad9e9-e734-499c-bcdc-0227499ce905 Virtual Environment · With a virtual environment, you are able to roll back from a failed upgrade, only under certain conditions. · In preparation for an upgrade, all SharePoint servers should be gracefully shut down. Once all SharePoint servers are turned off, then do the same for SQL. Once all machines are shut down, take a snapshot, that way there will be no lingering connections · The snapshots all have to be taken at the same time for all farms in the production environment including SQL if its on a different server ( SQL and SharePoint have to be at the same version/time of the snapshot.) · The easiest approach is to have SharePoint and SQL on the same server, however when a farm is as large as you have it, that is most likely not an option due to performance · When reverting you have to revert all 9 servers including SQL · I am not aware of any public documentation regarding this These are some sites for the best practices for SharePoint: http://technet.microsoft.com/en-us/office/sharepointserver/bb736746.aspx Thanks Manas

Most of the links in your post, Manas-MSFT, were to articles or threads about SP 2010. One was even for WSS *2.0* which is equally way off. This is a pre-SP 2010 forum and we've already established that this is NOT a SP 2010 question, so please save the time of other moderators who need to tidy up after you by in future only posting links to MOSS 2007 (or WSS 3.0) threads/articles when replying in the pre-SP 2010 forums. Moderator pre-SP 2010 forums SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx Both also have links to extensive book lists and to (free) on-line chapters