cdmiller at adams
Jul 22, 2009, 3:12 PM
Post #6 of 9
Here is what I would do, and I'll be pursuing something similar pretty
soon for our production stuff:
1) Set up the new server, put as many bricolage prerequisites in place
as possible, this will include an Apache 1.3 install for Bricolage 1.10.x.
2) Run a make clone on your production server.
3) Put the clone image on the new server and run a make install, specify
a new database when you do this.
4) Run a make upgrade to Bricolage 1.11.x on the new server.
5) Install apache 2 on the new server and manually fix the Bricolage
1.11.x configuration to use it.
6) Test new server/database with different preview/publish targets
before flipping the switch.
I think there are some tips for switching the configuration from apache
1.3 to apache 2 buried somewhere in the list archives.
Hope that is helpful.
Fletcher, Michael wrote:
> Ideally, I'd like to copy my data to the new server without having to run 'make upgrade' because I don't want to change the existing server running Bric 1.10.2. Getting Bricolage 1.11.1 installed on the new server was no easy task with all the prerequisites. Doing the upgrade on our production server seems very risky to me, not to mention we are a 24/7 news service and it would require way too much down time for our business.
> Isn't there any way that I can copy the data over to the new server running Bric 1.11.1, run JUST the data conversion portion of 'make upgrade' and test all my data on the new server? Then if all goes well, I can do that again in a short period of time and switch everyone over the to new server.
> I must be misunderstanding you, because you said that my idea of doing this once for testing and then again when we go live is "Smart", but I think you're telling me I have to run 'make upgrade' on the existing production server. How would I do that twice and not affect the existing version of Bricolage on that server? As you can see, I'm confused.
> Thanks for your help,
> On July 21, 2009 9:40 AM David E. Wheeler wrote:
>>> I'm putting Bric 1.11.1 and the new instance of a PostgreSQL database
>>> on brand new servers. The database is not on the same local server as
>>> Bric. My production environment is also on two separate servers, 1
>>> for Bric and 1 for the database. I would like to backup my PostgreSQL
>>> database on the old server and restore it on the new server, which is
>>> no problem but I don't know how to convert the data to the new Bric
>>> data structures. It seems like 'make upgrade' is intended for
>>> upgrading on the same server - which is not the case for me.
>> I recommend that you run `make upgrade` to update your local server,
>> then restore it to the new box and change your connection settings.
>>> My new server configuration is:
>>> CentOS 5.2
>>> Apache 2.2.11
>>> mod_perl 2.0.4
>>> Perl 5.8.5
>>> PostgreSQL 8.3
>> You will also need to reconfigure things for mod_perl2.
>>> I will be doing the data migration twice - once for testing the new
>>> environment, and then again on the day we actually switch over to the
>>> new system.