Details
-
Suggestion
-
Resolution: Won't Fix
-
None
-
Tomcat 6, MS SQL host. Both systems running on separate Xen VM's
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Backups that fail to complete within a specified time period (can be decided either programmatically or by the user) should provide some level of warning within the web interface that they have failed. This is a critical operation, and failure to complete backups is a very high-risk situation.
For information about how backups can potentially fail, see JRA-18018. In this case, I've been able to cause the backup-process to hang indefinitely through high packet loss between the JIRA instance and the MS SQL server
Attachments
Issue Links
- incorporates
-
JRASERVER-18018 Failed backups are not identified as corrupted
- Gathering Impact
-
JDEV-29467 Loading...
- relates to
-
JRACLOUD-18019 Scheduled backups that fail to complete within a certain time period should provide indications
- Closed