Dear Team,

How to activate bit locker in my laptop? or how can i come to bit locker activated in my laptop or not?
My idea is to enabling bit locker option for External hard drive (such as pendrive ,usb har dsik).Please guide how to activate it 

I have been backing up two file servers in a trusted subdomain, and suddenly am no longer able to back them up with the following error as of April 25th of this year.

The DPM service was unable to communicate with the protection agent on  (ID 52 Details: The encryption type requested is not supported by the KDC (0x80090342))

DPM server is 2012 R2 SP1 with latest CU (4.2.1417.0) on Server 2012 R2 which is fully patched. File servers I am backing up are 2008 R2, and 2012 R2, both fully patched as well. 

Things I've tried:

1. Restarting bot the DPM server and File servers to be backed up.
2. Refreshing the agent (Management tab shows both agents as updated and "OK" for their status)
3. Consistency Checks
4. Pausing and resuming protection.

In the event logs I can see the DPM RA start on the File Servers when I perform a consistency check. I don't see any errors in the file server Event Logs. I can browse to the file servers via Windows Explorer and see all shares from the DPM server. I csn also backup the system state and BMR on a domain controller within the subdomain without issue.

Suggestions?

For the USN journal to work the backed file server have to be added to DPM as Shares or normal catalogs. I have two Files servers added as normal catalogs (each ~500 GB) and the consistency check takes several hours.

According to this

https://blogs.technet.microsoft.com/dpm/2016/02/25/backup-of-enterprise-data-made-easier-with-system-center-data-protection-manager/#comment-10723

it should be up to 60x faster then before UR9

Setup:

2 node Failover Cluster Dell PE430

Storage Matrix MD3820i

Network backbone 2 Cisco WS-C3850-24T

DPM Server is a VM on Windows 2012 R2

Protected Server is a VM on Windows 2008 R2

Every thing is updated

Running DPM 2012R2 (4.2.1338.0) on Windows 2012 R2 with at latest patch level.

Recently changed the file server and at first we were running with deduplication enabled. After seeing this error (see title) when running backup to tape, we turned deduplication off.

Now deduplication is turned off on the file server but we are still getting the error every time when performing tape backups. There are no issues performing recovery points, synchronizations or consistency checks to disk. We have only had one successful tape backup, just after we migrated to this file server but none since. After running the first few consistency checks DPM fixed thousands of items but now there are no items to correct and the check goes through.

The backup goes to 170 GB and then fail with error: (ID 2019 Details: An existing connection was forcibly closed by the remote host (0x80072746))

As I understand it, the tape backup does not retrieve information from the protected server, instead it shuffles data from the DPM server to the tape loader, so it should not be an issue at the protected server?

Any ideas or suggestions welcome.

Thanks, /M 

Hi

We are moving from protecting our DPM server with another server to use an Azure Data Vault.  2 of the Protection Groups work fine, but the third - protecting a pair of Folders - fails.  On the DPM MMC it shows Online recovery point creation failed, and in the Event Log it shows -

The DPM server is the only one conducting any backups.  The target server is Win 2003 (for the moment). 

Could anyone give me any pointers?

Thanks

Hi,

We're currently running DPM 2012R2 on a Server 2012R2 server. We're using Azure online backups as an alternative to our weekly tape archive. This was set up and has been running mostly fine for the past month or two.

Recently I installed the latest rollup update (to build 4.2.13120) to allow our data server to backup to the cloud (our primary data server has a 1TB disk that was previously blocked by the 850GB limit). Since installing the update package, my second data server has not been able to complete an online backup and errors with the following:

"Online recovery point creation jobs for <Volume> on <Server> have failed 1 times. (ID 3188)
Backup has encountered an irrecoverable error. (ID 34504)"

Looking at the event log on the DPM server I can see the following error:

"Creation of online recovery points for <Volume> on <Server> have failed. The last online recovery point creation failed for the following reason: (ID: 3188)
The current operation failed due to an internal service error [0x7E3]. Please retry the operation after sometime. (ID: 100066)"

I can't seem to find much in the way of useful information for the cause or source for any of the above listed error codes. I've been attempting to run this backup for over a week, so it does not appear to be a transient error. The volumes that are in error are Deduped volumes on their host server (Server 2012 R2 server), although I haven't had any issues before this with creating replicas and recovery points on the local DPM server.

Hoping that someone out there can shed some light on the error codes and point me in a direction for solving this.

Thanks,

Nick.

Hi,

I have a DPM 2012 R2 installation that has been configured to use Azure for online protection.  All data is being successfully backed up for all servers except for the one of the three drives on file server.  The recovery point to the cloud starts fine and i can see data going up to the cloud, however at some point the data seems to stop and sits there for a day or so and then eventually returns a fail with ID 3188.  I havechecked the service as stated for this error and it is set to automatic as suggested in error code.

I have completely removed the online protection and tried starting again, but i receive the same outcome.

The protection agent is using the latest version available from Azure.  I can see from within Azure the data has been sent up but it will not register this as a recovery point to be able to restore from.

I have also made a registry change as suggested on other posts to increase failed file and this has not resolved the issue.  It now seems to sit running and never timing out now.

Can somebody assist please as it is getting very urgent this is resolved

Hi. 

We have protected our file server with DPM. All the backup operations works fine but we are facing trouble with restore operation. As part of our monthly schedule, we restore our backups to archiving server and then make another copy to off-site location. 

During data restoration, dpm prepends its internal path before the actual file / folder paths. This causes some files / folder exceeding 256 character limits and fails the copy operation.

Is there any way to change this default behavior of dpm?

It took us a while to figure this out, so I'm posting this in case it's helpful for someone out there. Plus, I have a question...

DPM gave the following error for one of our file servers:

Description: The replica of Volume D:\ on <servername> is inconsistent with the protected data source. Number of files skipped for synchronization due to errors has exceeded the maximum allowed limit of 100 files on this data source (ID 32538 Details: Internal error code: 0x809909FE)

Recommended action: Review the failure errors for individual files from the log file \\?\Volume{8492c150-f195-11de-a186-001cc4ef89a0}\B1E9D373-2C03-464E-A472-99BC93DB1E2A\FailedFilesLog.txt and take appropriate action. If some files fail consistently, you can exclude the folders containing these files by modifying the protection group or moving the files to another location.

So, how do you actually open the FailedFilesLog.txt file shown in this DPM alert? What is this path referring to? Well, this is the mount point for the protected server's replica volume on the DPM server, which is mounted under \Program Files\Microsoft DPM\DPM\Volumes\Replica\servername\File System. Here you'll see the mount points for all of the server's protected volumes. However, if you try to open one of these mounted volumesin Windows Explorer, you'll get Access Denied, even if you have administrator rights. (If someone knows of a way around this, please let me know). As a workaround, you can access this mounted volume in an elevatedcommand prompt. Steps:

1. Open an Administrator Command Prompt
2. Type mountvol <AnyAvailableDriveLetter>: \\?\Volume{VolumeGUID}
3. Example:  mountvol m: \\?\Volume{8492c150-f195-11de-a186-001cc4ef89a0}   Note that we're only using the first part of the path to the FailedFilesLog.txt file given in the DPM alert, starting from \\? and ending after the} character.
4. Next, type m: to change to the newly mounted m: drive.
5. Then type cd B1E9D373-2C03-464E-A472-99BC93DB1E2A   This is actually a folder name so we're just going into this folder.
6. Finally type dir and you should see the FailedFilesLog.txt file. This file can be copied to another location where it's easier to use (i.e. in Windows Explorer).
7. Be sure to unmount this volume when you're done by typing mountvol m: /d in the command prompt. (Mountvol reference:http://technet.microsoft.com/en-us/library/cc772586(WS.10).aspx.)

What a pain, eh? But at least by reviewing the FailedFilesLog.txt file you can determine which files or folders caused the sync to fail and thus take action accordingly.

Now, here's my question: Where is that registry key that lets me adjust the limit of 100 files that DPM allows to be skipped before it fails the replica? Hopefully someone out there will tell me. I know this can be done because Kapil Malhotra said so in this post: http://groups.google.com/group/microsoft.public.dataprotectionmanager/browse_thread/thread/a179fa30fb50c9b0/e9a348f2a9386063?lnk=raot.

Also, does anyone know what the internal error code 0x809909FE means in this alert? Knowing this my help us determine what caused these files to fail. Interestingly, in the FailedFilesLog.txt file, it gave a different error code next to each failed file: 0x80070002.

-Taylorbox

Hi,

I am backing up a server through DPM 2012 R2 UR9.

The problem Im having is that one drive is failing on a server that is protected.

When I start the backup it doesnt transfer any data. I´ve run "vssadmin list writers" on the server and nothing is abnormal. There is also enough free space for shadow copies to be created.

I have also restarted the server and the Cryptographic Services.

While backing up the F: drive on the server I get the following error in DPM,

"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 specified object was not found. (0x80042308))"

"Please check that the Event Service, the VSS service and the shadow copy provider service is running, and check for errors associated with these services in the Application Event Log on the server SERVERNAME. Please allow 10 minutes for VSS to repair itself and then retry the operation."

When I am checking in eventviewer for VSS error I find the following,

"Volume Shadow Copy Service error: Unexpected error calling routine GetVolumeNameForVolumeMountPoint is now failing on the volume, winerror 0x00000001. .  hr = 0x80070001, Incorrect function."

and

"Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume{cadf72ad-6468-42af-8ba5-04f2755f7435} - 0000000000000244,0x0053c010,0000008806E9B160,0,0000008806E9C170,4096,[0]). 

Operation: 

Committing shadow copies

Context:   

Execution Context: System Provider"

Any ideas? :-)

I am backing up a file server with DPM.  There is currently 23.7TB of data being backed up.  The replica volume size was 26TB.  I ran into a scenario where the volume needed a consistency check.  I started the check and let it run.  A day later, the check failed saying it ran out of disk space.  Turns out, the replica volume had totally filled up.  So I added an additional 2TB of space and kicked the job off again.  After another day, the job failed and the volume was full again.  I've ran consistency checks in the past and they have never needed this much space to finish.  In fact, they never appeared to need any additional space at all.  I have several questions?

1.  Is something not working as it's supposed to?

2. How much space will DPM need to successfully complete the consistency check?

3. Why is the consistency check taking up so much space?

We've been running DPM 2012 for a couple months now after replacing our old failing backup system.  Everything is going great other than we're having real issues backing up 2 volumes from one of our file servers.   Both of these volumes have dedup enabled.

We are running DPM 2012 R2 (4.2.1417.0) on Server 2012 and the dedup role is installed.

I have checked the 'details' of each failure and they're both pretty much identical;

Type:	Synchronization
Status:	Failed
Description:	The replica of Volume V:\ on SERVERNAME is not consistent with the protected data source. (ID 91)
	More information
End time:	13/06/2016 18:35:41
Start time:	13/06/2016 18:35:40
Time elapsed:	00:00:00
Data transferred:	0 MB
Cluster node	-
Source details:	V:\
Protection group members:	7
	Details
Protection group:	File Servers

Because the synchronisation fails the Recovery Point then also fails

Type:	Recovery point
Status:	Failed
Description:	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)
	More information
End time:	13/06/2016 18:04:09
Start time:	13/06/2016 18:04:06
Time elapsed:	00:00:02
Data transferred:	0 MB
Source details:	T:\
Protection group members:	8
	Details
Protection group:	File Servers

All of the other drives on this particular server are backing up fine so I'm pretty sure it's an issue with them being dedup'd at this point.

Does anyone have any further advice on what could be causing this?  I have aleady ran several consistency checks but they take days to finish and when they do they're pretty much straight back to inconsistent.

Hello

I would like to backup data from a TrueCrypt encrypted USB drive to Tape using DPM.  I have mounted the volume and added PG.  However backup to tape fails with errors shown below.

I'm guessing it's a VSS issue with TrueCrypt but wanted to ask if it was technically possible?

Thanks

The back up to tape job failed for the following reason: (ID: 3311) Failure
occurred while adding one or more of the volumes involved in backup operation to
snapshot set. Please check the event log on <server> to
troubleshoot the issue. (ID: 30290)

Log Name:      Application
Source:        VSS
Date:          6/16/2016 12:33:08 PM
Event ID:      12293
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
].

Operation:
   Check If Volume Is Supported by Provider
   Add a Volume to a Shadow Copy Set

Context:
   Execution Context: Coordinator
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Volume Name: \\?\Volume{b29301f1-3052-11e6-80c3-1402ec36e687}\
   Execution Context: Coordinator
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">12293</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-06-16T16:33:08.000000000Z" />
    <EventRecordID>9872</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
    <Data>IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff</Data>
    <Data>0x8000ffff, Catastrophic failure
</Data>
    <Data>

Operation:
   Check If Volume Is Supported by Provider
   Add a Volume to a Shadow Copy Set

Context:
   Execution Context: Coordinator
   Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Volume Name: \\?\Volume{b29301f1-3052-11e6-80c3-1402ec36e687}\
   Execution Context: Coordinator</Data>
    <Binary>2D20436F64653A20434F52434F4F524330303030313739302D2043616C6C3A20434F52434F4F524330303030313731302D205049443A202030303030373334342D205449443A202030303031313234342D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>

Hi All,

When I am running a tape job for a dedup file server, the backup fails with following error

Description:        The Operation failed since DPM was unable to access the file/folder \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1505\197d1387-eb5a-4a87-a459-06d757b2d875\Full\DATA\General\Knowles Limited\95864 Primeplace Limited v Knowles Limited\Letters\Thumbs.db on  UKDAR1BK011.hillintl.com. 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))

The actual file on file server is accessible. what should be the next action plan.

I am experiencing a problem with backing up one of my volumes to Azure via DPM 2012 R2 (Rollup 10).

From viewing the CBEngineCurr.errlog i have found that the VHD file that the job tries to mount at the start of the job is failing to do so. I can verify this by going to "Disk Management" and it pops up with a message asking me to initialise a new drive.

The VHD that it is trying to mount shows in Disk Management as 54400.00GB which is far larger than the capacity available on the volume (the scratch volume is 800GB in size).

I have tried following steps suggested by other posts in this forum that have had similar issues, but i am failing to get any success.

I have pasted the section of the errlog file that is displaying the errors below.

If anyone has any idea of how to sort this it would be greatly appreciated.

13D0	1A58	06/23	13:05:53.152	03	miscellaneousutils.cpp(292)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x8007007e] GetModuleHandle failed for Library [RefCountedVhdManager], will try LoadLibrary
13D0	1A58	06/23	13:05:53.214	03	registryutils.cpp(321)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	RegUtils::GetStringFromRegKey(), Read value from registry: HKLM\Software\Microsoft\Windows Azure Backup\Config\scratchLocation
13D0	1A58	06/23	13:05:53.246	22	vdshelper.cpp(293)	[000000001C2E5D10]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	VdsHelper: VDS Service started
13D0	1A58	06/23	13:05:53.246	03	miscellaneousutils.cpp(292)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x8007007e] GetModuleHandle failed for Library [HypervVhdHelper], will try LoadLibrary
13D0	1A58	06/23	13:05:53.292	32	vhdhelper.cpp(15)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	pVhdHelper:[1c2468700x, Type:[1]]
13D0	1A58	06/23	13:05:53.292	03	miscellaneousutils.cpp(292)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x8007007e] GetModuleHandle failed for Library [NativeVHDProvider], will try LoadLibrary
13D0	18DC	06/23	13:05:53.339	03	timer.cpp(490)																					ACTIVITY	CTimerMgr::TimerThread
13D0	18DC	06/23	13:05:53.339	03	timer.cpp(503)	[000000001C245140]																ACTIVITY	CTimerMgr::TimerThreadInternal
13D0	1A58	06/23	13:05:53.339	79	WcfClient.cs(948)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Executing web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.ROCatalog.Interface.IROCatalogExternalChannel}{Description = GetReplica}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ROCatalogExternalService.svc}
13D0	1A58	06/23	13:05:53.339	69	CBEngineWcfClientHelper.cs(358)							6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Setting RequestId header for outgoing request | Params: {RequestId = 902db79b-5802-4aa4-83d6-4a891e933402}{WorkitemId = 7479e44e-ebff-40c6-b40e-3fb61f49f681}{TaskId = 6a6b1b09-ed07-456a-bd1b-a97b82c2ef00}{AgentVersion = 2.0.9037.0}
13D0	1A58	06/23	13:05:53.746	79	WcfClient.cs(969)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Finished web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.ROCatalog.Interface.IROCatalogExternalChannel}{Description = GetReplica}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ROCatalogExternalService.svc}
13D0	1A58	06/23	13:05:53.761	32	vhdmgmt.cpp(223)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Configured scratch location for VHDs, Catalog as [F:\Scratch\Scratch]
13D0	1A58	06/23	13:05:53.761	71	nativeutils.hpp(47)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	RegUtils::GetValueFromRegKey(), Read value from registry : [Software\Microsoft\Windows Azure Backup\Config\CloudBackupProvider] : [ResyncNeeded_46c0ed58-6411-4ae8-b3bf-4d7ffe8304bd]
13D0	1A58	06/23	13:05:53.761	71	replica.cpp(762)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	CBpDsReplicaContext::IsOperationSet(), Read value from registry: [Software\Microsoft\Windows Azure Backup\Config\CloudBackupProvider] : [ResyncNeeded_46c0ed58-6411-4ae8-b3bf-4d7ffe8304bd]
13D0	1A58	06/23	13:05:53.761	32	vhdmgmt.cpp(426)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Allocate - ReplicaId [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}], LunSize [2147483648] StorageFormat [1]
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(292)	[000000001C97E6F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : hFile = ::CreateFileW(ssCurrentFilePath.PeekStr(), (0x80000000L), 0, 0, 3, 0x00000080, 0)
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(127)	[000000001C97E6F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : ReadFile(ssFilePath, ssObjectStr)
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(140)	[000000001C97E6F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990fa5] : Failed to find record for specified object
13D0	1A58	06/23	13:05:53.777	32	vhdmgmt.cpp(316)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Found old replica size : [46c0ed58-6411-4ae8-b3bf-4d7ffe8304bd] [0]
13D0	1A58	06/23	13:05:53.777	32	vhdmgmt.cpp(1662)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Deallocate - StorageInfoId [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}]
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(292)	[000000001C97E570]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : hFile = ::CreateFileW(ssCurrentFilePath.PeekStr(), (0x80000000L), 0, 0, 3, 0x00000080, 0)
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(127)	[000000001C97E570]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : ReadFile(ssFilePath, ssObjectStr)
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:53.777	32	filebasedcatalog.h(140)	[000000001C97E570]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990fa5] : Failed to find record for specified object
13D0	1A58	06/23	13:05:53.777	32	vhdmgmt.cpp(1791)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Database file not found. Trying to unmount and delete all data under Dir: F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\
13D0	1A58	06/23	13:05:53.777	32	vhdhelper.cpp(15)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	pVhdHelper:[1c245a000x, Type:[1]]
13D0	1A58	06/23	13:05:53.777	32	vhdmgmt.cpp(2383)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Trying dismount on all VHDs. Mount - MountInfoId [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}], MountInfoType [1], Force [1]
13D0	1A58	06/23	13:05:53.777	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\
13D0	1A58	06/23	13:05:53.777	18	fsutils.cpp(2900)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : FSWrapperGetFileAttributes(ssInputDirPath.PeekStr(), &dwAttribs, fCaseSensitive)
13D0	1A58	06/23	13:05:53.777	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\
13D0	1A58	06/23	13:05:53.777	18	fsutils.cpp(2900)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : FSWrapperGetFileAttributes(ssInputDirPath.PeekStr(), &dwAttribs, fCaseSensitive)
13D0	1A58	06/23	13:05:53.777	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\
13D0	1A58	06/23	13:05:53.824	79	WcfClient.cs(948)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Executing web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.Protection.Interface.IProtectionServiceChannel}{Description = GetServiceProperty}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ProtectionService.svc}
13D0	1A58	06/23	13:05:53.824	69	CBEngineWcfClientHelper.cs(358)							6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Setting RequestId header for outgoing request | Params: {RequestId = 3da544f4-5e4f-47ae-a921-b22852ffbbf9}{WorkitemId = cb5dcc1d-26db-4337-ae48-e8aa1210f921}{TaskId = 6a6b1b09-ed07-456a-bd1b-a97b82c2ef00}{AgentVersion = 2.0.9037.0}
13D0	1A58	06/23	13:05:54.089	79	WcfClient.cs(969)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Finished web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.Protection.Interface.IProtectionServiceChannel}{Description = GetServiceProperty}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ProtectionService.svc}
13D0	1A58	06/23	13:05:54.089	32	salcataloghelper.cpp(1404)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	GetServiceProperty API succeeded.  Returned size [58411555225600]
13D0	1A58	06/23	13:05:54.089	32	salcataloghelper.cpp(948)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	AllocateStorageProc API - StorageInfoId = {46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}, Size = 1099511627776
13D0	1A58	06/23	13:05:54.121	79	WcfClient.cs(948)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Executing web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.Protection.Interface.IProtectionServiceChannel}{Description = AllocateStorage}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ProtectionService.svc}
13D0	1A58	06/23	13:05:54.121	69	CBEngineWcfClientHelper.cs(358)							6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Setting RequestId header for outgoing request | Params: {RequestId = d5da1cee-13b3-4bcf-8896-d7ef57a56ab1}{WorkitemId = 793fb03c-11ee-41c6-91f7-c1b49bcba587}{TaskId = 6a6b1b09-ed07-456a-bd1b-a97b82c2ef00}{AgentVersion = 2.0.9037.0}
13D0	1A58	06/23	13:05:55.105	79	WcfClient.cs(969)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Finished web service call | Params: {ServiceInterface = Microsoft.Internal.CloudBackup.Common.Protection.Interface.IProtectionServiceChannel}{Description = AllocateStorage}{TargetEndpoint = https://pod01-prot1.ne.backup.windowsazure.com/ProtectionService.svc}
13D0	1A58	06/23	13:05:55.105	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:55.105	32	filebasedcatalog.h(292)	[000000001C97E4F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : hFile = ::CreateFileW(ssCurrentFilePath.PeekStr(), (0x80000000L), 0, 0, 3, 0x00000080, 0)
13D0	1A58	06/23	13:05:55.105	32	filebasedcatalog.h(127)	[000000001C97E4F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Encountered Failure: : lVal : ReadFile(ssFilePath, ssObjectStr)
13D0	1A58	06/23	13:05:55.105	32	filebasedcatalog.h(134)									6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	FileBasedCatalog::Read failed for file F:\Scratch\Scratch\Catalog\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.dat
13D0	1A58	06/23	13:05:55.105	32	filebasedcatalog.h(140)	[000000001C97E4F0]				6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990fa5] : Failed to find record for specified object
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for \\?\F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(657)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : Failed to get attributes for \\?\F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for \\?\F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx
13D0	1A58	06/23	13:05:55.105	32	vhdmgmt.cpp(4811)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x1c31b8a0] CVhdMgmt::VerifyVhdExists(), FSWrapperGetFileAttributes() for vhd path: F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.vhdx
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.vhdx
13D0	1A58	06/23	13:05:55.105	32	vhdmgmt.cpp(4811)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x1c31b620] CVhdMgmt::VerifyVhdExists(), FSWrapperGetFileAttributes() for vhd path: F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.vhdx
13D0	1A58	06/23	13:05:55.105	32	vhdmgmt.cpp(513)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	VHD initialization required for Replica Id = [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}] at scratch location [F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}]
13D0	1A58	06/23	13:05:55.105	32	vhdhelper.cpp(15)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	pVhdHelper:[1c2456800x, Type:[1]]
13D0	1A58	06/23	13:05:55.105	32	vhdhelper.cpp(15)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	pVhdHelper:[1c2467900x, Type:[1]]
13D0	1A58	06/23	13:05:55.105	22	vdshelper.cpp(293)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	VdsHelper: VDS Service started
13D0	1A58	06/23	13:05:55.105	22	nativevhdprovider.cpp(487)	[000000001C2AF790]			6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx: lVal : pfnOpenVirtualDisk(&storageType, ssVhdPath.PeekStr(), AccessMask, OPEN_VIRTUAL_DISK_FLAG_NONE, &vdOpenParam, &hDisk )
13D0	1A58	06/23	13:05:55.105	22	nativevhdprovider.cpp(487)	[000000001C2AF790]			6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx: lVal : pfnOpenVirtualDisk(&storageType, ssVhdPath.PeekStr(), AccessMask, OPEN_VIRTUAL_DISK_FLAG_NONE, &vdOpenParam, &hDisk )
13D0	1A58	06/23	13:05:55.105	22	nativevhdprovider.cpp(487)	[000000001C2AF790]			6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx: lVal : pfnOpenVirtualDisk(&storageType, ssVhdPath.PeekStr(), AccessMask, OPEN_VIRTUAL_DISK_FLAG_NONE, &vdOpenParam, &hDisk )
13D0	1A58	06/23	13:05:55.105	22	nativevhdprovider.cpp(487)	[000000001C2AF790]			6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80070002] : F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx: lVal : pfnOpenVirtualDisk(&storageType, ssVhdPath.PeekStr(), AccessMask, OPEN_VIRTUAL_DISK_FLAG_NONE, &vdOpenParam, &hDisk )
13D0	1A58	06/23	13:05:55.105	32	vhdmgmt.cpp(1407)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990ff2] : Encountered Failure: : lVal : UnmountVhdImpl(ssVhdFileAbsolutePath , fIsForced)
13D0	1A58	06/23	13:05:55.105	18	fsutils.cpp(4165)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80070002] Unable to GetFileAttributes for F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx
13D0	1A58	06/23	13:05:55.105	32	vhdmgmt.cpp(1321)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Attempt to delete old vhd [F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx] returned Hr: = [0x00000000]. Ignoring any error.
13D0	1A58	06/23	13:06:04.792	22	vdshelper.cpp(1991)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Disk Name, fIsDiskFound = Port2Path0Target0Lun0, 0x0
13D0	1A58	06/23	13:06:04.792	22	vdshelper.cpp(1991)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Disk Name, fIsDiskFound = Port0Path0Target4Lun0, 0x0
13D0	1A58	06/23	13:06:04.792	22	vdshelper.cpp(1819)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Vds Pack for the disk \\?\PHYSICALDRIVE4 not found with VDS
13D0	1A58	06/23	13:06:04.792	22	vdshelper.cpp(923)										6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Hr: = [0x80990fb0] Disk [\\?\PHYSICALDRIVE4] is not found as unknown
13D0	1A58	06/23	13:06:04.792	22	vdshelper.cpp(1733)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990fb2] : Encountered Failure: : lVal : QueryAllocatedDiskInternal( ssDiskSCSIAddress, pDiskProperties, &pVdsPack, fIsPackFound)
13D0	1A58	06/23	13:06:09.808	22	vdshelper.cpp(1991)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Disk Name, fIsDiskFound = Port2Path0Target0Lun0, 0x0
13D0	1A58	06/23	13:06:09.808	22	vdshelper.cpp(1991)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	Disk Name, fIsDiskFound = Port0Path0Target4Lun0, 0x0
13D0	1A58	06/23	13:06:09.808	22	vdshelper.cpp(1819)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Vds Pack for the disk \\?\PHYSICALDRIVE4 not found with VDS
13D0	1A58	06/23	13:06:09.808	22	vdshelper.cpp(1733)	[000000001C2E74D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Failed: Hr: = [0x80990fb2] : Encountered Failure: : lVal : QueryAllocatedDiskInternal( ssDiskSCSIAddress, pDiskProperties, &pVdsPack, fIsPackFound)
13D0	1A58	06/23	13:06:09.808	32	vhdmgmt.cpp(1350)	[000000001AF495D0]					6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	SCSI address for [F:\Scratch\Scratch\VHDs\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}\{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}.tmp.vhdx] metadata Vhd is \\?\PHYSICALDRIVE4
13D0	1A58	06/23	13:06:09.808	32	rebuildmetadatavhdmanager.cpp(95)	[000000001C2C9330]	6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	CRebuildMetadataVHDManager::Rebuild - Replica Id = [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}], Initializing metadata VHD downloader.
13D0	1A58	06/23	13:06:09.808	32	msfstreamdownloader.cpp(73)	[000000001C2AFBB0]			6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	CMSFStreamDownloader::Initialize Using GUID = {71DEA6D3-99C4-4781-B577-2D9999291F6F} for metadata vhd block blob download
13D0	1A58	06/23	13:06:09.808	32	msfstreamdownloader.cpp(126)	[000000001C2AFBB0]		6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	NORMAL	RebuildMetadataBlockStream API - Replica Id = [{46C0ED58-6411-4AE8-B3BF-4D7FFE8304BD}]
13D0	1A58	06/23	13:06:09.808	79	SWTTokenValidator.cs(56)								6A6B1B09-ED07-456A-BD1B-A97B82C2EF00	WARNING	Cached Token Expired | Params: {ErrorCode = IdTokenExpiredError}{ExpiryTimeWindow (ulong) = 28800}

Hi all - I'm trying to setup a scenario where I can compress my (local, not Azure) Disk backups and Encrypt my (local, not Azure) Tape backups in DPM 2012 R2 for the same clustered File Server.  Unfortunately, if I have the Tape Job already created, there doesn't seem to be a way in the DPM Console to do this (setup a separate, disk-only protection group for the same Cluster Resource).  Am I missing something, or can it be done with the Management Shell, or is it simply not possible?

Thanks in advance.

Ken

-Ken

A DPM 2010 backup of a 2008 R2 DC keeps failing, although the single other file server within that Protection Group succeeds. The protection status is perpetually 'replica is inconsistent', and the error on the DPM server is' Creation of recovery points for Non VSS Datasource Writer on DCNAME.Domain.rootdomain have failed. The last recovery point creation failed for the following reason: (ID: 3114) DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code: 0x9563F0). (ID: 30229)

   On the DC there are plenty of errors pertaining to the Windows backup service including:

    The backup operation that started at '‎2016‎-‎06‎-‎14T14:44:09.190508100Z' has failed with following error code '0x8078015B' (Windows Backup encountered an error when accessing the remote shared folder. Please retry the operation after making sure that the remote shared folder is available and accessible.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

In Windows Server Backup it says 'operation failed. Retry the operation. If the issue persists, delete and recreate the scheduled backup settings. The remote shared folder does not exist

I have checked the backup path and it goes to a share on the DPM 2010 server which indeed does not exist, although lots of others do. These are all mounted volumes distributed accross several physical disks, so I do not wish to just create a share with the same name manually as I doubt very much I can get all the configuration to be the same as it should be. How can I get DPM 2010 to create this share again? I have removed this DC from the Protection Group, and then created a new Protection Group in which I added this DC, but the problem remains the same.

Thanks.