Automatic backup service enabled....no backups are created

[C_ Faysal]

hey i was just wondering why confluence isn't creating automatic backups if the service is enabled..

version 5.2.3 any ideas?

thank you

[Septa Cahyadiputra · Accepted solution]

Hi there,

There are a lot of possible causes that could leads to Confluence unable to create daily XML backup as configured. FYI, XML backup creation require a huge resources which eventually leads to OOM Heap Space if the memory available is not sufficient.

In order to get a better idea, it is necessary for you to review atlassian-confluence.log or use our inbuilt log scanner to see if there are any known issue related to your current issue.

Hope it helps.

Cheers,
Septa Cahyadiputra

[C_ Faysal]

not exactly what went wrong here but after setting back up to not include attachments it worked for me..at least until i built a cold standby system setup

[Lukasz Borek]

Doesn't really work for me, Confluence 6.15.7.

After minor upgrade the scheduled backups are no longer working on 2 of our instances. Manual backup over interface works, permissions are correct, no new errors in the logs. 

Last backup info is false, pointing to a day 2 months ago when it really stopped doing backups 2 weeks ago. In history it shows done backup with 2ms job time. No backup file, nothing in temp. 

[Andrew Lister]

@Rostyslav Maryliak :

Worked for me as well - version 6.15.4 - the latest - installed today.  Thanks so much

[Andrew Lister]

Changing it back to the default after the initial creation worked as well.

[Ferdinand Babas]

Same for me.  I changed it back to the default date pattern and the backups continue to work.

[BernardoA]

I think is necessary to check your confluence log firstly just to see the last entries and see if there's some aparent error as well ensure that you have Read\ Write permission.

[C_ Faysal]

i understand you point...

is the user differing between manual and cron triggered backups?

[hsuhailah]

Possibly Confluence was unable to write onto the home directory to create the backup files. This could be due to insufficient permission given to Confluence Home Directory. Double check and ensure that the user who runs Confluence has full read and write permission onto both Confluence installation and home directories. Check also the backup path and ensure that it's a valid one if you have configured a non-default/custom path for it.

[C_ Faysal]

permissions are set fine..

i can see in ${confluence-home}/temp that the backup process is creating the dumps there.

but it won't end up in ${confluence-home}/backups like it did before.

all paths are fine. user confluence who runs the app owns entire ${confluence-home}/ and relevant directories in ${confluence-install}/ like work,log,temp

i still wonder why the history says backup has been created but is available nowhere.

there is enough diskspace, enough memory

ls -lat /var/atlassian/application-data/confluence/backups/
total 44
drwxr-xr-x 18 confluence confluence 4096 Aug 31 05:26 ..
drwxr-xr-x  2 confluence confluence 4096 Aug 23 02:00 .
-rwxr-xr-x  1 confluence confluence 9868 Aug 23 02:00 backup-2013_08_23.zip
-rwxr-xr-x  1 confluence confluence 9787 Aug 22 02:00 backup-2013_08_22.zip
-rwxr-xr-x  1 confluence confluence 9528 Aug 21 02:00 backup-2013_08_21.zip

ls -1 /var/atlassian/application-data/confluence/backups/*|wc -l
3

[hsuhailah]

You were referring to the daily automated backup, right? What's the 'Backup Path' setting in Confluence Admin > Backup Administration?

Do you happened to make any customization/automate a script for the backup process that may have caused this path shift?

[C_ Faysal]

backup path is as shown above /var/atlassian/application-data/confluence/backups

no modifications werde made.

right now i just unticked "backup attachments" and manually ran the backup process. it was able to finish and placed the finally created .zip file in backups.

but automatically triggered backups wont end up in the backups directory....

[Rostyslav Maryliak]

I had exact the same problem: the "Automatic Backups" were enabled, backup destination path is set correctly, I can see the history of successful backups, I can even see them in temp folder... but there are NO backups files at "/var/atlassian/application-data/confluence/backups/".
I solved it by simply changing "Backup File Date Pattern" from "yyyy_MM_dd" to "yyyy_MM_dd_HHmmss".
I have no idea why does this solve the problem, but after that backups started to appear at backup destination path.

[Matt Stein]

Thanks for mentioning that,@Rostyslav Maryliak! Your strange solution of appending `_HHmmss` to the backup filename worked immediately for me as well with Confluence 6.8.1.

[detsikas]

Worked for me as well! 

[Jared Merson]

@Rostyslav Maryliak Worked for me as well!  Thank you!

[Help_Desk]

I needed to do this as well to get the file to appear on a NAS via cifs. Thanks !!

[Deleted user]

I can confirm that this does the trick for Confluence 6.15.9 as well. At Backup Administration page I had "Perform backups Disabled" and a note that I can change that in Scheduled Jobs administration page ... where for Back Up Confluence job there already was status "Scheduled".

Conflluence log, however, showed each day:

2019-10-15 02:00:00,016 WARN [Caesium-1-4] [impl.schedule.caesium.JobRunnerWrapper] runJob Scheduled job BackupJob#BackupJob completed unsuccessfully with re
sponse JobRunnerResponse[runOutcome=ABORTED,message='Backup daily setting off']

After changing the "Backup File Date Pattern" that "Disabled" changed to "Enabled" at "Perform backups" line. And it stayed that way after changing the file date pattern back to previous setting. :-)