none
DPM recovery points and synchronization sequencing RRS feed

  • Question

  • 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.

    Friday, February 7, 2020 5:26 PM

All replies

  • Hi,

    I don't think they can run exactly simultaneously, but the synchronization will be done first.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 7, 2020 7:02 PM
  • Hi,

    I don't think they can run exactly simultaneously, but the synchronization will be done first.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    I would have thought so as well, but I don't now for sure and I need to.  On a secondary system I am observing the synchronization start and the recovery point fail because the recovery point starts before after the synchronization, but before the sync is completed. It thus fails with error 208.

    The system is set up for one recovery point per day and one sync per day both at midnight.

    Friday, February 7, 2020 8:18 PM
  • From my quick test I had both recovery point and synchronization at the same time and the synchronization delayed the recovery point just by a few min.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 7, 2020 8:46 PM
  • That's what I'm observing as well. But the sync sometimes runs a long time (~3 hrs) and the recovery starts a few minutes into the sync and then quickly fails stating no changes have been made (error 208).
    Friday, February 7, 2020 8:50 PM
  • If it's only one sync per day, it will take time, I would synchronize more often, this way your recovery point schedule at midnight will stay on time.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 7, 2020 9:57 PM
  • I never had this problem in the past with the same schedule in place on older DPM systems. It seems like unique to 2019.  I don't know why it's not waiting  I would think this process would be equivalent to a manual "create recovery point after synchronization" process.

    If I sync say every 6 hours (00:00, 06:00, 12:00, 18:00) is the midnight recovery point for data synchronized at midnight or at 18:00?  Sometimes I need to know that.  There is no guarantee that the changes between 18:00 and 00:00 will be synced in only a couple of minutes.

    Friday, February 7, 2020 11:20 PM
  • It depends also on the type of workload that is being backed up, and how often that data changes, then you need to configure your synchronizations based on that.

    If I sync say every 6 hours (00:00, 06:00, 12:00, 18:00) is the midnight recovery point for data synchronized at midnight or at 18:00? 

    >> If the midnight synchronization has time to complete it will be synchronized, otherwise it will still have the data from 18:00.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 7, 2020 11:32 PM
  • So what you are saying is that it does NOT wait for the sync to complete to start the recovery process and that it is like the manual "create recovery point WITOUT synchronizing"?
    Friday, February 7, 2020 11:36 PM
  • To my knowledge no, but DPM also automatically identifies whether the replica is inconsistent or not.

    Would it maybe be better in your case to modify the protection group for this workload to perform a synchronization before creation of replica?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, February 7, 2020 11:50 PM
  • I think I'm going to first try to sync more during the day and see what the effect is.  I'll post if I find something of interest. Thanks so far.
    Friday, February 7, 2020 11:55 PM
  • Hi,

    Just checking in to see if you have any update?


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, February 12, 2020 9:58 PM
  • This is a question for my secondary protection. Unfortunately, I'm have persistent msdpm service crashes on my primary system which is making it a little difficult to work with my secondary system. I have an open MS case on this crash.  This started about a couple of months ago with DPM 2019 and still remains after upgrading to UR1.  No changes have been made to the system besides regular Windows updates.

    Once it's resolved, I post back.

    Thursday, February 13, 2020 1:53 PM