none
DPM 2019 Replication Server - Console Crashing RRS feed

  • Question

  • Support Forum,

    I have a DPM 2019 server running on a Windows 2016 with SQL 2016 with the latest updates/Service packs applied for Windows and SQL.  My Primary DPM server is working great, my replication DPM on with all of the same software versions is failing on drives with lots of files.  So the replication for Virtual Servers, System Protection/Bare Metal, and SQL DBs all work.  The new protection for Files being backed up for drives that have lots of files my DPM MMC crashes with error 999.  I have successfully added drives with less files to the Files - Servers protection group.

    I did find this old issue with DPM 2012 and made this change, but it didn't fix it.

    https://social.technet.microsoft.com/Forums/lync/en-US/35fafe8d-ee62-4d84-9c35-2ae7bff3a2b4/decipher-dpm-crash-files?forum=dataprotectionmanager

    Any ideas will be appreciated.

    Thanks, Ryan

    Tuesday, August 13, 2019 6:04 PM

All replies

  • Hello Ryan,

    To make things clear, does your DPM console on your secondary DPM server crash when you try to add files in a share/volume to a protection group, only when there are too many files?

    Could you explain in very detail how you are adding the objects, and what type of objects to the protection group?

    Please also check your DPM log on the DPM server for more clues, you'll find the logs over here:

    • C:\Program Files\Microsoft System Center\DPM\DPM\Temp\MSDPMCurr.errlog

    Try moving the MSDPMCurr.errlogs from the Temp folder (so that DPM creates a new empty one, this is to avoid having a huge log to go through). Then replicate the things you've done to receive the error, then upload the latest MSDPMCurr.errlog to OneDrive and share it here.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Tuesday, August 13, 2019 7:37 PM
    Tuesday, August 13, 2019 7:37 PM
  • Leon,

    I don't know what number is "too many", but I am going to the Primary DPM server, selecting Protected servers, then expanding the server name of our file server and then I am selecting the D and/or E drive and when it gets to screen where it determines the drive space and which DPM storage drive to use for the replication the console fails/crashed.  My Tech server that has less, but larger files and is able to be added.  Also on DPM 1807 this was working previously in this capacity.  The link below is to a folder and the files will be in there in about 5 minutes.

    Link: https://1drv.ms/u/s!Al3oRbeQKN97sj3sDdTYXr44Ermn?e=DOi086

    Thanks,

    Ryan

    Wednesday, August 14, 2019 8:02 PM
  • When you create a Protection Group to back up files and folders, size calculation can take a long time if the folders contain many files. There is a registry key that you can change to instruct DPM to accept the volume size as default instead of calculating the size of each file, thereby saving time.

    With DPM 2016 and later, you can configure DPM to accept the volume size as default instead of calculating the size of each file. The corresponding registry key is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Configuration\DiskStorage with the Key, EnableCustomAllocationOnReFSStorage as a string set to 1 to enable custom size allocation, set to 0 for default size allocation with DPM.

    Reference:
    https://docs.microsoft.com/en-us/system-center/dpm/add-storage?view=sc-dpm-2019#custom-size-allocation-1

    If you don't have the registry key simply create it (remember that it has to be a "String" key.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, August 14, 2019 11:04 PM
  • Hi,

    Any update on your issue?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 20, 2019 7:05 AM
  • Leon,

    Here is the Registry value I added:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Configuration\DiskStorage]
    "EnableCustomAllocationOnReFSStorage"="1"

    I then rebooted the Server and things still crashed.  I have added the new crash and error log files from today's attempts.  By the way, I was using ReFS storage previously with DPM 2016 when this was working.

    Thanks,

    Ryan

    Tuesday, August 20, 2019 8:58 PM
  • What kind of drives are you trying to protect? (NTFS/ReFS)

    What is the protected server operating system version?

    Is the protected server a standalone or clustered? If clustered what type of cluster?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, August 21, 2019 8:07 AM
  • So since this is DPM replication, I am trying to replicate Drives from the Primary DPM server is a 2016 OS that has ReFS drives which the backups reside on. 

    The original server being backed up that I am trying to replicate is on a 2012r2 server.  The files on that server reside on a NTFS partition.  The file server is on a Hyper-V cluster, but I have a DPM agent installed directly on the file server and am backing up the D and E drives via that agent.

    Wednesday, August 21, 2019 3:53 PM
  • Okay, nothing out of the ordinary there.

    I stumbled upon a similar issue, have you had a look at it?
    Console crashes on DPM secondary server with Event 999 when trying to protect a primary DPM server


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, August 21, 2019 6:33 PM
  • Leon,

    This looks very similar to the issues I am currently having, but this was not occurring on DPM 1807.  These are originally being backed up as file shares on my File server for End user Recovery purposes, but my other Server that I am backing up the D and E drives directly without Shares are erroring out as well.  Not really sure where to go from here.

    Thanks,

    Ryan

    Thursday, August 22, 2019 3:03 PM
  • This looks very similar to the issues I am currently having, but this was not occurring on DPM 1807.  These are originally being backed up as file shares on my File server for End user Recovery purposes, but my other Server that I am backing up the D and E drives directly without Shares are erroring out as well.  Not really sure where to go from here.


    Could you elaborate a bit on the bolded sentence?

    As DPM 2019 is quite new, there is a higher chance for flaws, your best shot might be to raise a ticket directly to Microsoft about your issue.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, August 22, 2019 10:08 PM
  • On our file server we backup the shares and not the folders via the drive letters as this allows users to recover their own files via the shadow copies tab when looking at the properties of a file or folder, that is if the rest of the requirements for End User Recovery are setup. 
    Friday, August 23, 2019 3:17 PM
  • Does anyone have any other suggestions?

    Thanks,

    Ryan

    Tuesday, August 27, 2019 8:10 PM
  • Did you try the workaround provided by Mike in the other thread with the similar issue?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, August 27, 2019 8:36 PM