I have Artifactory 5.4 running and would like to upgrade it to the latest available one: 6.3.3. Do I need to upgrade it to some interim version or can I go straight to 6.3.3 ?
You should be able to upgrade from version 5 to 6 without the need for an interim version.
Before doing so, however, it is strongly suggested that you
Do a complete system export. If at any time you decide to roll back to the older version, you can use the export to reproduce the system in its entirety.
Backup your database.
Related
I would like to replace a physical jfrog server with a virtual one with a newer version of jfrog.
But I want to move the old repositories, not all of them, just some.
Does anyone know how I can achieve that?
I am reading the documentation which doesn't recommend exporting and importing from two different versions.
We want to upgrade Artifactory OSS version from 5.4.4 to latest 7.15.3. Is there documentation for how to proceed? And can upgrade be done directly between these version, or is intermediate upgrade necesssary first?
The OSS version behaves pretty much the same as the Pro when it comes to upgrading. You should follow the official documentation. In general, you will want to upgrade to 6.10.0 and then you can upgrade to the latest 7.x.
The upgrade to 6.x should not result in any major changes but the final upgrade to 7.x does have big changes you should review. The most obvious is that the application now needs two ports to run (8081 and 8082). If you have a reverse proxy, that will need to be updated when you jump to 7.x to accommodate this change, as well as potentially having to modify firewall rules.
Just integrated Flyway into our app and it works great in the following situations:
brand new app install with empty schema, creates the schema_version table and executes the complete schema script after which app is on it's way..works great!
have a patch sql script, we set the version higher than the current version, patch get's applied automatically, version is incremented, no issues here!
Now the problem is the following:
We have older versions of our app out there. Say our current application version is 7.5 (schema version 1.0), when a user is using 7.4 of the application (we will manually set the schema version to say 0.9) and is upgraded to 7.5 the schema upgrade to v 1.0 should be migrated using an Upgrade script rather than the complete script for an empty database. Make sense? How can I approach this scenario, it does not seem to be covered by Flyway.
In summary we have these two scenarios:
Brand new install of our app v7.5:
- installation of new schema v1.0 uses MX_1_0__complete.sql
Upgrade of app from v7.4 to v7.5:
- upgrade of schema from v0.9 to v1.0 should use MX_1_0__74upgrade.sql
since both target schema versions are 1.0 how does Flyway choose one over the other? In addition either only an upgrade or a complete script is to be executed depending on the existing version#, not both!! If current version is 0.9 then upgrade script to be chosen, if current version is 1.0 then nothing is to be done, if there is no current version then the complete 1.0 script to be applied to create a new schema.
Should be simple enough...
Always run all scripts.
Brand new install of v7.4: Run 0.9 script.
Brand new install of v7.5: Run 0.9 script and 1.0 upgrade.
Upgrade v7.4 to v7.5 ... : Run 1.0 upgrade.
Plone Experts:
I inherited a Plone site running Plone 3.3.1. It has a Data.fs size of about 1 GB. It seemed reasonable to try to take advantage of newer features and, in particular, of blobstorage by upgrading to Plone 4.
Thus far I've successfully upgraded from Plone 3.3.1 to Plone 3.3.6 including appropriate data migration for our production usage.
Next, on a RH Linux development server, I did a fresh UnifiedInstall of Plone 4.2.1 which went smoothly. We have virtually no third-party or add-on packages to this is should be a comparatively "vanilla" installation.
Then, I copied in the Data.fs from the Plone 3.3.6 install and did the portal migration step to upgrade from 3.3.6 to 4.2.1.
That also seemed to go smoothly and I can see that I've got many files now in var/blobstorage that seem to be consuming something like 750 MB of space. Great, I thought!
However, the size of Data.fs still still seems to be very close to 1 GB.
So, did the portal migration step create blobstorage but I failed to do something that allows my site to begin to actually use the blobstorage? Or is there something that I need to do to "trim" Data.fs so that it no longer contains the content that has been moved to blobstorage? (Note: I did do a pack of Data.fs but with no significant reduction in the file size) Is there a log file that I can examine that would tell me if I'm using the content in blobstorage?
Thanks for your consideration,
John
Note: as is likely obvious from my question, I'm a Plone neophyte. I'm working on Martin Aspeli's Professional Plone 4 Development book, but haven't found the answer to my questions either in there or in searches of various fora.
the default zeopack configuration only trims objects greater than a day old. If you just ran the migration, likely all those objects are not going to be packed. You can either customize the recipe to retain a different amount of days(0) or just customize the zeopack script directly and then retry packing.
http://pypi.python.org/pypi/plone.recipe.zeoserver
I have a Plone installation at version 2.5.5. I need to upgrade it to 3.3.5. I'm not terribly familiar with Plone or Zope or Python.
This is in a windows 2008 R2 environment. I have the install files for both versions and I'm not worried about breaking anything because everything is backed up a dozen times.
The steps I've taken so far:
1) backed up the old files
2) tried installing 3.3.5 to the same directory...received several DLL entry point errors at the end of the process.
3) had to restart the computer
4) after restart the version 2.5.5 plone controller was still working but the 3.3.5 controller was not.
Did I do something wrong? The notes at www.plone.org/upgrade couldn't have been more unhelpful for my experience level.
Thanks for any advice!
http://plone.org/documentation/manual/upgrade-guide/
this is a good starting point, always.
Basically install Plone 3.3.X somewhere, install the same add-ons (and check compatibility, thus), copy the data.fs over and start plone 3. If it works, run the upgrade steps going in ZMI and following the noticies.
I think no Plone upgrade over major releases I have done went without complications.
My advice is to not upgrade in-place, but instead install the newer Plone version to another directory, create a new instance and copy the Data.fs file from the old site over to the new one. So you can at least compare your new to your old site, running side-by-side.
You then use the "migrate" product to update the database. Try using "dry-run" first. If you encounter errors during migration, try to disable the products that cause the error, and re-try.
That's -- roughly -- the advice from the Plone upgrade documents.