tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/13113-site-importCascade CMS: Discussion 2013-08-20T01:22:27Ztag:help-archives.hannonhill.com,2010-02-09:Comment/262086812013-04-03T18:55:39Z2013-04-03T18:55:39ZSite import<div><p>Hi Christian,</p>
<p>Unfortunately it sounds as though you are running into an issue
we're aware of where large export files fail to import. There are a
couple of different problems with this functionality that we're
aware of:</p>
<ul>
<li>The operation is unzipping the site export multiple times and
those files are not being removed (so, on application servers with
very little available HD space this could cause an issue)</li>
<li>The operation can consume large amounts of the available
memory</li>
</ul>
<p>I have a feeling you are running into the latter. You
<em>might</em> be able to get this working properly by allocating
more RAM to your Cascade Server instance, but I would recommend
trying the import first in a test environment (with the same RAM
allocation). For example, I had an issue recently with a 350M
import that was only resolved for me once I increased my maximum
heap size to 4G.</p>
<p>We'll be working to correct both of these problems in a patch
release. Let me know if you have any further questions about the
problem.</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/262086812013-04-03T21:42:51Z2013-04-03T21:42:51ZSite import<div><p>Thanks Tim, we did upgrade the server RAM, but had no luck.
We'll wait for the patch.</p></div>Cristian Hortatag:help-archives.hannonhill.com,2010-02-09:Comment/262086812013-04-03T21:47:16Z2013-04-03T21:47:16ZSite import<div><p>OK, Christian. Sounds good. Apologies for the inconvenience!</p>
<p>Take care.</p></div>Tim