DPM 2012 is unable to enumerate contents in "Servername_folder"

I have two DPM servers backing up a hyper-v cluster. Using D-D-D
The second DPM server has this issue, the main DPM server does not
Does this mean that the data on the first DPM server is corrupt?
I feel that I need to check the hard drive on my IFSCDPM server. But how can I do this, as the drive does not have a letter? (Chkdsk)

Please try following on the SQL Serber
Start "WBEMTEST"
connect to "root\Microsoft\SqlServer\ComputerManagement10"
an try the Query:
SELECT * FROM ServerSettings
do you get an error?
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

Similar Messages

DPM2012SP1 is unable to enumerate contents in msssql... ID error:38

I have a server with WIN2008R2 SP1 and SQL2008R2 SP1.
I have also a DPM2012SP1 running on WIN2008R2SP1.
evething looks good on both servers.
But when i go to create a group a protection group and spand the sql server i get this error message:
dpm is unable to enumerate contents in msssql server on the protected computer... ID Error: 38.
could some one help me please.
i just try reinstall dpm the agent on protected server, restart all sql service.

Please try following on the SQL Serber
Start "WBEMTEST"
connect to "root\Microsoft\SqlServer\ComputerManagement10"
an try the Query:
SELECT * FROM ServerSettings
do you get an error?
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

DPM 2012 SP1: Unable to connect to the DPM DB, because the DB is inconsistent state.

We are getting the following error when we try to recover from a specific server ( Recovery Tab | Domain | File Server )
Unable to connect to the DPM Database because the database is in an inconsistent state. (ID943)
=> There are no double entries for the specific server in the database. Verified by the following query:
select servername, domainname from dbo.tbl_AM_Server order by servername
=> DBCC Check DPMDB results in no errors.
=> Yesterday we used the following script to remove a ghost tape from our reports. The tape belongs to the PG where the File Server is member of.
http://social.technet.microsoft.com/Forums/en-US/a654c323-7b48-4ab5-8812-850115d9e430/dpm-2012-ghost-tapes-in-weekly-report?forum=dpmtapebackuprecovery
Is there a relation between our error and the removal of the ghost tape? Any idea how to fix this?

Hi,
I have not heard of that script causing any problems in the past, so may or may not be related. What are the details of the msdpm service crash found in the msdpmcurr.errlog after the error ?
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, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 unable to connect to Database after failed Update Rollup 4 Installation

We have a DPM 2012 R2 Server with SQL Server 2012 installed locally.
We tried to install Rollup 4 for DPM 2012 R2 (KB3009516) using Windows Update
and it failed with error code 0x80070643. Now when we open the DPM Console
it is totally empty (no Protection Groups, Servers, Disks, just like a fresh install).
In the eventlog we get a lot of Errors and warnings:
Event 941 (MSDPM)
Unable to connect to the DPM database. Make sure that SQL Server is running and that it is configured correctly.
Cannot open database "DPMDB" requested by the login. The login failed.
Event 4209 (MSDPM)
The description for Event ID 4209 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
DPM Writer encountered an internal error. Please restart the DPM Writer service, and then try the backup operation again. For additional troubleshooting information, review the application event log and the DPM Troubleshooting Guide.
Event 107 (Report Server Windows Service (MSSQLSERVER)
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event 274 (SQLISService110)
Microsoft SSIS Service:
Registry setting specifying configuration file does not exist.
Attempting to load default config file.
Then there are some Errors/warnings from SQLSERVERAGENT about failed scheduled Jobs.
I think the failed Installation changed some database Settings, so that now the DPM Console
cant access the database anymore.
I would be happy if someone can help me getting this Server working again!

Our biggest problem is, that the DPM is not working any more. So there is no chance to backup the SQL Server via DPM.
I think the main problem is that DPM have no access to the database. Every time I start the DPM Application, I get an error "verify that the DPM service is running on this computer". In the eventlog are many errors that the msdpm service was unable
to connect to DPM Database. Another "information" is that the user 'nt authority\system' failed to open the database of dpm.
We've tried to reinstall the DPM but its still the same problem. I suppose that is a corrupt database.
Tomorrow I try to restore the database and hope it will be the solution of our problem.

DPM 2012 R2 Unable to create protection groups after Cluster Migration

Hi Team
we have an issue relating to DPM 2012 R2. In our environment we have a Hyper-V Cluster and we recently did a Cluster Migration since Hyper-V Cluster was upgraded to Windows Server 2012 R2.
Before the upgrade, Windows Server 2008 R2 Cluster was protected by DPM Environment. After we upgraded we are unable to Create new protection Groups existing the new cluster and when we select VMs it's not showing up any members.
Please let us know how we can solve this issue since the Cluster Nodes and the Cluster Name is different from previous Cluster, we were expecting that DPM would allow us to create new Protection Groups while preserving old protection groups for recovery later
if needed.

Hi,
you need to stop the Protection of the old HyperV Datasources
Clear the Cache of the Protectiongroup,
and read the new VM to Protectiongroup
Seidl Michael | http://www.techguy.at | twitter.com/techguyat |
facebook.com/techguyat |
youtube.com/techguyat

DPM 2012 R2 cannot browse the contents of the virtual machine, Error 958, Details: Internal error code 0x80990F4E

Hi,
We have a Microsoft System Center 2012 R2 Data Protection Manager Version 4.2.1235.0 as a Guest system on a Hyper-V node. The Hyper-V role is on a Windows Server 2012 R2
I receive this error message:
DPM cannot browse the contents of the virtual machine on the protected computer [computername]. Item level recovery is not supported in the following scenarios.
1. The VHD contains a dynamic disk inside the guest OS.2. The VHD has no volume.
3. HyperV role is not installed on DPM server.
4. Automatic mounting of volumes is disabled on the DPM server.
1) Try enabling automatic mounting of volumes using mountvol on the DPM server to perform item level recovery
2) Otherwise perform a full restore of the virtual machine.
ID: 958
Details: Internal error code: 0x80990F4E
One of our protected Hyper-V guest systems backup suddenly refuses to browse the content of the VHD file. The system has 2 VHDs. One for the operating system and one for the data. The OS VHD has no problem with content browsing only the data VHDX started
this error after the installation of september update. I already checked the status that was suggested (1. the vhd contains a dynamic disk... etc. ) and everything is well configured. I have no free space to make a full recovery cause it's 6TB of data.
The updates that were installed are:
DPM Server
KB2977629
KB2966828
KB2988948
KB2993651
KB890830
KB2977765
KB2894856
Protected Guest system
KB2972213
KB2977629
KB2894852
KB2973114
KB2993651
KB2988948
KB890830
KB2977765
KB2894856
Any advice? Thank you in advance for any help.
Andras

Hi,
Does the protected VM have Windows dedup enabled on the volume that cannot be mounted ?
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, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 Failed to update permissions used in end-user recovery

Hello everyone,
I'm going to try the clearest way possible to describe the problem.
Our test server is Windows Server 2012 with DPM 2012 SP1 CU2 (BKP-SRV01) with a Remote SQL server 2012 (PBASC)
I protected a share folder on a DC on Windows Server 2008 R2 (PAD)
When I activate End-User Recovery I get a warning in the monitor tab that say this
Failed to update permissions used for end-user recovery on pad. Permissions update failed for the following reason: (ID 3123)
DPM is unable to enumerate contents in pad_PartageTest on the protected computer BKP-SRV01. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other removable media cannot be protected. (ID 38 Details:
the end user recovery is working, but i do not know if it affect other things. I also get that message when i try to browse on the DPM server when creating a protection group
When I go see the DPM Server / File and Storage Services / Shares on Server Manager i get "Failed to retrieve folder permission" in the properties of the Protected server share.
I tried to search for almost 2 days without finding anything about that particular issue.
Is there a way (clean way) to fix the issue?
Thanks in advance for the help!

Closing for housekeeping.
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, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.
That's not very helpful. I've got the same issue :(
Comes up for servers where a protection group related to it errors out (recovery point failure usually).

DPM 2012 R2 Repoting Protection Status as OK but no replica exists for the volume

2012R2 server running 2012R2 DPM. I am using LeftHand SAN as my DPM disks for storing backups. Our production SAN is an EMC VNX5300. I have created a mount point of a LUN and attached it to the DPM server. I have attached a snapshot to the mount point. When
I brought the volume online in Disk Management, it assigned it a drive letter. I removed the drive letter and connected it to a mount point in an empty folder in C:\ActiveVolumes. I am able to browse the folder and look at data in the folder without issue
(except having to elevate for some of the folders when browsing through GUI). In DPM, I created a new protection group. I added the mount point path (C:\ActiveVolumes\MyMountPoint) as a member of the PG. I walked through the wizard and configured my short
term and long term protection options as I have done for other jobs. I had it create the group. At the end of the process, it reported success. Based on having done this with other mount points in similar ways, I was expecting the volume to spend some hours
creating its replica as it is multiple hundreds of gig in size. After less than 15 minutes, it was sitting there with a Green OK display for Protection Status. That seemed entirely to quick so I started to investigate. When I tried to create do anything, it
failed. I looked in Monitoring/Failed jobs for yesterday and today. There was a failed job for the PG that said as follows:
Type: Replica creation
Status: Failed
Description: The Operation failed since DPM was unable to access the file/folder
\\?\Volume{GUID}\Company\Logs\Cleanup\filename.txt on dpm01.domain.pri. This could be due to the file/folder being corrupt or the file system on the volume being corrupt. (ID 2036 Details:
The file or directory is corrupted and unreadable (0x80070570))
There is a second error stating that No recovery point was created, either because synchronization has not occurred since the last recovery point was created, or because no changes were found during synchronization. (ID 208)
When I check the file in question on the original source, it is fine. When I connect to the mount point on the dpm server, browsing to the location, I find that the file says it is indeed corrupt. I will open a call with EMC as well, but it is a little concerning
that a single file can prevent a whole replica from being created. I also tried deleting the corrupt file and tried to synchronize again and it failed on another file in the same folder.
Some additional stuff I noticed as different:
In PG setup wizard, when expanding the DPM server under available members, after a few minutes, I get the following error:
"DPM is unable to enumerate contents in <longalphanumericstring> on the protected computer dpm01.domain.pri. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs Quorum Disk (for cluster) and other removable media cannot
be protected. (ID:38)"
Followed by the following:
"The database of this DPM server is located on a remote instance of SQL server.
To protect the database of this DPM server, you must install a protection agent on the computer running the remote instance of SQL server. After the protection agent is installed, open this wizard, navigate tot eh remote instance of SQL server, and select
the DPM database for protection.
Production server name: dpm01.domain.pri
DPM SQL DB name: MSSQLSERVER
DPM Protection agent: Not Installed"
The above is inaccurate because I am running the SQL on the same machine as my DPM server in the default SQL instance name. I have gotten both of the above errors before when trying to backup other mount points but I was able to back up those mount points
without issue.
I also noticed a difference since I created my first mount point backup. I created two folders on the root of the C: drive. ActiveVolumes and StaticVolumes. I had attached mount points under StaticVolumes previously (c:\staticvolumes\imagefolder1, etc.)
and was able to back those up without issue. When I was configuring that one, it allowed me to select to backup StaticVolumes and then it gave me a warning about mount points and did I want to back those up to. To which I replied yes, back them up. When I
was configuring this one, backing up ActiveVolumes was not an option, only the mount point below it. And it never gave me the warning about mount points. I don't know if this has anything to do with this problem.
Any assistance you can provide on figuring out why this isn't working would be much appreciated. I tried deleting the PG and starting over and got the same results. I am at a loss for how to back this up right now.

Hi,
Not sure what you want help with. Did you fix the underlying volume corruption issue ? For future posts, please limit the scope to a single well defined problem so the community can assist you best.
Please re-define a single problem statement if you still want assistance, other wise mark the post as resolved.
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, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 Replace secondary server

DPM
2012R2 UR 3
I had a secondary server die, and am trying to re-setup thee secondary server and
am running into problems
I am attempting to backup my 2 primary DPM servers (DPM1 and DPM2) with a 3rd DPM
server (DPM3).
I run in to 2 issues.
Through the console, i will install the agent on DPM1 and DPM2, and it says
it installed successfully. Then I will go and try to configure protection for that server:
It lists the server I "installed" the agent on, and shows it as a DPM server
However, when i expand the server to list the items to back up it throws an error
"DPM is unable to enumerate contents in 06eb093b9b0d43cebb20ad33fa7d83d3,
ect ect" It will allow me to backup the SQL server and the C
drive.
What I think is going on is that the agent is not being installed on the primary dpm
server (DPM1 and DPM2).
So I manually try to install the agent on DPM1 and I get another error that says
"Protection agent cannot be installed on machine where dpm is installed
DPM"

on the DPM server I am trying to backup I get the following error in the Application log:
The description for Event ID 945 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Unable to connect to the DPM database because of a general database failure. Make sure that SQL Server is running and that it is configured correctly.
Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>9188</Seq><TimeCreated>10/30/2014 2:23:41 AM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlException</ExceptionType><ExceptionMessage>Invalid
object name '##017127d2_c270_4cd3_9ee0_5ddc0adabb88tmp_tbl_ProtectedPS'.</ExceptionMessage><ExceptionDetails>System.Data.SqlClient.SqlException (0x80131904): Invalid object name '##017127d2_c270_4cd3_9ee0_5ddc0adabb88tmp_tbl_ProtectedPS'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlRetryCommand.ExecuteNonQuery()
   at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.DB.AMServerInfo.GenerateProtectedPSServerIDs(SqlContext ctx)
   at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.DB.ProtectedPSs.GeneratePSInfoXml(Object obj)</ExceptionDetails></FatalServiceError>
the message resource is present but the message is not found in the string/message table
NuttyBar

DPM 2012 R2 Bug: Unable to backup a VM with the same name as an old VM

Scenario:
You have a VM called "Virtual Machine 1" running on a Windows Server 2012 R2 Hyper-V cluster and you backup this virtual machine using DPM 2012 R2.
You remove "Virtual Machine 1" from DPM, selecting delete replicas and expire all tape backups, and then delete the VM from the cluster as it is no longer required.
Later you create a new virtual machine called "Virtual Machine 1" on the same cluster. You attempt to backup the VM with DPM however when attempting to add the VM to a protection group you get the error "DPM cannot access the path \Online\Virtual
Machine 1 because part of the path has been deleted or renamed. Check the path and enter it again". Refreshing the data source/clearing the cache doesn't help
The only solution I could find that worked was to delete the data source record in DPMDB..tbl_IM_DataSource for the virtual machine. This also required deleting records that referenced the DataSourceId in other tables.

Hi
yo need to clear the Cache on the ProtectionGroup Wizard.
Seidl Michael | http://www.techguy.at | twitter.com/techguyat |
facebook.com/techguyat |
youtube.com/techguyat

Upgrading DPM 2012 SP1 to DPM 2012 R2 fails (DPM Setup is unable to connect to the specific instance of SQL Server Reporting Service (ID: 33431)

The Background:
1. DPM 2012 SP1 was originally installed on a server with local SQL 2008 R2 instance (SQL was installed as part of DPM)
2. SQL database was upgraded to SQL 2012 SP1
Now I want to upgrade DPM 2012 SP1 CU3 to R2. It is throwing the following error. Any help would be appreciated.

This absolutely fixed my issue. I had upgraded my version of SQL and was then trying to upgrade DPM 2012 to 2012R2 and I could not figure out where the installation was querying old version of the reporting services.
DPM Log Before:
[6/4/2014 2:53:32 PM] Information : Query WMI provider for path of configuration file for SQL Server 2008 Reporting Services.
[6/4/2014 2:53:32 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ReportServer\RS_MSDPM2012\v10\admin for query: SELECT * FROM MSReportServer_ConfigurationSetting WHERE InstanceName='MSDPM2012'
[6/4/2014 2:53:32 PM] * Exception : => System.Management.ManagementException: Provider load failure
DPM Log After:
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is not present on this system.
[6/4/2014 3:25:36 PM] Information : Query WMI provider for SQL Server 2008.
[6/4/2014 3:25:36 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ComputerManagement11 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPM2012' and PropertyName='Version'
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is present on this system.
[6/4/2014 3:25:36 PM] Information : Inspect context initialized with
SQL Server namespace: \\{0}\root\Microsoft\SqlServer\ComputerManagement11
Reporting namespace: \\{0}\root\Microsoft\SqlServer\ReportServer\RS_{1}\v11\admin
SqlServerDetected: True
[6/4/2014 3:25:36 PM] Information : Check if SQL Server 2012 Service Pack 1 Tools is installed.
[6/4/2014 3:25:36 PM] Information : Inspect.CheckSqlServerTools : MsiQueryProductState returned : INSTALLSTATE_DEFAULT
[6/4/2014 3:25:36 PM] Information : **********************************************************************************
Thanks for This FIX!

DPM 2012 R2 - Replica is inconsistent (ID 104 Details: The parameter is incorrect (0x80070057))

Since implementing DPM 2012 R2, we have been having issues with several replicas in different protection groups. We are running version 4.2.1254.0. We have been unable to backup, as we are receiving the following error when running a consistency check:
An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))
Any idea how to get this fixed?

104
An unexpected error occurred while the job was running.
This error can appear if you are trying to protect a SQL Server database that has files on a remote share. This is not supported by DPM.
Please check below DPM error codes list for reference.
http://social.technet.microsoft.com/wiki/contents/articles/24613.system-center-data-protection-manager-error-codes.aspx

Some free tapes are not used by backup job - dpm 2012 r2

Hi,
I have DPM 2012 R2 with IBM TotalStorage 3572 tape library. It is 8 slot tape library. All was working with initial 8 tapes I added to tape library. I had one Protection group to be archived on 8 tapes. I was doing Daily and weekly backups. Every 2nd week
I would do a weekly backup and keep it for 2 weeks i.e. I need 2 tapes for weekly backups. All was working ok until I introduced two new weekly tapes as a replacement for 2 weekly tapes in library. Because of disaster recovery procedure - I have to take
weekly tapes out of library and store them in disaster recovery location for some time. So I pulled out 2 weekly tapes and added 2 new tapes. New tapes were marked free and they are showing as Free tapes.
Now - the trouble is that these 2 free tapes are not used by backup job and instead - backup job writes weekly backup on any of the available Daily tapes (like from 4-5 days ago) instead of using one of the Free tapes that are available.
I'd like the backup job (Protection group) to use Free tapes first and only if there are no available free tapes - to go and do backup on Daily tape or ask for a free tape.
I am probably doing something wrong here - so I would really appriciate if anyone can help me with this? Any ideas?
Thanks,
Damir.
D.

Hi,
What update rollup are you running on the DPM 2012 R2 server ? DPM 2012 R2 UR5 introduced a new refresh feature that will re-enumerate data sources on an individual protected server.
Check for VSS errors inside the guests that are having problems being backed up.
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, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs and Some Hyper-v VMs are not appearing in the DPM

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
(0x800423F3))
All the vss Writers are in stable state
Also Some Hyper-v VMs are not appearing in the DPM 2012 R2 Console When I try to create the Protection Group please note that they are not part of cluster.
Host is 2012 R2 and The VM is also 2012 R2.

Hi,
What update rollup are you running on the DPM 2012 R2 server ? DPM 2012 R2 UR5 introduced a new refresh feature that will re-enumerate data sources on an individual protected server.
Check for VSS errors inside the guests that are having problems being backed up.
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, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

DPm 2012 r2 problem after moving Sharepoint 2013 to a differnt SQL using another alias

Hi,
I have resently installed DPM 2012 r2 and I want to backup my Sharepoint 2013 farm. I can install the client on Sharepoint server and the SQL server. This is a new protection and I have earlier moved the Sharepoint 2013 farm to a different SQL server
not with the same name using the SQL alias method.
When I try to create a Sharepoint backup I get the old SQL server name and error to check the SQL wss is running. The wss is running and the DPM user is local admin and sysadmin og the new SQL server. I added in hosts the old SQL server name
pointing to the new sql server ip address.
I need to know if this is doable in DPM or must I do something else?
thanks.
Erró

Here is the information you needed.
* WRITER "SharePoint Services Writer"
- Writer ID = {da452614-4858-5e53-a512-38aab25c61ad}
- Writer instance ID = {b8787079-eacd-4ced-9c7d-1e9aa5ac240a}
- Supports restore events = TRUE
- Writer restore conditions = VSS_WRE_ALWAYS
- Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
- Requires reboot after restore = FALSE
- Excluded files:
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Config"
- Name: AVA_SP2013_Config
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Config
- Caption: Configuration Database AVA_SP2013_Config
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Config"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_State_Svc"
- Name: AVA_SP2013_State_Svc
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_State_Svc
- Caption: Generic Database AVA_SP2013_State_Svc
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_State_Svc"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Heimar"
- Name: AVA_SP2013_Content_Heimar
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Heimar
- Caption: Content Database AVA_SP2013_Content_Heimar
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Heimar"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Wiki"
- Name: AVA_SP2013_Content_Wiki
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Wiki
- Caption: Content Database AVA_SP2013_Content_Wiki
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Wiki"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
- Name: AVA_SP2013_Content_ActiveProjects
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_ActiveProjects
- Caption: Content Database AVA_SP2013_Content_ActiveProjects
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_ActiveProjects"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite"
- Name: AVA_SP2013_Content_Mysite
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite
- Caption: Content Database AVA_SP2013_Content_Mysite
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite1"
- Name: AVA_SP2013_Content_Mysite1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite1
- Caption: Content Database AVA_SP2013_Content_Mysite1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite2"
- Name: AVA_SP2013_Content_Mysite2
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite2
- Caption: Content Database AVA_SP2013_Content_Mysite2
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite2"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite3"
- Name: AVA_SP2013_Content_Mysite3
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite3
- Caption: Content Database AVA_SP2013_Content_Mysite3
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite3"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Content_Mysite4"
- Name: AVA_SP2013_Content_Mysite4
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Content_Mysite4
- Caption: Content Database AVA_SP2013_Content_Mysite4
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Content_Mysite4"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
- Name: AVA_SP2013_SharePoint_Admin_Content
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content
- Caption: Content Database AVA_SP2013_SharePoint_Admin_Content
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_SharePoint_Admin_Content"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
- Name: AVA_SP2013_Secure_Store_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB
- Caption: Generic Database AVA_SP2013_Secure_Store_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Secure_Store_Service_DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
- Name: AVA_SP2013_PerformancePoint Service Application
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_PerformancePoint Service Application
- Caption: Generic Database AVA_SP2013_PerformancePoint Service Application
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_PerformancePoint Service Application"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Managed Metadata Service"
- Name: AVA_SP2013_Managed Metadata Service
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Managed Metadata Service
- Caption: Generic Database AVA_SP2013_Managed Metadata Service
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Managed Metadata Service"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Word_Automation"
- Name: AVA_SP2013_Word_Automation
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Word_Automation
- Caption: Generic Database AVA_SP2013_Word_Automation
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Word_Automation"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Profile DB"
- Name: AVA_SP2013_Profile DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Profile DB
- Caption: Generic Database AVA_SP2013_Profile DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Profile DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\Sync DB1"
- Name: Sync DB1
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\Sync DB1
- Caption: Generic Database Sync DB1
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\Sync DB1"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_Social DB"
- Name: AVA_SP2013_Social DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_Social DB
- Caption: Generic Database AVA_SP2013_Social DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_Social DB"
+ Component "SharePoint Services Writer:\OldSQL.domain.com\AVA_SP2013_BDC_Service_DB"
- Name: AVA_SP2013_BDC_Service_DB
- Logical path: OldSQL.domain.com
- Full path: \OldSQL.domain.com\AVA_SP2013_BDC_Service_DB
- Caption: Generic Database AVA_SP2013_BDC_Service_DB
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\NewSQL.domain.com\NewSQL.domain.com\AVA_SP2013_BDC_Service_DB"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
- Name: Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\3cdf2288-dd08-4bc7-997d-6cad63d46328\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf
- Caption: OSearch Administration Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_DB_fcb92dbb4fbd4b39808465c5301802cf"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
- Name: Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\014481c8-0135-4957-82ab-55bf8417321d\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e
- Caption: OSearch Crawl Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_CrawlStoreDB_85660a45376440f5be52b67bc3df014e"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
- Name: Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\5613596c-7658-4479-8fba-e87e9cc81578\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9
- Caption: OSearch Analytics Reporting Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_AnalyticsReportingStoreDB_11cce20eb0084a9b80594dbffc122fa9"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
- Name: Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\41d46cb5-c603-4f60-9b2e-1fc96903329d\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50
- Caption: OSearch Links Database
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\OldSQL.domain.com\NewSQL.domain.com\Search_Service_Application_LinksStoreDB_df4336e1ef254b38adac1ee66311aa50"
+ Component "SharePoint Services Writer:\6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
- Name: IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Logical path: 6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e
- Full path: \6d68e675-85f9-4742-9dcc-d7df18d8c3ea\efa26bb2-ccc6-4e86-92fe-a423462f943e\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Caption: OSearch15 Content Index Catalog_6d68e675-85f9-4742-9dcc-d7df18d8c3ea
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{0ff1ce15-0201-0000-0000-000000000000}:\IndexComponentGroup_6d68e675-85f9-4742-9dcc-d7df18d8c3ea"
Erró

DPM 2012 is unable to enumerate contents in "Servername_folder"

Similar Messages

Maybe you are looking for