|
Hi Charles,
Thanks for the suggestions. Yes, right now we are doing file system backup in addition to database backup. Following is bit more enhancement to this request of Attachment Quota: Attachment Quota should be able to set in 3 ways: 1. On global level set the limit so that all spaces can store attachment data of x size lime for eg. let's say 200MB etc. 2. If needed, we should be able to increase the attachment data limit in increments may be in 50 MBs (if Space Admins request.) 3. In case of highly active/used wiki space, we should be able to set the attachment data limit to different value like 1GB (this value will over-ride global limit!) This will give more fine control to Adminstrations to handle angry users thanks again, ..also, since it's perhaps implied, but wasn't explicitely mentioned above, dividing the upload directory structure such that uploads are stored in directories associated with spaces would add considerable flexibility
We have a small Wiki, but have this problem in spades. Users upload all kinds of junk.
Maybe if the attachments were more integrated into the "edit" cycle, users would be more likely to delete (or mark obsolete) old attachments? It would also be a great help if the attachments were divided into spaces, and stored with natural filenames – for several reasons. (1) so we can scan the attachments to find the 40mB powerpoint files, and (2) because it is often far more practical to manipulate attachments in the filesystem, and (3) so that filesystem scanning tools [like google desktop search] can help users find attached data. I'd love to have this feature. We are discussing eliminating our "junk yard" Windows file share and using Confluence instead. I envision creating a page like "My Shared Files" for each user in their personal space. This would make it easy for everyone in the company to share files with others.
However, as other posters have mentioned, users love to create but they rarely delete. Having a per-space quota would be great. Adding on to Rajendra's comment, I'd like the ability to set a default value for personal space quota, say 200 MB, but be able to override an individual's space quota. This would be helpful to our institution as well. We have become accustomed to to providing folks with a pre-defined amount of "stuff" (Exchange, file shares, web documents, etc.). The ability to actively hinder our users and punish our contributors would be a welcome "feature."
This, too, is really hurting us. It's hard to police the users by hand, especially because there's no way to quickly sum the usage per space, let alone tell them not to do it anymore.
To build on Jeff's point: "However, as other posters have mentioned, users love to create but they rarely delete. Having a per-space quota would be great. Adding on to Rajendra's comment, I'd like the ability to set a default value for personal space quota, say 200 MB, but be able to override an individual's space quota." I'd like a separate quota for personal spaces versus regular spaces, and on top of that have the ability to override on an individual space. Has any more effort been given to this issue?
Controlling the quota on spaces using the administration tools is very desirable for us in a University setting. Please let me know if this feature will be include anytime soon? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Attachment Quota per space
In the meantime, to reduce the strain on backup, you can actually back up attachments separately. Add the [Confluence home]/attachments directory to your regular filesystem backup regime, and set Confluence's global backup preferences to not include attachments. This will make the Confluence backup much smaller, but if you need to restore, you'll need to copy the attachments directory back in separately (there might also be some data-loss if the Confluence and filesystem backups were made at different times, so try to get them as close together as possible).