Last Backup information is incorrect

Description

Tested with Everest v0.0.0-9aa3f5d version.

Create a mysql, mogodb and postgresql database of 1 node. Enable scheduled backups of every hour at minute 0 for all three databases.

After a while all three databases have a different Last Backup time, though the scheduled backups were taken at the same time

 

image-20240408-125719.png

Scheduled backups for mysql

 

image-20240408-125840.png

Scheduled backups for mongodb

 

image-20240408-125928.png

Scheduled backups for postgresql

 

image-20240408-130019.png

Of all the three, the Last Backup time of mongodb database is correct.

Environment

None

Attachments

7
  • 05 Jun 2024, 01:34 PM
  • 04 Jun 2024, 12:41 PM
  • 04 Jun 2024, 12:41 PM
  • 08 Apr 2024, 01:01 PM
  • 08 Apr 2024, 01:01 PM
  • 08 Apr 2024, 01:01 PM
  • 08 Apr 2024, 01:01 PM

Activity

Show:

Manish Chawla June 27, 2024 at 1:35 PM

Tested with Everest 1.0.0 rc3 version and did not observe the issue.

Manish Chawla June 5, 2024 at 1:34 PM

Today I got a difference in Last Backup time for all the databases

image-20240605-133403.png

Manish Chawla June 4, 2024 at 12:41 PM

Hi , In dev-latest (Everest v0.0.0-dfa0d28 version), I am still seeing a difference in backups of different databases

image-20240604-121909.png

In the above all three databases has the same backup schedule and backups completed at the same time but the mysql db shows 3h 14 min ago instead of 14 min ago. Please check, thanks.

In the mysql database, these backups are already completed

image-20240604-124036.png

Diogo Recharte June 4, 2024 at 8:29 AM

I saw that the status was outdated and actually meant to move it to the ready for qa state, thank you for noticing that I moved it to the incorrect state.

Manish Chawla June 4, 2024 at 6:53 AM

Hi , Is this issue fixed? Please let me know the reason for closing this issue. Thanks.

Done

Details

Assignee

Reporter

Sprint

Fix versions

Affects versions

Priority

Smart Checklist

Created April 8, 2024 at 1:01 PM
Updated July 1, 2024 at 9:23 AM
Resolved May 31, 2024 at 10:56 AM

Flag notifications