Veritas NetBackup 6.5.4 for Microsoft Share Point Server Administrators Guide

Veritas NetBackup™ forMicrosoft SharePoint ServerAdministrator’s Guide

Release 6.5.4

Veritas NetBackup™ NetBackup for SharePoint ServerAdministrator's Guide

The software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version 6.5.4

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and NetBackup are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-DigestAlgorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’s Maintenance Programs, you can visit our Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About NetBackup for SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About NetBackup for SharePoint features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Backup operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Automatic backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Manual backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15User-directed backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About the contents of a SharePoint Server 2007 and WindowsSharePoint Services 3.0 backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About the contents of a SharePoint Server 2003 and WindowsSharePoint Services 2.0 backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Restore operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Server-directed restore .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Redirecting a restore .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Limitations on backups and restores ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18NetBackup File System daemon .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2 Installing NetBackup for SharePoint Server . . . . . . . . . . . . . . . . . . 19

About installing the NetBackup for SharePoint Server agent ... . . . . . . . . . . . . . 19Verifying the operating system and platform compatibility for

NetBackup for SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About NetBackup server and client software requirements for

NetBackup for SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About the database software requirements for NetBackup for

SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21About installation requirements for restores of individual

SharePoint Server items using Granular RecoveryTechnology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

About the requirements for installing the SQL back-end serversin a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Adding the NetBackup for SharePoint Server license key .... . . . . . . . . . . . . . . . . . 22

Contents

Chapter 3 Installing and configuring NFS for SharePointGranular Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

About installing and configuring Network File System (NFS) forSharePoint Server Granular Recovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

About requirements to perform backups and restores with GranularRecovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

About supported media server platforms for the jobs that use GranularRecovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

About supported SharePoint Server configurations for the backupsthat use Granular Recovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . 26

About configuring Services for Network File System (NFS) on theWindows 2008 NetBackup media server and NetBackupclients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Enabling Services for Network File System (NFS) on Windows

2008 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Disabling the Client for NFS on the media server ... . . . . . . . . . . . . . . . . . . . . . . 31Disabling the Server for NFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

About configuring Services for Network File System (NFS) on theWindows 2003 R2 SP2 NetBackup media server and NetBackupclients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installing Services for NFS on the Windows 2003 R2 SP2 media

server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing Services for NFS on SQL back-end servers with

Windows 2003 R2 SP2 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38About configuring a UNIX or Linux media server and Windows clients

for backups and restores that use Granular RecoveryTechnology .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring a different network port for NBFSD .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Configuring NetBackup for SharePoint Server . . . . . . . . . . . . . 43

About user interface terminology .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Configuring the log on account for the NetBackup Client Service ... . . . . . . . 44Specifying the account that logs on to the SharePoint application

server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Performing consistency checks .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45About consistency check options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Configuring restores for multiple SharePoint Server hosts ... . . . . . . . . . . . . . . . 47About configuring backups that use Granular Recovery Technology

(GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47About non-granular backups vs. backups that use Granular

Recovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Contents8

About disk storage units supported for restores using GranularRecovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

About limitations and conditions for restores using GranularRecovery Technology (GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

About configuring a backup policy for a SharePoint database .... . . . . . . . . . . . 50Policy recommendations for SharePoint Server 2007 .... . . . . . . . . . . . . . . . . 51Policy recommendations for SharePoint Server 2003 .... . . . . . . . . . . . . . . . . 53Adding a new policy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54About policy attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Adding schedules to a NetBackup for SharePoint Server

policy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Adding clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Creating a backup selections list for a SharePoint Server

policy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Testing configuration settings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 5 Performing backups and restores of SharePointServer and Windows SharePoint Services . . . . . . . . . . . . . . . 65

About NetBackup for SharePoint Server backup and restores ... . . . . . . . . . . . . 65About user-directed backups of SharePoint Server and Windows

SharePoint Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Specifying the server and client for a SharePoint Server backup

operation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66About backup options for NetBackup for SharePoint ... . . . . . . . . . . . . . . . . . 66Performing a user-directed backup of SharePoint Server or

Windows SharePoint Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67About restores of SharePoint Server and Windows SharePoint

Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Specifying the server, client, and the policy type for a SharePoint

Server restore operation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Restore options for SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69How the NetBackup Recovery Assistant restores SharePoint

Server and Windows SharePoint Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . 73Restoring SharePoint Server or Windows SharePoint

Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Restoring the SharePoint 2007 Shared Services Provider when

in a state of unprovisioning .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76About requirements for restores of individual SharePoint

items .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Restoring individual SharePoint items from full database

backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

9Contents

Recovering a SharePoint 2007 Web application in a NetworkLoad Balancing farm .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Redirecting a restore of a SharePoint Web application, portalsite, or team site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Redirecting individual SharePoint items to a file path .... . . . . . . . . . . . . . . . 84About restoring deleted sub-sites or top-level sites ... . . . . . . . . . . . . . . . . . . . . 86

Chapter 6 Recovering backward-compatible document libraryobjects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

About recovering backward-compatible document libraries ... . . . . . . . . . . . . . 87Restoring the backward-compatible document store .... . . . . . . . . . . . . . . . . . . . . . . . 88Restoring the backward-compatible document libraries ... . . . . . . . . . . . . . . . . . . . 88Restoring versioned documents (in the backward-compatible

document libraries) to the documents folder ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Restoring other file revisions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Rebuilding restored revisions of a document .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Redirecting the restore of a SharePoint 2001 document library or

workspace .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 7 Disaster recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

About disaster recovery of a SharePoint Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Requirements for disaster recovery of a SharePoint Server ... . . . . . . . . . . . . . . . 93Recovering a SharePoint 2007 Server or MOSS 3.0 (without

BMR) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Recovering SharePoint 2003 Server (without BMR) .... . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

About troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97About debug logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Enabling debug logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Setting the debug level on a Windows client ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

About NetBackup status reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About operational reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100About progress reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Viewing the status of a NetBackup operation .... . . . . . . . . . . . . . . . . . . . . . . . . . 100

About troubleshooting jobs that use Granular Recovery Technology(GRT) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

About troubleshooting restore operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Contents10

Introduction

This chapter includes the following topics:

■ About NetBackup for SharePoint Server

■ About NetBackup for SharePoint features

■ Backup operations

■ About the contents of a SharePoint Server 2007 and Windows SharePointServices 3.0 backup

■ About the contents of a SharePoint Server 2003 and Windows SharePointServices 2.0 backup

■ Restore operations

■ Limitations on backups and restores

■ NetBackup File System daemon

About NetBackup for SharePoint ServerNetBackup for SharePoint extends the capabilities of NetBackup to include onlinebackups and restores of the following:

■ Microsoft Office SharePoint Server 2007

■ Microsoft SharePoint Portal Server 2003

■ Windows SharePoint Services (WSS) 3.0

■ Windows SharePoint Services (WSS) 2.0

For both SharePoint 2007 and SharePoint 2003, the database agent protectsConfiguration databases, and Single Sign-on databases. For SharePoint Server2007, the agent also protects SharePoint Web applications, Global Settings, and

1Chapter

Shared Services. For SharePoint Server 2003, the agent also protects SharePointportals, team sites, and the backward-compatible document store and documentlibraries.

Users can restore individual SharePoint database objects. Users can also restoreindividual items from a SharePoint Web application database, a SharePoint portal,or a team site database backup.

These capabilities are add-ons to the NetBackup for Windows client software.Because this product is tightly integrated with the Backup, Archive, and Restoreinterface, this manual provides only an overview of NetBackup functionality.Backup operations and restore operations for SharePoint Server are identical toother NetBackup file operations, except where noted.

Microsoft Office SharePoint Server or Microsoft SharePoint Portal Server maybe abbreviated to either SharePoint Server or to SharePoint. Unless otherwisenoted, the text implies Windows SharePoint Services when SharePoint is discussed.

About NetBackup for SharePoint featuresTable 1-1 describes the features for the NetBackup for SharePoint agent.

Table 1-1 NetBackup for SharePoint agent features

DescriptionFeature

SharePoint Server objects can be backed up without taking theSharePoint Server offline. SharePoint services and data areavailable during the backup.

Online backup

NetBackup supports full and differential-incremental backupsof SharePoint.

SharePoint Serverbackup methods

Tight integration with NetBackup means the following:

■ An administrator already familiar with NetBackupprocedures and software can easily configure and useNetBackup to perform SharePoint Server backup and restoreoperations.

■ Features and strengths of the NetBackup product suite areavailable to the SharePoint Server backup user. Thesefeatures include scheduled and user-directed operations andin-line tape copy. These features are described in detail.

See the NetBackup Administrator’s Guide, Volume I.

Tight NetBackupintegration

You can administer the backup and recovery of multipleSharePoint Server installations from a central location.

Central administration

IntroductionAbout NetBackup for SharePoint features

12

Table 1-1 NetBackup for SharePoint agent features (continued)

DescriptionFeature

SharePoint Server backups are saved directly to a wide varietyof storage devices that NetBackup supports.

Media management

Administrators can set up schedules for automatic, unattendedbackups for local or remote clients across the network. Thesebackups are managed entirely by the NetBackup server from acentral location. The administrator can also manually back upthe clients. Auto discovery is used for SharePoint Serverinstallations. The topology is read from the SharePoint front-endWeb server and the backup selection list is automatically built.

See “About the contents of a SharePoint Server 2007 andWindows SharePoint Services 3.0 backup” on page 15.

See “About the contents of a SharePoint Server 2003 andWindows SharePoint Services 2.0 backup” on page 16.

Automated backups

A user can perform backups of SharePoint Server resourcesthrough the Backup, Archive, and Restore client interface onthe front-end Web server.

User-directed backups

NetBackup can back up and restore standalone installations ofWindows SharePoint Services.

Backups and restores ofstandalone WindowsSharePoint Services(WSS)

Compression increases backup performance over the networkand reduces the size of the backup image that is stored on thedisk or tape. NetBackup does not support compression of thebackups that use Granular Recovery Technology.

Compression of backups

When the Encryption attribute is enabled, the server encryptsthe backup for the clients that are listed in the policy. NetBackupdoes not support encryption of backups that use GRT.

Encryption

In SharePoint 2003, the backward-compatible document storeis an optional, updated version of the Web storage system thatis used in SharePoint Server 2001.

Backup and restore ofdocument libraries anddocument store

An administrator who uses the Backup, Archive, and Restoreinterface can browse SharePoint Server backups and select theones to restore.

Restore operations

13IntroductionAbout NetBackup for SharePoint features

Table 1-1 NetBackup for SharePoint agent features (continued)

DescriptionFeature

When a backup uses GRT, users can restore individual itemsdirectly from any full database backup of a Web application orportal. A separate granular-level backup is not needed. Thisfeature adds an extra step that identifies the items within thedatabase. This step lets you recover individual items later.

Restores of individualitems using GranularRecovery Technology

You can redirect the restore of the following:

■ SharePoint Web applications or portals to an alternate URLwithin the same farm.

■ Document libraries or workspaces to another documentlibrary or workspace.

■ Individual SharePoint items to a file path on the same site.

Redirected restore

You can restore the backups that were created with versions ofNetBackup before 6.5.4. However, new 6.5.4 features are notsupported with backups that were created with previousversions. For example, you cannot restore list items from aNetBackup 6.5.3 or earlier backup.

Support for backups thatwere created withprevious NetBackupversions

Backup operationsYou can use the NetBackup for SharePoint Server agent to back up the entireSharePoint Server farm or individual components.

See “About the contents of a SharePoint Server 2007 and Windows SharePointServices 3.0 backup” on page 15.

See “About the contents of a SharePoint Server 2003 and Windows SharePointServices 2.0 backup” on page 16.

NetBackup provides the following methods to perform backups:

■ Automatic

■ Manual

■ User-directed

For general information on backup methods in NetBackup see the NetBackupAdministrator’s Guide, Volume I.

IntroductionBackup operations

14

Automatic backupsThe NetBackup administrator can schedule the backups that occur automaticallyand unattended under the control of the NetBackup Server.

The following types of automatic backups that are available:

The entire contents in the backup selections list are backedup.

Full schedule

Only the contents that have been added or changed since theprevious full or incremental are included in the backup.

Differential incremental

Manual backupsManual backup may be used for special events. A manual backup includes all theitems in the backup selections list of the policy you selected for backup.

User-directed backupsUser directed backups require a User Backup schedule to be defined on aSharePoint policy on the NetBackup Server. A user-directed backup includes theentire contents of the items that are selected for backup. This type of backup isonly supported from the SharePoint application host, not on other hosts whereonly SharePoint objects are present.

About the contents of a SharePoint Server 2007 andWindows SharePoint Services 3.0 backup

Table 1-2 lists the SharePoint Server farm components or Windows SharePointServices that you can back up and restore with NetBackup for SharePoint.

Table 1-2 Comparison of SharePoint Server 2007 and Windows SharePointServices 3.0 components

Windows SharePoint ServicesSharePoint Server 2007 farm

Configuration databaseConfiguration database

Global settings

Single Sign-on database

15IntroductionAbout the contents of a SharePoint Server 2007 and Windows SharePoint Services 3.0 backup

Table 1-2 Comparison of SharePoint Server 2007 and Windows SharePointServices 3.0 components (continued)

Windows SharePoint ServicesSharePoint Server 2007 farm

WSS Help Search:

■ Index files

■ Search database

Shared Services:

■ Services database

■ Shared Search Index

■ Index files

■ Search database

■ Web application

■ Content database

WSS Administration:

■ Web application


Web application

About the contents of a SharePoint Server 2003 andWindows SharePoint Services 2.0 backup

Table 1-3 lists the SharePoint Server farm components or Windows SharePointServices that you can back up and restore with the SharePoint agent.

Table 1-3 Comparison of SharePoint Server 2003 Farm and WindowsSharePoint Services 2.0 components

Windows SharePoint ServicesSharePoint Server Farm

Configuration databaseConfiguration database

Team site:

■ Team database

Single Sign-on database

Backward-compatible document store

Backward-compatible document libraries(Web Storage System-Based)

IntroductionAbout the contents of a SharePoint Server 2003 and Windows SharePoint Services 2.0 backup

16

Table 1-3 Comparison of SharePoint Server 2003 Farm and WindowsSharePoint Services 2.0 components (continued)

Windows SharePoint ServicesSharePoint Server Farm

Portal sites and their associated databases:


■ User profile database


■ Index databases

■ Team databases

Restore operationsUse the Backup, Archive, and Restore interface to initiate SharePoint Serverrestore operations. This interface lets you select the NetBackup Server from whichthe objects are restored and the client whose backups you want to browse. Basedupon these selections, you can browse the backup history, select individual itemsand launch a restore. The NetBackup Recovery Assistant lets you restoreSharePoint resources with one click and determines the sequence in which theresources are restored.

Server-directed restoreAn administrator can browse for and restore databases and individual items. Usersalso can restore the security settings on a selected item. Objects that users canrestore include the following:

■ One or more databases

■ Individual documents in the Document library

■ Entire sites

■ Sub-sites

■ Entire lists

■ Individual list items

Redirecting a restoreSharePoint Web applications, portal sites, team sites, and backward-compatibledocument libraries can be redirected to a different location from which they werebacked up. Web applications or portal sites can be redirected to a Web applicationor portal site on another Web server in an existing farm. Team sites can be

17IntroductionRestore operations

redirected to another Windows SharePoint Services site on the Web server.Individual documents or items can be redirected to a file system.

Limitations on backups and restoresThe following limitations exist when you perform backups and restores of theSharePoint Server:

■ Redirected restores are only supported for Web applications or portals andfor backward-compatible libraries. The following cannot be redirected to adifferent location:

■ Documents and folders can be redirected to a file system.

■ A team site cannot be redirected to a site in another farm (but you canredirect to another site within the original farm)

■ Farm Configuration database and Single Sign-on database

■ Index Files or Index database

■ You cannot restore a Windows Microsoft SQL Server 2000 Desktop Engine(WMSDE) database to an alternate location because of a WMSDE limitation.

■ SharePoint policies do not support multiple data streams.

NetBackup File System daemonThe Network File System Daemon (nbfsd) on the NetBackup media server is aprocess which allows access to mount, browse, and read tar images by NetBackupclients. This process is used for restores that use Granular Recovery Technology(GRT).

IntroductionLimitations on backups and restores

18

Installing NetBackup forSharePoint Server


■ About installing the NetBackup for SharePoint Server agent

■ Verifying the operating system and platform compatibility for NetBackup forSharePoint Server

■ Adding the NetBackup for SharePoint Server license key

About installing theNetBackup for SharePoint Serveragent

Every NetBackup server includes the NetBackup client software by default.Therefore you can use NetBackup for SharePoint Server on a NetBackup serveror client (if NetBackup for SharePoint Server is supported on that platform).Perform the following tasks before you use NetBackup for SharePoint Server:

■ Verify the installation prerequisites.

■ See “Verifying the operating system and platform compatibility forNetBackup for SharePoint Server” on page 20.

■ See “About NetBackup server and client software requirements forNetBackup for SharePoint Server” on page 20.

■ See “About the database software requirements for NetBackup forSharePoint Server” on page 21.

■ See “About installation requirements for restores of individual SharePointServer items using Granular Recovery Technology (GRT)” on page 21.

2Chapter

■ See “About the requirements for installing the SQL back-end servers in acluster” on page 22.

■ Add the license key for NetBackup for SharePoint Server.See “Adding the NetBackup for SharePoint Server license key” on page 22.

Verifying the operating system and platformcompatibility for NetBackup for SharePoint Server

Verify that the NetBackup for SharePoint Server agent is supported on youroperating system or platform.

To verify operating system and compatibility

1 Go to the Symantec Support Web page:

http://www.symantec.com/business/support/index.jsp

2 In the Product Finder box, type NetBackup Enterprise Server and clickthe > icon.

3 From the list on the right, click on Compatibility List.

4 In the list of documents, click on the following link:

Veritas NetBackup (tm) x.x Database Agent Compatibility (Updated

date_updated).

For x.x, look for the current release. For date_updated, look for the mostrecent date.

About NetBackup server and client software requirements forNetBackup for SharePoint Server

Verify that the following requirements are met for the NetBackup server andclient software:

■ The NetBackup server software is installed and operational on the NetBackupserver. The NetBackup server platform can be any that NetBackup supports.See the NetBackup Installation Guide.

■ The NetBackup client software is installed on the following: each front-endWeb server, the SQL database host, and the Index database host. Also installthe client on the host that contains the backward-compatible document librarystore. The client software does not need to be installed on the Search or Jobservers.

Installing NetBackup for SharePoint ServerVerifying the operating system and platform compatibility for NetBackup for SharePoint Server

20

http://www.symantec.com/business/support/index.jsp

■ The NetBackup client software is installed on the computer that has thedatabases you want to back up. This step also installs the database agent.If the client is also a NetBackup server, the client software and database agentis installed along with the server software.

■ If you want to take advantage of features included in NetBackup 6.5.4, themedia server and clients must be at the same NetBackup version. If you upgradeyour media server to NetBackup 6.5.4, you must also upgrade your clients toversion 6.5.4.

■ Make sure that you configure any backup media that the storage unit uses.

The number of media volumes that are required depends on several things:

■ The devices used

■ The sizes of the databases that you want to back up

■ The amount of data that you want to archive

■ The size of your backups

■ The frequency of backups or archives


About the database software requirements for NetBackup forSharePoint Server

Verify the following regarding the database software on the NetBackup server orclient:

■ SharePoint server software must be installed and operational.

■ When you use SharePoint load balancing, all load-balanced Web sites must beuniformly identified in IIS. Identify the sites with either host headers or IPaddresses, but not both. Environments which mix host headers and IP addressesacross load-balanced servers are not supported.

■ To prevent restore failures, the IIS Default Application Pool identity must bea valid SharePoint user ID.

■ The SharePoint user should be an administrator user account.

About installation requirements for restores of individual SharePointServer items using Granular Recovery Technology (GRT)

Additional installation requirements exist if you want to restore individualSharePoint Server items using Granular Recovery Technology (GRT).

21Installing NetBackup for SharePoint ServerVerifying the operating system and platform compatibility for NetBackup for SharePoint Server

See “About installing and configuring Network File System (NFS) for SharePointServer Granular Recovery” on page 24.

About the requirements for installing the SQL back-end servers in acluster

NetBackup supports a cluster of a back-end SQL Server in a Veritas Cluster Server(VCS) or a Microsoft Cluster Server (MSCS) environment.

For more information, see your VCS or your MSCS documentation.

Adding the NetBackup for SharePoint Server licensekey

Every NetBackup server includes the NetBackup client software by default.Therefore you can use NetBackup for SharePoint Server on a NetBackup serveror client (if NetBackup for SharePoint Server is supported on that platform). Touse this agent, add a valid license key for it on the master or the media server.

For information on how to add license keys, see the NetBackup Administrator’sGuide, Volume I.

To add a NetBackup for SharePoint Server license key in the NetBackupAdministration Console

1 On the master or the media server, open the NetBackup AdministrationConsole.

2 Choose Help > License Keys.

3 Click the New icon.

4 Type the license key and click Add.

Installing NetBackup for SharePoint ServerAdding the NetBackup for SharePoint Server license key

22

Installing and configuringNFS for SharePointGranular Recovery


■ About installing and configuring Network File System (NFS) for SharePointServer Granular Recovery

■ About requirements to perform backups and restores with Granular RecoveryTechnology (GRT)

■ About supported media server platforms for the jobs that use GranularRecovery Technology (GRT)

■ About supported SharePoint Server configurations for the backups that useGranular Recovery Technology (GRT)

■ About configuring Services for Network File System (NFS) on the Windows2008 NetBackup media server and NetBackup clients

■ About configuring Services for Network File System (NFS) on the Windows2003 R2 SP2 NetBackup media server and NetBackup clients

■ About configuring a UNIX or Linux media server and Windows clients forbackups and restores that use Granular Recovery Technology

■ Configuring a different network port for NBFSD

3Chapter

About installing and configuringNetwork File System(NFS) for SharePoint Server Granular Recovery

NetBackup Granular Recovery leverages Network File System, or NFS, to readindividual objects from a database backup image. Specifically, the NetBackupclient uses NFS to extract data from the backup image on the NetBackup mediaserver. The NetBackup client uses “Client for NFS” to mount and access a mappeddrive that is connected to the NetBackup media server. The NetBackup mediaserver handles the I/O requests from the client through NBFSD.

NBFSD is the NetBackup File System (NBFS) service that runs on the media server.NBFSD makes a NetBackup backup image appear as a file system.

Network File System, or NFS, is a widely recognized, open standard for client andserver file access over a network. It allows clients to access files on dissimilarservers through a shared TCP/IP network. NFS is typically bundled with the hostoperating system. NetBackup uses Granular Recovery Technology (GRT) and NFSto recover the individual objects that reside within a database backup image, suchas:

■ A user account from an Active Directory database backup

■ Email messages or folders from an Exchange database backup

■ A document from a SharePoint database backup

Multiple NetBackup agents that support GRT (for example, Exchange, SharePoint,and Active Directory) can use the same media server.

Note: If you do not correctly configure NFS, restores of individual items usingGRT fail with an error 223 (An invalid entry was encountered).

About requirements to performbackups and restoreswith Granular Recovery Technology (GRT)

Ensure that your environment meets the following requirements:

■ You have a supported SharePoint Server configuration and a supportedoperating system for the media server.See “About supported SharePoint Server configurations for the backups thatuse Granular Recovery Technology (GRT)” on page 26.

■ On all SQL back-end servers and the media server, ensure that the computerhas an available drive letter on which to mount the backup image.

Installing and configuring NFS for SharePoint Granular RecoveryAbout installing and configuring Network File System (NFS) for SharePoint Server Granular Recovery

24

■ On all SQL back-end servers, do the following:

■ Configure the NetBackup Client Service to log on with a domain-privilegedaccount.See “Configuring the log on account for the NetBackup Client Service”on page 44.

■ For Windows 2003 R2 SP2, install the hotfix for Client for NFS.The hotfix is available at the following location:http://support.microsoft.com/kb/947186

■ Enable or configure NFS for your environment.

■ Windows 2008 media server and clientsSee “About configuring Services for Network File System (NFS) on theWindows 2008 NetBackup media server and NetBackup clients” on page 27.

■ Windows 2003 R2 SP2 media server and clientsSee “About configuring Services for Network File System (NFS) on theWindows 2003 R2 SP2 NetBackup media server and NetBackup clients”on page 34.

■ UNIX/Linux media server and Windows clientsSee “About configuring a UNIX or Linux media server and Windows clientsfor backups and restores that use Granular Recovery Technology”on page 41.See “About configuring Services for Network File System (NFS) on theWindows 2008 NetBackup media server and NetBackup clients” on page 27.See “About configuring Services for Network File System (NFS) on theWindows 2003 R2 SP2 NetBackup media server and NetBackup clients”on page 34.

About supportedmedia server platforms for the jobsthat use Granular Recovery Technology (GRT)

Table 3-1 shows the supported platforms for NetBackup media servers that supportgranular recovery operations.

Table 3-1 Supported media server platforms for the jobs that use GranularRecovery Technology

Supported media server platforms

AIX 5L

HP-UX HP 9000 PA-RISC

25Installing and configuring NFS for SharePoint Granular RecoveryAbout supported media server platforms for the jobs that use Granular Recovery Technology (GRT)

http://support.microsoft.com/kb/947186

Table 3-1 Supported media server platforms for the jobs that use GranularRecovery Technology (continued)

Supported media server platforms

HP-UX HP Integrity (IA-64)

RedHat Enterprise Linux

Solaris SPARC

SUSE Linux Enterprise Server

Windows 2003 R2 SP2 x86/x64

Windows 2008

About supported SharePoint Server configurationsfor the backups that use Granular RecoveryTechnology (GRT)

Table 3-2 shows the configurations that are supported for SharePoint ServerGranular Recovery.

Note: NetBackup does not support Granular Recovery Technology (GRT) withWindows Server 2003 R1 or earlier versions.

Table 3-2 Configurations that are supported for SharePoint Granular Recovery

Media serverWindows ServerSQL ServerSharePoint/WSS

See “About supportedmedia server platforms forthe jobs that use GranularRecovery Technology(GRT)” on page 25.

Windows Server 2008SQL 2008

SQL 2005 (32-bit or 64-bit)

SQL Express

SharePoint Server 2007 SP1(32-bit and 64-bit)

WSS 3.0 (32-bit and 64-bit)


Windows Server 2003 R2SP2 or later, 32-bit or 64-bit


SQL Express

SharePoint Server 2007 SP1(32-bit and 64-bit)

WSS 3.0 (32-bit and 64-bit)

Installing and configuring NFS for SharePoint Granular RecoveryAbout supported SharePoint Server configurations for the backups that use Granular Recovery Technology (GRT)

26

Table 3-2 Configurations that are supported for SharePoint Granular Recovery(continued)

Media serverWindows ServerSQL ServerSharePoint/WSS


Windows Server 2003 R2SP2 or later, 32-bit or 64-bit


SQL Express

SharePoint Server 2003 SP2

WSS 2.0

About configuring Services for Network File System(NFS) on theWindows 2008 NetBackupmedia serverand NetBackup clients

To configure NFS in a Windows 2008 environment, perform the followingconfiguration:

■ Enable NFS on the following:

■ The NetBackup media server

■ The SQL back-end servers

See “Enabling Services for Network File System (NFS) on Windows 2008”on page 27.

■ You can disable the Server for NFS on the following:

■ The NetBackup media server

■ The SQL back-end servers

See “Disabling the Server for NFS” on page 32.

■ You can disable the Client for NFS on the NetBackup media server.See “Disabling the Client for NFS on the media server” on page 31.If the SQL back-end server resides on the media server, do not disable theClient for NFS.

Enabling Services for Network File System (NFS) on Windows 2008To restore individual items from backups that use Granular Recovery Technology(GRT), you must enable Services for Network File System. (You do not need toconfigure Server Roles for Windows 2003 R2 SP2.)

When this configuration is completed on the media server and the SQL back-endservers, you can disable any unnecessary NFS services.

27Installing and configuring NFS for SharePoint Granular RecoveryAbout configuringServices forNetwork File System (NFS) on theWindows2008NetBackupmedia server andNetBackup

clients

To enable Services for Network File System (NFS) on Windows 2008

1 Open the Server Manager.

2 In the left pane, click Roles and, in the right pane, click Add Roles.

3 In the Add Roles Wizard, on the Before You Begin page, click Next.

Installing and configuring NFS for SharePoint Granular RecoveryAbout configuring Services forNetwork File System (NFS) on theWindows2008NetBackupmedia server andNetBackupclients

28

4 On the Select Server Roles page, under Roles, check the File Services checkbox.

5 Click Next.

6 On the Files Services page, click Next.

7 On the Select Role Services page, uncheck File Server.


clients

8 Check Services for Network File System.

9 Click Next and complete the wizard.

10 On the media server, configure the portmap service to start automatically atserver restart.

Issue the following from the command prompt:

sc config portmap start= auto

This command should return the status[SC] ChangeServiceConfig SUCCESS.

11 For each host in your configuration, choose from one of the following:

■ If you have a single host that functions as both the media server and theSQL back-end server, you can disable the Server for NFS.

■ For a host that is only the NetBackup media server, you can disable theServer for NFS and the Client for NFS.


30

■ For a host that is only a SQL back-end server, you can disable the Serverfor NFS.

See “Disabling the Server for NFS” on page 32.

See “Disabling the Client for NFS on the media server” on page 31.

Disabling the Client for NFS on the media serverTo disable the Client for NFS on the NetBackup media server


2 In the left pane, expand Configuration.

3 Click Services.

4 In the right pane, right-click on Client for NFS and click Stop.

5 In the right pane, right-click on Client for NFS and click Properties.


clients

6 In the Client for NFS Properties dialog box, for Startup type, click Disabled.

7 Click OK.

Disabling the Server for NFSAfter you enable Services for Network File System (NFS) on the media server andon the SQL back-end servers, you can disable Server for NFS.

To disable the Server for NFS


2 In the left pane, expand Configuration.


32

3 Click Services.

4 In the right pane, right-click on Server for NFS and click Stop.

5 In the right pane, right-click on Server for NFS and click Properties.


clients

6 In the Server for NFS Properties dialog box, for Startuptype, click Disabled.

7 Click OK.

8 Repeat this procedure for the media server and for each SQL back-end server.

About configuring Services for Network File System(NFS) on theWindows2003R2SP2NetBackupmediaserver and NetBackup clients

Note: NetBackup does not support Granular Recovery Technology (GRT) withWindows Server 2003 R1 or earlier versions.

Perform the following configuration:

■ Install the necessary NFS components on the NetBackup media server.See “Installing Services for NFS on the Windows 2003 R2 SP2 media server”on page 35.

■ Install the necessary NFS components on the SQL back-end servers

Installing and configuring NFS for SharePoint Granular RecoveryAbout configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server andNetBackup clients

34

See “Installing Services for NFS on SQL back-end servers with Windows 2003R2 SP2” on page 38.

Table 3-3 describes the NFS components that are necessary for the NetBackupclient and the NetBackup media server.

Table 3-3 NFS components required for Windows 2003 R2 SP2

NetBackupmedia server

NetBackupclientNFS component

XClient for NFS

XMicrosoft Services for NFS Administration

XXRPC External Data Representation

XRPC Port Mapper

Note: If the SQL back-end server resides on the media server, install all thecomponents on the media server.

Installing Services for NFS on the Windows 2003 R2 SP2 media serverThis topic describes how to install Services for NFS on a Windows 2003 R2 SP2media server.

To install Services for NFS on the Windows 2003 R2 SP2 media server

1 Click Start > Control Panel > Add or Remove Programs.

2 Click Add/Remove Windows Components.

35Installing and configuring NFS for SharePoint Granular RecoveryAbout configuring Services for Network File System (NFS) on the Windows 2003 R2 SP2 NetBackup media server and

NetBackup clients

3 Check Other Network File and Print Services and click Details.

4 Check Microsoft Service for NFS and click Details.


36

5 Install the components that apply to your configuration.

■ If the host is only a NetBackup media server, check the followingcomponents:

■ RPC External Data Representation

■ RPC Port Mapper

■ If you have a single host that functions as both the media server and theSQL back-end server, check the following components:

■ Client for NFS

■ Microsoft Services for NFS Administration


■ RPC Port Mapper

Media serverand client

Mediaserver only

6 Click OK.

7 Click OK.

8 Click Next and complete the Windows Components Wizard.

9 After the installation is complete, open Services in the Control Panel.


NetBackup clients

10 Ensure the following:

Services notrequired

Servicesrequired

Host type

Client for NFS isrunning.

A single host that has both the media serverand the SQL back-end server

Client for NFS canbe stopped anddisabled.

A host that is only a NetBackup media server

11 Configure the portmap service to start automatically at server restart.

Issue the following from the command prompt:

sc config portmap start= auto

This command should return the status[SC] ChangeServiceConfig SUCCESS.

Installing Services for NFS on SQL back-end servers with Windows2003 R2 SP2

This topic describes how to install NFS on the NetBackup clients with Windows2003 R2 SP2. Only the clients that are SQL back-end servers require NFS. If a SQLback-end server is also a NetBackup media server, you must follow a differentprocedure.

See “Installing Services for NFS on the Windows 2003 R2 SP2 media server”on page 35.

To install Services for NFS on the NetBackup clients with Windows 2003 R2 SP2

1 Click Start > Control Panel > Add or Remove Programs.

2 Click Add/Remove Windows Components.


38

3 Check Other Network File and Print Services and click Details.

4 Check Microsoft Service for NFS and click Details.


NetBackup clients

5 Check the following components:

■ Client for NFS

■ Microsoft Services for NFS Administration


6 Click OK.

7 Click OK.

8 Click Next and complete the Windows Components Wizard.

9 After the installation is complete, open Services in the Control Panel.

10 Ensure the following that the Client for NFS service is running.

11 Repeat this procedure for each SQL back-end server.


40

About configuring a UNIX or Linux media server andWindows clients for backups and restores that useGranular Recovery Technology

To perform backups and restores that use Granular Recovery Technology, performthe following configuration if you use a UNIX or Linux media server and Windowsclients:

■ Confirm that your media server is installed on a platform that supportsgranular recovery.See “About supported media server platforms for the jobs that use GranularRecovery Technology (GRT)” on page 25.

■ No other configuration is required for the UNIX or Linux media server.

■ Enable or install NFS on the SQL back-end servers.

See “Enabling Services for Network File System (NFS) on Windows2008” on page 27.

Windows 2008

See “Installing Services for NFS on SQL back-end servers withWindows 2003 R2 SP2” on page 38.

Windows 2003 R2

■ You can configure a different network port for NBFSD.See “Configuring a different network port for NBFSD” on page 41.

Configuring a different network port for NBFSDNBFSD runs on port 7394. If another service uses the standard NBFSD port in yourorganization, you can configure the service on another port. The followingprocedures describe how to configure a NetBackup server to use a network portother than the default.

To configure a different network port for NBFSD (Windows server)

1 Log on as administrator on the computer where NetBackup server is installed.

2 Open Regedit.

3 Open the following key.:

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config

4 Create a new DWORD value named FSE_PORT.

5 Right-click on the new value and click Modify.

41Installing and configuring NFS for SharePoint Granular RecoveryAbout configuring a UNIX or Linux media server and Windows clients for backups and restores that use Granular

Recovery Technology

6 In the Value data box, provide a port number between 1 and 65535.

7 Click OK.

To configure a different network port for NBFSD (UNIX or Linux server)

1 Log on as root on the computer where NetBackup server is installed.

2 Open the bp.conf file.

3 Add the following entry, where XXXX is an integer and is a port numberbetween 1 and 65535.

FSE_PORT = XXXX

Installing and configuring NFS for SharePoint Granular RecoveryConfiguring a different network port for NBFSD

42

Configuring NetBackup forSharePoint Server


■ About user interface terminology

■ Configuring the log on account for the NetBackup Client Service

■ Specifying the account that logs on to the SharePoint application server

■ Performing consistency checks

■ About consistency check options

■ Configuring restores for multiple SharePoint Server hosts

■ About configuring backups that use Granular Recovery Technology (GRT)

■ About configuring a backup policy for a SharePoint database

■ Testing configuration settings

About user interface terminologyYou can perform many of the configuration steps in this topic from the NetBackupadministration console on the master server. The type of console available dependson your master server’s platform. NetBackup supports a Java interface for bothWindows and UNIX master servers. In addition, NetBackup supports a Windowsinterface for Windows master servers.

The Java and Windows interfaces are nearly identical. If interface differencesexist in the configuration procedures, the term "Windows interface" or "Javainterface" appears in the procedure to differentiate between the two interfaces.

4Chapter

Configuring the log on account for the NetBackupClient Service

The NetBackup Client Service must be authorized to run as the systemadministrator (Windows 2008) or the SharePoint administrator (Windows 2003).In Windows Services, configure the NetBackup Client Service properties for thehost(s) where the Index Files or Index database(s) and where the document librariesreside. To change this account, you must have administrator group privileges.

To configure the log on account for the NetBackup Client Service

1 Open the Windows Services application.

2 Double-click on the NetBackup Client Service entry.

3 Click on the Log On tab.

4 If Local System account is not selected as the Log on as account, proceedwith step 8.

5 Provide the name of the account for the system administrator (Windows2008) or the SharePoint administrator (Windows 2003).

6 Type the password.

7 Stop and start the NetBackup Client Service.

8 Close the Services control panel application.

Specifying the account that logs on to theSharePointapplication server

To perform backups and restores, NetBackup must know the user name andpassword of the account for the SharePoint Administrator account. NetBackupalso requires this information so you can browse for SharePoint objects when youcreate a backup policy. NetBackup validates the user name and password youprovide.

This account must meet the following requirements:

■ The logon account you use for backups and restores of SharePoint Server datamust have local administrative rights on the servers where the SharePointcomponents are installed. Additionally, to restore individual documents inbackward-compatible document libraries, the account must be granted theCoordinator role in SharePoint. This role must be applied to all folders to beaccessed in the workspace library or document library.

Configuring NetBackup for SharePoint ServerConfiguring the log on account for the NetBackup Client Service

44

■ The logon account should have the “Replace process level token” local securityprivilege on the servers which have the content of the SharePoint farm. Thisprivilege is necessary since the NetBackup agent logs on as the SharePointuser when it accesses data. After this local security policy privilege is allowedfor the account, run gpupdate /Force (group policy update) for this changeto take effect.

■ Front-end servers and back-end hosts need to have certain privileges. Theback-end client has to have registry access to the front-end server.

■ The credentials of the logon account that is used for backups and restores ofthe Single Sign-on database can be the account name. Or the credentials canbe a member of the group for that account. (See the “Account name” box inthe “Single Sign-on Settings”. These settings are located on the “ManageSettings for the Single Sign-on administration” page that is in SharePointServer.)

■ Internet Information Services (IIS) rights can affect database backups andrestores. Ensure that the logon account that is used for backups and restoreshas rights to access the IIS sites. Integrated Windows Security should beenabled within the IIS rights.

To specify the logon account for the SharePoint application server

1 Open the NetBackup Administration Console.

2 Expand Host Properties.

3 Click on Clients.

4 In the right pane, right-click on the client and click Properties.

5 In the left pane, expand Windows Client and click SharePoint.

6 In the Password box, specify the password for the account.

7 Click OK to save your changes.

Performing consistency checksYou can perform consistency checks of the SQL Server database(s) beforeNetBackup begins a backup operation. These checks are performed for bothserver-directed and user-directed backups.

45Configuring NetBackup for SharePoint ServerPerforming consistency checks

To perform consistency checks

1 Open the NetBackup Administration Console.

2 Expand Host Properties.

3 Click on Clients.

4 In the right pane, right-click on the client and select Properties.

5 In the left pane, expand Windows Client and click SharePoint.

6 From the Consistency check before backup list, choose which checkNetBackup should perform before backups.

See Table 4-1 for descriptions of these options.

If you choose to perform a consistency check, you can select Continue withbackup if consistencycheck fails. NetBackup then continues to perform thebackup if the consistency check fails.


About consistency check optionsTable 4-1 lists the consistency checks can be performed before a backup.

Table 4-1 Description of Consistency options

DescriptionOption

Do not perform consistency checking.None

Select this option to exclude indexes from the consistency check.If indexes are not checked, the consistency check runs significantlyfaster but is not as thorough. Only the data pages and clusteredindex pages for each user table are included in the consistencycheck. The consistency of the non-clustered index pages is notchecked.

Full check, excludingindexes

Include indexes in the consistency check. Any errors are logged.Full check, includingindexes

Select this option to perform a low overhead check of the physicalconsistency of the SQL Server 2000 database. This option onlychecks the integrity of the physical structure of the page headersand record headers. It also checks the consistency between thepages’ object ID and index ID and the allocation structures.

Physical check only(SQL 2000 only)

Configuring NetBackup for SharePoint ServerAbout consistency check options

46

Configuring restores for multiple SharePoint Serverhosts

NetBackup catalogs backup images under the SharePoint front-end server name.To allow NetBackup to restore SQL databases to the correct hosts in a farm, youmust provide a list of the SharePoint hosts. Set the following configurationparameters in the host properties for the master server.

To configure restores for multiple SharePoint hosts

1 On the master server, open the NetBackup Administration Console.

2 Select Host Properties > Master Servers.

3 In the right pane, double-click on the master server.

4 Select SharePoint Hosts.

5 Click Add.

6 For one of the hosts in the farm, provide the name of the front-end host andthe name of the component host in the farm.

7 Repeat step 5 and step 6 for each host in the farm.

8 If the back-end server is a clustered SQL host, add the virtual name and thephysical node names that the server can run on in the cluster.

About configuring backups that use GranularRecovery Technology (GRT)

To configure backups that use Granular Recovery Technology (GRT), review thefollowing information and configuration steps.

■ Review the types of backups that are supported.See “About the types of SharePoint Server backups” on page 58.

■ Review the limitations and conditions.See “About limitations and conditions for restores using Granular RecoveryTechnology (GRT)” on page 50.

■ Configure a backup policy.See “About configuring a backup policy for a SharePoint database” on page 50.

47Configuring NetBackup for SharePoint ServerConfiguring restores for multiple SharePoint Server hosts

About non-granular backups vs. backups that use Granular RecoveryTechnology (GRT)

Non-granular backups allow the restore of SharePoint objects at the level of WebApplication or portal, team site, portal databases, and the Single Sign-on database.The backward-compatible document libraries and the backward-compatibledocument library store can also be restored from non-granular backups. Individualitems cannot be restored from non-granular backups.

To restore individual items using Granular Recovery Technology (GRT), NetBackupperforms a granular-level backup of the SharePoint Web Application, portal, andteam site content. You can restore the entire database or you can restore itemsindividually. Items can then be restored to the existing Web Application or portal,team site, or redirected to a file system location. Individual items are catalogedfor restore browsing and for recovery on a granular-level backup image.

Note: The farm databases (Configuration, Single Sign-on, Index Files or Indexdatabase) cannot be backed up with a policy that is enabled for individual itemrestores. For comprehensive farm disaster recovery, back up those databases witha separate policy where individual document restores are disabled.

Table 4-2 describes what objects can be restored with non-granular andgranular-level backups.

Table 4-2 SharePoint Server 2007 non-granular backups vs. backups that useGranular Recovery Technology

Can be restored from abackup that usesGranular RecoveryTechnology

Can be restored from anon-granular backup

Object

NoYesConfiguration database

NoYesSingle Sign-on database

NoYesGlobal Settings

NoYesIndex Files

YesYesShared Services

YesYesWeb Applications

YesNoIndividual documents

Configuring NetBackup for SharePoint ServerAbout configuring backups that use Granular Recovery Technology (GRT)

48

Table 4-3 describes what objects can be restored with non-granular andgranular-level backups.

Table 4-3 SharePoint Server 2003 non-granular backups vs. backups that useGranular Recovery Technology

Can be restored from abackup that usesGranular RecoveryTechnology

Can be restored from anon-granular backup

Object

NoYesConfiguration database

NoYesIndex database

YesYesPortal

YesYesTeam site

YesYesPortal databases

NoYesSingle Sign-on database

NoYesBackward-compatible documentlibraries

NoYesBackward-compatible documentlibrary store

YesNoIndividual documents

About disk storage units supported for restores using GranularRecovery Technology (GRT)

You can only perform restores of individual items using Granular RecoveryTechnology (GRT) if the backup resides on a disk storage unit. If you configurebackups to a disk storage unit, no further configuration is required. If you configurebackups to tape, you must copy the backup image to a disk storage unit beforeyou can restore individual items. Use the bpduplicate command to copy theimage to disk storage.

Table 4-4 lists the disk storage units that support Granular Recovery.

Table 4-4 Supported disk storage units

Granular Recovery supportDisk storage unit

YesBasicDisk

49Configuring NetBackup for SharePoint ServerAbout configuring backups that use Granular Recovery Technology (GRT)

Table 4-4 Supported disk storage units (continued)

Granular Recovery supportDisk storage unit

YesAdvancedDisk

NoNearStore

NoOpenStorage

YesPureDisk

NoSharedDisk

NoSnapVault

About limitations and conditions for restores using Granular RecoveryTechnology (GRT)

The following limitations and conditions exist for jobs using Granular RecoveryTechnology (GRT):

■ The feature is limited to certain versions of SharePoint Server and WindowsServer.See “About supported SharePoint Server configurations for the backups thatuse Granular Recovery Technology (GRT)” on page 26.

■ The master server(s), media server(s), and clients need to have NetBackup6.5.4.

■ This feature only supports full and user-directed backups. NetBackup lets youcreate a complete policy for disaster recovery, with all the various types ofschedules. However, an incremental schedule produces a backup image thatcan only be used for database recovery.

■ Backups must be made to a disk storage unit, not to tape, and restores that useGRT must be made from a disk storage unit. You can manually duplicate thebackup image to disk, but you cannot restore from the tape copy.

About configuring a backup policy for a SharePointdatabase

A backup policy for a database defines the backup criteria for a specific group ofone or more clients.

These criteria include the following:

Configuring NetBackup for SharePoint ServerAbout configuring a backup policy for a SharePoint database

50

■ Storage unit and media to use

■ Policy attributes

■ Backup schedules

■ Clients to be backed up

■ Items (database objects) to be backed up

To back up a SharePoint or WSS environment, define at least one MS-SharePointpolicy with the appropriate schedules. A configuration can have a single policythat includes all clients, or there can be many policies, some of which include onlyone client.

Most requirements for database policies are the same as for file system backups.In addition to the policy attributes for this database agent, other attributes areavailable that you should consider.


To add and configure a policy, see the following procedures:

■ See “Adding a new policy” on page 54.

■ See “Adding schedules to a NetBackup for SharePoint Server policy” on page 56.

■ See “Adding clients” on page 60.

■ See “Creating a backup selections list for a SharePoint Server policy”on page 61.

Policy recommendations for SharePoint Server 2007Refer to the following recommendations when you create policies:

■ For recovery purposes, perform a farm-level backup of SharePoint Server.

■ Exclude the Index Files from incremental backups in this policy (inTable 4-5, see Policy A-1). Or exclude the Index Files from both full andincremental backups and instead back up that database in a separate policy(in Table 4-5, Policy A-2).

■ Do not enable the “Enable granular recovery” option on the policy attributespage. The purpose of this policy is to create an image that contains theentire SharePoint installation.

■ To fully protect SharePoint Server 2007, create an MS-Windows-NT policy.This policy should include the filesystem where SharePoint Web parts can beinstalled and System State directive (Shadow Copy Components). Exclude anydatabases from this filesystem policy; they are included in the SharePoint

51Configuring NetBackup for SharePoint ServerAbout configuring a backup policy for a SharePoint database

policy backup. A backup of the System State protects the IIS metadata. (InTable 4-5, see Policy B.)

■ To restore individual items using Granular Recovery Technology (GRT), createa policy for each individual Web Application. Enable the “Enable granularrecovery” option. (In Table 4-5, see Policy C.)

Table 4-5 describes the policies you can create to back up SharePoint Server 2007.

Table 4-5 NetBackup policy examples for SharePoint Server 2007

Other configurationEnabledocumentrestore

Auto backupfrequency

Backup selectionsPolicy andpolicy type

Include the Index Files in the fullfarm backup and exclude theIndex Files from the farmincremental backups. Adddirectives for individual IndexFiles to the Exclude list:

Microsoft SharePointResources:\Web Applicationname\Index-DB*

To back up the Index with aseparate policy, see Policy A-2.

NoWeekly Full

Daily Incremental

Microsoft SharePointResources:\*

Policy A-1

MS- SharePoint

Optionally, you can back up theIndex Files with this separatepolicy. Exclude the Index Filesfrom the full and incrementalfarm backups (Policy A-1). Adddirectives for individual IndexFiles to the Exclude list:

Microsoft SharePointResources:\Web Applicationname\Index-DB*

NoWeekly FullMicrosoft SharePointResources:\Web Applicationname\Index-DB*

Policy A-2

MS-SharePoint

Exclude any databases from thispolicy. Add the paths for anydatabases to the Exclude list.

NoDaily Incremental

Weekly Full

Shadow Copy Components:\

ALL_LOCAL_DRIVES

Policy B

MS-Windows-NT


52

Table 4-5 NetBackup policy examples for SharePoint Server 2007 (continued)




To restore individual items usingGRT, create a separate policy withthe “AllWebs” directive or createa separate policy for each WebApplication. The backup imagemust reside on a disk storage unit.

YesWeekly FullMicrosoft SharePointResources:\AllWebs

Microsoft SharePointResources:\Web Applicationname

Policy C

MS-SharePoint

Policy recommendations for SharePoint Server 2003Refer to the following recommendations when you create policies:

■ For recovery purposes, perform a farm-level backup of SharePoint Server.

■ Exclude the Index database from incremental backups in this policy (inTable 4-6, see Policy A-1). Or exclude the Index database from both full andincremental backups and instead back up that database in a separate policy(in Table 4-6, Policy A-2).

■ Do not enable the “Enable granular recovery” option on the policy attributespage. The purpose of this policy is to create an image that contains theentire SharePoint installation.

■ To fully protect SharePoint Server, create an MS-Windows-NT policy. Thispolicy should include the filesystem where SharePoint Web parts can beinstalled and System State directive (Shadow Copy Components). However, becareful to exclude backing up any databases using the filesystem policy; theyare included in the SharePoint policy backup. A backup of the System Stateprotects the IIS metadata. (In Table 4-6, see Policy B.)

■ To restore individual items using Granular Recovery Technology (GRT), createa policy for each individual portal. Enable the “Enable granular recovery”option. (In Table 4-6, see Policy C.)

■ Create a separate policy for the backward-compatible document store and forthe backward-compatible document libraries. (In Table 4-6, see Policy D andPolicy E.)

Table 4-6 describes the policies you can create to back up SharePoint Server 2003.


Table 4-6 NetBackup policy examples for SharePoint Server 2003




Exclude the Index database fromincremental backups. Add thedirective for an individual Indexdatabase to the Exclude list:

Microsoft SharePointResources:\http://Portalname\Index DB*

NoDaily Incremental

Weekly Full

Microsoft SharePointResources:\*

Policy A-1

MS-SharePoint

Optionally, you can back up theIndex database with this separatepolicy. Exclude the Index databasefrom the full and incrementalfarm backups (Policy A-1). Adddirectives for individual Indexdatabase to the Exclude list:

Microsoft SharePointResources:\Portalname\Index DB*

NoWeekly FullMicrosoft SharePointResources:\http://Portalname\Index DB*

Policy A-2

MS-SharePoint

Exclude any databases from thispolicy. Add the paths for anydatabases to the Exclude list.

NoDaily Incremental

Weekly Full

Shadow Copy Components:\

ALL_LOCAL_DRIVES

Policy B

MS-Windows-NT

To restore individual items usingGRT, create a separate policy foreach portal. The backup imagemust reside on a disk storage unit.

YesWeekly FullMicrosoft SharePointResources:\http://Portalname

Policy C

MS-SharePoint

NoWeekly FullMicrosoft SharePointResources:\DocumentLibrary Store*

Policy D

MS-SharePoint

YesDaily Incremental

Weekly Full

Microsoft SharePointResources:\DocumentLibraries*

Policy E

MS-SharePoint

Adding a new policyThis topic describes how to add a new backup policy for a database.


54

To add a new policy

1 Log on to the master server as administrator (Windows) or root (UNIX).

2 Start the NetBackup Administration console.

3 If your site has more than one master server, choose the one on which youwant to add the policy.

4 (Windows interface) In the left pane, right-click Policies and choose NewPolicy.

5 (Java interface) In the left pane, click Policies. In the All Policies pane,right-click the master server, and click New Policy.

6 In the Add a New Policy dialog box, in the Policy name box, type a uniquename for the new policy.

7 Click OK.

8 In the Add a New Policy or Change Policy dialog box, in the Policy type list,select the MS-SharePoint policy type.

The database agent policy type does not appear in the drop-down list unlessyour master server has a license key for the database agent.

9 Complete the entries on the Attributes tab.

See “About policy attributes” on page 55.

10 Add other policy information as follows:

■ Add schedules.Adding schedules to a NetBackup for SharePoint Server policy

■ Add clients.See “Adding clients” on page 60.

■ Add database objects to the backup selections list.See “Creating a backup selections list for a SharePoint Server policy”on page 61.

11 When you have added all the schedules, clients, and backup selections youneed, click OK.

About policy attributesWith a few exceptions, NetBackup manages a database backup like a file systembackup. Other policy attributes vary according to your specific backup strategyand system configuration.

For more information on policy attributes, see the NetBackup Administrator’sGuide, Volume I.


Table 4-7 shows the policy attributes that are different for SharePoint backups.

Table 4-7 Policy attribute descriptions

DescriptionAttribute

Determines the types of clients that can be in the policy. In somecases the policy type determines the types of backups thatNetBackup can perform on those clients. To use the databaseagent, you must define at least one policy of type that isMS-SharePoint.

Policy type

Limits the number of jobs that NetBackup performs concurrentlywith this policy. Set this option to 1 for the policies that are usedto back up SharePoint databases.

Limit jobs per policy

Checkpoint restart is not supported with NetBackup for SharePointServer policies.

Take checkpointsevery

For SharePoint policies, do not select this option. SharePointpolicies do not support multiple data streams.

Allow multiple datastreams

Allows restores of individual items using Granular RecoveryTechnology (GRT). Documents external to the document librarysuch as lists, calendars, and discussion boards cannot be restoredindividually. Users can only restore individual items from a fullbackup.

You can restore individual items only if the backup image resideson a disk storage unit. Special configuration is required if youwant to back up images to tape.

See “About disk storage units supported for restores usingGranular Recovery Technology (GRT)” on page 49.

SharePoint Server GRT-enabled backups do not support encryptionor compression, .

Enable granularrecovery

A textual description of a backup. Useful for browsing backupsand restores.

Keyword phrase

Adding schedules to a NetBackup for SharePoint Server policyEach policy has its own set of schedules. These schedules control the initiationof automatic backups and also specify when user operations can be initiated.


56

To add a schedule

1 In the Policy dialog box, click the Schedules tab.

To access the Policy dialog box, double-click the policy name in the Policieslist in the NetBackup Administration Console.

2 Click New.

3 Specify a unique name for the schedule.

4 Select the Type of backup.

See “About the types of SharePoint Server backups” on page 58.

5 Choose a frequency level appropriate for the type of backup.

See “Policy recommendations for SharePoint Server 2007” on page 51.

See “Policy recommendations for SharePoint Server 2003” on page 53.

6 Specify the other properties for the schedule.

See “About schedule properties” on page 57.

7 Click OK.

About schedule propertiesSome of the schedule properties have a different meaning for database backupsthan for a regular file system backup.

Table 4-8 explains the schedule properties.

Table 4-8 Description of schedule properties

DescriptionProperty

Specifies the type of backup that this schedule controls. Theselection list shows only the backup types that apply to the policyyou want to configure.

See “About the types of SharePoint Server backups” on page 58.

Type of backup

This setting is used only for scheduled backups and not foruser-directed backups. Frequency specifies the period of time thatcan elapse until the next backup or archive operation begins onthis schedule. For example, assume that the frequency is sevendays and a successful backup occurs on Wednesday. The next fullbackup does not occur until the following Wednesday. Typically,incremental backups have a shorter frequency than full backups.

Frequency


Table 4-8 Description of schedule properties (continued)

DescriptionProperty

This setting is used only for scheduled backups. It is not used foruser-directed backups. The Calendar option allows you to schedulebackup operations that are based on specific dates, recurring weekdays, or recurring days of the month.

Calendar

Other schedule properties vary according to your specific backup strategy andsystem configuration.

For more information on schedule properties, consult the NetBackupAdministrator’s Guide, Volume I.

About the types of SharePoint Server backupsTable 4-9 describes the type of backups available with the SharePoint agent.

Table 4-9 Description of types of backups

DescriptionType of Backup

Select this back up type to back up the entire SharePointcomponent database(s). Granular-level backups must be backedup with a full backup. A list is available for the objects that supportfull backups.

For SharePoint 2007, see Table 4-10.


Full Backup

A user backup is not automatically scheduled and is initiated fromthe front-end Web server.

You may want to consider creating a separate policy for UserBackup schedule types. With a separate policy, you can easilyseparate user-directed and scheduled backups when you restorefiles. If you decide to create separate policies for User Backupschedule types, the considerations are similar to those forautomatic backups. A Backup Selections list is not needed becauseusers select the files before the backup begins.

User Backup

This type of backup is not supported for SharePoint Server.CumulativeIncremental backup


58

Table 4-9 Description of types of backups (continued)

DescriptionType of Backup

Select this backup type to only back up the changes that are madeto the database since the last full backup or previous incrementalbackup. A list is available for the objects that support incrementalbackups.



Note: By default, the backward-compatible document store usescircular logging, which does not support differential backups. Ifthe backward-compatible document store is included in this typeof schedule, the Full backup method is instead used to back upthese resources.

Note: The SharePoint 2003 Index database and the SharePoint2007 Shared Search Index database and Index Files only supportfull backups. Therefore, Symantec recommends that thesedatabases are excluded from the differential incremental schedule.If these databases are included in this type of schedule, a fullbackup is performed as part of the incremental backup.

Note: Incremental backups are not supported for granular-levelbackups.

DifferentialIncremental backup

Table 4-10 describes the schedule types supported for SharePoint Server 2007and WSS objects.

Table 4-10 Schedule types supported for SharePoint Server 2007 and WSSobjects

Schedule typeSharePoint 2007/WSS objects

Full Backup, Differential Incremental backupConfiguration DB

Full Backup, Differential Incremental backupGlobal Settings

Full Backup, Differential Incremental backupSingle Sign-on

Full BackupWeb Appplication/Content DB/ (includingindividual document restores)

Full BackupWSS Help Search/Index Files

Full Backup, Differential Incremental backupWSS Help Search/Search DB

Full Backup, Differential Incremental backupWSS Administration/Web App/Content DB


Table 4-10 Schedule types supported for SharePoint Server 2007 and WSSobjects (continued)

Schedule typeSharePoint 2007/WSS objects

Full Backup, Differential Incremental backupShared Services/Services DB

Full BackupShared Services/Shared Search Index/IndexFiles

Full Backup, Differential Incremental backupShared Services/Shared Search Index/Search DB

Full Backup, Differential Incremental backupShared Services/Web App/Content DB

Table 4-11 describes the schedule types supported for SharePoint Server 2003and WSS objects.

Table 4-11 Schedule types supported for SharePoint Server 2003 and WSSobjects

Schedule typeSharePoint 2003 /WSS objects

Full Backup, Differential Incremental backupConfiguration database

Full Backup, Differential Incremental backupSingle Sign-on database

Full Backup, Differential Incremental backupPortal sites

Full Backup, Differential Incremental backupContent databases

Full Backup, Differential Incremental backupUser Profile database

Full Backup, Differential Incremental backupServices database

Full BackupIndex databases

Full Backup, Differential Incremental backupTeam databases

Adding clientsThe clients list contains a list of the clients that are backed up during an automaticbackup. A NetBackup client must be in at least one policy but can be in more thanone.

The NetBackup client software must be installed on each front-end Web serverand SQL database host, Index Files, or Index database host and on the server withthe backward-compatible document library store. The client software does notneed to be installed on the Search or Job servers.


60

To add clients to a policy

1 In the Policy dialog box, click the Clients tab.

To access the Policy dialog box, double-click the policy name in the Policieslist in the NetBackup Administration Console .

2 Click New.

3 (Windows interface) Type the name of the client and press Enter.

If NetBackup cannot detect the hardware and the operating system, a dialogbox appears so you can specify this information.

Only add the client that is the front-end Web server and knows about theSharePoint farm topology to the policy list.

4 (Java interface) Type the name of the client you want to add.

Only add the client that is the front-end Web server and knows about theSharePoint farm topology to the policy list.

The following options are available when you add a client:

Type the name of the client you want to add.Client name

Choose the applicable hardware and operating system of theclient.

Hardware andoperating system

5 (Java interface) Click Add.

6 (Java interface) To add another client, repeat steps 2, 4, and 5.

7 (Windows) To add another client, repeat step 2 and 3.

8 If this client is the last client, click OK.

Creating a backup selections list for a SharePoint Server policyThe backup selections list defines the SharePoint objects to be backed up. Youcan specify the entire farm or back up individual SharePoint components, suchas a Single Sign-on , Configuration, or Content database. For Windows SharePointServices (WSS) installation, you can back up all the WSS team sites or an individualWSS team site.

Symantec recommends that you create backup selections with the browse feature.Because SharePoint objects have long names, it is easy to mistype the object namewhen you create backup selections by adding and editing directives. One exceptionis the Microsoft SharePoint Resources:\AllWebs directive. Use this directiveto back up all Web applications or portals. You do not need to add a separatebackup selection for each Web application or portal.


To browse for the SharePoint objects, you must provide the credentials for theaccount that logs on to the SharePoint Server.

See “Specifying the account that logs on to the SharePoint application server ”on page 44.

Note: SharePoint policies do not support multiple data streams.

This topic includes the following procedures:

■ To create a backup selections list to back up SharePoint Server objects

■ To create a backup selections item for all Web applications or portals

To create a backup selections list to back up SharePoint Server objects

1 In the Policy dialog box, click the Backup Selections tab.

2 Click New.

3 Click the folder icon to browse for a SharePoint object.

4 In the left pane, expand the client and select the object you want to back up.

If you selected Enable granular recovery on the Attributes tab, the displayis limited to Web applications or portals.

5 Click OK.

6 Repeat step 2 through step 5 for each object you want to add.

To create a backup selections item for all Web applications or portals

1 In the Policy dialog box, click the Backup Selections tab.

2 Click New.

3 Click in the edit box and type Microsoft SharePoint Resources:\AllWebs.

This directive works for both SharePoint 2007 Web applications and forSharePoint 2003 portals. It is only supported for NetBackup 6.5.4 and later.

Testing configuration settingsAfter you configure the master server for NetBackup for SharePoint Server, testthe configuration settings. Perform a manual backup (or backups) with theautomatic backup schedules you created. A description of status codes and othertroubleshooting information is available.

See the NetBackup Troubleshooting Guide.

Configuring NetBackup for SharePoint ServerTesting configuration settings

62

To test the configuration settings

1 Log onto the master server as administrator (Windows) or root (UNIX).

2 Start the NetBackup Administration Console .

3 In the left pane, click Policies.

4 Click the policy you want to test.

5 Select Actions > Manual Backup.

The Schedules pane contains the name of an automatic schedule (or schedules)configured for the policy that you want to test. The Clients pane contains thename of the client(s) listed in the policy that you want to test.

6 Follow the directions in the Manual Backup dialog box.

7 To check the status of the backup, click Activity Monitor in the NetBackupAdministration Console.

A parent job contains the whole file list and one or more child jobs. A childjob is automatically launched for each host that contains SharePoint data.For example, assume that a SharePoint farm consists of four separate hosts.In this case, one parent job and four child jobs appear in the Activity Monitor.The front-end Web server is listed as the client name for all jobs.

See “About troubleshooting” on page 97.

63Configuring NetBackup for SharePoint ServerTesting configuration settings

Configuring NetBackup for SharePoint ServerTesting configuration settings

64

Performing backups andrestores of SharePointServer and WindowsSharePoint Services


■ About NetBackup for SharePoint Server backup and restores

■ About user-directed backups of SharePoint Server and Windows SharePointServices

■ About restores of SharePoint Server and Windows SharePoint Services

About NetBackup for SharePoint Server backup andrestores

With the NetBackup for SharePoint agent, the user can perform user-directedbackups and restores of SharePoint Server components. Users can restoreindividual items from the backups that use Granular Recovery Technology (GRT).

5Chapter

About user-directed backups of SharePoint Serverand Windows SharePoint Services

User-directed backups of SharePoint Server must be performed from the front-endWeb server. Back up the Content, Services, and User Profile databases together.Also select the Configuration database when you back up a portal.

If you chose to perform consistency checks, these checks are also performed beforeuser-directed backups.

See “Performing consistency checks” on page 45.

Note: If you open multiple backup windows (in the NetBackup client) to browseSharePoint resources, the windows may unexpectedly terminate. Instead, use asingle backup window to browse SharePoint resources for backup.

Specifying the server and client for a SharePoint Server backupoperation

When you perform user backups of SharePoint Server, you must specify the serverthat you want to perform the backups.

To specify the server and client for a backup operation

1 Log onto the server as Administrator.

2 Open the Backup, Archive, and Restore interface.

3 Select File > Specify NetBackup Machines and Policy Type.

4 In the Specify NetBackup Machines and Policy Type dialog box, provide thefollowing information:

Select the server you want to perform the backup.Server to use for backupsand restores

Select the client you want to back up.Sourceclientforrestores(orvirtual client for backups)

5 Click OK.

About backup options for NetBackup for SharePointTable 5-1 lists the options that are available when you perform backups ofSharePoint Server.

Performing backups and restores of SharePoint Server and Windows SharePoint ServicesAbout user-directed backups of SharePoint Server and Windows SharePoint Services

66

Table 5-1 Backup options

DescriptionOption

Identify the NetBackup server that you want to perform thebackup.

Backup to NetBackupserver

Contains a list of objects to be backed up.Items marked to bebacked up

Specify a keyword phrase, up to 128 characters in length, thatNetBackup can associate with the image created by this backupoperation. You then can restore the image by specifying thekeyword phrase in the Search Backups dialog box.

All printable characters are permitted including space (" ") andperiod ("."). The default keyword phrase is the null (empty)string.

Keyword phrase toassociate with thebackup or archive

Performing a user-directed backup of SharePoint Server or WindowsSharePoint Services

This topic describes how to perform a user-directed backup of SharePoint Serveror Windows SharePoint Services.

To back up SharePoint resources

1 Log onto the server as Administrator.


3 Choose File > Select Files and Folders to Backup.

4 In the Backup window, in the All Folders pane, expand MicrosoftSharePointResources.

5 Select the object(s) to back up.

6 Choose Actions > Backup.

See “About backup options for NetBackup for SharePoint” on page 66.

7 In the Backup Files dialog box, click Start Backup.

If you want to view the progress of the backup, click Yes. If you do not wantto view the progress of the backup, click No.

67Performing backups and restores of SharePoint Server and Windows SharePoint ServicesAbout user-directed backups of SharePoint Server and Windows SharePoint Services

About restores of SharePoint Server and WindowsSharePoint Services

Note the following when you perform restores:

■ Administer restores from the NetBackup master server or the SharePointfront-end server.

■ When you select items for restore, select the items from the Contents of pane,not the All Folders pane.

■ Note that during a SharePoint 2003 portal recovery, a two-minute delay occursbefore the Index Files or the Index database is restored. This delay allowspreviously restored databases to be committed.

■ The Configuration database contains all of the configuration information forthe entire SharePoint server farm . Use caution when you restore this database;upon restore, any changes are lost that you made to the farm topology afterthe backup was performed.

Refer to the following instructions and information when you restore SharePointServer:

■ See “Specifying the server, client, and the policy type for a SharePoint Serverrestore operation” on page 69.

■ See “Restore options for SharePoint Server” on page 69.

■ See “How the NetBackup Recovery Assistant restores SharePoint Server andWindows SharePoint Services” on page 73.

■ See “Restoring SharePoint Server or Windows SharePoint Services” on page 74.

■ See “Restoring the SharePoint 2007 Shared Services Provider when in a stateof unprovisioning” on page 76.

■ See “Restoring individual SharePoint items from full database backups”on page 77.

■ See “Redirecting a restore of a SharePoint Web application, portal site, or teamsite” on page 81.

■ See “Redirecting individual SharePoint items to a file path” on page 84.

■ See “Redirecting the restore of a SharePoint 2001 document library orworkspace” on page 91.

■ See “Recovering a SharePoint 2007 Web application in a Network LoadBalancing farm” on page 80.

Performing backups and restores of SharePoint Server and Windows SharePoint ServicesAbout restores of SharePoint Server and Windows SharePoint Services

68

Specifying the server, client, and the policy type for a SharePoint Serverrestore operation

To browse for and restore SharePoint backups, specify the following items:

■ The server that performed the backups

■ The SharePoint front-end client that was backed up

■ The SharePoint policy type

To specify the server, client, and policy type for a SharePoint Server restoreoperation

1 Click File > Specify NetBackup Machines and Policy Type.

2 In the Specify NetBackup Machines and Policy Type dialog box, from theServer touse forbackupsandrestores list, select the NetBackup server thatperformed the backup.

3 From the Source client for restores list, select the client.

The source client is the SharePoint Server computer name whose backupimages you would like to browse.

4 From the Policy type for restores list, choose MS-SharePoint.

5 Click OK.

Restore options for SharePoint ServerThe following options are available when you restore SharePoint Server orWindows SharePoint Services:

■ See “General tab” on page 69.

■ See “Microsoft SharePoint tab” on page 70.

General tabThe options on this tab are not supported for the NetBackup for SharePoint agent.

If you want to redirect a Web application, portal, or team site, you need to followa different procedure.

See “Redirecting a restore of a SharePoint Web application, portal site, or teamsite” on page 81.

See “Microsoft SharePoint tab” on page 70.

69Performing backups and restores of SharePoint Server and Windows SharePoint ServicesAbout restores of SharePoint Server and Windows SharePoint Services

Microsoft SharePoint tabOn this tab you can choose to bring databases online after a restore job. You canalso specify a different location to which to redirect a Web application, portal site,team site, or document library. The farm and the Web application, portal, or teamsite to which you want to redirect the restore must already exist.

Table 5-2 describes the options available on the Microsoft SharePoint tab.

Table 5-2 Microsoft SharePoint tab

DescriptionOption

Select this option to bring the databases online after a restore job. This option alsore-establishes the link between the restored databases and their corresponding Webapplications, portals, or team sites.

Bring restoreddatabases online andreconnect previousdatabase links

This option applies to SharePoint 2003 only. Check this option to have NetBackup releasethe lock on the SharePoint farm topology before you run the backup or restore operation.Because another application may have locked the topology, check with your SharePointadministrator before you select this option.

Release the lock on theSharePoint farmtopology, if it is set.

This option applies to SharePoint 2007 only. If the Web site and application pool for theSharePoint Web application that you restore already exists in IIS, this option preservesthem during restore. If you do not check this option, the Web site and application pool aredeleted from IIS during the restore. After they are deleted, they are recreated in the defaultlocation that SharePoint specifies.

Preserve existingInternet InformationServices (IIS) Web siteand application pool.


70

Table 5-2 Microsoft SharePoint tab (continued)

DescriptionOption

If versioning is enabled on the destination to which you want to restore an individual itemor document, select one of the following options:

■ Add as a new version

NetBackup restores the existing item or document as a new version, which makes it themost recent version of the existing item. For example, assume that you have five versionsoftestfile.doc and choose to restore version 2.0 of the file. When the file is restored,it is added as testfile.doc 6.0 and is the most recent version.

■ Skip if the item exists

NetBackup does not restore the item if an identical item or document exists in the restoredestination. NetBackup notes that the file was skipped in the job log.

■ Restore over existing items

NetBackup restores the existing item as a new version and deletes the existing version.

For example, assume that the version history is as follows:

testfile.doc version 3.0testfile.doc version 2.0testfile.doc version 1.0

testfile.doc version 3 is the most recent version. If you choose to restoretestfile.doc version 2.0, the restore adds testfile.doc version 4.0 and deletestestfile.doc version 2.0. So the version history appears as follows:

testfile.doc version 4.0testfile.doc version 3.0testfile.doc version 1.0

testfile.doc version 2.0 is now version 4.0 of the file.

If versioning is enabledon the restoredestination

If versioning is not enabled on the destination to which you want to restore an individualitem, select one of the following options:

■ Skip if the item exists

NetBackup does not restore the item if an identical item exists in the restore destination.NetBackup indicates that the file was skipped in the log.

■ Restore over existing items

NetBackup replaces the existing item with the restored item.

If versioning is notenabled on the restoredestination

Check this option to only restore the most recent version of an item. Note that NetBackuprestores the most recent version of the versions you selected for restore. If a more recentversion exists, but you did not select it for restore that version is not restored.

Restore only the mostrecent version of anitem


Table 5-2 Microsoft SharePoint tab (continued)

DescriptionOption

Check this option to restore any applicable security information with the item. Note thatsecurity information is restored only if you select a parent folder and not when you selectindividual items. For example, security information is restored when you select SharedDocuments, but not if you select an individual document. However, if an individual objecthas any user permissions that are defined with a level of “limited access,” permissions forthose users are not restored with that object.

You can restore different levels of security based on the SharePoint item you restore:

■ Sites

User and SharePoint Group information and security ACL are restored for top-levelsites.

■ Sub-sites

Security ACL is restored.

■ Lists

Security ACL and other security-related information are restored.

Include securityinformation

Check this option to redirect a Web application, portal, or team site.

See “Redirecting a restore of a SharePoint Web application, portal site, or team site”on page 81.

Redirect SharePointResources

To redirect a Web application, portal, or team site, specify the URL of the destination siteand the name of the front-end Web server .

Example URLs include the following:

http://portal

http://team site

http://URL toWeb application

For Web applications, portals, or team sites, indicate the hostname of the Web server towhich you want to redirect. The Web server must already exist on the destination location.

SharePoint 2003 portalsites or SharePoint2007 web applications

You can redirect SharePoint sites, documents, lists or items to a path, a workspace, or adocument library, as follows:

■ Redirect to path

In the Restore to drive or UNC path box, enter the drive letter or UNC Path. Use thefollowing format for a UNC path: \\servername\share.

In the Restore to path box, enter the path to which you want to direct the restore.

■ Redirect to workspace or document library (WebStorageSystem-based only).

This option only applies to SharePoint 2001 restores.

Note that when you direct items to a file system, any list items you selected are not restoredand appear as 0-KB files.

Individual SharePointsites, documents, lists,or items


72

How the NetBackup Recovery Assistant restores SharePoint Serverand Windows SharePoint Services

The NetBackup Recovery Assistant launches a restore job for each database in aWeb application, portal site, or team site. Databases are restored in the properorder to ensure that a working portal exists when the restore is complete. Afterall the databases are restored any items you selected are restored in a single job.If a SharePoint 2003 Index database is restored or redirected with any otherdatabase, the Recovery Assistant pauses the restore process for two minutes. Thepause in the restore lets the commits of the database and the portal site or teamsite to take effect. After the two minutes elapse, the Index database is restored.

For SharePoint 2007, the Recovery Assistant restores objects in the followingorder:

■ Configuration databases (only if assistant is run in disaster recovery mode)

■ Content databases

■ Services databases

■ Index Files

■ Single Sign-on databases

For SharePoint 2003, the Recovery Assistant restores objects in the followingorder:

■ Configuration databases (only if assistant is run in disaster recovery mode)

■ Content databases

■ Services databases

■ User Profile databases

■ Team databases

■ Index databases

■ Single Sign-on databases

■ Document libraries (backward-compatible)

■ Documents, lists, etc.

Objects are skipped if they are not found in the database configuration. Eachrestore may only restore a portion of the components depending on what objectsyou select and the backup image you select. When you restore an item, it does notrestore an entire Content database or Document library.


Restoring SharePoint Server or Windows SharePoint ServicesMultiple SharePoint Server resources can be restored together. The NetBackupRecovery Assistant determines the order in which the resources must be restored.You can restore any of the SharePoint resources in separate restore operations.

Note: NetBackup does not prevent you from restoring placeholders. NetBackupalso lets you restore any object that can hold a document, even if it does not containa document.

To restore SharePoint Server or Windows SharePoint Services

1 Enable the front-end Web server to redirect restores to the SQL hosts in thefarm.

A redirected restore is performed since backups are cataloged under thefront-end client name for the Federated SharePoint farm.

See “Configuring restores for multiple SharePoint Server hosts” on page 47.

2 Log on as Administrator.


4 Choose File > Select Files and Folders to Restore > from Normal Backup.

5 Select the MS-SharePoint policy type.

See “Specifying the server, client, and the policy type for a SharePoint Serverrestore operation” on page 69.

6 Click OK.

NetBackup browses for SharePoint Server backup images.

7 From the NetBackup History pane, select the image(s) that contain the objectsyou want to restore:

■ The last full backup, or

■ The last full backup and all subsequent differential backups

8 In the All Folders pane, expand Microsoft SharePoint Resources.

9 From the Contents of pane, select the SharePoint resources to restore.

10 Choose Actions > Restore.


74

11 In the Restore Marked Files dialog box, click the Microsoft SharePoint tab.

See “Restore options for SharePoint Server” on page 69.

12 Click Start Restore.


Restoring the SharePoint 2007 Shared Services Provider when in astate of unprovisioning

The following instructions describe how to restore the Shared Services Providerwhen it is in a state of unprovisioning.

To restore the SharePoint 2007 Shared Services Provider when in a state ofunprovisioning

1 Delete the Shared Services Provider.

Run the following command:

stsadm -o deletessp -title SSP name -force

2 Open the NetBackup Backup, Archive, and Restore interface.

3 Open a Restore window.

4 Select the Full backup that contains the shared services.

5 From the Contents of pane, select the following objects of the shared services:


■ Search-DB databaseThis database is under Shared Search Index. Do not select the Index Filesfor restore.

■ Shared Services Administration site(s)



8 Uncheck Bringrestoreddatabasesonlineandreconnectpreviousdatabaselinks.


10 Restore any incremental backups. Do not select Bring restored databasesonline and reconnect previous database links.

11 Use the SQL Server administrative tools to recover the SSP databases.

12 In SharePoint Administration interface, use the Shared ServicesAdministration page to reconnect the restored SSP.

About requirements for restores of individual SharePoint itemsThe following requirements must be met to restore individual items from fulldatabase backups:


76

■ The administrator has configured NetBackup to allow for restores of individualitems. This option is on the Attributes tab for the backup policy.See “About policy attributes” on page 55.

■ The user must restore from a full backup image.

■ You can only restore an individual item when the backup image resides on adisk storage unit.See “About disk storage units supported for restores using Granular RecoveryTechnology (GRT)” on page 49.

■ You cannot restore a document or a picture library item when the library orfolder does not exist. The library or folder is not recreated and the item is notrestored. In this situation, redirect the restore to a file system and then uploadthe items into SharePoint Server.

■ Use the Windows client to restore individual items. The NetBackup-Java clientuser interface does not yet support browsing of individual SharePoint itemsfor restore.

Restoring individual SharePoint items from full database backupsYou can restore individual documents, images, and list items from the fullSharePoint database backup jobs that use Granular Recovery Technology (GRT).

Note: For SharePoint Server 2003 and Windows SharePoint Services 2.0, you cannot restore a top-level site from a backup that uses GRT. In this case, you mustrestore the Content database. You can restore libraries, documents, and lists ifthe top-level site exists.

Note: When you restore an item, it is safe to ignore certain bprd errors in theActivity Monitor similar to the following:

7/12/2007 11:01:39 AM - Error bpdm (pid=2928) did not receive EXIT

STATUS from bprd, all blocks may not have been restored

Instead, rely upon the final status that is reported in the Activity Monitor todetermine the true success or failure of the restore operation.


To restore individual SharePoint items from full database backups

1 Enable the Sharepoint front-end Web server to restore to the SQL hosts inthe farm.

See “Configuring restores for multiple SharePoint Server hosts” on page 47.






6 Click OK.

NetBackup browses for SharePoint Server backup images.

7 From the NetBackup History pane, select the full backup image that containsthe items you want to restore.


9 In the Contents of pane, select the item(s) to restore.

Note that security information is restored only if you select a parent folderand not when you select individual items. For example, security informationis restored when you select Shared Documents, but not if you select anindividual document. However, if an individual object has the user permissionsthat are defined with a level of “limited access,” permissions for those usersare not restored with that object.



78


12 Choose your restore options, as follows:


Select one of the following options:

■ Add as a new versionNetBackup restores the existing item as a new version, making it the most recentversion of the existing item.

■ Skip if the item existsNetBackup does not restore the item if an identical item exists in the restoredestination. NetBackup notes that the file was skipped in the job log.

■ Restore over existing itemsIf the version exists, NetBackup removes it and adds the item as a new version.

If versioning is enabled onthe restore destination

Select one of the following options:

■ Skip if the item existsNetBackup does not restore the item if an identical item exists in the restoredestination. NetBackup notes that the file was skipped in the job log.

■ Restore over existing itemsNetBackup replaces the existing item with the restored item.

If versioning is not enabledon the restore destination

Check this option if you only want to restore the most recent versions of any individualitems you have selected for restore.

Restore only the most recentversion of an item

Check this option if you want to restore the SharePoint security information that isattached to the items you restore.


Include security information

13 Select the other restore options you want.



Recovering a SharePoint 2007 Web application in a Network LoadBalancing farm

To restore a deleted web application in a Network Load Balanced (NLB) farm, youmay need to perform a manual operation using the SharePoint 3.0 CentralAdministration interface. After the restore operation is successful, if the Webapplication on the NLB farm is offline, perform the following steps.

To recover a Web application in a Network Load Balancing farm

1 Open the SharePoint 3.0 Central Administration interface.

2 Under Central Administration, click Application Management.

3 Under “SharePoint Web Application Management,” click Create or extendWeb application.


80

4 Select Extend an existing Web application and fill-in the values to extendthe restored Web application.

5 Complete the restore operation on all of the NLB front-end servers.

Make sure that the server is extended on the other NLB servers. In the CentralAdministration interface, select Extend an existing virtual server from theVirtual Server List page.

Redirecting a restore of a SharePoint Web application, portal site, orteam site

In a MOSS installation, a Web application can be redirected to a Web applicationon another Web server in an existing farm. In a WSS installation, a Web applicationcan be redirected to another Web application on the Web server. The target Webapplication where you want to redirect the restore must already exist on thespecified Web server. The target Web application must also have the same databasestructure as the source Web application.

A SharePoint portal site can be redirected to a portal site on another Web serverin an existing farm. A team site can be redirected to another WSS site on the Webserver. The target portal site or team site where you want to redirect the restoremust already exist on the specified Web server. The target portal site or team sitemust also have the same database structure as the source site.

Note the following when you redirect a Web application, portal, or team site:

■ You can only redirect the restore of Web applications, portals, or team sites.You can restore the backward-compatible document store, Configurationdatabases, and Single Sign-on databases back to the original location only.Individual SharePoint items must be restored to their original site.

■ You can redirect a restore of a Web application or portal within the same farm.The SQL database host and the SharePoint host must be the same. A redirectedrestore is not supported if the SQL databases exist across multiple SQL hosts.

■ You must restore all SQL databases in one operation at the same time.

To redirect a Web application, portal site, or team site


2 Create the target Web application, portal site, or WSS site on the target Webserver. The target site must have the same database structure as the sourcesite.


3 Remove the source Web application.

If you attempt the redirected restore without removing the source, the restorecompletes successfully, but the databases are not properly connected to thevirtual server.









9 In the Contents of pane, select the Web application, portal site, or team siteto redirect.

10 Select Actions > Restore.


82


12 Select Redirect SharePoint Resources.

13 Click SharePoint 2003 portal sites or SharePoint 2007 web applications.

14 In the URL box, type one of the following:

■ The URL of the destination site.For example, http://norabl1vm2.

■ The URL of the portal site or team site to which you want to redirect therestore. For example:


http://portalhttp://team site

15 In the Front end web server name box, indicate the hostname of the Webserver.

More information is available on other available restore options.



Redirecting individual SharePoint items to a file pathYou can redirect the restore of SharePoint documents, images, lists and list items,and their versions. Individual items can only be redirected to a file location, notanother content database.

To redirect individual SharePoint items to a file path






5 From the NetBackup History pane, select the full backup image that containsthe objects you want to restore. You can not restore individual items from abackup that did not use Granular Recovery Technology.


7 Select the documents, images, lists, or list items you want to redirect.




11 Click Individual SharePoint sites, documents, lists, or items.

12 Click Redirect to path


84

13 In the Restore to drive or UNC path and Restore to path boxes, enter thedrive letter and path to which you want to direct the restore. Use the followingformat for a UNC path:

\\servername\share





About restoring deleted sub-sites or top-level sitesIn some situations Web Parts are not restored or do not function correctly fromthe backups that use Granular Recovery Technology (GRT).

Consider the following scenario:

■ You delete a sub-site or top-level site that has Web Parts

■ You restore the site from a backup using GRT

In this scenario, the Web Parts are not restored. To successfully restore the site,do one of the following:

■ Re-register the Web Parts on the sub-site or top-level site. Ensure that the safecontrols are defined in the web.config file for the sub-site or top-level site.

■ Restore the Content database. This restore recreates the Web Parts.


86

Recoveringbackward-compatibledocument library objects


■ About recovering backward-compatible document libraries

■ Restoring the backward-compatible document store

■ Restoring the backward-compatible document libraries

■ Restoring versioned documents (in the backward-compatible documentlibraries) to the documents folder

■ Restoring other file revisions

■ Rebuilding restored revisions of a document

■ Redirecting the restore of a SharePoint 2001 document library or workspace

About recovering backward-compatible documentlibraries

These topics only apply to SharePoint 2001 document repositories that have beenmigrated into SharePoint 2003. These repositories are called backward-compatibledocument libraries”. These topics do not apply to newly created document librariesin SharePoint 2003 or 2007.

6Chapter

Restoring the backward-compatible document storeThe backward-compatible document store can be restored to SharePoint 2003. Inthe SharePoint 2003 agent, the document library store appears under MicrosoftSharePoint Resources.

Caution:When you restore data from a backward-compatible document Store, alldata on the existing document store is overwritten.

To restore the backward-compatible document store


2 Ensure that the Microsoft Information service is running.



5 Select the SharePoint policy type (choose File>SpecifyNetBackupMachinesand Policy Type).

6 From the NetBackup History pane, select the image contain the objects youwant to restore.


8 Select Document Library Store.



Restoring the backward-compatible documentlibraries

Backward-compatible document libraries can be restored to SharePoint 2003.NetBackup can restore the Documents or Portal or Shadow folders, or individualfolders in those directories, from a document libraries backup. In the SharePoint2003 agent, the document libraries appear under Microsoft SharePoint Resources.

If you want to restore the Shadow folder, follow the instructions to restoreversioned documents.

See “Restoring versioned documents (in the backward-compatible documentlibraries) to the documents folder” on page 89.

Recovering backward-compatible document library objectsRestoring the backward-compatible document store

88

Note:NetBackup does not restore a document if it already exists in the destinationfolder. In this case, you can redirect the restore to a different location.

To restore the backward-compatible document libraries




4 Select the SharePoint policy type (choose File>SpecifyNetBackupMachinesand Policy Type).

5 From the NetBackup History pane, select the image that contain the objectsyou want to restore.


7 Expand Document Libraries.

8 Select a document library to restore.




Restoring versioned documents (in thebackward-compatible document libraries) to thedocuments folder

A backup of the Documents folder contains only the latest published version ororiginal version (if not published) of the files. To restore these files, perform anormal document level restore.

Other revisions of the files are located in the Shadow folder, with the same folderstructure as the original copy. The revisions of a file are identified with thefollowing name format:

original_name(x.y).ext.

original_name is the name of the file, .ext is the file extension, x is the publishedversion of the file, and y is the draft version of the file.

89Recovering backward-compatible document library objectsRestoring versioned documents (in the backward-compatible document libraries) to the documents folder

Restoring other file revisionsThis topic describes how to restore other file revisions.

To restore other revisions of files

1 Open a Restore window.

2 From the NetBackup History pane, select an image that contains the files youwant to restore.


4 Expand Document Libraries.

5 Expand the Shadow folder.

6 Select the Documents folder.

7 Select the revisions to restore.


9 Click on the Restore Marked Files tab.

10 Select Restore everything to a different location.

11 Click in the Destination box and remove theShadow folder from the pathname.


Rebuilding restored revisions of a documentDocuments that are restored from the Shadow folder are not associated as revisionsto documents in the Documents folder. Documents revisions have to be rebuiltmanually.

To rebuild the restored revisions of a document

1 Restore the Documents folder.

2 Restore all revisions.

See “Restoring other file revisions” on page 90.

After you have restored the revisions, the base document and all of therevisions are shown in the Documents folder of the document library.

3 Save each file revision to a temporary location.

4 In SharePoint Portal Server 2003, open the Documents folder in the documentlibrary.

Recovering backward-compatible document library objectsRestoring other file revisions

90

5 Below the name of a document name, the document that was restored in step1, click Show Actions.

6 Click Check In.

7 Browse to the temporary location for the revisions that you restored in step3.

8 Select the oldest revision you want to check in.

9 Check in this revision of the file. Update the document profile as necessary.

10 If necessary, publish the file to maintain the appropriate version.

11 Check out the file (you do not have to save the file).

12 Repeat step 6 through step 11 for all remaining revisions.

13 Delete the restored revision files from the Documents folder (leave the basedocument).

Redirecting the restore of a SharePoint 2001document library or workspace

Before you redirect the restore of a SharePoint 2001 document library, install theSharePoint Portal Server software on the target server. If any of the folders inthe original document library do not exist in the destination document library,they are created during the restore.

You can redirect the restore of a document library or workspace to anotherdocument library or workspace. You cannot redirect individual SharePoint itemsfrom backups using Granular Recovery Technology to another document libraryor workspace.

To redirect the restore of a SharePoint 2001 document library or workspace








91Recovering backward-compatible document library objectsRedirecting the restore of a SharePoint 2001 document library or workspace



7 In the Contents of pane, select the document library or workspace you wantto restore.




11 Click Individual SharePoint sites, documents, lists, or items.

12 Click Redirecttoworkspaceordocumentlibrary(WebStorageSystem-basedonly).

13 In the Restoretoserver box, type the name of the SharePoint server to whichyou want to restore. Use the following format:

\\servername

14 In the Restore to workspace or document library box, type the name of thedocument library to which you want to restore. If you have not yet createdthe document library, you must do so before you start the restore operation.




Recovering backward-compatible document library objectsRedirecting the restore of a SharePoint 2001 document library or workspace

92

Disaster recovery


■ About disaster recovery of a SharePoint Server

■ Requirements for disaster recovery of a SharePoint Server

■ Recovering a SharePoint 2007 Server or MOSS 3.0 (without BMR)

■ Recovering SharePoint 2003 Server (without BMR)

About disaster recovery of a SharePoint ServerSharePoint Server uses Windows 2003 or Windows 2008 security forauthentication. Because of this configuration, disaster recovery of a SharePointServer cannot be separated from the disaster recovery of Windows. You mustrecover the Windows server before you recover the SharePoint Server.

If you purchased the NetBackup Bare Metal Restore option. Refer to NetBackupBare Metal Recovery Administrator's Guide for more information. If you do nothave BMR, see the "Disaster Recovery" chapter in theNetBackupTroubleshootingGuide.

Requirements for disaster recovery of a SharePointServer

The following requirements exist for disaster recovery of a SharePoint Server:

■ A copy of NetBackup for Windows with the license for NetBackup forSharePoint Server added on the master server

■ The latest backup of the SharePoint Server you want to recover

■ The SharePoint Server CD

7Chapter

■ Any service packs that have been applied to the original installation

Recovering a SharePoint 2007 Server or MOSS 3.0(without BMR)

To recover a SharePoint 2007 Server or MOSS 3.0 (without BMR)

1 Configure the destination host the same as the the original host.

2 Install SharePoint 2007 or MOSS 3.0.

3 Create a new Configuration database and attach to it using the SharePointconfiguration wizard.

4 Configure the NetBackup master server that has the backup images from theoriginal host as the master server for the destination host.

5 Restore all the components of the SharePoint farm or MOSS, except theConfiguration database. Restore the components in the following order:

■ Search database

■ Web Application(s)

■ Shared Service Provider, if any

■ Single Sign-on database, if any

■ Search Index Files

Recovering SharePoint 2003 Server (without BMR)If you do not have BMR, the general process for recovering SharePoint Server isas follows:

■ Reinstall Windows and any Service Packs or Hotfixes.

■ Restore System State from the backup image.

■ Reinstall SharePoint Server. and any Service Packs.

■ Restore the Configuration database.When you restore the Configuration database, restore it individually and beforeany other object in the farm.

■ Restore all SQL databases.

■ Bring the Web Application(s) or portal(s) online.

Disaster recoveryRecovering a SharePoint 2007 Server or MOSS 3.0 (without BMR)

94

■ From a SharePoint front-end server, restore each Web Application or portalseparately.The front-end server is the client name that you specified in the MS-SharePointbackup policy.

■ Wait for SharePoint to initialize storage for the Search Index.This may take a few minutes to occur, after you have started a newly recoveredWeb Application or portal.

■ Restore the Search Index.

95Disaster recoveryRecovering SharePoint 2003 Server (without BMR)

Disaster recoveryRecovering SharePoint 2003 Server (without BMR)

96

Troubleshooting


■ About troubleshooting

■ About debug logging

■ About NetBackup status reports

■ About troubleshooting jobs that use Granular Recovery Technology (GRT)

■ About troubleshooting restore operations

About troubleshootingThe information in this topic includes resources available for troubleshootingNetBackup for SharePoint Server, including the following.

■ Debug logs

■ Status reports

About debug loggingThe NetBackup master server and client software offers a comprehensive set ofdebug logs for troubleshooting problems that can occur during NetBackupoperations. Debug logging is also available for SharePoint Server backup andrestore operations.

You can control the amount of information written to debug logs.

See “Setting the debug level on a Windows client” on page 99.

8Chapter

After you determine the cause of the problem, disable debug logging by removingthe previously created debug logging directories. Details are available on thecontents of these debug logs.

See the NetBackup Troubleshooting Guide.

Additional information about NetBackup client logs and NetBackup master serverlogs is available.

See the online help for the Backup, Archive, and Restore interface.


Note: When debug logging is enabled, the files can become large. The same filesare used by normal file backups.

To create all debug logs, run the following batch file:

install_path\NetBackup\logs\mklogdir.bat

Enabling debug loggingTo turn on debug logging, create the log directories in the following location:

install_path\Netbackup\logs

Create the following log directories on the SQL Server, the front-end Web server,the media server, and the master server:

SharePoint managed code in the SharePoint front-end serverbeds

all backupsbpbkar

Snapshot backupsbpfis

(Pre-6.5.4 backup images) SharePoint individual item restoreusing Granular Recovery Technology (GRT)

bppfi

all backups and restoresbpresolver

all restoresbpbrm

all restoresbprd

SharePoint individual item restore using GRT

The new ncf processes nbgre.exe and nblbc.exe control thebrowsing and restore of a granular backup image.

ncf

SharePoint individual item restore using GRTnbfsd

TroubleshootingAbout debug logging

98

SharePoint managed code in the SharePoint front-end serverspps

Recovery Assistantspsv2ra

all restorestar

After you create these directories and perform a backup or restore, debug logginginformation is placed in the directory in a file named mmddyy.log.

The SharePoint Recovery Assistant uses Veritas Unified Logging. To view the logsrun vxlogview -i 254 from the NetBackup bin directory. For more informationabout unified logging, see theNetBackupAdministrator’s Guide. For informationon how to use the log commands, see the NetBackup Troubleshooting Guide.

Setting the debug level on a Windows clientTo control the amount of information that is written to the debug logs, changethe General, Verbose, and Database debug levels on the client(s). Typically, thedefault value of 0 is sufficient. However, technical support may ask you to set thevalue higher to analyze a problem.

The debug logs are located in install_path\NetBackup\logs.

To set the debug level on a Windows client

1 From the Windows Start menu, choose Programs > Veritas NetBackup >Backup, Archive, and Restore.

2 Select File > NetBackup Client Properties.

3 Click the Troubleshooting tab.

4 Set the General debug level.

Set this level as high as 2.

5 Set the Verbose debug level.


6 Set the Database debug level.



99TroubleshootingAbout debug logging

About NetBackup status reportsNetBackup provides many standard status reports to verify the completion ofbackup and restore operations. In addition, users and the administrator can setup additional reports if a site requires them.

The following reports are available:

■ About operational reports

■ About progress reports

About operational reportsThe administrator has access to operational progress reports through theNetBackup Administration Console. Reports can be generated for Status ofBackups, Client Backups, Problems, All Log Entries, Media Lists, Media Contents,Images on Media, Media Logs, Media Summary, and Media Written. These reportscan be generated for a specific time frame, client, or master server.

See the NetBackup Administrator’s Guide, Volume I for details.

About progress reportsProgress reports on the client allow easy monitoring of user operations. Whenreports are created by the NetBackup client for each user-directed backup orrestore operation, administrators can monitor these operations and detect anyproblems that may occur.

Viewing the status of a NetBackup operationThis topic describes how to view the status of a NetBackup backup or restoreoperation.

To view the status of a NetBackup operation

1 Choose File > View Status.

2 Click the task for which you want to check the progress.

3 Click Refresh.

More information is available on progress reports and the meaning of themessages.

See the NetBackup Backup, Archive, and Restore Getting Started Guide.

TroubleshootingAbout NetBackup status reports

100

About troubleshooting jobs that use GranularRecovery Technology (GRT)

Note the following when you use NetBackup to perform backup or restoreoperations using Granular Recovery Technology:

■ Disable or uninstall Qlogic San Surfer software. It may conflict with the portmapper for Client for NFS.

■ In the Local Security Settings, the Users group must have User RightsAssignment “Allow log on locally”. By default, the Users group is included. Ifthe Users group does not have this right, the following error occurs:1385 -- Logon failure: the user has not been granted the requested logon typeat this computer.

■ Backups of the SharePoint Web applications or portals that use GranularRecovery Technology (GRT) and that contain a larger number of contentdatabases (100+) may timeout. In this situation, increase the default “Clientread timeout” setting to 900 seconds.

About troubleshooting restore operationsNote the following when you perform restores:

■ NetBackup does not prevent you from restoring placeholders.

■ NetBackup lets you restore any object that can hold a document, even it doesnot contain a document.

■ You cannot restore a document or a picture library item when the library orfolder does not exist. The library or folder is not recreated and the item is notrestored. In this situation, redirect the restore to a file system and then uploadthe items into SharePoint Server.

101TroubleshootingAbout troubleshooting jobs that use Granular Recovery Technology (GRT)

TroubleshootingAbout troubleshooting restore operations

102

AAllow multiple data streams 56

Bbackup media required 21Backup selections list

adding SharePoint resources 61adding the AllWebs directive 61

backupsautomatic 15backup types 58manual 62SharePoint backup options 66SharePoint objects that are included in 15–16user-directed

of SharePoint resources 67of Windows SharePoint Services 67overview 15

bpbkar log 98bpfis log 98bppfi log 98Bring restored databases online and reconnect

previous database links 70

Ccheckpoint restart 56clients list

for backup policies 60compatibility information 20compression 56Configuration database

precautions when you restore SharePoint 68configuring restores for multiple SharePoint hosts 47consistency checks

options 46performing 46

Ddebug logs 97–98differential-incremental backups 59

disaster recoveryrequirements 93without BMR 94

document libraries (backward-compatible)restores of 88

document libraries (backward-compatible):versioneddocuments

restores of 89document library store (backward-compatible)

restores of 88

EEnable granular recovery 56encryption 56

Ffederated farms

configuring NetBackup for 47

IIIS Default Application Pool identity 21installation

adding a license key 22requirements for NetBackup software 20

JJava interface 43

Llicense keys, adding 22

Mmanual backups 15

Nnbfsd log 98nbfsd port 41ncf log 98

Index

NetBackup Client Service log on account,configuring 44

Ppolicy configuration

adding clients 61attributes 55for databases 55overview 50schedules 56specifying objects to back up 61testing 62

policy recommendations 53Policy type for restores 69

Rredirected restores

to different clients 69redirecting restores

of Web applications, portals, and team sites 81reports

client 100media 100operational 100

restoresdocument libraries (backward-compatible) 88document libraries (backward-compatible), and

rebuilding versioned documents 90document libraries (backward-compatible),

versioned documents 89document library store

(backward-compatible) 88from GRT-enabled backups, configuring storage

units for 49of individual items 76, 78of SharePoint Server or Windows SharePoint

Services 74redirecting 18redirecting Web applications, portals, and team

sites 81server-directed 17SharePoint 2007 restore options 69

Sschedules

adding 56frequency 57properties 57

Server to use for backups and restores 69Services for NFS

installing on Windows 2003 R2 SP2 38SharePoint application server log on account 45SharePoint application server logon account 44SharePoint Hosts properties 47SharePoint load balancing 21SharePoint user 21Source client for restores 69spsv2ra 99

Ttar log 99testing policy configuration 62troubleshooting

NetBackup debug logs 97status of NetBackup operations 100

Uuser-directed backups

of SharePoint resources 67of Windows SharePoint Services 67SharePoint backup options 66

WWindows interface 43

Index104