HP Data Protector A.06.
Legal and notice information © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Publication history .............................................................. 11 About the guide ................................................................. 13 Intended audience ............................................................................................. Document conventions and symbols ..................................................................... General Information ...........................................................................................
Opening the HP Data Protector Granular Recovery Extension GUI ........................... Procedure .................................................................................................. Importing content databases from backup ............................................................. Prerequisites ............................................................................................... Considerations ......................................................................................
Browsing sites ............................................................................................ 63 Displaying Granular Recovery version ........................................................... 63 7 Troubleshooting ............................................................... 65 An import job fails ............................................................................................. Problem .............................................................................................
Index ................................................................................
Figures 1 Installing a medium farm that uses the HP Data Protector Microsoft SharePoint Server VSS based solution (an example) ............................. 21 2 Data Protector user rights .................................................................. 24 3 Selecting content databases .............................................................. 26 4 HP Data Protector Granular Recovery Extension links ............................ 32 5 Recovery Cache Management (empty) ...................................
24 Recovering site items to a network share ............................................. 52 25 Removing a content database ........................................................... 53 26 Monitoring an import job progress ..................................................... 54 27 Changing Granular Recovery settings ................................................ 55 28 Retrieving the command line help ...................................................... 58 29 Restore fails with not enough user rights .
Tables 1 Edition history ................................................................................. 11 2 Document conventions ...................................................................... 13 3 Granular Recovery cache management ..............................................
Publication history Guide updates may be issued between editions to correct errors or document product changes. To ensure that you receive updated or new editions, subscribe to the appropriate product support service. See your HP sales representative for details. Table 1 Edition history Part number Guide edition Product N/A June 2010 HP Data Protector A.06.11 Granular Recovery Extension 1.00 N/A October 2010 HP Data Protector A.06.11 Granular Recovery Extension 1.
Publication history
About the guide Intended audience This guide is intended for administrators responsible for planning, setting up, and maintaining backups and recovery of Microsoft SharePoint Server. It assumes you are familiar with: • Basic Data Protector functionality • Microsoft SharePoint Server administration Document conventions and symbols Table 2 Document conventions Convention Element Blue text: Table 2 on page 13 Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
Convention Element Monospace, italic text • Code variables • Command variables Monospace, bold text Emphasized monospace text NOTE: Provides additional information. TIP: Provides helpful hints and shortcuts. General Information General information about HP Data Protector Granular Recovery Extension for Microsoft SharePoint Server can be found at http://www.hp.com/go/dataprotector and http://www.hp.com/go/imhub .
Subscription service HP recommends that you register your product at the Subscriber’s Choice for Business website: http://www.hp.com/go/e-updates After registering, you will receive e-mail notification of product enhancements, new driver versions, firmware updates, and other product resources. HP websites For additional information, see the following HP websites: • • • • • http://www.hp.com http://www.hp.com/go/dataprotector http://www.hp.com/go/imhub http://www.hp.com/support/manuals http://www.hp.
About the guide
1 Introduction This document describes the HP Data Protector Granular Recovery Extension for Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Server 2010 (Microsoft SharePoint Server).
Accidental deletion of a site is no longer an issue, even if you cannot use the recycle bin to recover your site. Granular Recovery Extension can recover an entire site with multiple subsites. • ease to search The Granular Recovery Extension advanced and quick search helps you find the item you need to recover. This search system checks object's metadata, enabling you to filter your search by document type, author, date and so on. Objects are displayed in object tree browser.
2 Installation This chapter describes how to install HP Data Protector Granular Recovery Extension.
Prerequisites Microsoft SQL Server packages Install the following packages for Microsoft SQL Server 2005 or Microsoft SQL Server 2008: • Microsoft SQL Server Native Client • Microsoft Core XML Services (MSXML) 6.
In the Figure 1 on page 21, the HP Data Protector components are colored blue, the Microsoft SQL Server install packages are green, and the HP Data Protector Granular Recovery Extension component red. Figure 1 Installing a medium farm that uses the HP Data Protector Microsoft SharePoint Server VSS based solution (an example) Procedure 1. Log on to the Microsoft SharePoint Server Central Administration system under a Microsoft SharePoint Server Farm Administrator user account. 2.
5. Run grm_install to install the HP Data Protector Granular Recovery Extension solution. Once the installation is complete, the following message is displayed in the Command Prompt window: Operation completed successfully. Timer job successfully created. Done.
3 Configuration This section describes the configuration steps that you need to follow. Not following this steps may lead to failure in recovering your objects. Verifying the configuration of the Recovery Web Application Procedure 1. Open the Central Administration web page and click the Application Management tab. 2. Under Application Security, click Authentication providers and click Default. 3.
3. Ensure the user account under which the Windows SharePoint Services Timer service is running is assigned the Data Protector Start restore and See private objects user rights. Figure 2 Data Protector user rights NOTE: The See private objects user right is useful in case you created your backup specification configured with access type private, and backup object owner. This is either the account under which the backup was executed or the account specified in the Ownership Backup Option.
Configuring Data Protector backup specifications • Ensure the option track the replica for instant recovery is not selected, when you create VSS transportable backup.
Figure 3 Selecting content databases NOTE: If you have a backup specification with individual content databases selected, each time a Farm Administrator adds a new content database, you need to include the newly-added content database in the backup specification. • If a separate Microsoft SQL Server instance is used for granular recovery purposes, specify this system as the destination Microsoft SQL Server for the Import From Backup procedure.
To be able to recover items to a filesystem, verify if the user specified in these application pools is granted enough permission. Ensure this user is granted full control of the filesystem. To verify which user account is configured in the Recovery Web Application or SharePoint Central Administration (v3 for Microsoft Office SharePoint Server 2007 or v4 for Microsoft SharePoint Server 2010) application pools: 1. Connect to the Microsoft SharePoint Server Central Administration system. 2.
Configuration
4 Backup Back up Microsoft SharePoint Server data as described in your backup solution documentation.
Backup
5 Recovery Each site has its data stored in a Microsoft SQL Server database (content database). Therefore, to recover site items, follow this basic procedure: 1. Import a. Restore Restore the content database from backup to a temporary location on a Microsoft SQL Server system. b. Mount Present the restored content database (recovery content database) to the Microsoft SharePoint Server. This creates a temporary site (recovery site). 2.
2.
3. Click Granular Recovery Cache Management. The Recovery Cache Management page is displayed. The Granular Recovery Cache shows which recovery content databases are currently mounted to the Microsoft SharePoint Server. In the beginning, the Granular Recovery Cache is empty. See Figure 5 on page 33. Figure 5 Recovery Cache Management (empty) Figure 6 on page 34 shows available functionality of the Recovery Cache Management when a content database is already mounted.
Figure 6 Recovery Cache Management with a content database mounted 34 Recovery
Table 3 Granular Recovery cache management • Import From Backup After you have backed up your content database with an HP Data Protector backup solution, use Import From Backup to restore the database to a temporary location and to mount the database to the Microsoft SharePoint Server. For details, see “Importing content databases from backup” on page 36. • Import Job Status This enables you to monitor import jobs (importing a content database from backup or from filesystem) status.
Importing content databases from backup Prerequisites On the destination Microsoft SQL Server system, you need enough disk space for the content database that you want to import. Considerations Content databases from VDI backups cannot be imported. Procedure 1. On the Recovery Cache Management page, click Import From Backup. The Site Collection Selection page is displayed. Select the content database of the site you want to recover and click Continue.
2. On the Backup Version Selection page, select the content database version that you want to restore and click Continue. Figure 8 Backup Version Selection page 3. The Content Database Recovery page is displayed: Figure 9 Content Database Recovery page In the SQL Server drop-down list, select the destination Microsoft SQL Server instance. You can change the default restore location by specifying a new path. The default is C:\Restore.
4. Optionally, to monitor job status, click Continue. The Granular Recovery Import Job Status page is displayed: Figure 10 Monitoring job status 5. Click Recovery Cache Management to return to that page. The content database is mounted to the Microsoft SharePoint Server. Figure 11 Recovery Cache Management NOTE: Once the content database is mounted to the Microsoft SharePoint Server, a Perform content recovery task is assigned to the Site Collection Administrator.
Importing content databases from the filesystem Prerequisites • The content database must be restored to the filesystem. • The user account under which the Windows SharePoint Services Timer service is running must be granted full control permission for the content database. Considerations • The Microsoft SQL Server Database Primary Data Files and all transaction log files cannot be imported from a network share.
2. On the Enter content database data page, specify the location of the Microsoft SQL Server Database Primary Data File AbsolutePath.mdf and all transaction log files AbsolutePath.ldf. Click Add. Click Continue. Figure 12 Specifying content database files 3. In the SQL Server drop-down list, select the destination Microsoft SQL Server instance. Figure 13 Importing a content database from filesystem The content database name and version are filled in automatically.
4. Optionally, to monitor job status, click Continue. The Granular Recovery Import Job Status page is displayed: Figure 14 Monitoring job status 5. Click Recovery Cache Management to return to that page. The content database is mounted to the Microsoft SharePoint Server. Figure 15 Recovery Cache Management NOTE: Once the content database is mounted to the Microsoft SharePoint Server, a Perform content recovery task is assigned to the Site Collection Administrator.
Executing Perform content recovery tasks Prerequisites • The content database must be mounted to the Microsoft SharePoint Server, by Importing content databases from backup, page 36 or by Importing content databases from the filesystem, page 39. • You must be a Site Collection Administrator of the site you want to recover.
Figure 17 Perform content recovery link Procedure 1. Click the link in the Perform content recovery task. The Browse and Select Objects page is displayed. 2. Proceed with the step 2 of the procedure “Recovering site items” on page 43. Recovering site items Prerequisites • On all the front-end Web Server systems, you need enough disk space for the site items that you plan to recover. The default location is C:\Recovery.
• Ensure that site's URL path is no longer than 260 characters: If you use the Rename if Exists recovery mode, the URL path has to be smaller than 255. Considerations • If the data to be recovered already exists at the destination, depending on the recovery mode, note the following: • Rename if Exists: Files, folders, and items are recovered with different names, OriginalName_MOSSGR_Timestamp. For example, suppose that on November 17, 2009 at 10:59:35 you start a recovery of the file wizard.txt.
• Workflow history cannot be recovered.
Procedure 1. On the Recovery Cache Management page, select the content database and the sites you want to recover. Note that a content database may contain data of multiple sites. TIP: To recover items from multiple sites, hold Ctrl while selecting specific sites under Sites, and then click Start Recovery. You can also hold Shift while selecting a group of sites under Sites, and then click Start Recovery.
2. On the Browse and Select Objects page, select the site items that you want to recover. Figure 19 Selecting site items NOTE: All items can be previewed by clicking on the item name. TIP: To select multiple list view items, hold Ctrl while selecting specific items. Alternatively, you can hold Shift while selecting a group of items.
Figure 20 Advanced search TIP: You can filter the items using the Advanced search. For example, in Result type, select Microsoft Office Word documents. In Add properties restriction, select a property and click Search. For details about the advanced and quick search, see the Microsoft SharePoint Server Help. To select multiple list view items, hold Ctrl while selecting specific items. Alternatively, you can hold Shift while selecting a group of items. Click Continue.
3. On the Recovery Objects page, the selected site items are displayed. NOTE: The Recovery mode drop-down list offers the following options: • Rename if Exists: Items such as files and folders are recovered with a new name OriginalName_MOSSGR_Timestamp. • Leave Existing: Items are not recovered, the existing items remain the same in the target location. • Overwrite Existing: Recovered items replace the existing items.
NOTE: The Into drop-down list specifies the recovery destination: • Original Location: The item is recovered to the original location in the original site. • Other Location: The item is recovered to a different site or a different location in the original site. Use this location, if the original site no longer exists. • Other Farm: The item is recovered to a different destination farm. • Filesystem: The item is recovered to a directory in your filesystem. This option is available only for files and folders.
• If you select Other Location, the Recovery to other location dialog box is displayed. Figure 22 Recovering site items to another location In the Site drop-down list, select the destination site. If you select the Apply to all items of the same type option, items of the same type (for example, calendar items) are recovered to the same location. Click OK. TIP: The sites listed in the Recovery to other location dialog box are those for which you have enough permission.
• If you select Filesystem, the Recovery to Filesystem dialog box is displayed. Figure 24 Recovering site items to a network share In Path, specify the destination directory. When specifying a network share as a destination, ensure that: • Read, write, and change permissions are granted to the user that starts the recovery session. • All necessary permissions are granted to the network share.
Removing content databases from the cache Procedure Content databases are available for three weeks, after that they are removed from the cache automatically. To manually remove the content database from the Recovery Cache, proceed as follows: 1. On the Recovery Cache Management page, select which content database to remove, and click Remove From Recovery Cache. The Remove From Recovery Cache page is displayed. 2. To keep the content database files on the disk, clear the Delete files from disk option.
2. Once you start a content database import session, HP Data Protector Granular Recovery Extension starts monitoring the import job progress. Figure 26 Monitoring an import job progress Optionally, after the recovery job is finished and you no longer need the job statuses, click Clear History.
Procedure 1. To change these default locations, connect to the Central Administration web page, click the Operations tab (Microsoft Office SharePoint Server 2007), look for HP Data Protector Granular Recovery Extension, and click Granular Recovery Settings. 2. On the Granular Recovery Settings page, enter a new restore location or temporary recovery location and click OK.
Recovery
6 Command line reference Use the HP.SharePoint.GranularRecovery.CLI.exe command line tool that is located in: Microsoft Office SharePoint Server 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN Microsoft SharePoint Server 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN To display descriptions of options and their usage, run: HP.SharePoint.GranularRecovery.CLI.exe --help.
Figure 28 Retrieving the command line help NOTE: In the examples below, HP.SharePoint.GranularRecovery.CLI.exe is omitted for simplicity.
--StartImportJob --ContentDB WSS_Content_054a5bfa-f23c-49b8-8f78-e0b3ce00b193 --BackupID "2010/04/20-4" ––Server computer ––Instance OFFICESERVERS --TargetLocation C:\Restore • Suppose you want to start a restore job by importing the content database from a filesystem to the Microsoft SharePoint Server to the default restore location C:\Restore. If the Microsoft SQL Server Database Primary Data File is WSS_Content_054a5bfa-f23c-49b8-8f78-e0b3ce00b193.
Removing restore jobs • To delete all the restore job statuses, specify: --DeleteAllJobs Confirm • To delete a specific restore job, specify: --DeleteJob=JobID Recovering a site item to the original site • Suppose you want to recover the site item /Shared Documents/Document.txt that was backed up from the site http://computer.company.com:25884/sites/AnikyB. Suppose the recovery site is http://computer.company.com:38000/sites/AnikyB.
Removing content databases from the cache • To remove a database from the cache, specify: --RemoveFromCache --ContentDB DatabaseName--BackupIDBackupID • To remove all the content databases from the cache, specify: --RemoveFromCache ––All Removing content databases from disk • To delete a content database from the disk after you have removed it from the cache, specify: --RemoveFromCache --ContentDB DatabaseName -–DeleteFiles Setting content database automatic removal • To display the time (number of days)
Listing exported items • To list the exported items, specify: --ListExport --Location Importing items from a content database • To import an item from a content database, specify: --Import --Destination destination --Location path --Item item • To import items from a content database, specify: --Import --Destination destination --Location path --Items item1 item2 item3 NOTE: Workflows cannot be imported.
--ListSites Browsing sites • To browse a My Site structure and items such as: Forms, Lists, Template Gallery, Master Page Gallery, Personal Documents, Shared Documents, Shared Pictures, Site Template Gallery, User Information List, and Web Part Gallery, specify: --BrowseSite --Site http://ivanka/personal/anikyb Displaying Granular Recovery version • To display Granular Recovery version, specify: --Version Granular Recovery Extension for Microsoft SharePoint Server 63
Command line reference
7 Troubleshooting The folder with debugs entries and logs is located in the folder: • Microsoft Office SharePoint Server 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\GranularRecovery • Microsoft SharePoint Server 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\GranularRecovery This folder contains the files debugs.txt, debugs_cliproxy.txt, note.txt, and note_cliproxy.txt.
Figure 29 Restore fails with not enough user rights Action Ensure the user account under which the Windows SharePoint Services Timer service is running is assigned the Data Protector Start restore, and the See private objects user rights. For example, if the Windows SharePoint Services Timer service is the one running under the Network Service account: 1. Open the Data Protector GUI (Data Protector Manager). 2. In the Context list, select Users.
A recovery session fails Problem If you start a recovery session by connecting to the original web site, the following message is displayed: No recovery available for this site http://computer:25884/sites/User! Please contact Granular Recovery Administrator for further info! Action The root cause of the problem is that the content database is not in the cache. Perform an import job.
Click the Deactivate button by HP Data Protector Granular Recovery Extension. The Warning page is displayed, click the Deactivate this feature link, and then go back to Manage Farm Features, and click Activate by the HP Data Protector Granular Recovery Extension.
Actions > Site Settings > Granular Recovery from My Sites. The Granular Recovery Cache Management link is not accessible from My Sites. The message "Access denied." is displayed. The following debug entry is displayed: [6 - Fatal] FATAL debugs - Recovery.aspx: OnPreInit: Exception: Thread was being aborted. Action All application pool users must be granted the Read permission on the Recovery Web Application. To grant the Read permission to application pool user accounts: 1.
Figure 31 Granting Full Read permission HP Data Protector Granular Recovery Extension cannot be removed Problem The root cause of the problem is that having the HP Data Protector Granular Recovery Extension installation package on the system is a prerequisite for the removal procedure.
Action To remove HP Data Protector Granular Recovery Extension, use the Microsoft SharePoint Server command line tool stsadm that is located in Microsoft Office SharePoint Server 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN Microsoft SharePoint Server 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN stsadm -o retractsolution -name HPDP-GRE-version.
Action To disable the HP Data Protector Granular Recovery Extension signature verification, locate the cliproxy.exe and the HP.Sharepoint.GranularRecovery.CLI.exe files in the Microsoft SharePoint Server BIN folder. By default, the path of the BIN folder is: Microsoft Office SharePoint Server 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN. Microsoft SharePoint Server 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN.
HP.Sharepoint.GranularRecovery.CLI.exe files in the Microsoft SharePoint Server BIN folder. By default, the path of the BIN folder is Microsoft Office SharePoint Server 2007: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN. Microsoft SharePoint Server 2010: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN. In the BIN folder, create the configuration files cliproxy.exe.config and HP.Sharepoint.GranularRecovery.CLI.exe.
The restoring - Mount Request Pending status Problem When performing an import from backup session, the status Restoring - Mount Request Pending is displayed on the Granular Recovery Import Job Status page. Action 1. Open the Data Protector GUI (Data Protector Manager). 2. In the Monitor context, check for any mount requests. Confirm the mount requests and restart the backup session. 3. Once the backup session is finished, perform an import from backup session again.
Granular Recovery Extension upgrade fails Problem After upgrading from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010 and then upgrading from Granular Recovery Extension 1.00 to Granular Recovery Extension 1.00 with patch, the upgrade fails with the following message: A solution with the same name "moss_gr-1.1.5037.1353.wsp" or id "67f59f7b-5744-4f8f-98ea-94ea50a3db d3" already exists in the solution store. MOSS_GRE_2010.wsp: The Solution installation failed. "MOSS_GRE_2010.
Troubleshooting
8 Removal Procedure 1. Log on to the Microsoft SharePoint Server Central Administration system under a Microsoft SharePoint Server Farm Administrator user account. 2. In the Start menu, right-click Command Prompt and select Run as Administrator. 3. Change the current directory to the directory where the files from the self-extracting archive DPWIN_00482.exe were extracted during the product installation process. 4. Run grm_uninstall to remove the HP Data Protector Granular Recovery Extension solution.
Removal
Index A advanced search, 48 audience, 13 B backup, 29 backup solutions, 17 more information, 20 backup specifications configuring, 25 backup, importing content databases from, 36 browsing sites, 63 C cache management, 35 removing content databases, 53, 61 changing settings, 54 CLI, 57 command line reference, 57 configuring, 23 Data Protector backup specifications, 25 user rights, 23 content databases importing, 36 content databases, 17 displaying information, 62 exporting items, 61 importing, 39 importin
filesystem, importing content databases from, 39 G granular recovery cache management, 35 Data Protector service is not running error message, 73 link not accessible, 67, 68 monitoring import jobs, 53 starting, 31 granularity, 17 GUI, opening, 31 H help, obtaining, 14 HP Data Protector Granular Recovery Extension cannot be removed, 70 changing settings, 54 HP Data Protector Granular Recovery Extension installing, 19 removing, 77 HP technical support, 14 I IIS application pools, verifying configuration, 2
recovery, 31 fails, 67 Recovery Web Application settings, 23 Recovery Web Application verifying configuration, 23 removal, 77 removing content databases from cache, 53, 61 from disk, 61 HP Data Protector Granular Recovery Extension, 77 HP Data Protector Granular Recovery Extension not possible, 70 restore jobs, 60 restore fails, 65 jobs, removing, 60 T tasks, content recovery, 42 technical support service locator website, 15 technical support, HP, 14 troubleshooting, 65 U user rights, 23 V verifying conf
