Export (0) Print
Expand All
ABS
AND
ASC
COS
DAY
DDB
EXP
FV
IF
INT
LEN
LN
LOG
MAX
Me
MID
MIN
MOD
NOT
IS
NPV
ODD
OR
PI
PMT
PV
SIN
SLN
SUM
SYD
T
TAN
VAR
Expand Minimize

Backing Up and Restoring Servers

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Data on three types of servers were backed up: front-end Webservers, Active Directory servers, and servers running SQLServer.

Front-End Web Servers

The data backed up from front-end Web servers was archived foranalysis and long-term off-line reference, and never intended to berestored to the server. The following log files were backed up fromthese servers:

  • Internet Information Services (IIS)logs C:\Winnt\System32\Logfiles\W3svc1\*.log

  • Usage analysislog C:\Windows\System32\LogFiles\STS\ if usageanalysis is enabled

  • Other Windows SharePoint Serviceslogs STSAdm.log and OWSTimer.log from theC:\Documents andSettings\ Windows_SharePoint_Services_Administrator_Account \LocalSettings\Temp directory.

Active Directory Servers

Backing Up Active Directory Servers

In this deployment, user accounts were replicated between thetwo peer Active Directory domain controller servers. In addition,the system state data on each Active Directory server was firstsaved to disk and then picked up nightly by the backup tape device.To avoid possible timing, performance, and replication issues, thesystem state was saved to disk at different start times for eachActive Directory server. For example, the system state for thefirst server was saved at 19:30, the system state for the secondserver was saved at 21:30, and then the backup of the system statesand user accounts began at 22:00. The Internet Platform andOperations Group used the Scheduled Tasks tool in Microsoft WindowsServer 2003 to schedule these tasks.

System state data on the Active Directory serves included ActiveDirectory and all other system components and services on whichActive Directory is dependent, the system startup files, systemregistry, file replication service (the SYSVOL directory), andDomain Name System (DNS, if it is installed). The DNS data includesDNS zone information that is integrated with Active Directory.Active Directory includes the following files:

  • Ntds.dit The Active Directorydatabase.

  • Edb.chk The checkpoint file.

  • Edb*.log The transaction logs

  • Res1.log and Res2.log Reservedtransaction logs

Note: You must be a memberof the local Administrators group on the Active Directory serversto back up Active Directory data.

Restoring Active Directory Servers

If data on disks is destroyed, an administrator can copy thedata from tapes to a newly allocated hard disk, and then restorethe Active Directory by using either a normal (non-authoritative)restore or an authoritative restore.

The normal restore allows the Active Directory server that wasnot restored to replicate changes to the restored Active Directoryserver. The restored server therefore reflects changes made afterthe backup that was used to restore it. The authoritative restorethrough the Ntdsutil utility prevents replication between serversfor all items created before the restore. For example, you may onlywant to restore the users or OUs (Organizational Units) that areaccidentally deleted from Active Directory, so that the deletedobjects are recovered and replicated.

For more information about the different kinds of restores andrestoring Active Directory servers, see Windows Server 2003 andActive Directory documentation.

Servers Running SQL Server

Backing Up Servers Running SQL Server

Windows SharePoint Services content and configuration databasesand the MSSQL database were backed up first to disk by using SQLServer 200 Enterprise Manager, and then to the tape device by usingVeritas Backup Exec software. Separate SAN partitions wereconfigured for the data and backup drives.

Because the Internet Platform and Operations deployment ofWindows SharePoint Services hosted test sites for beta users andthe deployment was designed with enough fault tolerance to surviveduring some disk and server failures, the Internet Platform andOperations group used the SQL Server simple recovery model. In theSQL Server simple recovery model, log files are not backed up. Forbusiness-critical deployments, administrators should use fullrecovery mode. For information about the different recovery modes,see SQL Server documentation.

SQL Server Enterprise Manager allows administrators to schedulebackups for each database in the system. In SQL Server EnterpriseManager, the Internet Platform and Operations Group entered backuptasks for daily and weekly backups of each database on both virtualservers.

The following diagram illustrates the scheduled job activity onthe first virtual server. Similarly, on the second virtual server,the content and system databases are written to disk before theyare copied to tape.

SQL Server Agent in SQL Server Enterprise Manager shows thestatus of the disk backup jobs in Figure 6, so administrators candetermine whether backups are successful.

Figure 6 SQL Server Enterprise Manager

Cc750442.ZA011705721033(en-us,TechNet.10).gif

Table 6 Disk backup schedule for SQL Server databases

Database

Server

Type

Sun

Mon

Tues

Wed

Thurs

Fri

Sat

MSSQL

Virtual servers 1 and 2

Full

19:00

19:00

19:00

19:00

19:00

19:00

19:00

Configuration database

Virtual server 1

Full

19:30

19:30

19:30

19:30

19:30

19:30

19:30

Content database 1

Virtual server 1

Diff.

20:30

20:30

20:30

20:30

20:30

20:30

 


 


 


Full

 


 


 


 


 


 


20:30

Restoring Servers Running SQL Server

SQL Server provides command-line options and graphical userinterface options that administrators can use to restore data toservers. For more information, see SQL Server documentation.

Backup Failures

Administrators should choose backup software that alerts them ifa backup job does not run or stops prematurely. Software shouldalso track jobs that run successfully. Refer to your backupsoftware documentation for specific setup and configuration.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft