Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I upgraded from beta2 (git) to 1.1 (deb), the upgrade process suceeded but it failed to produce a backup of the old hostmaster platform.
I followed the steps outlined on this page : http://community.aegirproject.org/upgrading/debian#Upgrading_from_non-De...
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedWe don't do backups when we destroy platforms in the frontend either. How did you expect this to work?
Comment #2
lavamind CreditAttribution: lavamind commentedIf the upgrade process doesn't create a backup of the old hostmaster platform, then how can you Roll-back the upgrade?
Specifically this : "During the upgrade, a backup was done and you need to find which backup file it was in the backups directory. Use this backup to redeploy the older platform"
So perhaps this is just a documentation problem?
Comment #3
anarcat CreditAttribution: anarcat commentedThat is true - we used to do backups, and now we don't anymore...
I am not sure how to fix this cleanly.. I think in 2.x we'll start using the drush archive commands more extensively, and those are designed to backup complete platforms. So we could adapt provision-backup to platform-level backups...
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedDo we have to destroy the old platform from the backend? We don't instruct to do so in the manual instructions, and it can be just safely removed later from the frontend by the user..
Comment #5
anarcat CreditAttribution: anarcat commentedOkay, let's not destroy the old platform. The way we do it isn't clean anyways, as long as we don't depend on the drupal6 package we're non-compliant anyways. I have uploaded a -3 package to the unstable repository to test this (and change the DEBUG flags...).
Comment #6
anarcat CreditAttribution: anarcat commentedi think this is fixed. i had to upload a -4 release because i don't think it's right to just *remove* DEBUG, we should deprecate it, as the docs all over state DEBUG works.