Quantcast
Channel: Data Protection Manager -SharePoint Protection forum
Viewing all 238 articles
Browse latest View live
↧

DPM 2012 Sharepoint Protection - cross forest domain issues

August 6, 2012, 4:17 pm
$
0
0

Hi,

 I've just upgraded to DPM 2012 this week and i'm trying to implement Sharepoint Protection for multiple cross-forest domain Front-Ends. I've done the following, without any luck. When i go to create a new protection group, sharepoint farm protection isnt available as one of the options.

- insured DPM agent is install on all servers in environment

- logged in as farm admin account and ran command: configuresharepoint.exe -enablesharepointprotection. It comes back as operation completed successfully.

- insured VSS writer is only running on one Front End

- ran sysadm -o unregisterwsswriter and registerwsswriter and both come back successful.

I've tried this on multiple environments with the same results. Not sure where to go from now. Anyone experience this before? Is it an issue with the front ends being on a seperate domain from the DPM server?

↧
Search

Sharepoint node not showing up in DPM when creating a new protection group

April 5, 2013, 2:43 am
$
0
0
Hi, I've seen similar questions in this forum section and read them all... my problem seems to be different. Title says it all. Trying to protect a sharepoint 2010 WFE with DPM 2012 and the sharepoint node is not showing up. Only the 'all shares', 'all volumes' and 'system protection'. The account used is local admin on the DPM server and the sharepoint WFE and is also farm administrator.

Steps taken so far:

- installed DPM Agent on the WFE using the local admin/farm admin account above.

- ran configuresharepoint.exe -enablesharepointprotection with elevated privileges using the local admin/farm admin account (all ok)

-ran setdpmserver.exe -servername S2922P (thats our DPM server) with elevated privileges. (all ok)

I can see the firewall rules are created but since it's a domain network the firewall is turned off so that shouldn't be the issue, right?

↧
↧

Sharepoint Protection of Sharepoint 2007 Farm fails after installing DPM 2012 SP1 UR2

April 16, 2013, 11:38 am
$
0
0

Hi,
Windows Update installed UR2 on our server this Saturday. It failed during Windows Update (WU shows "failed" although DPM showed the new build number), but I have downloaded the update and applied it manually. I was able to update all agents successfully.

Since then all backups of our Sharepoint 2007 farm fail (Sharepoint 2010 runs fine) with the following errors:

1. SharePoint_Config fails with
DPM could not obtain backup metadata information for SharePoint Farm Sharepoint Farm\<server>\SharePoint_Config on <servername>. If the data source is a SharePoint farm then a valid recovery point has been created. However, content databases from this recovery point can be recovered using the alternate location option only. (ID 3134)

2. SSP_<server>\SharePoint_Config\SSPComponent_SharedServices_P4S and SPSearch_<server>\SharePoint_Config\SPSearchComponent_<server> fail with
An unexpected error occurred while the job was running. (ID 104 Details: Invalid pointer (0x80004003))

Everything was working perfectly before. I have found no error on the SharePoint or on the backup Database server (just 3 warnings).

This is serious since we need workings backups from this production farm. Please help.

Regards

Uwe

↧

Backup metadata enumeration failed

April 16, 2013, 1:24 pm
$
0
0
 

Hello,

I keep seeing this error on my DPM 2007 server VErsion: 2.0.8868.0 (installed on Server 2008 standard x64 SP2). SharePoint 2007 SP2 (Installed on Server 2003 x32 SP2 standard edition)

Affected area: Sharepoint Farm\sql03\SharePoint_Config
Occurred since: 15/04/2013 6:05:28 PM
Description: DPM failed to obtain catalog information as part of the backup for SharePoint Farm Sharepoint Farm\sql03\SharePoint_Config on sps02.momentumhealthware.local. Your recovery point is valid, but you will be unable to perform item-level recoveries using this recovery point. (ID 3103)
Recommended action: 1) If you do not expect to be performing item-level restores using this recovery point, then dismiss this alert; otherwise, take the recommended actions in the subsequent steps.
2) If the operation failed for a short-term backup to disk, in the Protection task area, select the data source and click Create recovery point to restart the backup.
3) If the operation failed for a short-term backup to tape, in the Protection task area, select all the failed data sources that belong to the same protection group, and click Create recovery point – tape. This will ensure that the tape backups are located on the same tape.
4) Dismiss this alert immediately after starting your backup.
Resolution: DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
 Inactivate alert

Troubleshooting: Manual backup to disk completes successfully but scheduled one fails from time to time. THis time around it's failing every time the backup runs.

- I've reset all crawled contents and manually stated the crawl with no success.

- Maybe there is a site that’s corrupted and needed to be removed and re-added as per my research but im not sure how to go about doing this.

Can i request one of you geniuses to assist me on this please?

Much appreciated


↧

Error message while backing up a SharePoint database by using DPM 2012...

December 26, 2012, 5:00 am
$
0
0

Hi;

I have DPM 2012 with update rollups 3 in my network. Everything is OK except DPM cannot backup one of my SharePoint 2003' databases. The error message is:

DPM encountered an error while performing an operation for \\?\GLOBALROOT\Device\Harddisk\VolumeShadowCopy955\SQLDATA\Shareoint1_SITE.mdf on sharepoint.mydomain.com (ID 2033 Details: Insufficient system resource exits to complete that requested service (0x800705AA))

The steps to resolve this problem that I have been applied so far:

  • Increased the Recovery Point volume, related to the database.
  • Increased the Page File on DPM server from 32 GB to 64 GB for the 32 GB RAM and approximately 1 TB Recovery point volume storage.

Any ideas?

Please VOTE as HELPFUL if the post helps you and 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.

↧
↧

Item level restore failed for SharePoint2013 on DPM 2012 SP1

March 20, 2013, 2:22 am
$
0
0

When trying to restore a document from SharePoint 2013 DPM starts the recovery prosess but failed with error:

object reference not set to an instance of an object..(ID 32017 Details: invalid pointer(0x80004003))

We have 2 Web Front End servers running Server 2012 Standard and 2 SQL servers running om Server 2012.

ConfigureSharePoint -EnableSharePointProtection are run only on one of the WFE servers.

Backup jobs seems OK but when trying to run a recovery of one document using "Recover without using a recovery farm" it fail.

I can see the .mdf and .ldf files in the folder I set for temp recovery.

From the WssCmdletsWrapperCurr.errlog:
WARNING The parameter 'spSiteCollection' is null.

↧

Item level restore failed for SharePoint2013 on DPM 2012 SP1 with Rollup2

April 30, 2013, 4:36 am
$
0
0

When trying to restore a document from SharePoint, DPM starts the recovery prosess but failed with error:
object reference not set to an instance of an object..(ID 32017 Details: invalid pointer(0x80004003))

We have 2 Web Front End servers running Server 2012 Standard and 1 SQL server running om Server 2012 with SQL2012
ConfigureSharePoint -EnableSharePointProtection have been run only on one of the WFE servers.

Backup is running without errors.

Restore prosess:
-Recover to orginale site
-Recover without using a recovery farm
- temp SQL (another SQL instanse on the same SQL server) Farm_admin is sysadmin
- DB temp location ( Folder on orginal DB server) The group EVERYONE has "Full Control)
- Folder on the web front end server (EVERYONE = Full Control

Progress.
Restore job starts
- The DPM_xxxxx are generated on the temp SQL_instance
- The .mdf and .ldf file are copied to the Temp folder under a GUID
- Then the .mdf and .ldf files are gone
There is an empty folder left on the web Front end server with the GUID from the job.

The the restore job failed with error:
DPM was unable to export the item https ://xxxxx.xxxx.xx/mysites/personal/bgrfol/Documents from  the content database xxxxx\xx\Tenant_Content_DMO.
Exception Message = Object reference not set to an instance of an object..(ID 32017 Details: Invalid pointer (0x80004003))

From the WssCmdletsWrapperCurr.errlog on the Web front end server:
4F7C 6080 WARNING ASSERT: (FileName:WSSObjectModelHelper.cs; LineNumber:494)
4F7C 6080 WARNING The parameter 'spSiteCollection' is null.
4F7C 6080 WARNING ASSERT: (FileName:WssExportHelper.cs; LineNumber:270)
4F7C 6080 WARNING spSite should not be null

Hope someone can give me a solution.

↧

DPM 2012 was unable to query the unattached content database

April 30, 2013, 4:12 am
$
0
0

Hello,

When i try to restore a SharePoint Item i get the below message.

I'm Recovering to original site, and recovery without using a recovery farm. The temporary SQL server is the DPM server itself.

Type: SharePoint export and import task
Status: Failed
Description: DPM was unable to query the unattached content database DB01\DB01\SP-Content. Exception Message = A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.). (ID 32018 Details: Unknown error (0x80131904) (0x80131904))

More information
End time: 30-04-2013 12:09:11
Start time: 30-04-2013 12:07:14
Time elapsed: 00:01:57
Data transferred: 0 MB (0 bytes)
Source details: bs1.corp.local
Target details: sp1.corp.local
Cluster node -

↧
Search

DPM 2012 ... is it Service Application Aware?

April 30, 2013, 11:02 am
$
0
0

I used DPM 2010 to protect SP2010. One of the problem was that DPM did not understand the databases which belong tot he service applications.

So we had to protect the DB of service apps like SQL databases. But this does not give restore capabilities of DPM.

Has this changed with DPM 2012? 

val it: unit=()

↧
↧

DPM cannot protect this Sharepoint Farm

May 7, 2013, 9:21 am
$
0
0

Hi

I’ve run into a problem with protecting SharePoint with DPM. The original Sharepoint SQL cluster was hosted on a SAN which unfortunately had crashed. We had managed to rebuild the environment on a different storage array and SharePoint is back up and running. I’m trying to protect it with DPM and I keep getting DPM cannot protect this Sharepoint Farm message box with 3 possible reasons on why.

1)Ensure that the Sharepoint VSS writer is reporting content database on the front-end web server

2)Verify that the SQL server VSS writer is enabled ad running in a healthy state on all the backend SQL server machines

3)Verify if some of the database that are part of this Sharepoint farm are already being protected by DPM.

The previous PG was deleted from DPM along with the replica.

I can create a PG with the new SQL cluster and can tick all the db’s on there without any problems, and I can select folders on the WFE and select them for protection without any issues. But when I select Sharepoint it fails with the error message.

I’ve checked the VSS writers and no error messages, and re-run the ConfigureSharepoint commands including the ResolveSqlAliases, but I’m still unable to protect Sharepoint. All Sharepoint servers have been restarted.

One this I have noticed is that when I select the Sharepoint box it shows as just ‘Sharepoint’ not Sharepoint\ServerName\Sharepoint_Config

Any ideas on steps I can take next??


↧

Unable to protect .. DPM Tries to connect to wrong SQL instance

December 27, 2012, 4:07 pm
$
0
0

DPM 2012 SP0, MOSS 2010 SP1, Clustered SQL 2008 R2 SP1, Windows 2008 R2 SP1

I have a farm with 3 front ends and clustered SQL back end. I have successfully setup DPM to backup our test farm that should be identical except for hostnames. When I moved to our production farm and attemtped to add protection for sharepoint, I keep getting error 966. (DPM could not connect to SQL server instance OLDSQLSERVER\INSTANCE on the protected computer CLUSTERHOST01). The odd thing is that this instance no longer exists and was never used in the SP2010 farm. It is the instance name that held our previous SP2007 farm. The upgrade was done via database attach method, so there is no reason the new farm should even know about the old instance name.

I have verified that all SQL aliases on all WFEs are correct. I cannot find reference to the incorrect name in central admin or with get-spdatabase. In all cases the SQL alias is what is listed for SQL server. I also checked both DPMRACurr.errlog and WssCmdletsWrapperCurr.errlog and could not find reference to the incorrect name. In all cases that I saw a database server listed it was either the Alias or the correct server that the alias points to.

Does anyone have any suggestions on where to go looking for the location DPM is getting the old server info from?

Thank you for any suggestions or consideration of this matter.

Regards,

Joe M.

↧

DPM 2012 SP1 & SharePoint 2013 item level backup

May 13, 2013, 7:09 am
$
0
0

I'm running DPM 2012 SP1 with the latest updates. I backup two separate SharePoint farms: a 2010 farm and a new 2013 far.
On the 2010 farm I have always been able to drill down to the file level when going in the recovery tab of DPM, but on the 2013 farm I cannot drill down from the top content DBs.

I deployed the agent on both 2013 FE and SQL servers and on the FE I ran the ConfigureSharePoint CMDLET with the switch -EnableSharePointProtection without problems. Not sure what I am doing wrong.

Tahnks.

↧

No Sharepoint Server 2007 Installation was detected on the local machine

May 16, 2013, 10:38 am
$
0
0

I have an environment with DPM 2012 sp1 and I am trying to enable search protection for Sharepoint 2013 w\SQL2012 backend.

When I try to enable protection of Sharepoint search I get the error below:

---

C:\Windows\system32>cd C:\Program Files\Microsoft Data Protect
n

C:\Program Files\Microsoft Data Protection Manager\DPM\bin>Con
xe -EnableSPSearchProtection
No Sharepoint Server 2007 Installation was detected on the local machine.

---

Does this feature need to be enabled for SP/OWA 2013?  When I configure the protection group in DPM I only see the farm listed, there are no search components listed?

For documentation all I can find is the following:

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

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

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

Which seems to indicate that I do need to enable search protection?

Thanks in advance,

K

↧
↧

Backup Metadata enumeration failed DPM 2012 SP2007

February 24, 2013, 4:39 pm
$
0
0

Hi

SharePoint 2007 backup with DPM2012 SP1 report error:

Affected area: Sharepoint Farm\SRV\DEVSP_SRV_Config
Occurred since: 24/02/2013 19:56:19
Description: DPM failed to gather item level catalog for 1 database(s) of the SharePoint Farm Sharepoint Farm\SRV\DEVSP_SRV_Config on SRV.domain.com. Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog. (ID 3133)
 More information
Recommended action: 
 To re-run the catalog job manually for the farm, run Start-CreateCatalog command in PowerShell.
Resolution: DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
 Inactivate

Diego Riera | Linkedin |Twitter | diegoriera.wordpress.com

Por favor, lembre-se de clicar em "Marcar como Resposta" no post que o ajuda, e clique em "Desmarcar como resposta" se um post marcado na verdade não responder a sua pergunta. Isto pode ser benéfico para outros membros da comunidade. Esta postagem é fornecida, sem garantias e sem direitos.

↧

Restore SharePoint farm into different SharePoint server

February 13, 2013, 8:22 pm
$
0
0

SERVER1
-FARM1
-SITE1

SERVER2
-FARM2
-SITE2

QUESTIONS

1. Is that possible for DPM to backup SharePoint FARM1 in SERVER1 and restore into SERVER2

2. Backup FARM1 and restore SITE1 into FARM2 in SERVER2

if possible, please explain the procedure.

I ever try restore file into same server but not to different server

thanks

↧
Search

Move content database files to different disk on a farm protected by DPM

March 13, 2013, 11:58 pm
$
0
0

Hi all,

We have found the following issue (DPM 2012 RU3): when moving content database files (.ldf, .mdf) to new disks (due to lack of space), DPM is not aware of these changes until, apparently, the SharePoint protection is stopped (with retention) + redefined (otherwise, the sync jobs fail with a file not found message as it tries to get the file from the original location).

This looks specially delicate when moving the SharePoint Config database. We had a disk issue and after moving this db's transaction log file, dpm was not able to recover of this situation and we had to stop protection (preserving data), and setting a parallel SQL Server protection of the content databases as re-engaging the sharepoint protection did not recover the situation. once we had enough retention on the SQL Server protection, we removed the old sharepoint data and recreated the SharePoint PG from scratch.

A similar situation happens when removing a content database.

Have you ever moved the SharePoint config database files to other disks? How do you do this, on a DPM context?

Regards

↧

SharePoint item level catalog failed

March 20, 2013, 3:37 am
$
0
0

Hi,

I install DPM 2010 and sharepoint 2010 SP1

Log Name:      DPM Alerts
Source:        DPM-EM

Description : DPM failed to gather item level catalog for 7 database(s) of the SharePoint Farm ash-portaldb\sharepointdb2010\sharepoint on ash-portal.andalusia.loc. Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog. (ID: 3133)

recommended action : To re-run the catalog job manually for the farm, run Start-CreateCatalog command in PowerShell

Note : 1. i was uninstall my DPM and re- install another one.

2. i run the following command shell on DPM Get-ProtectionGroup ash-dpm-02 | Get-
Datasource | Where-Object{$_.type-Like "*sharepoint*"} | Start-CreateCatalog ... but the following result apprear

job category                                status                                  Hascompleted

------------------                              ------------                          ---------------------

sharepointcatalog                        in progress                       False

---------------------------------------------------------------------------------------------------------

Mohamed Yahia | Syshunt@live.com

↧
↧

DPM failed to gather item level catalog

March 20, 2013, 3:40 am
$
0
0

Hi,

I install DPM 2010 and sharepoint 2010 SP1

Log Name:      DPM Alerts
Source:        DPM-EM

Description : DPM failed to gather item level catalog for 7 database(s) of the SharePoint Farm ash-portaldb\sharepointdb2010\sharepoint on ash-portal.andalusia.loc. Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog. (ID: 3133)

recommended action : To re-run the catalog job manually for the farm, run Start-CreateCatalog command in PowerShell

Note : 1. i was uninstall my DPM and re- install another one.

2. i run the following command shell on DPM Get-ProtectionGroup ash-dpm-02 | Get-
Datasource | Where-Object{$_.type-Like "*sharepoint*"} | Start-CreateCatalog ... but the following result apprear

job category                                status                                  Hascompleted

------------------                              ------------                          ---------------------

sharepointcatalog                        in progress                       False

---------------------------------------------------------------------------------------------------------

Mohamed Yahia | Syshunt@live.com

↧

Item level restore failed for SharePoint2013 on DPM 2012 SP1

March 20, 2013, 2:22 am
$
0
0

When trying to restore a document from SharePoint 2013 DPM starts the recovery prosess but failed with error:

object reference not set to an instance of an object..(ID 32017 Details: invalid pointer(0x80004003))

We have 2 Web Front End servers running Server 2012 Standard and 2 SQL servers running om Server 2012.

ConfigureSharePoint -EnableSharePointProtection are run only on one of the WFE servers.

Backup jobs seems OK but when trying to run a recovery of one document using "Recover without using a recovery farm" it fail.

I can see the .mdf and .ldf files in the folder I set for temp recovery.

From the WssCmdletsWrapperCurr.errlog:
WARNING The parameter 'spSiteCollection' is null.

↧

Sharepoint node not showing up in DPM when creating a new protection group

April 5, 2013, 2:43 am
$
0
0
Hi, I've seen similar questions in this forum section and read them all... my problem seems to be different. Title says it all. Trying to protect a sharepoint 2010 WFE with DPM 2012 and the sharepoint node is not showing up. Only the 'all shares', 'all volumes' and 'system protection'. The account used is local admin on the DPM server and the sharepoint WFE and is also farm administrator.

Steps taken so far:

- installed DPM Agent on the WFE using the local admin/farm admin account above.

- ran configuresharepoint.exe -enablesharepointprotection with elevated privileges using the local admin/farm admin account (all ok)

-ran setdpmserver.exe -servername S2922P (thats our DPM server) with elevated privileges. (all ok)

I can see the firewall rules are created but since it's a domain network the firewall is turned off so that shouldn't be the issue, right?

↧
Viewing all 238 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>