Hi Christian - Thanks for responding to Frank, that info is super useful. I have a related question with a similar scenario:
I'm trying to move from this: - RHEL5 - RB 1.6.14 - External MySQL DB TO: - RHEL6 - RB 2.5.7 (or whatever you'd recommend) - A different external MySQL DB than the current one I'm a little fuzzy about the exact upgrade path I should follow, so far I've done this: - Made a full dump of the current DB, and also migrated the current DB (using AWS DMS to the new DB instance). Not sure if the migration service method will work, that's why I got the full dump of the DB. - Created the new RHEL6 instance for ReviewBoard and followed the instructions here: https://www.reviewboard.org/docs/manual/1.0/admin/installation/linux/ Following from your response, it seems like I should copy the old site to the new box and then do 'rb-site upgrade', but I'm unsure of how the DB piece will work, since I need to point my site at the new DB (maybe this is just in a config file somewhere?). Btw, in case you couldn't tell, I inherited this system from someone else, and am a ReviewBoard n00b, so any help is greatly appreciated! Thanks much, -Will On Thursday, December 29, 2016 at 6:25:56 PM UTC-6, Christian Hammond wrote: > > Hi Frank, > > You'll definitely want to do a full backup of the database, and also of > the site directory. That's all you'll need to back up, really. > > What I'd suggest is attempting a trial upgrade using a copy of your > database and site directory on the new server. Just import the database on > the new server and copy (retaining attributes/owners) the site directory. > Since you're going between different Linux distros, you may need to adjust > ownership of certain Apache-owned directories (data/, logs/, > htdocs/media/uploaded/, etc.), as the username/UID for Apache may not be > the same. > > You can then use our upgrade instructions to do the upgrade. Simply > upgrade the ReviewBoard Python package using a modern version of pip, and > then use `rb-site upgrade` on the site directory. > > It should Just Work, but if you hit database upgrade issues (which > sometimes happens on old systems in certain cases), we'll try to help you > through them. > > Christian > > > On Thu, Dec 29, 2016 at 08:03 drosera <[email protected] <javascript:>> > wrote: > >> Dear all, >> >> we have an old instance of Reviewboard (1.6.5) on an old server (openSuSE >> 12.1). This installation should be updated and finally be migrated to an >> up-to-date Debian server. Not having done the installation myself and not >> having any practical experience with Reviewboard I hesitate to just follow >> the upgrade steps from the documentation (1.6.5. is quite a step away from >> the current version). Are there any best practices around regarding such >> upgrades? What - apart from the Postgres database - should be backed up >> prior to trying an upgrade? >> >> And related to the migration: Is the database everything that has to be >> migrated to the new server? Would you suggest to upgrade before the >> migration or to migrate before the upgrade? >> >> Any help is highly appreciated. >> >> Cheers >> frank >> >> >> >> >> >> >> >> >> -- >> >> >> Supercharge your Review Board with Power Pack: >> https://www.reviewboard.org/powerpack/ >> >> >> Want us to host Review Board for you? Check out RBCommons: >> https://rbcommons.com/ >> >> >> Happy user? Let us know! https://www.reviewboard.org/users/ >> >> >> --- >> >> >> You received this message because you are subscribed to the Google Groups >> "reviewboard" group. >> >> >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> >> >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
