Announcing the SharePoint Administration Toolkit

The Microsoft SharePoint Administration Toolkit contains functionality to help administrateer (good catch A Mondale) and manage Office SharePoint Server 2007 and Windows SharePoint Services version 3.0. This toolkit contains two new functions – the ability to perform bulk operations on site collections and a Stsadm operation to update alert emails after a Web application has changed URLs.


 Download x86 | x64

Tip of the Day, April 25, 2008

Tip of the day:  Deleting orphaned Timer Jobs

Open SharePoint Central 3.0 Central Administration and click Operations.

Select Timer job definitions under Global Configuration.

image

Select the orphaned Timer Job from the list of Timer Jobs.

Locate the Globally Unique Identifier (GUID) for the Timer Job in the browser address bar.

image

Copy the GUID to the clipboard and replace %2D in the GUID with hyphens.  For example the entry in the illustration above should appear as fc42d1d3-1e94-4dee-998d-e0086b6f8300.

Open a Command Prompt and change directories to %commonprogramfiles%Microsoft SharedWeb Server Extensions12BIN.

Run stsadm -o deleteconfigurationobject {guid} where {guid} is the GUID captured in the previous steps.

NOTE Use this process to manage other orphaned configuration objects in addition to Timer Jobs!

High-Availability and Disaster Recovery with Microsoft SQL Server 2005 Database Mirroring and Microsoft SQL Server 2005 Log Shipping for Microsoft SharePoint Products and Technologies

I’ve discussed on several occasions Microsoft SQL Server 2005 Database Mirroring with Microsoft SharePoint Products and Technologies as a method by which database mirroring can provide intra-datacenter high-availability; however, am frequently asked how Microsoft SQL Server 2005 Database Mirroring can provide protection from datacenter failure.  While possible, you generally do not want to geographically distribute your principal and mirror instances due to potential problems with maintaining synchronicity and bandwidth/latency constraints instead maintaining and intra-datacenter session to provide local fault tolerance; however, you can implement Microsoft SQL Server 2005 Log Shipping in conjunction with Microsoft SQL Server 2005 Database Mirroring to provide a standby copy of your databases in the remote datacenter.

General Assumptions

Microsoft SQL Server 2005 Database Mirroring is installed and configured in high-safety mode with a witness server (synchronous).

Mirroring w Witness

The illustration above depicts Microsoft SQL Server 2005 Database Mirroring in high-safety mode with a witness server.  SQL01p is the principal server, SQL02m is the mirror server, and SQL01w is the witness server in the Microsoft SQL Server 2005 Database Mirroring session.

Configure the Principal/Primary Server

Configure Microsoft SQL Server 2005 Log Shipping on the principal Microsoft SQL Server 2005 server using either the Microsoft SQL Server Management Studio or Transact-SQL for each database to be mirrored using either a backup share on a separate host server or local folder.

See notes on Log Shipping with Microsoft SharePoint Products and Technologies.

When the Microsoft SQL Server 2005 Log Shipping configuration has been applied on the Microsoft SQL Server 2005 Database Mirroring principal server, failover the databases to the Microsoft SQL Server 2005 Database Mirroring mirror server.

Configure the Mirror/Primary Server

Configure Microsoft SQL Server 2005 Log Shipping on the mirror Microsoft SQL Server 2005 server using Transact-SQL, Microsoft SQL Server Management Studio cannot be used to configure the mirror server where participating in a shared Microsoft SQL Server 2005 Log Shipping session.

When the Microsoft SQL Server 2005 Log Shipping configuration has been applied on the Microsoft SQL Server 2005 Database Mirroring mirror server, failover the databases to the Microsoft SQL Server 2005 Database Mirroring principal server.

NOTE When configuring Microsoft SQL Server 2005 Log Shipping on the mirror/primary server you will receive an error indicating a transactional log backup could not be generated because the database is in either NORECOVERY mode or STANDBY mode.  The error is expected due to the state of the databases and can be ignored.

Log Shipping

The illustration above depicts both the principal and mirror configured as log shipping primary; however, in this scenario only the principal generates log backups.  In the event failover occurs within the Microsoft SQL Server 2005 Database Mirroring session, the new principal (previously mirror) will begin generating log backups at the log backup destination used by the original principal.

When the configuration of Microsoft SQL Server 2005 Log Shipping has been completed on the Microsoft SQL Server 2005 Database Mirroring pair, the log backup job will on the principal server will generate log backups on the backup share that will be applied by the primary server, the log backup job on the mirror server will continue to execute though will not generate logs until failover occurs within the Microsoft SQL Server 2005 Database Mirroring session.

Resources

Microsoft SQL Server 2005 Database Mirroring

Microsoft SQL Server 2000/2005 Log Shipping

Data Protection Manager 2007 Whitepaper on Backup and Recovery of Microsoft Office SharePoint Server 2007 Search Components

A new whitepaper has been published on protecting the Microsoft Office SharePoint Server 2007 Search components.  The whitepaper includes scripts to enable Data Protection Manager 2007 to backup and recover the Microsoft Office SharePoint Server 2007 Search components and a detailed set of instructions on configuring Data Protection Manager 2007. The sample scripts provide guidance on backing up the search index, Search and Shared Services Provider databases.


Read more…