Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
6Activity
0 of .
Results for:
No results containing your search query
P. 1
Disaster Recovery

Disaster Recovery

Ratings: (0)|Views: 137|Likes:
Published by api-3801209
Microsoft SharePoint Products and Technologies Administrator's Pocket Consultant
\

\
Chapter 14: Backup and Restore of SharePoint Products and Technologies
Microsoft SharePoint Products and Technologies Administrator's Pocket Consultant
\

\
Chapter 14: Backup and Restore of SharePoint Products and Technologies

More info:

Published by: api-3801209 on Oct 17, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

Disaster Recovery

When content level recovery methods do not work or when you have a complete farm failure, disaster
recovery methods should be used to restore content. Be aware that disaster recovery methods may
cause a loss of data. For example, if you restore a content database from a previous night's backup, all
content written to that database since that backup occurred will be lost. For this reason, always attempt a
restore using a content recovery method first.

Using Central Administration Backup and Restore

The new backup and restore tool for Windows SharePoint Services 3.0 and SharePoint Server 2007 is
greatly improved over the last version. You now have the ability to restore entire farms, including the
configuration database. The backup and restore tool even allows restoration to an alternate SQL Server
instance to permit alternate server farm restoration and testing. Unfortunately, you still do not have the
ability to back up to tape or schedule backups from the GUI. You access the GUI Backup interface from
Central Administration > Operations > Backup And Restore > Perform A Backup, as shown in Figure 14-

5. On opening the Perform A Backup Web page, you are presented with all of the available components
that can be backed up.
Figure 14-5: To back up or restore SharePoint Products content, browse to Central Administration >
Operations > Backup And Restore.
In the following discussion, the termitems refers to Web applications, content databases, SSPs, or
content indexes and their associated search databases.
Performing a Farm-Level Backup from the GUI
1. Select the item you would like to back up. To back up the entire farm, check the box next to Farm,

as shown in Figure 14-6.
2. After selecting the entire farm, all components should be highlighted.
3. Select Continue To Backup Operations.
4. If this is the first backup of the farm, check Full for the backup type.

Note All native SharePoint Products tools must be backed up to a disk drive. You must use an
additional backup program, such as Windows Server 2003 Backup or Restore, to move that
content to tape.
ImportantYou cannot perform a differential backup of the farm until at least one full backup

has occurred. You also cannot perform a differential backup after adding a
content database or Web application. Whenever you add any of these
components to the farm, you must run another full backup before a differential
backup will be successful.

Page 1 of 8
Disaster Recovery
19.03.2008
mk:@MSITStore:C:\DOCUME~1\KUDRJA~1\LOCALS~1\Tem \_tc\2007.MsPress....

5. You must enter a location to back up to. You cannot back up to tape. The backup location should be in the same domain and shared. The following accounts should have write access to the NTFS directory and File Share:

\ue000The account authenticated to Central Administration
\ue000The Farm account (should be the Central Administration application pool identity)
\ue000The SQL Server instance account, if you are using SQL authentication
\ue000The SPTimer service account, which should be the farm account in most implementations

6. Select OK.
Figure 14-6: Select the component or set of components you want to back up.

After selecting OK, the job is scheduled with Owstimer.exe (SPtimer). If your job should fail for any
reason, you mustma n u al l y delete the Timer Job Definition. Failing to do so prevents any further backup
or restore from succeeding, whether the backup was initiated from the GUI or the command line.

Deleting a Failed Backup/Restore Job

1. Open Central Administration > Operations > Global Configuration > Timer Job Definitions.
2. Select Backup/Restore in the Title column.
3. Click on the Delete button.

Restoring Items from an Existing Backup
1. Open Central Administration > Operations > Backup And Restore > Restore From Backup.
2. Enter the location where the backup exists. There must be an Spbrtoc.xml file in the root of this
backup location, or the restore will fail.

3. Select the backup that contains the item you wish to restore, and select Continue Restore
Process. If you use multiple backup locations for disk management and do not see the correct
backup listed, you may also change the directory from this interface from the menu.

4. From the Select Component To Restore screen, select the component to restore, such as an
individual content database or an entire Web application that includes the IIS Virtual Server and
associated content database(s).

5. Select Continue Restore Process.
6. Select the Type of restore you want to perform. You have two choices, as shown in Figure 14-7:
\ue000Selecting New Configuration allows you to restore the Web application, content database, or
both as a different name and thereby recover content. In addition, you can restore the
content to a different SQL Server instance.
\ue000The option Same Configuration actually meansOverwrite. It completely overwrites any
Page 2 of 8
Disaster Recovery
19.03.2008
mk:@MSITStore:C:\DOCUME~1\KUDRJA~1\LOCALS~1\Tem \_tc\2007.MsPress....
selected components, such as Web applications and content databases, with the backed-up
content.
7. Select OK.
Figure 14-7: You must select New Configuration or Same Configuration to continue. Selecting Same
Configuration overwrites your existing content.

If you choose to restore content to a different SQL Server instance or restore content databases with a
different name to the same SQL Server instance, you must associate the content database with a Web
application to retrieve the content. Never associate the restored content databases with Web applications
that hosted the original content. Site collections, which are stored in those content databases, are
assigned a unique identifier (UID) when created. UID conflicts are caused when associating restored
content databases with a Web application with which the original content database is still associated.
Therefore, always associate content databases that are restored, with the new option, to a different Web
application from the one with which they were originally associated.

Command-Line Farm-Level Backup and Restore

You can also back up your entire farm by using stsadm.exe -o backup -directory, also known as
STSADM Catastrophic Mode. Using the-directory command-line option invokes additional options that
you can use to back up the entire farm or individual items, such as Web applications or content
databases. However, you cannot restore object-level items such as documents. Because you cannot
schedule backup jobs from the Central Administration GUI, using the command line is the best way to
reliably schedule backup jobs on your server farm. The following is an example of backing up an entire
server farm using Stsadm.exe in Catastrophic Mode:

stsadm.exe -o backup -directory
\\backupservername\backups\ -backupmethod full

This example is the simplest form of backing up your entire server using the Full option. There are
several optional parameters you can define when backing up, such as-ba c k up t h r ea d s , that are useful
and you may use them as well.

The parameters available using stsadm.exe -o backup -directory are as follows:
\ue000-item The-item option must be used in conjunction with the- s h ow t r ee option. An item from the list
generated bysh ow tr ee must be specified and the command run again omitting thesh ow tr ee
parameter.
\ue000-percentage The-pe rc e nt ag e parameter shows the progress increments on screen. For example,
10 would show the progress in 10% increments.
\ue000-backupthreads This value should be between 1 and 10. Be careful not to use high thread counts
during content indexing or other system maintenance.
\ue000-showtree The- sh ow tr ee parameter shows all items that can be backed up. This information can
ImportantThe only time the configuration database is backed up is during a farm-level backup.
The only way to restore the configuration database is by performing a farm-level
restore.
Page 3 of 8
Disaster Recovery
19.03.2008
mk:@MSITStore:C:\DOCUME~1\KUDRJA~1\LOCALS~1\Tem \_tc\2007.MsPress....

Activity (6)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
lennywalsh liked this
sudeepjm liked this
mahadev12345 liked this
mallupatil liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->