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.
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-
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.
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.
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
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.
1. Open Central Administration > Operations > Global Configuration > Timer Job Definitions.
2. Select Backup/Restore in the Title column.
3. Click on the Delete button.
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).
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.
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:
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.
This action might not be possible to undo. Are you sure you want to continue?