SharePoint
(1)
Database
(1)
Vignesh
(1)
Ivan
(1)
Consistensy
(1)
HVSPRGS0023
(1)
Datatabase
(1)
Reprotect
(1)

Cannot modify protection group - sharepoint

Asked By iku
21-Nov-09 01:46 PM
Hello,
I made following mistake:
- I added second database to sharepoint
- before the datatabase was backed up as part of sharepoint I had added
it to protection group as ordinary database
- the database was backed up but sharepoint backup is inconsistent now,
because it cannot back up the second database

When I want to change protection group, the result is the same for all
operations:
Removing Sharepoint Farm\hvsprgs0023\SharePoint_Config_htcz failed:
Error 201: DPM failed to protect the SQL database HVSPRGS0023
\hvsprgs0028_DS since this was part of the SharePoint Farm hvsprgs0023
\SharePoint_Config_htcz which is either under active protection or has
an inactive replica available.

I cannot even remove the whole protection group.

Can I do something with it ?

Thanks for your help,
Ivan

Hi,can you stop protecting the second db as ordinary db ( you can do

C.Prashanth [MSFT] replied to iku
24-Nov-09 12:24 PM
Hi,
can you stop protecting the second db as ordinary db ( you can do stop
protection for it from protection ui) and then try to do modify pg of
sharepoint and expand the sharepoint node and complete the wizard. if that
still fails, please do a stop protection of sharepoint farm with retain data
and reprotect it again

--
Thanks,
C.Prashanth [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

prashcha@online.microsoft.com says...

iku replied to C.Prashanth [MSFT]
25-Nov-09 04:39 AM
prashcha@online.microsoft.com says...

Hello,
I cannot stop protection of the second db - the message is still the
same. I cannot stop sharepoint protection - message is the same.
I did even this:
- I removed the second database from sharepoint
- I made consistensy check - now it was ok
- I tried to stop protecting the second database - still the same
message
- I tried to stop protecting sharepoint farm - the same message
- I tried to stop protecting the whole group - still the same

Ivan

[This followup was posted to microsoft.public.

iku replied to C.Prashanth [MSFT]
04-Dec-09 05:42 AM
[This followup was posted to microsoft.public.dataprotectionmanager and
a copy was sent to the cited author.]

prashcha@online.microsoft.com says...

Hello,
I cannot stop protection of the second db - the message is still the
same. I cannot stop sharepoint protection - message is the same.
I did even this:
- I removed the second database from sharepoint
- I made consistensy check - now it was ok
- I tried to stop protecting the second database - still the same
message
- I tried to stop protecting sharepoint farm - the same message
- I tried to stop protecting the whole group - still the same

Ivan
This is a multi-part message in MIME format.------=_NextPart_000_003B_01CA8175.
Vigneshwaran Chandramohan [MSFT] replied to iku
20-Dec-09 02:38 AM
This is a multi-part message in MIME format.

------=_NextPart_000_003B_01CA8175.7B11EED0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit

Hi,

What is the DPM version that you are in? In DPM V2 this was an issue and
there is a SQL script to get DPM out of this situation. The issue is fixed
in SP1 , so users cannot get into this state after installing SP1 .

Thanks,
Vignesh

This posting is provided "AS IS" with no warranties, and confers no rights

------=_NextPart_000_003B_01CA8175.7B11EED0
Content-Type: text/x-vcard;
name=".vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=".vcf"

BEGIN:VCARD
VERSION:2.1
N:;viki
REV:20091220T073809Z
END:VCARD

------=_NextPart_000_003B_01CA8175.7B11EED0--
Hello,unfortunately you can get into this state even after SP1 - I am theprove.
iku replied to Vigneshwaran Chandramohan [MSFT]
23-Dec-09 03:14 PM
Hello,
unfortunately you can get into this state even after SP1 - I am the
prove.
In the meantime the problem was solved with microsoft support. He
directly modified the dpm database to get rid of bad reference to sql
database. It was easy. Then it took one week to find the job which was
in the dpm database and crashed the dpm every day.

Regards,
iku
Post Question To EggHeadCafe