tsmsharept_6.1_ds8000_v1.8

8/6/2019 TSMsharept_6.1_DS8000_v1.8

1/38

8/6/2019 TSMsharept_6.1_DS8000_v1.8

2/38

IBM TSM for SharePoint 6.1 VSS Backup andRestore Solution Guide

Page 2 Dave West, David Hartman

Copyright IBM Corp. 2009

Table of Contents

Introduction ............................................................................. 3IBMSystem Storage DS6000 ............................................ 3IBMSystem Storage DS8000 ............................................ 4Storage Sizing and Configuration ......................................... 5The IBM DS Open API CIM Agent .......................................... 6

Installation .............................................................................................................. 7Configuration ........................................................................................................ 11

IBM System Storage Support for Microsoft VSS ................ 13Installing the IBM Hardware Provider .................................................................. 14Configuring the free and reserved VSS volume pools ......................................... 16Verifying the Installation ....................................................................................... 17Sample Disk Configuration for SharePoint VSS backups ................................... 18

Tivoli Storage Manager for SharePoint ............................... 18Solution Overview ................................................................................................ 18System Requirements .......................................................................................... 20TSM Server Requirements .................................................................................. 22

Installing the DocAve Manager .......................................................... 24Installing the DocAve Agent ............................................................... 25Configuring Integration with TSM Server ........................................... 27The DocAve Dashboard ..................................................................... 30

Backup Procedures .............................................................. 31

Selecting SharePoint Content .............................................................................. 32Configuring and Running the Backup .................................................................. 33

Restore Procedures .............................................................. 34Setting the Date Range ........................................................................................ 34Finding and Selecting Data for Restore ............................................................... 34Advanced Restore Options .................................................................................. 36Performing the Restore ........................................................................................ 36

Conclusion ......................................................................................... 37

8/6/2019 TSMsharept_6.1_DS8000_v1.8

3/38




Introduction

Many customers rely on Microsoft Office SharePoint Server (MOSS) 2007 as a keybusiness application, and even short periods of unexpected downtime can seriously

affect company productivity and collaboration. Companies of all sizes are using theadvanced data management, collaboration, and web integration features of MOSS 2007,creating large content repositories serviced by front-end portals. Search requirementsresult in large indexes of these repositories and possibly other external content sources,resulting in an enormous amount of data to protect.

Because of this ability to easily store and manage multiple application databases, datarepositories, and web portals serviced through a variety of interfaces, the ability tobackup and restore disparate data types, at a granular level, efficiently and consistentlyis essential. The demand for accurate backup and restore is growing as companies storemore of their business-critical data on SharePoint Server 2007. In addition, manyorganizations are moving towards SharePoint as a replacement for traditional file

servers, and extensions to Exchange & SQL Server.

IBMTivoli Storage Manager (TSM) for SharePoint provides farm, site, subsite, anditem-level backup with restore granularity down to the single document or version level.Granular restore capability is the key to quicker restore times with SharePoint. WhenTSM is combined with a reliable, scalable disk subsystem like the IBM SystemStorage DS series, the result is a highly effective solution that is ready to help yourorganization meet demanding backup and recovery point/time objectives, without addedadministrative complexity.

Due to the ever expanding amount of storage space required by complex and distributedSharePoint environments, the scalable IBM System Storage DS6000 or DS8000 areideal platforms for medium to large companies.

IBMSystem Storage DS6000

Note: The solution outlined in this document is available on all IBM System Storagedisk products. However, it is important to install the correct VSS hardware provider forthe disk product in use.

The IBM System Storage DS6000 series is a member of the DS family of products andis built upon 2 Gbps fibre channel technology that provides RAID-protected storage withadvanced functionality, scalability, and increased addressing capabilities.

The DS6000 series is designed to offer a high reliability and high performance midrangestorage solution through the use of hot-swappable redundant RAID controllers in aspace efficient modular design. The DS6000 series provides storage sharing andconsolidation for a wide variety of operating systems and mixed server environments.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

4/38




The DS6000 series is designed to offer high scalability while maintaining excellentperformance. With the DS6800 (Model 1750-522), you can install up to 16 disk drivemodules (DDMs).

For those needing more storage capacity, the optional DS6000 expansion enclosures(Model 1750-EX2) allow for a maximum of 128 DDMs per storage system and provide amaximum physical storage capability of 57.6 TB with fibre channel drives.

The DS6800 measures 5.25-in. high and is available in a 19-in. rack mountable packagewith an optional modular expansion enclosure of the same size for additional capacity tohelp address your growing business needs.

The DS6000 series addresses business efficiency needs through its heterogeneousconnectivity, high performance and manageability functions, thereby helping to reducetotal cost of ownership.

The DS6000 series offers the following major features:

PowerPC 750GX processors Dual active controllers are designed to maintain operations through the use of two

processors that form a pair to back up the other

A selection of Fibre Channel (FC) disk drives, including 73GB, 146GB, 300GB, and450GB sizes with speeds of 10,000 or 15,000 revolutions per minute (RPM)

Fibre Channel and FICON host attachments of up to 8 ports, which can beconfigured with an intermix of Fibre Channel Protocol (FCP) and FICON FibreChannel Arbitrated Loop (FC-AL) switched device attachment of up to 2 dual loops

4GB battery backed, mirrored cache Redundant power and cooling system Disaster Recovery and Copy Service solutions

Additional information on the DS6000 can be found here:

http://www-03.ibm.com/systems/storage/disk/ds6000/index.html

IBMSystem Storage DS8000

Created specifically for medium and large enterprises, the IBM System Storage DS8000series offers high-capacity storage systems that are designed to deliver performance,scalability, resiliency and value.

The DS8000 series is designed to provide exceptional performance while addingvirtualization capabilities that can help you allocate system resources more effectivelyand better control application quality of service. The DS8000 series also offers powerfulfunctions that are designed to help protect data from unforeseen events and maintaindata availability, which can benefit businesses that must have continuous access toinformation.
http://www-03.ibm.com/systems/storage/disk/ds6000/index.htmlhttp://www-03.ibm.com/systems/storage/disk/ds6000/index.htmlhttp://www-03.ibm.com/systems/storage/disk/ds6000/index.html

8/6/2019 TSMsharept_6.1_DS8000_v1.8

5/38




The DS8000 series offers:

Exceptional flexibility and scalability. The current physical storage capacity of theDS8000 series system can range from 1.1TB to 512TB, and it has an architecture

designed to scale to over a petabyte. Significant addressing enhancements, IBM System Storage FlashCopy, Global and

Metro Mirror functions, and streamlined configuration and management capabilitiesthrough the easy-to-use IBM DS Storage Manager are just some of the manyadditional advanced features of the DS8000 series.

Innovative design creates impressive performance. With 4Gbps FC host adapters,the DS8000 models are as much as six times faster than the IBM TotalStorageEnterprise Storage Server (ESS) Model 800.

Utilizing IBM POWER5+ processor technology, the DS8000 series delivers the firstuse of the IBM Virtualization Engine, which is designed to bring to a disk storagesystem the logical partition flexibility usually reserved for servers.

Additional information on DS8000 can be found here:

http://www-03.ibm.com/systems/storage/disk/ds8000/index.html

Storage Sizing and Configuration

In order to fully leverage the performance capabilities of the IBM System StorageDS6000 and 8000, consideration needs to be given to the logical configuration of theunit. Because most of SharePoints data is stored within SQL Server (with the exceptionof SharePoint index files), the LUN setup and tuning recommendations are similar to ourSQL server tuning recommendations.

Note: For more information on configuring IBMSystem Storage for use withMicrosoft SQL Server 2005, and SQL Server 2008, please refer to the SQL Server 2005with IBMSystem Storage DS8000 & DS4000 Best Practices Guide, or the SQLServer 2008 with IBMSystem Storage DS8000 & DS4000 Best Practices Guide.Both documents are available at:

http://www-03.ibm.com/systems/storage/solutions/isv/#microsoft

It is important during the planning stages to understand how large the SharePoint indexfiles can become, particularly if external file servers are being indexed as contentsources. SharePoint indexes can grow up to 50% of the size of the content beingindexed. If indexing is pointed at an external file server with 800GB of data, your

SharePoint index file could be as large as 400GB for that content source alone.

From a backup and restore perspective, many organizations do not backup the indexfiles because they are regularly refreshed, are often massive in size, and can simply berebuilt. However, if demanding RTO requirements include highly available SharePointsearch capabilities, then the index should also be backed up.
http://www-03.ibm.com/systems/storage/disk/ds8000/index.htmlhttp://www-03.ibm.com/systems/storage/disk/ds8000/index.htmlhttp://www-03.ibm.com/systems/storage/solutions/isv/#microsofthttp://www-03.ibm.com/systems/storage/solutions/isv/#microsofthttp://www-03.ibm.com/systems/storage/solutions/isv/#microsofthttp://www-03.ibm.com/systems/storage/disk/ds8000/index.html

8/6/2019 TSMsharept_6.1_DS8000_v1.8

6/38




In order to minimize application and user impact:

Backups should occur when application is least active. Use of VSS backup greatlyminimizes the impact on production systems, however there is still disk activity and

network bandwidth to consider. Volume creation and storage sizing for maximum performance should follow

published Microsoftguidelines for SharePoint. Please see the MicrosoftSharePoint Deployment Guides for detailed information.

For Microsoft Office SharePoint Server 2007:

http://technet.microsoft.com/en-us/library/cc262957.aspx

For Windows SharePoint Services v3.0:

http://technet.microsoft.com/en-us/library/cc288426.aspx

The IBM DS Open API CIM Agent

The IBM System Storage DS Open Application Programming Interface (API) is a storagemanagement client application that supports standard LUN management activities suchas LUN creation, mapping and masking, and the creation or deletion of volumes. The DSOpen API supports these activities through the use of the Storage Management InitiativeSpecification (SMI-S), as defined by the Storage Networking Industry Association(SNIA).

The DS Open API is implemented through the IBM System Storage CommonInformation Model (CIM) agent, a middleware application that provides a CIM-compliant

interface. The DS Open API uses the CIM technology to manage proprietary devices asopen system devices through storage management applications. The DS Open APIallows these storage management applications to communicate with a storage unit. Forthis solution, the IBM VSS hardware provider communicates through the CIM agent tomanage LUN and snapshot processes on the DS6000 or 8000.

This section includes an overview of the installation process and instructions forinstalling and configuring the CIM agent on a Windows 2003 or later operating system.Although this solution has the CIM agent on a dedicated Windows server, that is not arequirement. The CIM agent can be installed on any non-clustered server available. Weadvise using the most recent version of the CIM agent available on the IBM site. Thissolution covers installation of version 5.4

This section contains information from the IBM System Storage DS Open ApplicationProgramming Interface 5.4 Installation and Reference guide. For more detailedinformation the document can be downloaded from here:

http://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=en
http://technet.microsoft.com/en-us/library/cc262957.aspxhttp://technet.microsoft.com/en-us/library/cc262957.aspxhttp://technet.microsoft.com/en-us/library/cc288426.aspxhttp://technet.microsoft.com/en-us/library/cc288426.aspxhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://www-01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA420&uid=ssg1S7002567&loc=en_US&cs=utf-8&lang=enhttp://technet.microsoft.com/en-us/library/cc288426.aspxhttp://technet.microsoft.com/en-us/library/cc262957.aspx

8/6/2019 TSMsharept_6.1_DS8000_v1.8

7/38




Note: Recent DS6000s and DS8000s include a version of the CIM preinstalled on theHost Management Console (HMC), also known as imbedded CIM. You may use theimbedded CIM agent if it is enabled and configured. Contact IBM support to confirmstatus of the imbedded CIM on your system.

Security Levels

Secure Mode

All requests between the client application and the CIMOM are XML encoded requestssent over Hypertext Transfer Protocol (HTTP) or HTTP over Secure Sockets Layer(SSL).

The CIMOM, upon receiving a request, parses the request and processes it. Responses,when they are returned to the client application, are transformed into XML-encoded CIMstatus and returned in HTTP responses to the client. The default of the CIM agent is torun in secure mode using SSL.

Unsecure Mode

Some vendor software might not be capable of communicating with the CIM agent in asecure mode. You can still use this vendor software by configuring the CIM agent to runwith only basic user name and password security. See the configuration instructions foryour operating system for the instructions for configuring the CIM agent for this lesssecure mode.

Installation

The following summarizes the installation steps covered in this section.

Install the agent Verify the CIM agent installation Configure the CIM agent Verify the connection to your storage unit

Perform the following steps to install the CIM agent

Log on to your system as a local administrator. Verify you have a recent version of IBM Java installed. Insert the CIM agent CD into the CD-ROM drive. The CIM agent program should

start if you have autorun set on your system, or navigate to the CD-ROM drive andstart the LaunchPad.bat file.

Click Installation wizard from the LaunchPad window to start the installation. TheLaunchPad window remains open behind the installation wizard so that you canaccess product information during the installation process.

There may be a delay while the software initially loads. After the software loads, aDOS prompt window opens with the message: Initializing InstallShield Wizard...Preparing Java Virtual Machine...

8/6/2019 TSMsharept_6.1_DS8000_v1.8

8/38




The Welcome window opens suggesting what documentation you should reviewprior to installation. Click Next to continue.

Read the license agreement, and click Accept to continue. If the installation wizard detects a prior installation of the CIM agent, the Product

Installation Check window opens. Check the Preserve Configuration check box ifyou want to preserve your configuration settings. Follow any specific instructions inthe window. After you have followed all instructions, select Next.

The Destination Directory window opens. Click Next to accept the default directory,or click Browse to select a different directory for installation and then click Next.The Destination Directory window is displayed only if a version of CIM agent is notalready installed. Otherwise, the CIM agent is reinstalled or upgraded to the sameinstall location.

The Server Communication Configuration window opens as shown below. If one ormore of the default ports is the same as another port already in use, modify thedefault port and click Next.

Note: Use this command to check ports in use: netstat -an

Select the appropriate communication protocol and click Next to continue withinstallation.

Note: If your applications do not support secure communications, select HTTP as theprotocol or both to enable either one, as shown below. This setting can be changed laterif needed.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

9/38




The Configuration Parameters window opens as shown below. Optionally enter auser name and password for the CIM server.

Click Add to optionally enter any information about devices that you would like toconfigure the agent to communicate with. When adding a device, a device type, IP

address, username, and password must be specified. When adding a DS6000 or DS8000 family device, the device type should be ds, the

IP address should be of the master console, and the username and password shouldbe the same one used to log into the DS Command Line Interface or DS StorageManager.

After you have finished adding the configuration information, click Next.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

10/38




The Installation Preview window opens. Click Install to confirm the installationlocation and file size.

The Installation Progress window indicates how much of the installation has beencompleted. The installation installs the CIM agent files, starts the Service Location

Protocol (SLP) service, and starts the CIM Object Manager service. When the Installation Progress window closes, the Finish window opens. Click

Finish to exit the installation wizard.

Exit the LaunchPad program by clicking Exit on the LaunchPad window. If you havenot done so already, continue with the post installation tasks for the CIM agent usingthe instructions in the following sections. Restart your system if required.

Verifying the installation

Perform the following steps to verify your CIM agent installation:

Verify the installation of the Service Location Protocol (SLP) from Windows services

panel. Find the SLP service and verify it is started and set to manual. Start theservice if it is not running. The CIM agent controls starting and stopping of thisservice as needed.

Verify the installation of the CIM agent from Windows services panel. Find the IBMSystem Storage CIM Agent for DS Open API and verify it is started and set toautomatic. Start the service if it is not running.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

11/38




If you are able to perform all of the verification tasks successfully, the DS CIM agent hasbeen successfully installed.

Configuration

This section configures the CIM agent after it has been installed. These steps are thesame instructions listed in the Post Installation Tasks option on the LaunchPad window.

Verify you can ping each DS that the CIM agent will manage by typing the followingcommand: ping , using the IP address of the target DS.

If you did not enter the DS storage system information during installation, or want toadd another storage unit, type the following command to configure the CIM agent foreach DS server that the CIM agent can access.

dscimcli mkdev -type -user -password

ip For a DS server, this is the IP address of the primary hardware orsoftware master console (HMC/SMC).

type For DS6000/8000, this entry should be ds

user/password For a DS server, this is the storage manager GUI or DSCLIuser name and password

After you have defined the DS server(s), type the following command to verify thedevices were correctly added and have connected:

dscimcli lsdev -l

Below is a sample of expected output from the command

Note: The CIM agent periodically collects and caches information from the definedstorage units, therefore the CIM agent might periodically take longer to respond torequests, including immediately after adding a new storage unit.

Configure the CIMOM for each user that you want to have authority to use the

CIMOM by running the CIMOM configuration program. During the CIM agentinstallation, the default user name to access the CIM agent CIMOM is created.

The default user name is superuser with a default password of passw0rd. Youmust use the default user name and password when you use the mkuser commandfor the first time after installation. After you have added other users, you can initiatethe mkuser command using a user name that you defined instead of using thedefault.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

12/38




1. Start the CIM agent, if it is not started, by typing the following command:

startagent

2. Type the following command:

dscimcli mkuser -user cimuser -password cimpass

3. You can change the default password for superuser by starting the mkusercommand for a user that you added. Issue the following command to change thepassword:

dscimcli chuser superuser -password passw0rd -newpassword

Type the exit command to close the CIMOM configuration program. If you were able toperform all of the configuring tasks successfully, the CIM agent has been successfullyinstalled and configured.

Verifying CIM Agent Connection

During this task, the CIM agent software connects to the storage unit that you identifiedin the configuration task.

Verify that you have network connectivity to the DS unit from the system where theCIM agent is installed by pinging the IP address of the DS master console.

Verify that the DS CLI is operational and can connect to the storage unit. Open a

command prompt window and issue the following command:

dscimcli lsdev -l

You should see the following output:

Note: In some cases the DS CLI does not work correctly unless the system has beenrestarted following the new installation of the CLI.

Go to Windows Services and verify the Service Location Protocol (SLP) in the list ofservices is running. For this service, verify the status column is marked Started andthe Startup Type column is set to automatic. Start the service if it is not started.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

13/38




Verify that the CIMOM is active by finding CIM Object Manager - DS Open API in theWindows services panel. Verify the service is set to automatic and started.

IBM System Storage Support for Microsoft VSS

The Microsoft Volume Shadow Copy Service can provide a point-in-time (shadow) copyof a Windows host volume while the volume is mounted and files are in use.

The following components are used to provide support for the service:

IBM System Storage hardware provider, known as the IBM System Storage Supportfor Microsoft Volume Shadow Copy Service and Virtual Disk Service software. Thisis also referred to as the IBM hardware provider.

Microsoft Volume Shadow Copy Service (VSS)

For this solution, the IBM hardware provider is installed on the SharePoint and SQL

servers and a VSS non-persistent backup is performed. To provide the point-in-timeshadow copy, the components complete the following process:

The TSM for SharePoint Docave Agent (VSS requestor) on the SharePoint serverinitiates a snapshot backup.

VSS notifies the IBM hardware provider that a copy is needed. The DS6000/8000 prepares the volumes for a snapshot, placing the volumes into the

VSS_Reserved pool. The SharePoint VSS writer gathers information on whichvolumes are being used by SharePoint and SQL, and coordinates with the hardwareprovider to reserve the appropriate size VSS volumes.

VSS quiesces the software applications (Microsoft Office SharePoint Server 2007,and SQL Server 2008 in this case) that are writing data on the hosts and flushes filesystem buffers to prepare for the copy.

The VSS volumes are then mounted to the SharePoint and SQL servers by the IBMVSS hardware provider.

The DS6000/8000 creates the shadow copy using the IBMs FlashCopy CopyService.

VSS notifies the writing applications that I/O operations can resume, and notifies thebackup application that the backup was successful.

Backup data is copied from the VSS volumes to TSM allocated storage After the data transfer to the TSM server is complete, VSS volumes are

disconnected from the SharePoint and SQL servers, and returned to the VSS_Freepool.

The IBM hardware provider maintains a free pool of LUNs for use as FlashCopy targetsand a reserved pool of LUNs which are disks currently hosting snapshots. These poolsare actually Volume Groups on the DS6000 or DS8000 and the hardware providermoves the volumes between the groups as needed.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

14/38




Installation Overview

The steps for implementing IBM System Storage Support for Microsoft VSS must becompleted in the correct sequence. Complete the following tasks:

Verify the system requirements. Confirm an IBM DS Open API CIM agent is available in the environment. Install the IBM System Storage Support for Microsoft VSS on each host. Verify the installation, configuration, and communication Create the free and reserve pool volume groups on the DS6000/8000

System Requirements

The following software is required:

IBM System Storage Support for Microsoft Volume Shadow Copy Service and Virtual

Disk Service software version 3.2 or later. Windows Server 2003 or 2008 operating system. The following editions of Windows

Server are supported:o Standard Server Edition 32-bit versiono Enterprise Edition, 32-bit versiono Standard Server Edition 64-bit versiono Enterprise Edition, 64-bit version

Installation of the Common Information Module (CIM) in the environment, which wascovered in the previous section, or access to imbedded CIM.

Installing the IBM Hardware Provider

Perform the following steps to install the IBM System Storage Support for Microsoft VSS:

Log on to Windows as an administrator. Download the IBM VSS installation package from the following Web sites (note that

code is system and firmware-version specific):

DS8000:

http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1

DS6000:

http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1
http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?brandind=5000028&familyind=5329629&taskind=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1http://www-304.ibm.com/systems/support/supportsite.wss/selectproduct?taskind=4&brandind=5000028&familyind=5329631&typeind=0&modelind=0&osind=0&psid=sr&continue.x=1

8/6/2019 TSMsharept_6.1_DS8000_v1.8

15/38




Double click on the name of the file that you downloaded to start the installationprocess. The Welcome panel is displayed.

Click Next to continue. The License Agreement panel is displayed. You can clickCancel at any time to exit the installation. To move back to previous screens while

using the wizard, click Back. Read the license agreement information. Select whether you accept the terms of the

license agreement, and click Next. If you do not accept, you cannot continue with theinstallation. The Choose Destination Location panel is displayed.

Click Next to accept the default directory where the setup program will install thefiles, or click Change to select a different directory. Click Next. The Ready to Installthe Program panel is displayed.

Click Install to begin the installation. The Setup Status panel is displayed. The Select CIM Server panel is displayed.

Select the required CIM server or select Enter the CIM Server address manually, andclick Next. The Enter CIM Server Details panel is displayed.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

16/38




Enter the following information in the fields:o In the CIM Server Address field, type the name of the server IP address where

the CIM agent is installed.o In the CIM User field, type the user name that the IBM System Storage Support

for Microsoft VSS will use to gain access to the server where the CIM agent isinstalled. For example, enter the name administrator. This account must beassigned to the Administrator role to function properly. You may also use thedefault superuser account or an account created specifically for this purpose.

In the CIM Password field, type the password for the user name that the IBM SystemStorage Support for Microsoft VSS will use to gain access to the CIM agent and clickNext.

Note: If these settings change after installation, you can use the ibmvcfg.exe toolto update IBM VSS provider software with the new settings. If you do not have theCIM agent server, port, or user information, contact your CIM agent administrator.

The InstallShield Wizard Complete panel is displayed. Click Finish. If necessary, the InstallShield Wizard prompts you to restart the

system.

Configuring the free and reserved VSS volume pools

The IBM System Storage Support for Microsoft VSS maintains a free and a reservedpool of volumes. When a shadow copy is created, the IBM System Storage Support forMicrosoft VSS software selects a volume in the free pool, assigns it to the reserved pool,and then removes it from the free pool.

This protects the volume from being overwritten by other VSS requests.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

17/38




To successfully perform a Volume Shadow Copy Service operation, there must beenough volumes in the free pool. The free pool volumes must be the same size or largerthan the source volumes.

Use the DS6000/8000 command-line interface (CLI) or the web based DS StorageManager console to perform the following steps:

Create a host attachment for the free pool of volumes, then create a volume groupand connect it to this host attachment. You can use the default name VSS_FREE orspecify a different name for both of these items. When setting up the hostattachment, use the worldwide port name (WWPN) 5000000000000000 (15 zeroes)

Create a host attachment for the reserved pool of volumes, then create a volumegroup and connect it to this host attachment. You can use the default nameVSS_RESERVED or specify a different name. When setting up the host attachment,use the WWPN 5000000000000001 (14 zeroes)

Restriction: The free pool volumes cannot be mapped to any other hosts.

Free pool volumes must be of the same size as the volumes you wish to backup.Volumes of varying sizes are permitted in the free pool. VSS will choose volumes of theappropriate size as needed.

Use the ibmvcfg add command to add volumes to the free pool. Alternately, you canuse the DS Storage Manager console to add volumes to the VSS_Free volume group.

NOTE: If you do not use the default WWPNs 5000000000000000 and5000000000000001, you must manually configure the IBM System Storage Support forMicrosoft VSS software with the alternate WWPNs.

Verifying the Installation

This task verifies that the IBM System Storage Support for Microsoft VSS software iscorrectly installed.

Perform the following steps to verify the installation:

From the Windows Services panel, ensure that the service named IBM SystemStorage Support for Microsoft Volume Shadow Copy Service and Virtual DiskService software appears and that Status is set to Started and Startup Type is set toAutomatic.

Open a command prompt window and issue the following command:

vssadmin list providers

Ensure that the service named IBM System Storage Support for Microsoft VSS softwareis listed as a provider.

Use the command ibmvcfg showconfig to confirm the parameters.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

18/38




Use the ibmvcfg listvols command to test the connection to the IBM SystemStorage master console.

Use the ibmvcfg listvols free command to verify volumes in the free pool.This can also be used to confirm the expected volumes are being used during a VSSbackup. You can observe them leaving the free pool and moving to the reservedpool.

Use the ibmvcfg listvols reserved command to view volumes in the reservepool

If you are able to successfully perform all of these verification tasks, the IBM SystemStorage Support for Microsoft VSS software was successfully installed.

Sample Disk Configuration for SharePoint VSS backups

The table below shows a small scale example of how the SharePoint, SQL, and VSSvolumes were configured to provide snapshot backup support for our test environment.

Volume Location LUN VSS (in VSS_Free)

MOSS_index SharePoint Server 100 GB 100 GB x 3

SQL_MOSS_dbs SQL Server 150 GB 150 GB x3

SQL_MOSS_logs SQL Server 70 GB 70 GB x 3

During a VSS backup, the IBM VSS hardware provider will take one complete set of

LUNs (100, 150 and 70 GB volumes) from the VSS Free pool per snapshot. This is aresult of the SharePoint VSS writer gathering information on all involved volumes on allservers in the farm, and coordinating the snapshot of those LUNs with the hardwareprovider. Notice the sets of LUNS in the free pool match the production volume sizes inuse.

Tivoli Storage Manager for SharePoint

Solution Overview

The Tivoli Storage Manager for SharePoint solution uses the AvePoint DocAve 5.1.2.1software, which fully integrates with the TSM backup server.

DocAve is an Enterprise scale, item level and full farm backup and restore solution forMOSS 2007 or Windows SharePoint Services 3.0. Combined with the powerful TSMbackup server, all SharePoint backup operations can be completely automated. TSM forSharepoint now includes VSS support for fast backups of the entire farm, and standardbackups for selected components, with granular item restore capability.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

19/38




This document covers the basic installation, configuration, and administration tasksrequired to setup and manage the backups and restores. For more detailed information,consult the TSM for SharePoint 6.1 DocAve User Guide at:

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdf

We recommend reading the entire User Guide, before following the steps in this specificsolution guide.

Supported Platforms

Microsoft Office SharePoint Server (MOSS) 2007, with Service Pack 1 Windows SharePoint Services (WSS) v3, with Service Pack 1 Windows Server 2003, 2008 SQL Server 2000, 2005,and 2008 All of the above are supported on x86 or x64 platforms

Note: SQL Embedded Edition is not supported, SQL Express is supported except forPlatform incremental backups.

DocAve Components

There are three core backup components required by this solution; the DocAveManager, the DocAve Agent, and the TSM Server where the backup data resides.

The DocAve Manager Server consists of 4 core services, which can be installed on oneserver, or distributed across multiple servers depending on the size of your environment

and performance requirements. The 4 services are:

Control Service Business logic and communication service Web Service Used to access the DocAve web management interface Media Service Manages and coordinates storage devices Search Service Generates full text index and performs search

Supported Backup and Restore Methods

Farm Level: Backs up the entire SharePoint Farm

Site Level: Backs up and restores the entire site collection.

Sub-Site Level: Backs up and restores an entire sub-site.

Item Level: allows selective backup within a site or sub-site and provides granularrestore options down to the item level. This is the most powerful and often used
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdfhttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdfhttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdfhttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdfhttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.ic.doc/DocAve_v5_IBM_TSM_User_Guide.pdf

8/6/2019 TSMsharept_6.1_DS8000_v1.8

20/38




backup method in an enterprise environment.

Full, Incremental, or Differential: Each of these backup methods are available foreach level (Farm, Site, Sub-Site, and Item Level) of backup.

VSS backup: Snapshot backup of all levels, with granular restore capability. VSSsnapshots are used temporarily to send the SQL database data to the DocAve mediaserver. Depending on the network connection between the SQL server and themedia server, the backup speed will vary. The main benefit is reduced impact onSQL and SharePoint servers

Real-time restores written directly onto a production SharePoint server are possible.Cross restores to an alternate server on the network are also supported. DocAve usesthe terms in place for restores to the original server location, or out of place forrestores to an alternate server

Automated data pruning, and a web-based centralized administration console simplifiesscheduling, monitoring, reporting, and account management.

Key Assumptions

While every attempt has been made to clearly describe the various installationprocesses required for this solution, this paper is intended for IT professionals familiarwith the following:

Microsoft Office SharePoint Server 2007 Microsoft SQL Server Windows Server 2008 IBM TSM Server IBM System Storage DS 6000 and 8000 management Storage subsystems and terminology VSS backup and restore terminology and processes

The ability to manage and maintain the above is assumed. Descriptions of the setup andmanagement of these systems is outside the scope of this document.

System Requirements

This section describes the minimum hardware, software, and operating systemrequirements for a successful installation.

DocAve Manager Server Requirements

Server andprocessor

Intel Pentium III-compatible 1000-MHz processor minimum. DualIntel Xeon 3.0 Ghz or faster recommended

8/6/2019 TSMsharept_6.1_DS8000_v1.8

21/38




Memory 2 GB of RAM minimum, 4 GB (or greater) recommended

Hard disk 1GB minimum available, 3GB (or greater) recommended.

Operatingsystem

Requires one of the following: Windows XP SP2 (supported forapplication design, development, and testing; no support forproduction use) Windows Server 2003 SP1, or Windows Server2008 (32bit and 64bit)

.NETFramework

Version 2.0 or higher

DocAve Client / Agent requirements

The Agent component requires the same system requirements above, with the followingadditional SharePoint and Storage requirements:

SharePoint Front-End Web Server for SharePoint: MOSS 2007/WSS3.0

Service PacksMicrosoft Office SharePoint Server 2007, SP1

Windows SharePoint Services 3.0, SP1

8/6/2019 TSMsharept_6.1_DS8000_v1.8

22/38




TSM Server Requirements

This solution requires some specific configurations on the TSM backup server(described below). The TSM server can be installed and configured either before or afterthe DocAve software components. The DocAve installation does not query the TSMbackup server during the installation as earlier versions did.

The DocAve Manager Server communicates with the TSM Backup Server, and storesthe backup data in the TSM servers backup pools. In this configuration, only indexingdata is stored on the Manager Server for catalog purposes, while the actual backup dataresides on the TSM server.

Note: The installation and configuration of a TSM 6.1 backup server is well beyond thescope of this document. However, detailed information on the subject can be found atthe IBMTivoli Storage Information Centerat the following URL:

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

The following are initial TSM server requirements to get started:

A TSM `server, with adequate disk and storage pool space assigned to it for yourenvironment. Gather all IP, port, and account information which the DocAve
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsphttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsphttp://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

8/6/2019 TSMsharept_6.1_DS8000_v1.8

23/38




connection will require when setting up the storage associations. The machine mayrun any OS supported by the TSM serve

A TSM client nodedefined for each DocAve manager server that will send data to

the TSM server.

Node passwords if password authentication is enabled on the TSM server.

Network Shareused by the DocAve Manager server and is required during thesetups steps below. This stores DocAve information and can be on any server in theenvironment, however creating it on the DocAve server is the most logical locationfor it.

Additional policies can be configured on the TSM server, and within the DocAveinterface, to provide complete control of the backup data and schedules. This provides

the flexibility and control needed to meet specific and complex data retention and spacerequirements. Some of these advanced options include:

Data Pruning Job Pruning Data Coalescing Filter Policies Data retention and versioning

All backup operations can be fully automated. Please see the DocAve AdministrationGuide for detailed information on these policies and options.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

24/38




Installing the DocAve Manager

Follow these steps to install the Manager components:

Log on to the server with an administrator account. Launch the DocAve Manager installation file and complete the standard license

agreement, user information, and installation path options.

Select which DocAve Manager services you wish to install. For our test environmentall services were installed on one server. Large environments may require dedicatedservers for some services. The availableservices are shown below:

If you are distributing the services across several servers, the Control servicemust be installed first. All other services will require you to input the ControlService Host Name and Port number in order to communicate with the Manager

server. Also make note of any SSL or HTTPs settings when installing thesecomponents. Click Next to continue.

Use the default port numbers unless a known conflict exists.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

25/38




Important: Make note of the port numbers and verify any firewalls between theDocAve Manager server and servers running the DocAve Agent are allowing

communication through these ports (this includes the Windows built in firewall, orother server based firewalls).

The Agent installation includes a communication test during the installation (coveredbelow) which checks for communication between all services.

Notice on the above dialog box, you can enable SSL and HTTPS to securecommunications between the Manager and Agent services. Please see the DocAve5 Administration Guide for details on configuring security certificates.

Installing the DocAve Agent

Follow the steps in this section to install the Agent component on the SharePoint server.

Note: You must install the DocAve Agent on a SharePoint server with the Front-EndWeb Server role.

Log in to the machine with an account that has local administrator rights, andadministrative permissions within SharePoint and SQL Server.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

26/38




Launch the DocAve Agent installer on the Front-End Web server. Proceed through the standard welcome, license, name, and installation path

dialog boxes by clicking Next.

After the files are copied, the following confirmation and test window appears.

Enter the name of the DocAve Manager Server running the Control Service andconfirm the ports are correct for your installation.

Click on the Test button to confirm communication between the Agent andManager servers. If the test fails, confirm that required ports are open betweenthe servers and any firewalls in use.

You may also test the account to be used by the Agent by entering the accountname and password, and clicking the Test button.

Important Note: For the User Account, you must select an account which has

administrative access to both the SharePoint Front-End Web Server and your SQLServer. Use of a SharePoint service account is recommended.

Click Finish to complete to DocAve Agent installation.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

27/38




Configuring Integration with TSM Server

There are several storage options for the DocAve backups. For this solution, we will onlycover configuration of backups to a TSM server. This provides a more robust, flexible,

and configurable backup environment. Before you can begin backing up to a TSM serveryou must configure a Network Share, which is used by the TSM Server data type. Thefollowing steps walk you through setting up both of these items.

Creating the Network Share

The Network share is a requirement to use TSM as the backup destination. It is used tostore DocAve information during backups to TSM server.

On the DocAve Manager server, create a network share and grant permissions tothe domain account being used by DocAve.

From the DocAve web interface, go to Control Panel, then Data Management, and

select Device Manager. Select Net Share in the Data Type from the drop-down box. Click Add next to Physical Device in the right panel.

Enter a name for the new device in the Physical Device text box.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

28/38




Input the path to the share you just created. The path must be provided in UNCformat:\\\\.

Input the Domain\username, and password to set up access to the network sharethat cached data will be written to and stored.

Click Save to save the profile for the new physical drive and it will be listed underPhysical Drive.

Creating a TSM device

From the DocAve web interface, go to Control Panel, then Data Management, andselect Device Manager.

Select TSM from the Data Type drop-down box. Click Add next to Physical Device in the right panel.

Enter a name for the device in the Device Name text box. Select a Communication Method from the corresponding drop-down box, there are

three options: TCP/IP; SHARED MEM; and NAMED PIPES.

Input the TCP Port, TCP Server Address, Node Name and Password to set upaccess to the network path that data will be written to and stored. Note: This is theTSM Server information that is being entered, not the TSM client node information.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

29/38




Click Save to save the profile for the new physical drive and it will be listed underPhysical Device.

Creating a Logical device

The below steps associate physical devices created earlier with a logical device, whichthe DocAve backup plans use as the storage target.

From the Device Manager screen, enter a name for the new Logical Device in theLogical Device Name box.

Select a Data Type from the drop-down box, for this solution select TSM. Select the Media Agent tab next to Physical Device tab. From the right panel, drag the icon of the TSM Server you created earlier to the open

area under the Media Agent tab.

Select the Physical Device tab next to the Media Agent tab, and drag the TSMServer to the open area under the Physical Device tab.

The TSM Data Type requires a Cache Storage location. From the drop down list,select the Net Share physical device you created earlier.

Click Save to save the device settings and they will be listed under Logical Device,as shown below.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

30/38




Note: If you modify TSM Logical Device configuration, including changes to the TSMPhysical Device configuration, the media service may need to be restarted. If you modifyany of the following, you must restart the media service.

TCP Server Address Node Name or Password TCP Port or Communication method

The DocAve Dashboard

Below is a view of the Dashboard when the DocAve console is opened. You can quicklyview the structure and status of your environment at a glance. It includes a tip of the day,system health, and the status of running or completed jobs.

You can specify the interval and the scope of the status using the drop-down boxes. Byclicking on different color parts in the pie chart, you can drill down into specific detail forthat item.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

31/38




Backup Procedures

DocAves Custom Backup Builder contains two types of backups: a Granular Backupand a Platform Backup. It allows administrators to backup their SharePoint environmenton any level, from an entire Farm down to a specific Folder/ List.

Note: VSS is only available for Platform Level backups, however you can still performgranular restores, down to the document level, from a VSS based Platform backup.

Note: According to Microsoft, STSADM backups are not recommended for sites greaterthan 15 GB. As a result, DocAves Site or Site Collection Granular backup options, whichleverage STSADM, are not recommended in such cases. We recommend using theGranular BackupItem Level option or Platform Level backups in most instances, both of

which offer the ability to restore at the Site or Site Collection level.

This section covers a Platform level backup plan using VSS snapshots. The steps toperform a non-VSS, or standard Granular level backup are fairly similar, and the DocAveinterface is very intuitive. For more detailed steps please refer to the DocAveAdministrators Guide.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

32/38




Platform Level Backup is a Farm-level backup solution which enables SharePointAdministrators to backup Web Applications, Content Databases, search and indexservers and Front-End servers. Platform Level Backup can also backup file systemresources on front-end servers.

Selecting SharePoint Content

The first step is to find and select the SharePoint data to backup, as follows:

Navigate to DocAve -> Data Protection -> Custom Backup Builder and selectPlatform Backup.

On the backup tree builder window, select the name of the Agent Host from the dropdown box. This is normally the SharePoint Front-End Web server where the DocAveAgent is installed.

Clicking on the Agent displays the SharePoint Farm topology. The expanded treelists the levels available for backup, with the exception of the SharePoint Front-End

Web Servers, the tree can be expanded to the lowest level. For each selected level, there is a check-box corresponding to each level on the data

tree, the box is unchecked by default. Checking the box indicates that all content onthat level and underneath that level will be backed up.

Below is a view of the DocAve Platform Backup Builder, with the entire SharePointFarm selected.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

33/38




Configuring and Running the Backup

Select the Backup Method, VSS in this case. Select a Data Pruning configuration (optional). Data Pruning is beyond the scope of

this document, and is covered well in the DocAve Administrators Guide. Select the TSMserver you created earlier from the Logical Device list. Specify your Scheduling and Restore Granularity options. Repeat these steps to create additional schedules as necessary. Save the plan by clicking Save. After the plan has successfully been saved, it will be

displayed in the right panel area.

To run the plan immediately, click Run Now. A confirmation window will appear sothat you can confirm or change options, then click Run.

After the job starts, click the Go to The Job Report button to view the status in JobMonitor.

Below is a view of the Job Monitor, showing a successful Platform VSS backup using

the configuration outlined in this paper. Note that you can click on the Details buttonfor more information.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

34/38




Restore Procedures

The restore process is very intuitive, and the steps for each type of restore job aresimilar, regardless of which type of backup job you are restoring from. This section only

covers restores from a Platform Level backup, since our solution is focused on VSSbackup and restore.

Setting the Date Range

The first step of the restore process is to enter the time window of backups you want torestore data from:

Navigate to DocAve -> Data Protection -> Restore Controller, and select PlatformRestore.

Select an Agent from the drop-down box. Choose a time range in the Time Window fields for From and To. By default, it is

set to one week prior than the current time. You can click on the calendar icon to the right of the From and To field to change

the time range. Select a date and time in the calendar pop-up window and click OK.

Click Load Timeline. It will display yellow points indicating when the backup jobs randuring the specified period.

Mouse-over the yellow time points and they will show a quick summary of thebackup job in a pop-up window.

Clicking on the time point, you can review the detailed contents of the job in the treemode area.

Finding and Selecting Data for Restore

In the Restore Controller\Platform Restore interface, click on the time point todisplay the backup data in tree view.

Click the Farm Name to expand the data tree. Click DB Filter to search a site collection by typing the URL of the site collection, and

then click Search, it will list the database which the site collection is in.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

35/38




Alternately, you can click Detail after the Content Database listing to view thecontent of the database under the Detail tab.

Under the Detail tab, it lists the content of the database. You can click thecorresponding URL to expand the tree. Click the Information icon to view the

content inside, and check the corresponding box to select the content to restore. TheDetail tab provides granularity down to the item level.

By default, once you check the content, all items in it will also be checked. If youuncheck some items inside, the check-box will become a dash sign.

For large environments, you may want to limit the results displayed in the tree byclicking the Search icon. For case-sensitive searches, check the Case Sensitivebox located in the lower-left of the window. You can view the search result under theSearch Result tab.

Select the data to be restored. There is a check-box corresponding to each selectedlevel on the data tree which is by default unchecked.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

36/38




Advanced Restore Options

Once the backed up data has been located and selected, there are several optionsavailable for the restore, as well as some prerequisites and additional configurationsneeded. Going into detail on these items is beyond the scope of this document, butincludes the following:

In Place and Out of Place restore Restore databases to most recent state Restore database only Safe Restore Include security Full Farm restore

Refer to the DocAve Administrators Guide for in-depth coverage of these options andconfigurations.

Performing the Restore

Continuing in the Platform Restore screen, with our data selected. The following stepscover launching a basic restore job:

In the Restore Settings panel, select In Place restore. Select a Restore Option: either Overwrite, Append, or Not Overwrite.

Not overwrite: Will not restore the content if it already exists on the target. Forexample, if an entire folders content is selected for restore, but only one documentwas removed from the destination folder, only the removed document will be

restored.

Overwrite: Will restore the content over whatever exists on the destination. This willdelete the content on the destination and replace it with the content selected to berestored.

Select a time for the restore to run. By default, Now is selected and will run theprocess as soon as Go is clicked. You can set a scheduled date and time for thisrestore by clicking the calendar icon.

Optionally, enter a Description to help identify the job in the Job Monitor. Click Go. If you set the start time as now, it will run the restore job immediately.

Otherwise, it will run the job at the specified time.

You can view the job status real-time in Job Monitor, similar to the backup jobmonitoring, and view or export the backup report.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

37/38




Below is a view of the completed restore with detailed status report window.

Conclusion

The system configurations described in this document are designed to addressdemanding enterprise requirements for highly-available MicrosoftOffice SharePointServer 2007 deployments. Tivoli Storage Manager for SharePoint is designed to enablegranular, reliable backups of SharePoint sites, sub-sites, and items. With the addition ofMicrosoft VSS support, the entire SharePoint farm can be quickly, easily, and reliablybacked up with a negligible impact on production services.

The granular restore capabilities help reduce backup and restore complexity and

duration because restores are performed directly on the production server, and only theneeded data is restored. These are the type of restores most often requested by users.

The DocAve GUI is highly intuitive, and abstracts the administrators from the complexityof diverse backup & restore functionality of large-scale environments. Coupled with theextremely powerful Tivoli Storage Manager, which offers advanced enterprise-classfunctionality such as data-deduplication, offloaded (LAN free) backups & restores, tieredstorage repositories and archive management, this solution can scale & integrate easily.

IBMSystem x servers and System Storage arrays are designed to provide theprocessing throughput and scalable storage needed for large SharePoint environments.IBMTivoli Storage Manager for SharePoint is designed to help support true fault and

disaster tolerance. The combination of IBM

Tivoli Storage Manager and SharePointforms a solid backup and recovery platform for mission-critical SharePoint deployments.

8/6/2019 TSMsharept_6.1_DS8000_v1.8

38/38

Copyright

2009 by International Business Machines Corporation.

This document could include technical inaccuracies or typographical errors. IBM may make changes,improvements or alterations to the products, programs and services described in this document, includingtermination of such products, programs and services, at any time and without notice. Any statements

regarding IBMs future direction and intent are subject to change or withdrawal without notice, and representgoals and objectives only.

The information contained in this document is current as of the initial date of publication only, and IBM shallhave no responsibility to update such information.

Performance data for IBM and non-IBM products and services contained in this document was derivedunder specific operating and environmental conditions. The actual results obtained by any partyimplementing any such products or services will depend on a large number of factors specific to such partysoperating environment and may vary significantly. IBM makes no representation that these results can beexpected or obtained in any implementation of any such products or services.

THE INFORMATION IN THIS DOCUMENT IS PROVIDED AS-IS WITHOUT ANY WARRANTY, EITHEREXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY,

FITNESS FOR A PARTICULAR PURPOSE OR INFRINGEMENT.

References in this document to IBM products, programs, or services does not imply that IBM intends tomake such products, programs or services available in all countries in which IBM operates or does business.Any reference to an IBM program or product in this document is not intended to state or imply that only thatprogram or product may be used. Any functionally equivalent program or product, that does not infringeupon IBMs intellectually property rights, may be used instead. It is the users responsibility to evaluate andverify the operation of any non-IBM product, program, or service.

The provision of the information contained herein is not intended to, and does not grant any right or licenseunder any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, inwriting, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

IBM, the IBM logo, System x, and System Storage are trademarks or registered trademarks of InternationalBusiness Machines Corporation in the United States, other countries, or both.

Microsoft, Windows, SharePoint, and SQL Server are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

i IBM Systems & Technology Group, Kirkland, WA,[email protected] IBM Systems & Technology Group, Raleigh, NC,[email protected]
mailto:[email protected]?subject=TSM%20SharePoint%206.1mailto:[email protected]?subject=TSM%20SharePoint%206.1mailto:[email protected]?subject=TSM%20SharePoint%206.1mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]?subject=TSM%20SharePoint%206.1

tsmsharept_6.1_ds8000_v1.8

Documents