nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Storing confluence attachments in database or file system / best practice

chrisi

Hi,

what reasons would there be other than running confluence in a cluster to store attachments in the database? ok backup may be a little bit easier but since I backup the home-directory anyway there is no big difference, isn't it?

The local file system access is much faster than our db-connection and if there are a lot of large attachments i would think this would slow down confluence noticeably.

Besides, there must be a reason why file system storage is the default configuration...

thanks in advance for your opinions and experiences!

Accepted answers

Tiago Comasseto

Hi Chrisi,

I can't think in any other reason besides facilitate the backup operation in a non-clustered environment, in fact, depending on the system configuration, store into the database can be wrost than storing into the file system, as you mentioned, file system tends to be faster than database.

Cheers

All comments

Tiago Comasseto

Hi Chrisi,

Cheers

David Grierson

Not so much back-up but production/DR replication for site failover purposes would be easier with the attachments held in the database.

If the attachments are on a filesystem being replicated (e.g. SRDF or snapshots) and the database replicated separately then to recover to DR you need to make sure that your replication is in sync.

Holding all of the data in the same place would mitigate this requirement.

Craig Oliver

It depends on the features of the database you have available and its performance. For example if you can afford a well specified Oracle Database and sufficient cache memory then performance of confluence with attachments is pretty good.

If you also have a database replication option such as Active DataGuard then you can replicate your whole database (with attachments) to another site and configure confluence for high availability using DNS resolution (e.g. F5 GTM).

Your attachments and pages are always going to be kept in sync on the remote site, and your recovery point and time of operation will be almost immediate.

If you were trying to do this with your attachments stored in a filesytem - perhaps using a regular rsync with cron... in the event of failure the attachments are likely to be out of sync with the database data.

However Atlassian have now deprecated database attachment storage... I would like to the reasons behind this decision.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

attachment

database

file-system