Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Several scheduled jobs haven't run in several days...

So I went to the backups-folder in our Confluence server to trim out old backups, and noticed that the last backup was run on the morning of November 5th. So our Confluence hasn't backed itself up for a week!

I then went into the Admin panel to look at the scheduled jobs, in case someone had disabled the job without telling me about it. And I see this:
image.png

The instance was installed on August 14th (migrated from another host) and backups have run fine so far. I find several of these "Last execution" and "Next execution" dates worrysome. The "Back Up Confluence" task is running because I started it manually to see if I could provoke anything in the logs, but nothing so far.

Confluence Server v6.15.9 running on a CentOS 7 server.

2 answers

0 votes
Alexis Robert Community Leader Nov 12, 2019

Hi @Snorre Selmer ,

 

it is not recommended to perform internal backups like these on a production instance, because these will take a lot of time as you get more content on your Confluence instance.

The best practice is to disable this job, and instead do a backup directly on your database. This is much better in terms of performance, and will be easier too to restore in case of issues.

 

Let me know if this helps, 

 

--Alexis

We do that as well, outside of business hours. It's a bit of a belt-and-suspenders thing.

Alexis Robert Community Leader Nov 12, 2019

In this case I would recommend disabling the internal Confluence backup job, as per Atlassian official recommandation on this page : https://confluence.atlassian.com/doc/production-backup-strategy-38797389.html

Although Confluence provides a scheduled XML backup, this backup method is only suitable for small sites, test sites, or in addition to database and directory backups.

Just as a quick followup, the backup finished successfully, the file is in the backup-folder. Clicking the History-link shows that the job has run every day, even though there's no file to show for it. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Confluence

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

462 views 24 9
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you