[#JRA-10383] Backup service fails if backup directory does not exist

JIRA

Backup service fails if backup directory does not exist

Created: 08/Jun/06 02:19 AM Updated: 05/May/08 05:32 AM

Component/s:

Services

Affects Version/s:

3.6.1

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Windows XP, Java 1.5.0_06, standalone

Participants:	Iver Grini, Jeff Turner [Atlassian], Larry Cummings and Tsahi Deleon
Since last comment:	18 weeks ago
Labels:

Description

« Hide

If the backup directory does not exist, the backup service fails. Even though there is a warning in JIRA's log file, I don't find this sufficient for such an important functionality.

I would suggest the following important improvement:
Make Jira create the directory if it does not exist.
If unable to create the directory, generate an email warning to the jira administrators in order to have the problem identified and fixed.

As everybody knows, having a backup may be crucial for if you experience a harddrive failure........

I found a quite similar request JRA-7912 where another backup failure is discussed, though I want to adress the directory problem specifically as this can be easily fixed (simply creating the directory will in most cases fix the problem).

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Larry Cummings added a comment - 08/Aug/06 12:45 AM

Just voted heartily and thought I would comment on why that vote was important for me to make.

This feature would have saved me about two hours of rebuilding issues for one project.

It would have saved me about 45 minutes of time it took me to explain why it happened.

It would have been priceless in saving me from being embarrassed by my not having a backup.

Happily I could rebuild the list in 2 hours.

Unhappily I lost most of the comments associated with these issues.

So, not to put too fine a point on it, yes please!

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 09/Aug/06 08:46 PM

Perhaps this should be generalized so that any errors get mailed to an administrator.

[ Permlink | « Hide ]

Iver Grini added a comment - 14/Aug/07 01:13 AM

Generating an email when an error occurs is definitely an option. Need to be careful if the error is related to the sending of emails though. Even though a generalized solution would probably be the best in the long run, a specific solution for the problem defined by this issue (since I concider it to be a very important one) would be quite simple and fast to implement.

In addition to the suggestions in the description, an extra check when setting up the backup service would of course also fix most of the problem (as long as we are not talking about moving the jira installation from one server to another using export-import)

[ Permlink | « Hide ]

Tsahi Deleon added a comment - 05/May/08 05:32 AM

Hello Jeff,

I wish to add a little bit different, preliminary point - maybe intended by Iver in his last comment.

Right now, it seems that no validity check is performed regarding JIRA Backup Directory.
For example, when creating our backup service, it was set (by a typing error) to "C:\Program Files\C:\Program Files\JIRA-Standard-3.12.1\backup".

I think that in such case of an invalid Backup Directory specified for Backup Service, that service should not be created/activated at all.

What do you think?

Thanks,
Tsahi

P.S. If you consider opening a separate issue for it, it looks more like a bug rather than an improvement