This page last changed on Mar 20, 2006 by jeremy@atlassian.com.
Confluence 2.2 introduces the ability to store Attachments in one of three places.
Local filesystem
In the past, Confluence has stored Attachments in the attachments directory within the configured Confluence home folder. This remains the default in version 2.2.
Database
Confluence 2.2 gives administrators the option to store attachments in the database that Confluence is configured to use.
There are a number of reasons why, as an administrator, you may want to choose this storage system:
- Ease of backup
- Avoid issues with certain characters in attachment filenames
 | While storing Attachments in the database can offer some advantages, please be aware that the amount of space used by the database will increase, because of the greater storage requirements of Confluence |
WebDAV
Confluence also allows administrators to set a WebDAV repository as the location for Attachment storage.
Migration between Attachment storage systems
An improvement introduced in Confluence 2.2 is the ability to "migrate" between different Attachment storage systems. All existing Attachments will be moved over to the new Attachment storage system.
 |
When the migration occurs, all other users will be locked out of the Confluence instance. This is to prevent modification of Attachments while the migration process occurs. Access will be restored as soon as the migration is complete. |
To perform a migration, perform the following steps:
- View the 'Administration Console'
- Click on 'Attachment Storage'. The current configuration will be displayed.

- Click on the 'Edit' button to modify the configuration. Select the storage system you desire.

- Click on the 'Save' button to save the changes.
- A screen will appear, asking you to confirm your changes. Clicking 'Migrate' will take you to a screen that displays the progress of the migration.

 
Is there any way for hosting companies to stop administrators from storing the files in the database? We're moving our database on to a seperate server and having attachments stored in there would be a major nightmare.

Posted by gfraser at Mar 21, 2006 19:51
|
You can change the .vm file to remove that option.
Tom

Posted by tom@atlassian.com at Mar 21, 2006 20:30
|
We are testing several wiki-engin at the moment for our company in Germany.
With Confluence, we have problems (cannot find and cannot remove attached file) after upload attachment file(s) form Windows 2000 with filwnams consist of "german charactors and empty-space".
Which database or filesystem should we consider? or any tips where should we ask such question?
Thanks in advance!

Posted by ccliew at Dec 10, 2006 11:16
|
Confluence allows german characters and empty spaces in filenames as they are stored in the filesystem with id's rather than the filename itself. Attachments can also be removed, searched and edited. If you would like a list of recommended databases and tips they can be found at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide
I would suggest installing a standalone version of Confluence from http://www.atlassian.com/software/confluence/ConfluenceDownloadCenter.jspa (you are allowed to evaluate it for 30 days as a demo without limits). If you do have any problems you can also issue support requests at http://support.atlassian.com or use this site to find any documentation.
Regards,
Agnes.

Posted by agnes@atlassian.com at Dec 11, 2006 18:53
|
Thanks for your reply. Later, we found out that "empty sapce" works, but filenames with German umlaut and special "S" are not working. In fact, the edit mode become unstable!! If you are right, then I have no idea what is happening now.
We are testing a evaluation version at the moment, but I am not the one who install and manage it. I am the one who propose and want to have a wiki in our workspace. The technical staff who installed it, told me that it happen "may be" because the database server is a linux server, and it can not work with german characters. Which I find it hard to belive, now.
OK, I will check it once again with my assitant. And see what we can do with it. And maybe come back to you again.
Thanks!

Posted by ccliew at Dec 18, 2006 14:45
|
You may be having some character encoding issues due to some configuration. Could you please get your technical staff to try steps 1 & 2 from http://confluence.atlassian.com/display/DOC/Troubleshooting+Character+Encodings
Also, you may encounter problems if you are using the postgres database. It seems the postgres doesn't handle the tolower and toupper of umlaut characters very well hence affecting Confluence.
For support questions such as these it is problem best to email our sales or support team than discussing it in here 
Regards,
Agnes.

Posted by agnes@atlassian.com at Dec 18, 2006 16:40
|
Has this setup been tried with the mod_dav_svn module in Apache 2.2? This module provides WebDAV service, where files are stored in a Subversion (version control) repository. I can configure Confluence (2.3.3) to use this type of WebDAV server for attachment storage, then the migration takes several minutes to run (as expected), but no files show up in the Subversion repository (almost as if the files were transfered but no "commits" never happened).

Posted by nessld@nationwide.com at Feb 28, 2007 11:52
|
I am trying to setup webDav as my attachment storage, but when i put in the details of my webdav server, i get the error message:
The following error(s) occurred:
* Warning: null
Ive looked through the log files but can't see anything todo with webdav.
I am running confluence version 2.3.3.
Does anyone know what this problem could be being caused by? Or how to turn on Debug logging to get a more detailed log output?
Thanks Simon

Posted by simon.croak@upco.co.uk at Mar 08, 2007 06:19
|
|