Macrium Reflect foreplay when updating incrementals?

Discussion in 'backup, imaging & disk mgmt' started by Tarnak, Apr 25, 2019.

  1. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    4,684
    I refer to my earlier posts a few days ago in the main Macrium Reflect topic.

    The daily update is working, again, but it starts and finishes later, and then says it says it [only] took 5m 36s....

    As can be shown by the screenshots, the process started at 9:54 am and finished at 11:38 am.

    So, I am confused because it never did this before. It usually was very quick when it ran. I am wondering what has caused this change in behaviour when the program runs.

    MacriumReflect_Microsoft.Exploer.Notification_01.JPG

    MacriumReflect_Microsoft.Exploer.Notification_02.JPG

    MacriumReflect_Microsoft.Exploer.Notification_03.JPG

    P.S. I thought I would go with the catchy thread title, because my original post a few days ago didn't rate a response. :(
     
  2. jphughan

    jphughan Registered Member

    Joined:
    May 3, 2018
    Posts:
    258
    Location:
    US
    Check your logs for indications of Incremental consolidation. Until recently, if Incremental consolidation (or Synthetic Full consolidation) occurred at the beginning of the job because the job has the "Run purge before backup" option checked, then the time occupied by the consolidation operation was not included in the overall completion time shown at the bottom of the log, even though it WAS included if the consolidation operation occurred at the end. (Either way, a separate elapsed time entry for the consolidation operation is included in the consolidation section of the log.) I called this discrepancy out in the Macrium forums, and as of 7.2.4063, consolidation time is now included in the overall job time calculation regardless of when it occurs. Are you maybe running an older version?
     
  3. Tarnak

    Tarnak Registered Member

    Joined:
    Feb 5, 2007
    Posts:
    4,684
    The problem seems to have resolved itself, recently. I don't know why. I am still running an older version - v6.3.1665
     
Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.