Just another WordPress.com weblog
DR Backup/Restore of SharePoint Farm
Before you can successfully backup and restore via the catastrophic backup/restore method you must ensure that your Alternate Access Mapping for the Default is set to the http://url:randomport, as seen below.
Note: This is required if you have multiple Web App’s utilizing SSL, but seems to work fine without doing this if you only have a single Web App.
Backup the IIS Metabase
Logon to the each of the WFE’s as the Farm Admin/Setup User account and run the following command to backup the IIS metabase:
iisback.vbs /backup /e <PASSWORD>
Catastrophic Farm Backup
Now we’re ready to perform the catastrophic farm backup. You can do this one of two ways, either via STSADM as so: stsadm.exe –o backup –directory <UNC Path> -backup full (example stsadm.exe –o backup –directory \\ServerName\ShareName -backupmethod full)
Or you can perform the backup via Central Admin’s Operations tab as shown below:
Insure to check ‘Farm’ which should highlight and check everything, and then click ‘Continue to Backup Options’.
Select ‘Full’, and then enter the UNC path of your backup location and click ‘OK’.
Remove SharePoint Servers from the Farm
Once the backup is completed, you are ready to remove all the servers from the farm, remove each server one at a time, removing the server that hosts Central Admin last via the ‘SharePoint Products and Technologies Configuration’ wizard.
Create a New SharePoint Farm
1. Starting with whatever server will host Central Admin, create a new farm using the ‘SharePoint Products and Technologies Configuration’ wizard. During the setup make sure you name the SharePoint Config database something different, because when you attempt to restore the entire farm, it will not allow you to overwrite and existing database. Also, choose the same port for Central Admin as you used previously for http access.
2. Add all remaining servers to the farm one at a time.
Now that all servers are in the farm, there are few steps you must complete prior to restoring the farm backup. The following services must be started on the appropriate servers, Excel Calculations Services, Office SharePoint Server Search, and Windows SharePoint Services Search.
1. Start Excel Calculations Services.
2. Start Office SharePoint Server Search, like so:
3. Now you need to start the Windows SharePoint Services Search like so:
Note: You need to use a different name for the Search Database than what was used previously.
4. You may now start any other services on which ever servers you would like, but it is not needed at this point. These three must be completed in order run the restore.
Restore From Farm Backup
You can either restore via stsadm with the following command:
stsadm.exe –o restore –directory <UNC Path> -restoremethod new
Ex: stsadm.exe –o restore –directory \\ServerName\ShareName -restoremethod new
Or if you’re restoring to a new database server/instance:
Stsadm –o restore –directory <UNC Path> -restoremethod new –newdatabaseserver <servername>
Ex: stsadm.exe –o restore –directory \\ServerName\ShareName -restoremethod new -newdatabaseserver mysqlserver.mydomain.com
You can also use Central Admin, which I highly recommend if you’re restoring to a new database server/instance, simply because you can verify every setting before continuing, as you’ll see below.
1. From the Operations tab of Central Admin, select ‘Restore from Backup’.
2. Enter the UNC path to the backup, and click ‘OK’.
3. Select the backup that you’d like to use, and then click ‘Continue Restore Process’.
4. Check ‘Farm’, which should check and highlight everything, and then click ‘Continue Restore Process’.
5. From this screen, you define the Login name and passwords for all of the Application Pools, as well as Web App URL’s, Database Server, database name, and db directory. There are three sections to this screen.
a. The fist, make sure that ‘Farm’ is selected, and that ‘New Configuration’ is selected.
b. The next section can be quite long depending on how many application pools you have. Here you need to verify the username and password for each application pool, like so.
c. Finally, you need to verify all URL’s, database server names, database names, and database file locations, and make any necessary changes.
6. Once you’re comfortable that all the information is correct click ‘OK’, and wait for the restore to complete.
Once the restore completes successfully there are a couple additional tasks you have to complete manually before your SharePoint farm will be ready for user access.
1. Set all of your Alternate Access Mappings. The restore only restores the Default mapping, so if you had any additional mappings you will have to manually add them like so:
2. Now you need to configure which IP address each IIS vserver will listen on, as well as add the necessary Cert if the site will use SSL.
3. Finally, for all sites that use SSL you will have to run the following command:
adsutil.vbs set /w3svc/[identifier]/SecureBindings “[IP Address]:443:[host header name]”
example: adsutil.vbs set /w3svc/1234567890/SecureBindings “192.168.1.10:443:wa1.mydomain.com”
At this point your farm should be completely functional.