DPM 2012 R2 cannot protect this SharePoint 2010 (ID: 32008)
Hello Support
we install DPM 2012 R2 in our company all works fine
except the SharePoint 2010 backup ,when I try to add the SharePoint to the protection group
it gives me error DPM 2012 R2 cannot protect this SharePoint 2010 (ID: 32008) see print screen attached
please need assistant
Thanks
Avi
January 15th, 2014 6:45am
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
January 15th, 2014 5:25pm
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
- Proposed as answer by
ivl
21 hours 10 minutes ago
January 15th, 2014 5:25pm
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
- Proposed as answer by
ivl
Friday, January 17, 2014 3:05 PM
January 15th, 2014 5:25pm
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
- Proposed as answer by
ivl
Friday, January 17, 2014 3:05 PM
January 15th, 2014 5:25pm
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
- Proposed as answer by
ivl
Friday, January 17, 2014 3:05 PM
January 15th, 2014 5:25pm
Hi
Please note the below regarding error ID: 32008. I would first ensure the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG). If you have identify
that the Share Point backend DBs are not in a SQL 2012 Always on Availability Group (AG) next look into items 1-3 noted in the error window reported.
At this time no versions of DPM (including DPM 2012 R2) support protecting SharePoint when using SQL 2012 Always on Availability Group (AG). Additionally
this issue will not be fixed in System Center DPM 2012 R2, but possibly post R2.
For future updates on the limitation outlined above please check the Announcement section of Data Protection Manager SharePoint Protection topic.
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."
- Proposed as answer by
ivl
Friday, January 17, 2014 3:05 PM
January 15th, 2014 5:25pm
We too have run into this issue.
Our SharePoint 2010 databases are in a SQL 2012 AlwaysOn Availability Group. We do not want to lose the high availability offered by SQL 2012 AlwaysOn, but we would like to backup our SharePoint 2010 farm using DPM 2012 R2. It is unfortunate that we cannot
have both.
I hope that this can be addressed sooner rather than later as we will now have to fall back to SQL based backups using DPM, therefore we lose item level recovery on our farm.
January 17th, 2014 10:06am
No I don't have SQL 2012 Always on Availability Group (AG).
We Use SQL 2008 R2
- Edited by
Avi Sunak
2 hours 54 minutes ago
January 21st, 2014 4:18am
No I don't have SQL 2012 Always on Availability Group (AG).
We Use SQL 2008 R2
- Edited by
Avi Sunak
Tuesday, January 21, 2014 9:17 AM
January 21st, 2014 12:16pm
No I don't have SQL 2012 Always on Availability Group (AG).
We Use SQL 2008 R2
- Edited by
Avi Sunak
Tuesday, January 21, 2014 9:17 AM
January 21st, 2014 12:16pm
No I don't have SQL 2012 Always on Availability Group (AG).
We Use SQL 2008 R2
- Edited by
Avi Sunak
Tuesday, January 21, 2014 9:17 AM
January 21st, 2014 12:16pm