SharePoint Online Content Migration Using Third-Party Solutions

Transcription

1 SharePoint Online Content Migration Using Third-Party Applies to: Office 365 Dedicated Topic Last Modified: This guide describes a new content migration policy that was created based on the decision to deprecate the existing content migration service of Microsoft SharePoint Online for enterprises dedicated plans as of It describes the reasons for the change as well as the benefits of using a third-party solution for content migration. Content Migration Service Deprecation Beginning in 2013, Microsoft will no longer offer the content migration service described in the SharePoint Online High Level Design Document. Content migration will instead be accomplished using third-party solutions, which will help simplify the process, reduce the time and effort required to migrate content, and reduce the instances of failed migrations due to file corruption and other causes. Several factors led to the decision to change the content migration process. For one, analysis shows that customers spend a lot of time preparing data to be migrated, and these efforts can be thwarted if the customers don t adhere to migration policies and process. The migration can be rejected during the given change window. Even if the process is followed, file corruption can occur during file transfer, thereby delaying the migration process and requiring additional attempts. Because of these risks, most customers already use third-party, independent software vendor (ISV) solutions for migrating content from on-premises SharePoint to the hosted service. ISVs provide effective solutions for migrating content online. Customers benefit from reduced training needs and fewer technical resources required to use the current database attach method. Using an ISV solution has the following specific benefits: No need for SQL Server expertise to prepare data Freedom from the restrictions of the current process No minimum database size requirement No need to ship content in advance

2 Content Migration Issues The table below details the main obstacles that have hindered the content migration process, and the impact of those obstacles on data security and migration timelines. Issue File corruption Incorrect password Non-encrypted files caused deletion of database Rejection of database due to low density Lack of Ok files on the BTS after the transfer Description The files were corrupted when transferred via Backup Transfer Share (BTS). The password for decryption was incorrect. Time zone issue and delays in the migration. Files were transferred to the BTS without encryption and therefore deleted in adherence to Microsoft data security policy. Content migration was delayed. The content database was not prepared according to policy, and the configuration request (CR) was rejected. The Ok files were not placed on the BTS after the file transfer. Resulting ambiguity regarding the transfer completion caused delays in the migration.

3 Method Comparison Topic Last Modified: This topic provides an overview of the two SharePoint content migration methods the old, database attach method and the new, ISV-based method along with benefits of the ISV method and links to more information. Comparison of Requirements The following table compares the work required of the two methods. Note that none of the work required of the old method is required of the new. Old Method The migration manifest is complete, including: ISV Method Site collection size and quota. Number of databases. Total size of migration per database. Files are encrypted. Password has been sent to SDM via secure message. If BTS, need OK files after transfer. Transfer date for differential transfer One backup set per backup Total size of uncompressed data must be less than the size agreed by SharePoint Operations team.

4 Old Method Content to be migrated has been fully upgraded, with no errors, to the required SharePoint version matching the production environment. Validate databases with DBCC CHECKDB, ensuring no errors or warnings. Per Content DB size should be less than 180 GB. Per Content DB size should be larger than 80 GB (with no more than 1 exception). Every database backup must be striped to <10 GB per stripe. SQL Server Backup Compression is being used. Ensure that no content database, site collection, or object needs to be upgraded, by running STSADMo localupgradestatus. Provide a mapping table to describe the relationship between content database and the backup files. Follow the backup file naming rule: DBNAME_WEBAPP_PART[nn].BAK. XL Site Collection (>90GB) is the only site collection in Content DB. No Managed Path used in content databases. Database should be the same build with the online environment. A customizations list must be provided. ISV Method Workflow Comparison of Migration Methods The following two workflow diagrams represent the old (Microsoft database attach) and new (ISVbased) content migration methods, beginning with the old.

5 Note the comparative simplicity of the ISV-based migration workflow, shown below.

6 Benefits of ISV There is no checklist required for ISV solutions, because these solutions do not use SQL backups. An ISV solution is as simple to use as copy and paste. You can migrate SharePoint sites, lists, and libraries between servers quickly and with full fidelity. You can migrate content from live sites and unattached content databases. There is no longer a need to upgrade the on-premises environment to match the version of the hosted service. You can upgrade from SharePoint 2003 and SharePoint 2007 to SharePoint Migrating provides an opportunity to re-organize or re-template your SharePoint content. You can manage your migrations with zero downtime, no change windows, and no prior planning. You can migrate to the cloud or hosted SharePoint environments and thereby reduce infrastructure costs.

7 ISV Content Migration Information For information about third-party solutions and for a complete list of approved ISVs, see the following documents, available from the Customer Handbooks: SharePoint Online Custom Solution Policies and Process SharePoint Online Custom Solution Developer s Guide