Enterprise Vault Whitepaper Managing SharePoint Migrations with Enterprise Vault

Transcription

1 Enterprise Vault Whitepaper Managing SharePoint Migrations with Enterprise Vault This document provides information on how to use Enterprise Vault to migrate existing SharePoint configurations to a newer installation of SharePoint. This document applies to the following versions of Enterprise Vault: 9.0.x, 10.0.x, and 11.x. If you have any feedback or questions about this document please them to IIG-TFE@symantec.com stating the document title. This document is provided for informational purposes only. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. Copyright 2014 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and the Checkmark Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

2

3 Enterprise Vault Whitepaper - Managing SharePoint Migrations with Enterprise Vault Document Control Contributors Who Amruta Purandare Evan Barrett David Scott Shahnawaz Khan Shree Joshi Ryan Pinto Contribution Author Reviewer Content Revision History Version Date Changes Version1 4 th March 2014 Version 2 14 th September 2014 Overview of manual migration added Overview of what needs to be migrated using migration tool added Split the archived SharePoint site into other site collections i

4 Enterprise Vault Whitepaper - Managing SharePoint Migrations with Enterprise Vault Table of Contents Introduction 3 How does Enterprise Vault Help? 3 Steps for Migrating from SharePoint 2007 to SharePoint Steps for Migrating from SharePoint 2007 or 2010 to SharePoint Site Collection Split and Migration 7 Working with 3 rd party Migration Solutions 9 Manual Migration using EVSPShortcutManager 9 Handling a Different Web Application Name (Different URL) in the new environment 11 ii

5 Introduction Enterprise Vault for SharePoint provides storage optimization and helps to prepare for ediscovery while maintaining seamless end-user access by using administrator-defined policies, moving older information off of SharePoint servers and into online vaults where it can be searched and accessed instantaneously. Enterprise Vault is primarily used to optimize storage and prepare for ediscovery however it can also be used to accelerate migrations to new versions of SharePoint. How does Enterprise Vault Help? The bottom line of any migration is to deliver the benefits of the new technology without introducing undue risk or ongoing costs (both storage and administrative) while delivering a seamless and transparent experience to the user. Enterprise Vault can accelerate SharePoint migrations by reducing the overall storage footprint and providing a mechanism to safely delete content from SharePoint after archiving it. Symantec recommends the following points be considered before commencing with the actual migration process: Reduce the content in the SharePoint database by moving content to the archive and optionally replacing it with shortcuts. Shortcuts are ~6 bytes in size and provide a seamless experience for the user Use the migration as a reason to examine content in SharePoint and eliminate stale/ unnecessary content by leveraging delete rules based on modified date to eliminate stale content prior to migration Archive and then delete entire sites that are no longer needed. Enterprise Vault provides that ability to archive documents, most lists, Blogs, WIKIs and discussions allowing admins to manually delete the unused sites prior to archiving while maintaining the important data for ediscovery or other purposes. Accelerate backup of old SharePoint environment prior to migration. Archiving reduces overall database size prior to backup through above archiving techniques. Disable scheduling on the respective targets before performing any migrations!

6 Steps for Migrating from SharePoint 2007 to SharePoint 2010 There are two ways to migrate SharePoint 2007 to SharePoint In-place migration This is a straightforward way to migrate SharePoint 2007 to SharePoint The steps involved for this migration are explained in Figure 1. Figure 1 - Steps for an in place migration of SharePoint 2007 SharePoint 2010 Database Attach Migration This is a more complex procedure as it requires SQL and SharePoint application changes, in addition to the Enterprise Vault Upgrade process. The steps involved for this migration are explained in Table 1.

7 Steps to migrate SharePoint 2007 to SharePoint 2010: Database Attach Migration 1 If on Enterprise Vault 8.x; upgrade to Enterprise Vault 9.x or later 2 Detach SharePoint 2007 Content Database 3 Create a new web app on SharePoint Attach SharePoint 2007 content database detached in step 2 to this web app Point the (newly attached) database to the web app by running the PowerShell script as mentioned below Run the Enterprise Vault SharePoint component on the target server where the web app is created Table 1 Steps to migrate SharePoint 2007 SharePoint 2010: Database Attach Method PowerShell script: Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication Where: <ContentDb> is the content database to be attached <DbServer> is the name of the database server is the name of the Web application to which the content database is being attached This migrates your sites to the new server. Steps for Migrating from SharePoint 2007 or 2010 to SharePoint 2013 Database Attach Migration The only way to migrate to SharePoint 2013 is using the database attach method. In place migration is no longer supported. NOTE: Before starting this migration, note that the name of the SharePoint 2013 server should be the same as that of the SharePoint 2010 server. If the name is different, the Enterprise Vault Search Web Part will not be able to perform a Restore file to the original location operation, as the file does not exist in the new location due to name

8 change. This is a minor inconvenience though as the shortcuts will continue to function and you will be able to search and open items from the Enterprise Vault Search Web Part. See the section on Handling a Different Web Application below for details on how to address this change. The steps involved for this migration are explained in Table 2. Steps for migrating SharePoint 2007/2010 to SharePoint If on Enterprise Vault 8.x; upgrade to Enterprise Vault or later 2 Detach SharePoint 2010 Content Database Create a new web app Attach the SharePoint 2010 database detached in step 2 to SharePoint 2013 SQL datbase (The name of the SharePoint 2013 MUST BE the same as that of SharePoint 2010.) Point the (newly attached) database to the web app by running the PowerShell script as mentioned below Run the Enterprise Vault SharePoint component on the target server where the webapp is created Table 2: Steps for migrating SharePoint SharePoint 2013: Database Attach Migration ONLY database attach method is supported! Note: The same procedure is followed if upgrading from 2007 to 2013 directly. PowerShell script: Mount-SPContentDatabase "<ContentDb>" -DatabaseServer "<DbServer>" -WebApplication Where: <ContentDb> is the content database to be attached <DbServer> is the name of the database server is the name of the Web application to which the content database is being attached

9 Site Collection Split and Migration A SharePoint database may grow in size even after archiving and replacing with shortcuts. The SharePoint administrator may need to split a site collection into smaller site collections. This is supported provided the updated site collections use Managed Paths to maintain the URL. Managed Paths allow users to specify the paths in the URL namespace of a web application to use for site collections. You can specify that one or more site collections exist at a specified path. This can be used to maintain the same URL of the original site collection once it has been split into two or more site collections. The following steps will allow you to split the site collection into two or more parts and still maintain shortcut access to archived content. 1. In Powershell, run the script backup-spsite -identity sitecollectionpath -path pathtobackupfile force 2. Next, in SharePoint Central Administrator, create a new Content database named Wss_Content_teams_subcollectionb. 3. Create a New Managed Explicit inclusion path named after the sub-site area of the collection you will be restoring (/def) 4. Create a new site collection using the managed path above and make sure it is created using the blank site template. 5. At this point the old content is not available. Only the blank site is available. 6. In Powershell, run the command: restore-spsite -identity newcollectionurl -p path fullpathtobackupfile -databaseserver sqlservername - databasename databasename force 7. When this is done, the result is that all the content in the site, but the URL will have an extra path in it ( that is: 8. Next, open the new site collection. Go to Site Settings and Site Collection features and turn on SharePoint Server Publishing Infrastructure if not already enabled. 9. Next, go to Site Manager for the new site root ( 10. If you see duplicate node (/def/def/), then expand the duplicate node. Then using Site Manager select each one of the sub-sites and select Move and set the destination at the root site (/def) and the site will be moved. For example, if the user has a site and wants to split the archived data from this to across multiple sites such as and it is possible to do so. The following operations will work as expected after the migration: Recall of shortcuts In-place restore Recall of shortcut in version history for documents Search through web part Send to option to different locations SharePoint archiving

10 Known Limitation: When we restore a document from Enterprise Vault search Web part, the document is restored to the site where it was archived from instead restoring to the current site. For example: xyz.doc was archived and a shortcut was created at site Now, split this site and migrate site collection to different site collection This is created in a different content database (using Managed Path). This file was moved as part of a migration to a different site collection ( A user launches and performs a search for xyz.doc. The user then restores the file using the Enterprise Vault Search web part for SharePoint. The file will be restored to its original content database (stored on instead of the new content database ( "xyz.doc" is restored to document library instead If site (source site) does not exist in SharePoint, then the restore operation fails.

11 Working with 3 rd party Migration Solutions If you are migrating Enterprise Vault for SharePoint shortcuts with a 3 rd party migration tool there are a couple of things to be aware of. Migration tools need to copy the custom property bag during migration. Enterprise Vault for SharePoint shortcuts requires custom properties to function. If the custom property bag is not included in the migration shortcuts will not function after the migration. Once the migration is complete, you need to install the Enterprise Vault for SharePoint components on the new version of SharePoint to make sure that Enterprise Vault works properly. Manual Migration using EVSPShortcutManager In some cases it may be easier to recall your existing shortcuts prior to the migration. This is only recommended as a last resort if you run into problems (example you want to use a 3 rd party migration tool that does not support moving the custom property bag) with your migration as it is a very manual process. To manually recall shortcuts and replace them with the original file, you can leverage the EVSPShortcutmanager tool. EVSPShortcutManager.exe is a command-line utility that enables you to manage the Enterprise Vault SharePoint shortcuts. This utility enables you to recall archived items to replace the shortcuts from the site, collections and libraries with the corresponding original documents. Permissions required for EVSPShortcutManager: On the SharePoint server: Local administrator Sysadmin server role on the SharePoint configuration database Along with ONE of the following roles: Site Collect Administrator Web Application Administrator Site Administrator

12 Syntax: EVSPShortcutManager operation location url url [options] Argument operation location URL options Description -recall: To replace shortcuts with the corresponding archived SharePoint documents. Run the convert option to ensure that all the HTML shortcuts are converted to new seamless shortcuts. -server: Processes the entire SharePoint server. Do not specify an URL in this case -site -library URL of the SharePoint site collection or library that needs to be processed -report -silent -log -norecurse: Use with site to avoid processing subsites

13 Handling a Different Web Application Name (Different URL) in the new environment Often when upgrading to a new SharePoint environment the Web Application name may change resulting in a new URL. If content has been archived prior to migrating to a new SharePoint environment we recommend keeping the same name, if possible. However, if you need to change the web application name (or have already done the migration), follow these steps to ensure your shortcuts continue to work properly: 1. Remove the target within the Enterprise Vault Admin console that points to the old web application name. NOTE: Deleting a target does not delete the archive. 2. Once the old target is removed, add the new Web Application as a target in the Vault Admin Console. NOTE: While re-adding the target ensure you are using the same vault store used before. 3. Run the archive task on the new target. When the target is re-added Enterprise Vault will reassociate the original archive with the new target URL so that you will be able to access content via shortcuts that were created under the old URL. These steps will preserve all functionality with one minor exception. When using the Enterprise Vault for SharePoint Search Web Part you will not be able to use the RESTORE option to restore the item to its original location as the original location will point to the original URL (a location which no longer exists). This is a minor issue as simply clicking on a shortcut will allow you to access the archived content. Also the Enterprise Vault for SharePoint Search Web Part will allow you to search for old content and open it only the restore option does not work.

14 About Symantec: Symantec is a global leader in providing security, storage, and systems management solutions to help consumers and organizations secure and manage their information-driven world. Our software and services protect against more risks at more points, more completely and efficiently, enabling confidence wherever information is used or stored. Headquartered in Mountain View, Calif., Symantec has operations in 40 countries. More information is available at For specific country offices and contact numbers, please visit our Web site: Symantec Corporation World Headquarters 350 Ellis Street Mountain View, CA USA +1 (650) (800) Copyright 2014 Symantec Corporation. All rights reserved. Symantec and the Symantec logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.