SPCA2013 - Successful Migration to SharePoint 2013
•Transferir como PPTX, PDF•
2 gostaram•944 visualizações
Successful Migration to SharePoint 2013
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (6)
Semelhante a SPCA2013 - Successful Migration to SharePoint 2013
Semelhante a SPCA2013 - Successful Migration to SharePoint 2013 (20)
Mais de NCCOMMS
Mais de NCCOMMS (20)
Último
Último (20)
SPCA2013 - Successful Migration to SharePoint 2013
- 3. Agenda Deferring Site Collection Upgrade Site Collection Health Checks Self-Service Site Collection Upgrades Queuing Site Collection upgrades Demos Planning Preparing Executing Finishing
- 4. Design Goals for 2013 Upgrades Removal of in-place version to version upgrades Adding site collection health checks (*saves ~2/3 upgrade time) Let site collection admins control their own destiny
- 5. Deferred Site Collection Upgrade Upgrade database now, upgrade site collections later Keep existing customizations, updated ones can wait Initially let users stay with 2010 experience: • Stay with the familiar • Keep using existing customizations Gradually move users over to 2013 experience: • As training occurs (e.g. incrementally for each team) • As users decide to adopt new experience/features • As new version compatible customizations are available
- 6. Site Collection Health Checks Same or different rules may apply Give advanced notice of potential future issues
- 7. Queuing Site Collection Upgrades In web application worker process: • Maximum in process site collection upgrade limits • IIS Process parallel site collection upgrade limit In any process: Eventually every site collection will have a single queue entry once it gets upgraded
- 8. Farm Upgrade
- 9. Prepare © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 10. Detach and Re-attach Databases © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 11. Powershell Command © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 12. Recap Upgrade Stages © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 13. Migration DEMO
- 14. Migration with Third Party Tools • SharePoint Administrator installs the new version on separate hardware or a separate farm, and migrates content and users using 3rd Party Tool Best For • • • Any size environment, from single server farms to large, distributed farms Restructuring content Preservation of any metadata or security Pros • Direct migration from 2007 to 2013 • Pre-scan to determine customisations • Granular migration • Virtually no downtime • Applicable to nonSharePoint repositories • Options for 24 x 7 Support? Cons • Costs associated with purchasing of additional software
- 15. DEMO DocAve Pre-Scan Tool
- 16. Summary of Farm Upgrade • • • • Search Administration database Profile, Social, and Sync databases Managed Metadata/Taxonomy database Secure Store database i. Remember to have Secure Store passphrase or you will lose all existing passwords • Project Server databases i. Remember to merge the four 2010 Project databases before attempting upgrade • Service Application upgrade i. http://technet.microsoft.com/en-us/library/jj839719.aspx • Site collection upgrade automatically deferred
- 18. Additional Resources White Papers Solution Briefs www.avepoint.com
- 19. AvePoint Corporate Overview Global Leader – SharePoint Governance & Management • • Founded and Debuted in 2001 World's Largest SharePoint-Exclusive Research & Development Team with 1,500 Employees (800+ in R&D) • • World's Largest Provider of Enterprise-Class Governance and Infrastructure Management Solutions 25 Offices, 13 Countries in 5 Continents & 8000+ Customers • • • Depth-Managed, Microsoft Certified Partner Comprehensive SharePoint Governance & Management Platform Offering True 24 x 7 Support - Microsoft Certified Technicians Specialized Experienced Invested © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 20. © 2011 AvePoint, Inc. All rights reserved. No part of this may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written consent of AvePoint, Inc.
- 21. Resources - www.AvePoint.com Visit us: http://www.AvePoint.com Email us: sales@avepoint.com Follow us: @AvePoint_Inc / @sharepointuk References http://blogs.dotnet-france.com/laurentv/post/Installation-de-SharePoint-foundation-2013-RTM.aspx Sean Livingston SPC2012 conference http://technet.microsoft.com/en-us/sharepoint/fp142375.aspx 21
- 22. Questions?
Notas do Editor
- This is a brief presentation on our vision for Collaboration incorporating Cloud as a platform.
- When Microsoft went into the Product development phase for SharePoint 2013, they realised that there were a few key things standing out for people. One of the big ones is that Customers want the upgrades to be safer. Customers also want reduced outages, they complain that the upgrades are too long, I have this big outage and impact my organisation. And then of course Microsoft came up with something a little innovative and they were doing this partially to bring back something that they took away in 2010 which was the gradual upgrade and also to address some of the scale and scheduling aspects. So first on safer upgrades, in all the previous releases Microsoft allowed you to do an in place upgrade. This was possible in all previous releases until now, it's now gone. They got rid of this mainly from the aspect of safety. A large amount of customers which had issues in previous versions were mainly due to in place upgrades. They would get half way through and then encounter issues, and then perhaps went via the database attach approach. They've given you the ability to do a preview of the site collection. It's been made a little bit more obvious in this release. As for outages one of the things they realised is that if we could reduce how much we have to upgrade when we do a version to version upgrade we can cut away 2 thirds of the upgrade time. And of course the last part is giving power to the people and giving them control which is the heart of the differed upgrade option.
- Lets go deeper into the site collection upgrade. When you did 2007 to 2010, your sites could keep your sites in the legacy 2007 UI mode, the problem you had is that you had in fact upgraded your site collections, all that happened is that the master pages were not switched around. The benefit of the deferred upgrade is that you leave the timelines to the hands of the users. For example, after they have been trained on how to use 2013. This gives lots more control and a self-service type migration. And perhaps stops users from lighting up your phone if you had done a weekend farm-wide upgrade.
- One of the things that Microsoft recognised is that if you give people the ability to perform self service upgrade without giving them some sort of safety control, there needs to be something in place that will detect those sites that are going to fail. This feature is called Site Collection Health Check. It's an extensible interface and you can build your own rules and they run on the server. Those rules always run before they go from the 14 to the 15 experience. However these rules will not run automatically during build to build upgrades, only version to version.
- One of the side affects of doing this, when we upgrade site collections, what Happens if everyone pushes upgrade at the same time? Well, MS thought about it and came up with several throttle mechanisms to protect the two places that can really be impacted, front end and memory. The second is the database itself. You can crank the throttle up or turn it down. You can forcibly upgrade the sites using powershell, and you can delete entries in the queue, assuming that someone attempts to start an upgrade for that 40GB site collection.
- =Performing self service upgrade=Go to site settings and click on site collection upgrade.Click refresh on landing page to show upgrade bar at the top of the page.Slight bug is that it says SharePoint 15!Clicking remind me later will mute the bar for 30 days, this is configurable by the farm admin.Let's actually click on start now and it brings you to site collection upgrade.A couple of controls appears, If you click on evaluation button, it will create a copy your site. Note the URL stating that it's EVAL. Let's go for the upgrade of the site collection and click on yes you are sure. First thing that is happen is the health check, it will refresh back and will state that the upgrade is in progress. The state that it is in is the queue and the site collection goes into a read only state. =Successful upgrade UI= =Log file= the copy of the log is placed not on the server but in a portion of the site collection. End users aren't supposed to read this, its for support purposes and the users can fire this to the IT pros. *end of demo*
- A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while upgrade is in progress on the new farm.Figure: Create new farm, set old farm to read-only
- Copy the SharePoint 2010 Products databasesThe second stage in the upgrade process copies the databases to the new environment. You use SQL Server Management Studio for these tasks.With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.
- =Performing self service upgrade=Go to site settings and click on site collection upgrade.Click refresh on landing page to show upgrade bar at the top of the page.Slight bug is that it says SharePoint 15!Clicking remind me later will mute the bar for 30 days, this is configurable by the farm admin.Let's actually click on start now and it brings you to site collection upgrade.A couple of controls appears, If you click on evaluation button, it will create a copy your site. Note the URL stating that it's EVAL. Let's go for the upgrade of the site collection and click on yes you are sure. First thing that is happen is the health check, it will refresh back and will state that the upgrade is in progress. The state that it is in is the queue and the site collection goes into a read only state. =Successful upgrade UI= =Log file= the copy of the log is placed not on the server but in a portion of the site collection. End users aren't supposed to read this, its for support purposes and the users can fire this to the IT pros. *end of demo*
- =Performing self service upgrade=Go to site settings and click on site collection upgrade.Click refresh on landing page to show upgrade bar at the top of the page.Slight bug is that it says SharePoint 15!Clicking remind me later will mute the bar for 30 days, this is configurable by the farm admin.Let's actually click on start now and it brings you to site collection upgrade.A couple of controls appears, If you click on evaluation button, it will create a copy your site. Note the URL stating that it's EVAL. Let's go for the upgrade of the site collection and click on yes you are sure. First thing that is happen is the health check, it will refresh back and will state that the upgrade is in progress. The state that it is in is the queue and the site collection goes into a read only state. =Successful upgrade UI= =Log file= the copy of the log is placed not on the server but in a portion of the site collection. End users aren't supposed to read this, its for support purposes and the users can fire this to the IT pros. *end of demo*
- There are a variety of resources available on avepoint.com to learn more about our products.