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.
backups can be a very time-consuming operation in aegir.
disable is designed to quickly disable a site without deleting the data. in essence, it just changes the virtual host configuration right now, but also changes the alias and does a backup.
this makes the disable task much less useful because the site can take a while to disable.
let's stop backing up sites on disable.
Comments
Comment #1
anarcat CreditAttribution: anarcat commentedpatch is obviously trivial:
we would need to document that as an API change in the 3.0 branch, and i wonder if we shouldn't backport this to 2.x...?
Comment #3
anarcat CreditAttribution: anarcat commentedi applied the patch to 3.x, and it also applies cleanly to 2.x. I am putting this as "to be ported" to get feedback from other maintainers.
Comment #4
ergonlogicI agree. Presumably we still backup before deletion, so there shouldn't be any danger here.
Comment #5
helmo CreditAttribution: helmo commentedack, as we don't lose any data I see no real reason to make a backup.
Comment #9
ergonlogicComment #11
helmo CreditAttribution: helmo at Initfour websolutions commentedThe 6.x-2.x branch will go EOL along with Drupal this week. So I'm closing
this issue. If it remains a confirmed issue in 7.x-3.x, feel free to re-open,
or better yet, create a new issue referencing this one.