<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CAST Imaging upgrade on Documentation - V2</title><link>https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/</link><description>Recent content in CAST Imaging upgrade on Documentation - V2</description><generator>Hugo</generator><language>en</language><atom:link href="https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/index.xml" rel="self" type="application/rss+xml"/><item><title>Update an existing installation - Docker</title><link>https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/update-an-existing-installation-docker/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/update-an-existing-installation-docker/</guid><description>&lt;div class="alert alert-info" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Info&lt;/div&gt;
&lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt;: information about how to update to a newer release of CAST Imaging.&lt;/p&gt;
&lt;/div&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&amp;#x2705;&lt;/td&gt;
 &lt;td&gt;CAST Imaging installed&lt;/td&gt;
 &lt;td&gt;The target server must already have an existing installation of CAST Imaging installed on it.&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="how-to-update"&gt;How to update&lt;/h2&gt;
&lt;h3 id="step-1---stop-the-instance-and-perform-a-backup"&gt;Step 1 - Stop the instance and perform a backup&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Stop CAST Imaging using the following command run from the existing Docker Installer path:&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-java" data-lang="java"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nl"&gt;Linux&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;imaging&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stop&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;Microsoft&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;Windows&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;imaging&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="na"&gt;exe&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="n"&gt;stop&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;ul&gt;
&lt;li&gt;Perform a &lt;strong&gt;backup&lt;/strong&gt; of the existing &lt;strong&gt;neo4j data folder&lt;/strong&gt;. This process is detailed in &lt;strong&gt;&lt;a href="https://doc.castsoftware.com/export-v2/imaging/cast-imaging-configuration-options/cast-imaging-backup-strategy/"&gt;CAST Imaging backup strategy&lt;/a&gt;&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Perform a &lt;strong&gt;backup&lt;/strong&gt; of the &lt;strong&gt;existing Docker Installer files&lt;/strong&gt; - simply copy the files to a different location.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="step-2---run-the-upgrade"&gt;Step 2 - Run the upgrade&lt;/h3&gt;
&lt;h4 id="using-the-imagingsetup-tool-provided-in-docker-installer-1211-funcrel"&gt;Using the imagingsetup tool provided in Docker Installer *≥*1.2.11-funcrel&lt;/h4&gt;
&lt;div class="alert alert-warning" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note&lt;/div&gt;
&lt;ul&gt;
&lt;li&gt;This method will allow you to upgrade to&lt;strong&gt;the specific release of CAST Imaging provided by the installer&lt;/strong&gt;, i.e. the 2.15.0-funcrel Docker Installer will allow upgrades to CAST Imaging 2.15.0-funcrel only.&lt;/li&gt;
&lt;li&gt;This method is supported for those using **Docker Installer &lt;em&gt;≥&lt;em&gt;1.2.9-funcrel.&lt;/em&gt;&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;p&gt;**Docker Installer &lt;em&gt;≥&lt;em&gt;1.2.11-funcrel&lt;/em&gt;&lt;/em&gt; has been changed and supports upgrading of the Docker Installer files themselves via a tool called &lt;strong&gt;imagingsetup&lt;/strong&gt; (introduced in 1.2.11), meaning that any customizations that have been made to any of these Docker Installer configuration files will now be preserved during the upgrade process (this was not the case in the past). To proceed:&lt;/p&gt;</description></item><item><title>Manual action to resolve cache issue</title><link>https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/manual-action-to-resolve-cache-issue/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://doc.castsoftware.com/export-v2/imaging/installation-and-deployment-process-for-cast-imaging/upgrade-process/cast-imaging-upgrade/manual-action-to-resolve-cache-issue/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;CAST Imaging has sometimes been affected by a cache issue where after upgrade to a new release of CAST Imaging, the release number in the splash page was incorrect (still shows the old release number). This issue has now been fixed for new installations &lt;strong&gt;starting 2.11&lt;/strong&gt;.  For those upgrading to &lt;strong&gt;2.11 (or above)&lt;/strong&gt; and still facing the issue, it can be resolved by editing the &lt;strong&gt;nginx.conf&lt;/strong&gt; file as detailed below:&lt;/p&gt;</description></item></channel></rss>