Copying a Cascade instance to another server
Hi there,
We're currently developing our new website using Cascade server.
We've got a development installation ( version 6.7.3 ) up and
running and we've started to enter real content into the
database.
We're running on tomcat, and did our installation using war files.
What we want to do next is set up our production instance, and copy the database from the dev instance.
Here's the plan:
First we're going to create a new installation.
We'll copy the Cascade v6.7.5 war file into tomcat on our
production server, connect to a clean database.
We'll install the production license.
Stop tomcat
Then we'll copy the dev database over top of the production
database.
Restart tomcat.
Does this sound like it will work? What are the best practices
for moving servers?
I wonder where the license info is stored. Is it in the database or
in a file somewhere?
Also is there any issue moving from v6.7.3 to v.6.7.5? The upgrade notes don't mention any database changes.
Thanks for your help.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Lee Roberson (F... on 28 Jan, 2011 06:40 AM
Jeff,
A few notes on this, some of which really aren't documented to my knowledge, so you should find them helpful.
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.
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.
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.
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].
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!
Tim closed this discussion on 30 Nov, 2011 07:07 PM.