BackupSessions remain in the Running phase when encountering failures or timeouts during the backup process. This occurs specifically when a post-backup hook is configured.
Specific Scenarios:
If the backup process terminates prematurely before initiating the post-backup hook, the BackupSession remains in the Running phase.
When the backup reaches the specified timeout without executing the post-backup hook, the BackupSession remains in the Running phase.
Challenges:
If a BackupSession is marked as failed due to an insufficient timeout, the actual backup process may still be ongoing within the backup job. This discrepancy can lead to problematic scenarios, such as initiating a new backup while the previous one is still active.
Problem:
BackupSessions remain in the
Runningphase when encountering failures or timeouts during the backup process. This occurs specifically when a post-backup hook is configured.Specific Scenarios:
Runningphase.Runningphase.Challenges:
If a BackupSession is marked as failed due to an insufficient timeout, the actual backup process may still be ongoing within the backup job. This discrepancy can lead to problematic scenarios, such as initiating a new backup while the previous one is still active.