Why is the update date different from the last recovery point?

oscar yesid alvarez 20 Reputation points
2024-12-13T14:33:54.71+00:00

Good day, In MARS, because the date of the last backup update is different from the last recovery point, I have more than 60 agents and the only one that appears that way is the one I mention. I attached an image of how it looks specifically. And what should I do to update both parts to the current date. In the attached image the inconvenience that I indicated is highlighted in Yellow.

IMG_9628

Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,320 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 47,836 Reputation points Microsoft Employee
    2024-12-13T18:32:50.8566667+00:00

    @oscar yesid alvarez Greetings!

    The date of the last backup update and the last recovery point date may differ due to several reasons. These two dates represent different events, and while they are related, they are not necessarily identical. Here's why:

    1. Backup Job Schedule vs. Recovery Point Creation
    • Last Backup Update: This refers to the last time the MARS agent successfully completed a backup job or when a backup job was triggered, even if it didn’t result in a new recovery point. For example, the agent may have successfully triggered a backup, performed the check, or updated its status in Azure, but no new recovery point was created because the data hasn't changed since the last backup.

    Last Recovery Point: This refers to the last successful snapshot or backup of the data that was created. A recovery point represents a specific instance of data that is available for recovery. A new recovery point is created only if data has changed and the backup job is successfully completed.

    Why different?: If there were no changes in the data or the backup job completed successfully but didn’t create a new recovery point (e.g., no data change), the last backup update date might reflect the latest backup attempt, but the last recovery point date would only be updated when actual data is backed up.

    1. Backup Job Failure or Delay

    Last Backup Update: If a backup job was scheduled or initiated but failed or was delayed (e.g., due to connectivity issues, insufficient disk space, or other errors), the agent may still report an updated backup attempt in the last backup update date, but no new recovery point would be created.

    Last Recovery Point: If a backup job fails, no recovery point is created, meaning the last recovery point date remains unchanged.

    Why different?: A failure in the backup job could update the agent’s status but not create a recovery point, causing the dates to differ.

    1. Backup Job Retries

    Last Backup Update: The MARS agent may attempt to back up the data and report the status as a backup update, even if it retries multiple times before succeeding.

    Last Recovery Point: The recovery point date only updates once a successful backup is completed, so if the backup job is retrying but hasn’t successfully completed, the recovery point date will remain unchanged.

    Why different?: The agent might report an "update" every time it retries or checks for a new backup, but it won’t update the recovery point date until the backup job is successfully finished.

    Summary of Key Differences:
    User's image

    Hope this answers your question. Feel free to reply if you have any questions or concerns.


    If the response helped, do "Accept Answer" and up-vote it

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.