Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to configure DPM protection for Sharepoint 2007

28 views
Skip to first unread message

Jelle

unread,
Jan 26, 2010, 6:03:01 AM1/26/10
to
Hi there,

Let me give you my configuration first.
2 Frontend Sharepoint servers which are load balanced
1 Indexing server
1 database server
All of the above run on Windows 2008 R2 x64
Sharepoint has SP2 installed and is using Microsoft SQL 2008

The DPM server has Windows 2008 SP1 standard installed and DPM is on SP1.

I want to configure the new sharepoint environment to be backupped with DPM
2007. However, I cannot get this to work.

I've tried two methods.
First thing I did was install the DPM clients on all sharepoint machines and
tried to run the "configuresharepoint.exe –EnableSharePointProtection"
command. After entereing the correct username and password for the shrepoint
admin I get the following error:

Object reference not set to an instance of an object.

An error occurred while trying to start the Sharepoint VSS Writer

After a few tries I removed the DPM client and tried to run "stsadmin -o
registerwsswriter" this resulted in:

Object reference not set to an instance of an object.

Can somebody help me out here? I have no idea what's going on.

Regards,

Jelle

Jelle

unread,
Jan 27, 2010, 8:55:01 AM1/27/10
to
Seems like I've solved the problem myself.

Here's what I did.

- Uninstalled all agents
- ran the Sharepoint Products and Technologies Configuration Wizard
- Installed all agents
- ran the Configuresharepoint.exe -EnableSharepointProtection command
- Created a new protectiongroup and selected the sharepoint data
- ran the Configuresharepoint.exe -EnableSPSearchProtection
- added the search components to the protected data.

and that's it, it all works like a charm now.

Also there was a network issue what prevented me from accessing the Database
server from the WFE servers. I think this combined with the Sharepoint
Products and Technologies Configuration Wizard was the problem.

0 new messages