tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/80-copying-a-cascade-instance-to-another-serverCascade CMS: Discussion 2018-10-18T20:36:10Ztag:help-archives.hannonhill.com,2010-02-09:Comment/49918542011-01-28T06:40:30Z2011-01-28T06:40:30ZCopying a Cascade instance to another server<div><p>Jeff,</p>
<p>A few notes on this, some of which really aren't documented to
my knowledge, so you should find them helpful.</p>
<p>Your plan for moving content to the new installation sounds
almost perfect. Be sure to search the KB for "test instance" --
there is an article in there that is very helpful for setting up a
"quiet running" copy of Cascade that doesn't execute duplicate
publish jobs or send out e-mail alerts. You may want to perform
those steps when and if you migrate content back over to the test
installation.</p>
<p>The license is stored in the database. That's the almost perfect
part. You'll be prompted to enter a valid license when you boot up
Cascade again. It's really not an issue, you just have to re-paste
your license in.</p>
<p>Not sure if there are database changes between those two
versions. They are rarely mentioned in changelogs. When you start
up the newer version of Cascade, if database schema changes are
required they will be applied automatically. The cascade.log file
will contain some notes during first start-up that do discuss the
process of updating the database schema if the version you are
starting up requires it.</p>
<p>One caveat, you can't move a database from a newer version of
the software that has an upgraded schema to an older version, i.e.
there is no "downgrade schema" script [at least not that I am aware
of].</p>
<p>I have accidentally hot-copied the production database to our
test server a few times without any huge issues but I wouldn't
recommend it. I would recommend stopping the source Cascade
instance first!</p></div>Lee Roberson (Function Digital LLC)