Hello Paul,
There is no filesystem attachement migration on startup, it has to be done
manually using
http://extensions.xwiki.org/xwiki/bin/view/Extension/Filesystem+Attachment+…
.
You will have to be very careful to use high memory setting during the
operation, to prevent issue. You may proceed to a dry-run of the operation
if you want to confirm it will work, but the dry-run could be as long as
the migration itself.
In your case, I would suggest the following procedure to minimize the
access downtime:
1) put your production wiki in read-only mode
2) make a full copy of the DB and permanent directory to temporary server
3) proceed to the attachement migration on the temporary server
4) move back the storage folder (from the permanent directory onto the
production server)
5) change the production server to filesystem attachement, and remove
read-only mode
Obviously, you will have a write access downtime, but this is almost
unavoidable.
Regards,
On Tue, Jan 6, 2015 at 6:19 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
Hello fellow XWiki developers,
At Curriki, we are considering more and the possibility to migrate to the
file-sytem attachment, however, the current solution (which does it at boot
time) is not acceptable since it would make our service unavailable for
several days (there are 73756 attachments on 591000 documents, when we
tried on a dev server, it took a week).
Where can I read more about the DB-migration that converts the DB
attachments to the file-systems' attachments?
Where is the source? What modules are used?
thanks in advance.
Paul
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO