Un dato muy importante para realizar un upgrade de SharePoint es saber el tiempo de inactividad de la intranet mientras se realiza esta actualización.
Como parte de las buenas prácticas es recomendable hacer el upgrade de sharepoint services 3.0 hacia el sp2 y luego el upgrade de sharepoint server sp2. El tiempo de inactividad de la intranet depende de la cantidad de sitecollections que se han implementado en tu intranet; para intranets con 1 solo site collection debería estar demorando alrededor de 15 minutos; en cambio para una intranet con 25 site collections el tiempo estimado es de 1 hora.
Esto debido a que el upgrade se hace a cada una de las bases de datos de cada sitecollection, al hacer el upgrade se genera un log de la actualización que nos muestra como analiza el estado de upgrade en cada base de datos de cada site collection.
[SPHierarchyManager] [DEBUG] [12/2/2009 5:45:43 PM]: -------------------- End Growing Tree --------------------
[SPManager] [INFO] [12/2/2009 5:45:43 PM]: Resetting the status of PersistedUpgradableObject: SPContentDatabase Name=WSS_Content1 Parent=SPDatabaseServiceInstance to Online.
[SPManager] [INFO] [12/2/2009 5:45:43 PM]: Finished upgrading SPContentDatabase Name=WSS_Content2 Parent=SPDatabaseServiceInstance.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content3 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content4 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content5 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content6 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content7 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content8 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_Content9 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT10 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT11 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT12 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT13 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT14 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: False.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT15 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT16 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
[SPManager] [DEBUG] [12/2/2009 5:45:43 PM]: Using cached [SPContentDatabase Name=WSS_ContenT17 Parent=SPDatabaseServiceInstance] NeedsUpgrade value: True.
Espero que esta información les ayude al momento de realizar actualizaciones en sus servidores sharepoint 2007.
Archivos de diciembre,2009
Tiempo de upgrade SharePoint SP1 hacia SP2
diciembre 02, 2009Eventos 7076, 6398, 6482 se muestran constantemente en el log del servidor SharePoint
diciembre 02, 2009
Detalles del Event Log:
Event Id: 7076
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
- A reference to the Metabase in the call stack.
Event Id: 6398
Event Source: Windows SharePoint Services 3
The Message text will contain:
- "Microsoft.Office.Server.Administration.
ApplicationServerAdministrationServiceJob"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Event Id: 6482
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
- A reference to the Metabase in the call stack.
La solución es aplicar el hotfix
946517
PlanetaPeru: buscador del Perú
Event Id: 7076
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
- A reference to the Metabase in the call stack.
Event Id: 6398
Event Source: Windows SharePoint Services 3
The Message text will contain:
- "Microsoft.Office.Server.Administration.
ApplicationServerAdministrationServiceJob"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
Event Id: 6482
Event Source: Office SharePoint Server
The Message text will contain:
- "Microsoft.Office.Server.Search.Administration.
SearchAdminSharedWebServiceInstance"
- "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
- A reference to the Metabase in the call stack.
La solución es aplicar el hotfix
946517
PlanetaPeru: buscador del Perú
