Real time database backup status indication and restore

1. A data management system, comprising:

one or more processors in communication with a database, the one or more processors configured to perform operations including:

retrieve start and end times of a backup of the database;

retrieve time stamps of log backups of the database;

retrieve sequence numbers of the log backups;

generate a graphical user interface illustrating a timeline of availability of database restoration and unavailability based on the retrieved sequence numbers, wherein non-consecutive sequence numbers indicate unavailability;

make a second backup of the database;

illustrate, on the graphical user interface during the making, pending availability of the second database backup;

receive a command to restore the database at an available time as illustrated by the graphical user interface; and

restore the database.

2. The system of claim 1 , wherein the unavailability starts at a time indicated by a time stamp of a first log backup having a non-consecutive sequence number.

3. The system of claim 1 , wherein the operations further include determining a cause of the unavailability and displaying the determined cause on the interface.

4. The system of claim 1 , wherein the making a second backup of the database is in response to determining there is a non-consecutive retrieved sequence number.

5. The system of claim 4 , wherein the operations further include receive a log backup having a sequence number preceding the non-consecutive number; and

update the graphical user interface to indicate availability based on the received log backup.

6. The system of claim 1 , wherein the operations further comprise receiving a log file with a sequence number that restores consecutiveness to the retrieved sequence numbers and updating the graphical user interface to illustrate availability based on the received log file.

7. A computer-implemented method at a data management system, the method comprising:

retrieving start and end times of a backup of a database;

retrieving time stamps of log backups of the database;

retrieving sequence numbers of the log backups;

generating a graphical user interface illustrating a timeline of availability of database restoration and unavailability based on the retrieved sequence numbers, wherein non-consecutive sequence numbers indicate unavailability;

making a second backup of the database;

illustrating, on the graphical user interface during the making, pending availability of the second database backup;

receiving a command to restore the database at an available time as illustrated by the graphical user interface; and

restoring the database.

8. The method of claim 7 , further comprising illustrating the timeline with different colors to indicate availability, unavailability, and pending availability.

9. The method of claim 7 , further comprising determining a cause of the unavailability and displaying the determined cause on the interface.

10. The method of claim 7 , wherein the making a second backup of the database is in response to determining there are non-consecutive retrieved sequence numbers.

11. The method of claim 10 , further comprising making additional log backups after the making the second database backup.

12. The method of claim 7 , further comprising receiving a log file with a sequence number that restores consecutiveness to the retrieved sequence numbers and updating the graphical user interface to illustrate availability based on the received log file.

13. A non-transitory, machine-readable medium storing instructions which, when read by a data management system, cause the data management system to perform operations comprising, at least:

retrieving start and end times of a backup of a database;

retrieving time stamps of log backups of the database;

retrieving sequence numbers of the log backups;

generating a graphical user interface illustrating a timeline of availability of database restoration and unavailability based on the retrieved sequence numbers, wherein non-consecutive sequence numbers indicate unavailability;

making a second backup of the database;

illustrating, on the graphical user interface during the making, pending availability of the second database backup;

receiving a command to restore the database at an available time as illustrated by the graphical user interface; and

restoring the database.

14. The medium of claim 13 , wherein the operations further comprise illustrating the timeline with different colors to indicate availability, unavailability, and pending availability.

15. The medium of claim 13 , wherein the operations further comprise determining a cause of the unavailability and displaying the determined cause on the interface.

16. The medium of claim 13 , wherein the making a second backup of the database is in response to determining there are non-consecutive retrieved sequence numbers.

17. The medium of claim 16 , wherein the operations further

comprise receiving a log backup having a sequence number preceding the non-consecutive number; and

updating the graphical user interface to indicate availability based on the received log backup.

18. The medium of claim 16 , wherein the operations further comprise making additional log backups after the making the second database backup.

19. The medium of claim 13 , wherein the operations further comprise receiving a log file with a sequence number that restores consecutiveness to the retrieved sequence numbers and updating the graphical user interface to illustrate availability based on the received log file.

20. The medium of claim 13 , wherein the unavailability starts at a time indicated by a time stamp of a first log backup having a non-consecutive sequence number.