If a file system recovery point and synchronization time are scheduled at the same time, does the recovery point process wait for the synchronization process to complete before it starts?
Thanks.
If a file system recovery point and synchronization time are scheduled at the same time, does the recovery point process wait for the synchronization process to complete before it starts?
Thanks.
I have a backup that was working for the past couple of years and all of a sudden I can't get it to complete a consistency check. The error I'm getting is:
Description:The replica of Volume F:\ on {server} is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover
data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
The Operation failed since DPM was unable to access the file/folder \\?\Volume{f2a105f3-3a28-4307-9ead-ed0cceb7d1b5}\Shares\Quote\blah\blah\blah\ (actual path replaced for security reasons) on {server}. 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))
Here's what I've tried/done
- Re-run the job to have it fail with the same error in the same spot
- Add additional space to the volume just in case there isn't enough space for the shadow copy (it made no difference)
- Run a full CHKDSK on all volumes on the entire target server (no difference)
- Run a CHKDSK on the DPM server just to make sure it's okay (no difference)
- Make sure the server is as up to date as possible with and DPM or Windows Updates (again, no difference)
- I even moved/deleted that entire set of sub-folders off the server so they don't even exist (no difference)
- Disable and re-enable Shadow Copies on that volume to flush then all out in case there was a problem with a specific shadow copy (no difference)
- I even removed our replication to Azure Site Recovery to make sure that wasn't the issue (no difference)
At this point, DON'T tell me to run a CHKDSK, I've done it... multiple times... and made sure the volume in question is okay, it's fine. Something else is going on here and I don't know what it is and the logs are being less than helpful!
Has anyone else run into this? Anyone have any suggestions from what I've tried if I missed something or something else to try to get this volume backing up again?
DPM Server 2016 is running on a Windows 2016 Hyper V Host in a Windows 2016 Guest VM
Creating a new Protection Group consisting of partial volumes of a Windows 2008 R2 (physical server). It's been stuck on Calculating Data Size on the "Review Disk Storage Allocation" screen of the Create New Protection Group wizard. It does this every time I attempt it for that server needing protecting. It never finishes. The total data size on disk is 1.2TB of a 1.4TB disk.
Did someone face any similar issue?
thanks
---
Status:FailedHello everybody,
At a customer's site, there is a DPM 2019 backing up 2 - 3 TB of files. Everything is running Windows Server 2019. The file server is running on a VMware cluster, DPM is a physical machine. The volumes to be backed up are ReFS formatted. DPM is using modern backup storage. All patches are current.
Wenn we try to back up the volumes with the files of the file server, the file server becomes unresponsive or nearly unresponsive. We see that SYSTEM occupies on CPU core 100% for hours, but the file server cannot even reboot. We had to hard turn off the VM and restart several times now.
What can we do in order to properly back up that file server's files with DPM again please?
Best Regards, Stefan Falk
Hi,
(See OUR PROBLEM, later below)
OUR CONFIG:
Our IT team has a Windows General Purpose File Server Cluster "ENGRFILER1" (active/passive) that is sharing a highly used volume (U: drive) which is 2 TB (915 GB currently in use). The volume is NTFS with deduplication enabled at the file server level. The file server cluster nodes are running Windows Server Core.
File server cluster node config (using MSINFO32):
OS Name Microsoft Windows Server 2019 Datacenter
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ENGR-FILER1N4
System Manufacturer Microsoft Corporation
System Model Virtual Machine
System Type x64-based PC
System SKU Not Available
Processor Intel(R) Xeon(R) Gold 6144 CPU @ 3.50GHz, 3492 Mhz, 3 Core(s), 6 Logical Processor(s)
BIOS Version/Date Microsoft Corporation Hyper-V UEFI Release v4.0, 3/13/2019
SMBIOS Version 3.1
BIOS Mode Not Available
BaseBoard Manufacturer Microsoft Corporation
BaseBoard Product Virtual Machine
BaseBoard Version Hyper-V UEFI Release v4.0
Platform Role Not Available
Secure Boot State Not Available
PCR7 Configuration Not Available
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.17763.831"
User Name Not Available
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) Not Available
Total Physical Memory 24.0 GB
Available Physical Memory 11.4 GB
Total Virtual Memory 27.5 GB
Available Virtual Memory 11.8 GB
Page File Space 3.50 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Not Available
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
( Note: The file server cluster nodes are virtualized, running hyper-converged within a Storage Spaces Direct SOFS cluster. The file server cluster node NTFS U: drive mounted volume share is actually a VHDX file inside a ReFS CSV on the storage
spaces pool. Deduplication is NOT enabled at the CSV S2D level. )
We have built a Microsoft Data Protection Manager 2019 server for backing up our file server volumes.
The DPM version is: 2019 - UR1 (10.19.260.0)
The DPM SQL Sever version info:
SQL Server Management Studio 15.0.18330.0
SQL Server Management Objects (SMO) 16.100.37971.0
Microsoft Analysis Services Client Tools 15.0.19040.0
Microsoft Data Access Components (MDAC) 10.0.17763.1
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.17763
The server that DPM is running on is: Windows Server 2019 Datacenter (1809, 17763.1131)
DPM sever config (MSINFO32):
OS Name Microsoft Windows Server 2019 Datacenter
Version 10.0.17763 Build 17763
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ENGR-BACKUP1
System Manufacturer Dell Inc.
System Model PowerEdge R610
System Type x64-based PC
System SKU Not Available
Processor Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2394 Mhz, 4 Core(s), 8 Logical Processor(s)
Processor Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2394 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. 6.1.0, 10/18/2011
SMBIOS Version 2.6
BIOS Mode Not Available
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 0F0XJ6
BaseBoard Version A13
Platform Role Not Available
Secure Boot State Not Available
PCR7 Configuration Not Available
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.17763.1131"
User Name Not Available
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) Not Available
Total Physical Memory 96.0 GB
Available Physical Memory 90.2 GB
Total Virtual Memory 110 GB
Available Virtual Memory 103 GB
Page File Space 14.0 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Not Available
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
The DPM server has all patches and is up to date as of: 4/21/2020
The DPM server and file server cluster are members of our AD domain.
The DPM storage pool is:
* 50 TB (25 TB currently free) on a 10 Gbit iSCSI connected SAN disk utilizing a SSD flash front-end tierd disk subsystem.
* Formatted as "Modern Backup Storage" (MBS) ReFS without depduplication enabled.
The connectivity of the DPM server to the file server cluster is 10 Gbit throughout.
The above config is all BOG standard Microsoft DPM and storage config, out-of-the-box, vannilla stuff.
---------------
OUR PROBLEM
When we use DPM to backup the U: drive volume on our file sever cluster we are seeing the exact same problem as outlined in the following thread:
https://social.technet.microsoft.com/Forums/en-US/52a4a412-3e78-447e-968a-3f2b291fc15b/fileserver-protection?forum=dpmfilebackup
The error message we have is:
U:\ on ENGRFILER1FS4.EngrFiler1.domain.x.y
C:\Program Files\Microsoft System Center\DPM\DPM\Volumes\Replica\f553adae-8a21-403e-b5d1-9a1a5e0b1a31\5564c443-64e0-45ff-b8bb-1a4adec0bba2\Full\
DPM failed to clean up data of old incremental backups on the replica for Volume U:\ on ENGRFILER1FS4.EngrFiler1.domain.x.y.
Synchronization will fail until the replica cleanup succeeds.
(ID 30134 Details: Cannot create a file when that file already exists (0x800700B7))
This error message occurs every time we backup the volume.
For troubleshooting, we have rebuilt the entire DPM server from scratch and still get the same error.
For troubleshooting we have disabled Windows defender on the DPM server, and we do not run any other antivirus products, nor do we have defender enabled on our file server cluster nodes.
We have not had trouble with DPM when backing up our other servers for our IT environment.
We seem to only have trouble with the volumes exposed by our file server cluster.
Running a "synchronization job with consistency check" seems to fix the problem for a short time, then the problem will re-appear within a few hours, or a day.
I have a guess that this problem is somehow caused by the U: drive volume we are backing up is being deduplicated, but I can't confirm this, as others have stated that turning off dedup didn't solve their problem.
This page says a lot about running deduplication with the DPM storage pool, but it says very little (if anything at all that I can find) about the whether there will be problems when backing up when the volume being backed up is deduplicated:
https://docs.microsoft.com/en-us/system-center/dpm/dpm-support-issues?view=sc-dpm-2019
The page needs more info for consumers if there are issues with backing up deduplicated volumes (on file server clusters or otherwise).
Any help would be greatly appreciated!
Thank you.
Arif
I have installed DPM 2019 then upgraded it with SP1. I installed DPM agent at a work group and one domain joined computer.
I am getting warning, "Update Available". So when I try to update it from DPM console, get below error. I tried to install agent manually at work group system from "protectionAgents\RA" bu no luck. can someone pls help step by step to
update the DPM agent
Arif
If I set synchronization at every 30 minutes and schedule recovery point at 8 PM (ONLY ONE TIME) in a day.
1. Then how many recovery points will be created in day?
2. If some disaster happens at protected server before 8 PM for example disaster happens at 7PM on 28th May. How much data loss will happen?
3. Will I be able to restore any data from 28th May ?
Arif
Anyone have experience with using DPM/VSS to backup Access MDB format files? We found that after restoring the files from several restore points, the content of the database is incorrect. As a matter of fact, the content of the backup appears to be unchanged from restore point to restore point although the modification time is changed. The MDB has indeed changed over that period. This is using MBS and Windows 2016/2019 servers.
Thanks.
I am using DPM2007 console.
I am using DPM 2016 to protect some servers and a couple of Windows 10 workstations, all domain joined.. We recently replaced one of the workstations (call it \\Computer-1). In doing this, I stopped protection on Computer-1 and uninstalled the RA. The replacement
computer is also named Computer-1. I re-installed the RA on Computer-1. When trying to add it to the protection group and protect a file share, I get the following error:
DPM cannot access the path C:\ because part of the path has been deleted or renamed.
Check the path and enter it again.
ID: 36
Details: Internal error code: 0x80990F43
Any ideas where I can look to resolve this?
Thanks,
Eric.
Eric Logsdon Cooperative Technologies, Inc.
Hi,
Im using DPM 2019 to back up a new file server cluster also on 2019.
When i go to display shares, only some show, not all. I have refreshed, still same.
I tried adding the dpm computer account to the share permissions but didnt work.
What are the permissions required for DPM to backup from share level. I can see the files at drive level but need them at share level.
Anyone had this before?
So I'm setting up DPM for a remote data center (no, I don't have the option to choose any other products, just in case that comes up). Server is plenty hardy for the job and the DPM install went off without a hitch, as did connecting the box to Azure. However, I'm a little flummoxed by the logic utilized by setting up Protection Groups.
The box containing all the file shares is....the folder equivalent of a bee's hive. Shares are kind of all over the place, no rhyme or reason to where specific folders were placed or the workloads represented by those files. Drive D:'s first folder contains SQL DB backup target location while the second folder contains 9 shares for that country's HR staff.
To wit, I want to create two protection groups (this is an example)
d:\SQL Backup Target
d:\HR Data
But....once I create a PG for #1, I'm excluded from creating a PG for #2 with the message
"Other items on this data source are members of another protection group"
#&@#^$
The only reasoning I can think of is that I might create policies that would cause the DPM Agent to backup different folders on the same volume simultaneously, creating an IO bottleneck.
A customer has a DPM 12.0.332.0 server, its protecting 12 other servers.
Backups have been failing for some time, Recovery points are now going through after deleting the last couple of backup sets however while running an online recovery one job seems to have frozen, it has been running for 90 hours with just over 17GB transferred, it has been in this state for at least the past 24 hours.
There is no obvious disk activity on the DPM server, is there a way to see via PS if this job is progressing?
Thanks
Hello Everyone....
We have 2 SCCM server .one is active with all roles installed , 2nd server is passive with main services installed.
No i want to install 2nd management point on passive node, in case primary node is down client automatically connects to 2nd management Point..My question is that Microsoft support 2nd management point on Passive node of SCCM.
and will this management point will be active or passive mode,as management point works in load balancing.
So I am trying to use Azure backup and I am getting a very odd issue when trying to register the server.
I have rebooted the server, checked that the time is correct.
The second warning, doesn't make sense as I have done other Servers where it says don't place the passphrase locally, but the registration still completes.
Hi all,
Quick question on an issue with a VHD backup.
So we had to create a new VHD after an issue with a volume on a file server. We restored to the DPM using an alternative location and got the data back on there but now DPM won't detect the new volume on the file server as obviously it's GUID has changed.
We could set up new protection for it but it's a rather large drive and things will get a bit messy, so is there anyway to tell DPM that's it OK to use this new volume with a different GUID as it's identical to the old one?
Regards
Paul