| Pedro Querido's profile"We Can Manage Technolog...BlogListsNetwork |  Tools  Help |
|
|
August 05 SHAREPOINT PROTECTION AND RECOVERY USING DPM 2007
Part 1 - How to Create a Recovery Farm DPM 2007 helps solve the problem of backup and restore granularity. The SharePoint backup APIs provide support for backing up content databases or the entire SharePoint farm. However, if you want to restore an individual site, list, or document, you had to use the SharePoint recovery farm architecture. With DPM 2007, you select an entire SharePoint farm to protect. During restore operations, you have the ability to select a single content database, site, list, or even document. In order to comply with SharePoint best practices, DPM does not directly modify the individual database contents. Instead, DPM restores the selected data to the appropriate location: · First, DPM restores the appropriate databases to the recovery farm. · Next, DPM uses the native SharePoint tools to inject the selected data back into the production SharePoint farm in a fully supported fashion.
So, first of all is important to understand the requirements of the Recovery Farm: · The Recovery Farm is a single machine SharePoint farm running both SharePoint front-end and SQL Server 2005 with SP2. · This machine must be separate from the DPM server, Active Directory and farm machines. · The version of SQL Server should be the same or higher than what was installed at the time of backup, and has to be in the Recovery Farm Server. · SQL VSS Writer should be running on the Recovery Farm. · The server has to be in the Domain and can be a Virtual Machine that is stopped and only starts when you want to make a recovery. It requires that you have enough space presented to the VM in order to restore any site ant its database. Consider the size of your largest Content database and its URL structure and add about 20%. · If you protect a MOSS farm, then the Recovery Farm must also be MOSS. · The features and templates installed on the Recovery Farm must match those of the target farm. · If a service pack or update is installed on the protected farm, the Recovery Farm must have the same service pack or update installed or item-level restore operations could fail. · Both the recovery and target farms must be in the same language and have the same language packs installed. · Install the DPM agent on this machine through the DPM server backing up the farm. The DPM Agent specially requires the VSS patch 940349 (http://go.microsoft.com/fwlink/?LinkId=99034) Not required in Windows Server 2008.
After this you have more 2 steps to finish the configuration of the Recovery Farm:
· Start and register the WSS Writer service. · Create the DPMRecoveryWebApplication in SharePoint.
Start and register the WSS Writer service
· In the Recovery Farm Server, open a command prompt window using elevated privileges. From within the Command Windows, navigate to C:\Program Files\Microsoft Data Protection Manager\DPM\bin and launch 'ConfigureSharepoint.exe'
· In the command window that appears, you will see the request "Enter the user name for “WSSCmdletsWrapper:" Enter the account name for the user account you granted Farm Administrator credentials ( I used the account that Log on the service, in my case the Database Access account of the Sharepoint)
o If you enter an invalid account, you will receive the following: Invalid user name.
o Examples of valid user name are "username@domain" and "domain\username".
o Once you add a Fully Qualified account name and hit enter, you are presented with the next line requesting a password.
· Enter the password for 'WSSCmdletsWrapper'.
After a moment of configuring, the entry "The command completed successfully" will appear and the CMD window will close.
DPM only offers the option of protecting the entire SharePoint farm as seen in the screenshot below. This changes when the discussion revolves around recovery of data, as we will see after. DPM provide a great deal of granularity when it comes to recovery of SharePoint data.
If the WSSCmdletsWrapper is not registered properly, then the SharePoint farm you see in the screen shot above will not appear. If it is missing, run the ConfigureSharePoint.exe utility on a SharePoint front-end web server to allow DPM to reconfigure the necessary options.
At this stage, you should be able to create a DPM Protection Group which contains the SharePoint servers take an initial replication of the content. Depending on the size of the sites, this can take a few minutes to hours to complete.
Before DPM can be used to recover any data to a protected Farm, the DPMRecoveryWebApplication must be created on the Recovery Farm server. As a requirement of the restoration process, it is helpful to understand the process necessary to create this SharePoint Web Application.
Below are the steps necessary to create the DPMRecoveryWebApplication.
· Open the SharePoint 3.0 Central Administration console from the Start Menu.
· Once the SharePoint 3.0 Central Administration console is open, click on the Application Management tab which opens to display all of the various options for managing your SharePoint installation.
· Look under the SharePoint Web Application Management heading to find the Web application list at the bottom and select this menu item.
· When the Web Application List appears, check through the list to confirm that the DPMRecoveryWebApplication does not already exist. If it does exist, you are free to delete it and continue with these instructions or you may continue with the one that exists. If it does not exist, please continue through the following steps to create one.
· Click the “back arrow” to return to the Application Management page. Under the SharePoint Web Application Management heading, click on the Create or Extend Web application.
· The Create or Extend Web application page appears with two options. The first called Create a new Web application is the one we will choose. The second option, Extend an existing Web application is not needed for this purpose.
· After clicking the Create a new Web application link, the Create New Web Application page appears displaying various necessary fields for details about the web application that is being created. Here is a brief summary of the important fields of this page.
o Chose the Create a new IIS web site and in the description, name it “DPMRecoveryWebApplication”.
o In the Port field, give it a unique port which is not shared by any other internal application. In the example below, note that the port is 911 since this is our emergency recovery web application for SharePoint failures.
o The Host Header and Path fields can remain unchanged.
o Scroll down to the radio button Create new application pool and in the Application pool name box, note that the entry name includes the port number and the SharePoint recovery server name.
o Under the Select a security account for this application pool, select the Configurable radio button and type in a suitable account and password in the fields that follow. Note the security warning at the top of the page indicating that the credentials of this account may be transmitted in clear-text across the network.
o Lastly, in the Database Name box, type in DPMRecoveryWebApplication.
This is the last entry to make before hitting OK to have the web application created. This will take a few moments but once complete, DPM will be able to recover SharePoint data. Upon completion of the DPMRecoveryWebApplication web application, the Application Created screen appears.
At this point, run ‘iisreset /noforce’ in a cmd and once complete, DPM will be able to recover SharePoint data using this recovery farm.
Now we should have:
|
|
|
