Hi folks, thanks for your replies,
@_sax: The commandline process works. The problem is that classpaths change with every release.
but thanks for your hint to import via webexplorer.
It works. I can export authorities, and people via command line from 2.1 and import the XML(!) into 3.4b via webexplorer.
First it seemed like it did not work but everything is fine after a reboot.
A full would be overkill on my system because of the datasize. During the export process alfresco is chacheing everything into the temp folder.
After that is seems to create an acp file for download. what means that you will need 3xRepositorySize of harddiskspace on your exporting machine.
I tried mount the tomcat/temp to a NFS drive but the export took about 5 hours and then the server crashed.
@mrogers:
Yes I know. But the described upgrade procedure only work to 80%. I already tried upgrading using the path described by _sax.
Every single step threw errors. (email-notification scripts failed to migrate, some scheme patches could not be applied because of missing tables or columns)
After working around the errors I managed to get the migrated 3.4b up and running. But some content was (randomly) crippled and the search function
became nearly useless (finding nearly nothing. yes, i did a full lucene rebuild).
The MasterPlan is to migrate the users by exporting and reimporting to 3.4 and then migrate the content Space by Space.
It seems to work quite well If I first import users and groups and then the content. Even all permissions stay functional.
I do not have any custom scripts so chances aren't bad.