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; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Problems with big acp export / import

boutch55555

Hi

I was trying to export a relatively big space (70GB) on a server and I need to decompress (the ACP is only a zip file after all…) it to modify the XML to remove the thumbnails references (exporting from 3.2r to 3.3 crashes if I don't do it). The final ACP is about 35GB. I was able to do it for smaller spaces (-2GB), but for this one, I cannot unzip it. Tested on windows with winzip and winrar, and on Debian x64 with unzip (v5) and even with the SID package of unzip6. I also checked it with DiskInternals Zip repair, but it failed to find any of the enclosed files. Is there a custom way for Alfresco to handle the exports when the size is over 2GB (old zip limitation) ? Or perhaps, is there a way, with the javascript API to automate the export process and generate lots of smaller packages ? I can't find the proper way to migrate the instance from 3.2r to 3.3, that's why I have to use the export way.

Thanks

Boutch

Find more posts tagged with

Comments

mrogers

You can't use ACP to export and import between versions. The way to upgrade an alfresco repo is well documented so there is no need to repeat it here.

Zip files used to be restricted to a maximum size of 4GB. While there are some implementations of the Zip algorithm that can handle larger files I'm not sure that all of Alfresco's zip file handlers are capable of large files.

If you want to continue with the zip file approach then yes you can script the production of the the acp files however I suggest that instead you modify the Exporter component to not export thumbnails in the first place.

amitabhandari1

Hi,

I am also planning to use the same approach of import /export ACP. I tried with the upgrade approach which is defined in wiki but that is not working for me since I face lot of exceptions especially with the patch 'VersionMigrator'.
I am on current version 2.1.1 and want to migrate to alfresco 3.3.1.
Can you please specify reason behind strongly declining for the import /export ACP.

Thanks,
Amita

gyro_gearless

AFAIK, Java does not support "large" ZIP Files (>4GB or so) until version 7 - so you might try running the import using a current build of JDK 7.
Not sure if this is stable enough to run Alfresco, but i used this successfully for a clienr-side import tool 🙂

HTH
Gyro

loftux

Hi,

I am also planning to use the same approach of import /export ACP. I tried with the upgrade approach which is defined in wiki but that is not working for me since I face lot of exceptions especially with the patch 'VersionMigrator'.
I am on current version 2.1.1 and want to migrate to alfresco 3.3.1.
Can you please specify reason behind strongly declining for the import /export ACP.

Thanks,
Amita

The you need to do a complete repository export to get versions as well, complete repository export is only available prior to version 3. Now you have several acp that you need to import. Not only is the data-model updated (2.2.1->3.3.1) so that you manually would have to edit each entry to fit a new model, but the version store is migrated. So document versions would need to go into the new version2store.
The versions you mention indicates you are using Alfresco Enterprise, contact support and ask them to help you out with the failing patch. It should be a lot less work than the acp approach, and more likely to succeed.

boutch55555

The problem was not with the ACP, but something with the database. It worked (the export part only) with a full index recovery. However, the ACP (zip) were always corrupted, no matter what size I tried over 4gb, there was always corruption. I was finally able to migrate the "regular way" after finding out that the update script only crashed because of the missing "Sites" folder.

If you wish to migrate with ACP, here is my script to remove the "thumbnails" property, since it messes up with the import. Note : you need php5-cli installed
It was only tested from 3.2r –> 3.3g, but should be adaptable.
http://www.sys-tech.net/fileadmin/user_upload/laboratoire/prune-script-3233.zip

Mini howto :

chmod u+x prune3233.sh
unzip package.acp
./prune3233.sh package.xml
zip -r -0 package_fresh.acp package/ package.xml

stefan2

In order to have a non-corrupt ACP file over 4Gb, you just need to replace the commons-compress-1.1.jar in webapps/alfresco/lib with a newer version ( commons-compress-1.5.jar ). The newer version does support large files while maintainging the same interface.

dmsalf2014

We have replaced the commons-compress-1.5.jar with commons-compress-1.8.jar . But still get same problem

mohdazam

why it comes during the migration
false
2014-12-21 15:24:00,455 ERROR [node.integrity.IntegrityChecker] [http-apr-8080-exec-3] Found 2 integrity violations:
Invalid property value:
   Node: workspace://SpacesStore/8004664a-dd99-4290-b2fa-6e13f524b64c
   Type: {http://www.cchindia.co.in/model/cch/stax/caseLaws/1.0}caseLawsDoc
   Property: {http://www.cchindia.co.in/model/cch/stax/caseLaws/1.0}serviceCategory
   Constraint: 11212418 The value is not an allowed value: Programme Production Services
Invalid property value:
   Node: workspace://SpacesStore/2f5986c1-eabb-4d9e-a51b-02efb8d29fad
   Type: {http://www.cchindia.co.in/model/cch/stax/caseLaws/1.0}caseLawsDoc
   Property: {http://www.cchindia.co.in/model/cch/stax/caseLaws/1.0}serviceCategory
   Constraint: 11212419 The value is not an allowed value: Internet Telecommunication Services
LocalName ::: casesDoc Prefix String ifrmCases:casesDoc Name Space Urihttp://www.cchindia.co.in/model/cch/ifrm/casesmodel/1.0