Hi,

I run a job in DPM 2012 to backup SharePoint server, I start backup up a week ago, It's run OK.

Yesterday I saw the job fail. there is event id 23 source: volsnap "There was insufficient disk space on volume C:\...a8a7-4ed1-9d70-a359e62e3581 to create the shadow copy of volume C:\...a8a7-4ed1-9d70-a359e62e3581.  Shadow copy storage creation failed."

all other jobs are running OK.

I got enough space in all disks.

need help with this issue.

Thanks

Hi, I'm trying to protect a Sharepoint 2013 farm with the databases on SQL 2012 AlwaysON AG on DPM 2012 SP1. I've read that 2 months ago was not supported but I wanted to know if there is any update on this issue. I keep receiving ID 32008 issue when I try to add the farm to a new Protection Group. I tried many workarounds and shortcuts to try to figure some alternative but there is none.

Similar posts or information: http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup

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

Thanks for any help on this matter.

I have a SharePoint 2010 server running on a 2008 R2 Hyper-V cluster that I'm trying to backup with DPM 2010

I'm getting the following error in DPM when I'm running either a consistency check, or a recovery point.

"DPM encountered a retryable VSS error.  (ID 30112 Details: VssError: The writer experience a transient error.  If the backup process is retried, the error may not occur. (0x800423F3))".

Running a VSSAdmin list writers command on the SharePoint server returns the following.

"Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {d6ff97de-6846-4b92-a30d-d4b33ab9af5f}
   State: [8] Failed
   Last error: Inconsistent shadow copy"

I was originally getting this error and "spserver $env:computername).NeedsUpgrade" in a SP mgmt. shell the result was "true" so I ran the "PSConfig.exe -cmd update -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures".

The backups then worked fine for approximately a week, now I'm back to where I was with the original error.  The upgrade command now returns "False".  I've tried restarting the server, restarting the SPSearch4 service etc etc, but still the same result

Any help would be appreciated.......

Hi,

We have Windows 2012 with DPM 2012 SP1 installed.

I am facing issue with one Protection group while automatic creating restore point

Even Though, I have enough storage in Storage Pool and selected Auto grow for each volumes

1. Error while synchronizing

Type:            Synchronization

Status:         Failed

Description:   DPM has run out of free space on the recovery point volume and will fail synchronization for E:\ on mybackup.mydc.local in order to prevent existing recovery points from being deleted. (ID 30195 Details: Internal error code: 0x80990AB2)

2. Error while creating recovery point

Type:            Recovery point

Status:         Failed

Description:  DPM does not have sufficient storage space available on the recovery point volume to create new recovery points. (ID 214)

However , When I create manual replication by right clicking its created without error.

Pls help

Thanks

Prakash

Hello Experts,

We have a DPM 2012 SP1 that is protecting SharePoint 2013 Farm [Which is installed over a SQL Cluster with named instance].

When I browse to the recoverable items, I find the content databases, and this error appears:

some of the databases were not available when the selected recovery point was created for farm recovery ensure that config and admin content databases are available in the recovery point

 Also there are two content databases that I cannot browse to restore the sites inside them. Whenever I double on the database nothing happens. I can browse the rest of databases and see the sites inside them.

Any ideas?

Thanks, Shehatovich

Hello - DPM is failing to restore a list to a site.  I've recovered successfully multiple times in the past and am confident that DPM and SharePoint are working well together overall. The restore point I'm trying to use is one prior to the installation of a Cumulative Update.  Source URL not found is the gist of the error and the details of the error do point out the requirement for the source and target must be at the same version. I'm just hoping for a little confirmation before telling the customer that we won't be able to restore from that time.

Thanks in advance for any information!

I recently started protecting my SharePoint 2013 site using DPM 2012 R2.  I was able to get item level recovery working, but not all of the database items are showing in the recovery section.  I go get the warning "DPM failed to gather item level catalog for 1 database(s) of the SharePoint Farm Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog. (ID 3133)"

I have looked on the SharePoint front end web server in the WssCmdletsWrapperCurr log file and I do not see any exception there.

It it is strange because I do get the option to restore some items, just not all of them.  Any help would be greatly appreciated.

In testing dpm 2k12r2 and sharepoint 2k13/sql 2k12, I had issues with the cataloging jobs failing and all of those jobs show 0 bytes transferred. When trying to restore I am able to drill down into the metadata.  In the SP WFE WssCmdletsWrapperCurr log file I noticed these lines. The service does not have computerManagement or computerManagement10 namespaces in wmi but does have computerManagement11 namespace for sql2012.  Any thoughts on if this is a bug or not?

17F8 185C 04/16 18:00:37.122 31 WSSCmdlets.cs(1022) [000000000095C870]  NORMAL ==>ResolveSqlAliasEx
17F8 185C 04/16 18:00:37.122 31 WssSqlAliasHelper.cs(442) [000000000095C870]  NORMAL SqlAliasResolutionDisabled = False
17F8 185C 04/16 18:00:40.054 31 WssSqlAliasHelper.cs(319) [000000000095C870]  NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement]
17F8 185C 04/16 18:00:40.117 31 WssSqlAliasHelper.cs(344) [000000000095C870]  NORMAL WMI namespace not found
17F8 185C 04/16 18:00:40.117 31 WssSqlAliasHelper.cs(319) [000000000095C870]  NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement10]
17F8 185C 04/16 18:00:40.117 31 WssSqlAliasHelper.cs(344) [000000000095C870]  NORMAL WMI namespace not found
17F8 185C 04/16 18:00:40.117 31 WssSqlAliasHelper.cs(495) [000000000095C870]  NORMAL count of the list of all aliases: 0
17F8 185C 04/16 18:00:40.117 31 WssSqlAliasHelper.cs(179) [000000000095C870]  NORMAL Unable to get the server name for the [SqlAlias: XXXXXXXXX\XXXXXXXXXXXXX]

Good Evening,

So I have 3 Servers in all, with the following configurations:

Server1: DPM2010.contoso.com (Domain A)

Server2: Sharepoint2010WFE.contoso.com (Domain A)

Server3: Sharepoint2010DB.contoso.net (Domain B)

I have prepared sharepoint2010wfe.contoso.com appropriatly by installing the DPM Agent, running configuresharepoint.exe -enablesharepointprotection & ConfigureSharepoint.exe enableSPSearchProtection.

I have prepared Sharepoint2010db.contoso.net by installing the DPM agent to the server using the manual installation method and creating local user credentials and connecting to the agent through install > attach agent.

In DPM all of agents are healthy so I go over to create the protection profile and I recieve the following error: DPM cannot protect your windows sharepoint services farm until you install agents on the following server: Sharepoint2010db.contoso.com (ID: 956)

I have already attempted creating an alias on the WFE server for Sharepoint2010db.contoso.com and have it point to Sharepoint2010DB.contoso.net but this did not resolve my issue at all.

Also please keep in mind that pinging Sharepoint2010db.contoso.com is invalid as there is not a valid DNS entry of any kind, Im not even sure where this name is coming from other than some sort of a mashup. Also I am unable to domain join the SQL server to contoso.com because of licensing costs.

A resolution to this issue woudl be greatly appreciated.

when will sharepoint single item recovery be possible when the content db is located in a SQL 2012 DAG?

Chris

I have a single SharePoint 2010 WFE and a SQL 2008 server backend. Since configuring DPM to run the SharePoint backup through the WFE, I have had no success with backups.

DPM Reports:

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. (0x800423F4))

Event Log on SQL Server Reports:

Log Name:      Application
Source:        SQLWRITER
Date:          4/24/2014 4:44:17 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf                                                                                                                                                                        ' is too long. Maximum length is 259.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf                                                                                                                                                                        ' is too long. Maximum length is 259.
</Data>
    <Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
  </EventData>
</Event>

Followed by:

Log Name:      Application
Source:        VSS
Date:          4/24/2014 4:44:17 PM
Event ID:      8229
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
   PostSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8229</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.
</Data>
    <Data>

Operation:
   PostSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036</Data>
    <Binary>2D20436F64653A20575254575254494330303030353239392D2043616C6C3A20575254575254494330303030333336352D205049443A202030303030363033362D205449443A202030303030323630342D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F66742053514C205365727665725C39305C5368617265645C73716C7772697465722E65786522202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>

When I run vssadmin list writers after the error, the "SqlServerWriter" show a State of [11]. I can restart the service and the error clears up showing stable, but the next time I run the backup it fails again.

From the error, it almost sounds like the path is too long. This doesn't totally make sense to me considering the database was successfully backed up before I tried to back it up as a SharePoint database.

Any suggestions would be appreciated.

Hi, we are having trouble restoring a SharePoint 2010 site collection using our DPM 2012 installation. The recovery process goes fine (restore of the database, attach to the sql server, export into WFE's filesystem) and the last phase, the SharePoint import, seems to end with an exception. We see this in the WssCmdletsWrapperCurr.errlog file:

Caught Exception while trying to import Url .....
Exception message =
There is an error during importing the Roles tag
Exception Stack =
  at Microsoft.SharePoint.Deployment.ReadAttribute.String(....
....

It looks like it is a SharePoint import issue, but I'm not sure. We have tried to restore the site into an empty one, and the exception appears again, although it *seems*  that the content has been recovered. We have imported using the security info on the recovery point.

I've searched for that error message in the Net but I've been unable to find anything appropriate.

Do you have any hints?

Thanks.

Hi, i have two farms with two dedicated DPM for each of them

• SP 2010 with SQL 2008 R2
• SP 2007 with SQL 2005

While recovery point is running for 2010 multiple databases are taken simultaneously while in 2007 only one database at time in sequential order which leads in large time for recovery point of farm.

any recommendations or modification known for this behavior

Thanks

Mina

Hi. Whenever I try to backup our Sharepoint 2007 Server, an error appears in the SQL and the backup Fails.

Source: SQLWRITER
EventID: 24583
Description: Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 5198
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: The path specified by "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy88\....." is a UNC path. UNC path is not supported in failover clustered enviornment.

With DPM 2010 we have no issue. The problem started when I migrate to the 2012 version of DPM.

DPM Server 2012
Sharepoint 2007 with SQL 2005 in Cluster

How can I solve this issue?

Thanks in advice.

Hi,

We use Vmware environment, have SharePoint on Vmware server. 

Is it possible to be protected by DPM 2012?

Because came across " http://technet.microsoft.com/en-us/library/hh757870.aspx " where it says ---

Front-End Web Server Running on Hyper-V Virtual Machine

Baskar.S

Hello,

I keep getting an Critical error from the Database Auto-Protection Failed.

It started when we removed a content DB from a SharePoint 2010 farm. I have double checked that nothing is referring that database any more.

I tried to re-configure the particular SharePoint protection group, and I tried to run the autoprotectinstances.ps1 but that alert comes everyday.

Description from DPM:

One or more databases could not be protected automatically because auto-protection failed. If the databases belong to a SharePoint farm, then the farm recovery points will continue to get created without these databases. (ID 32511)

Hi,

I've got a strange situation.

When I run:

ConfigureSharepoint.exe -EnableSharepointProtection

on a WFE - the SharePoint 2010 VSS Writer Service gets disabled!

I ran the command from an elevated CMD. The account used is the FarmAdmin Account that runs the farm Services.

The registry key: HKLM\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl

Domain\spfarmadmin is set to 0

When I run "stsadm.exe -o registerwsswriter" the SharePoint VSS Writer Service is set to automatically start and is running. Also the registry value is set to 1.

With this configuration I am able to protect SharePoint in DPM - but Single Item Recovery is not working.

DPM shows the error: Backup metadata enumeraton failed

My Environment:

DPM: 2012 R2 UR2 on Windows Server 2012 R2 with local SQL 2012 SP1

SharePoint: SharePoint 2010 on Windows Server 2008 R2 SP1

SQL: SQL Server 2008 Cluster on Windows Server 2003 x64 SP2

Does DPM 2012 support 15 minute incremental backups of SharePoint when backing up as a SP farm or only Express Full? When creating the protection group there is only the option for Express Full. The SharePoint SQL DB recovery models are set to FULL. Would expect it to do 15 minute incremental as this is what we can do with SQL.

Many thanks,

Marcus