View in #migration on Slack
@w.m.slob: A little late in the conversation, but couldnât we create a feature in which a user can connect a Dropbox account / Google Drive / whatnot, tied to the CP update core?
I use this plugin called âAll in One WP Migrationâ - which creates a .wpress file in which I can restore a complete site based on that file, the plugin and a clean install.
Personally I would be in favour of auto-update (forced) based on (serious) security patches. But I can understand the feeling users would want to have control over their back-up options.
@elisabetta.marina.cle: This is also a great idea @w.m.slob. Basically letting the plugin upload to storage a backup before updating in background. But again I think we should pair that with the ability to have an advanced menu to allow for disabling should the user prefer this at his own risk. One option doesnât exclude the other in my opinion.
@wpslayer: If it were possible to have an automatic backup that triggered upon notification of an update, that would be wonderful. I donât know how practical that might be for the current state of things.
Getting a migration plugin sorted to update and to migrate both single site and multisite seems to be quite a process (This observation is not meant to be a criticism, just what I have gathered). So I donât think hoping for something like auto backups for forced updates would be reality based for the near future. Though it would be nice. 
I use duplicator pro. It works perfectly with multisite and single site for scheduled backups. The automatic backup can be files and db or just db or just files. I send those updates to dropbox.
However, on a forced update, there isnât a schedule. The update occurs without warning and therefore, potential for loss of data is a real concern and has been for me since WP 3.7.
@w.m.slob: No plugin governing plugins? I know nothing of practice but in abstraction it should be if update available, then run backup based on preset, then update
@wpslayer: That would be really nice but I havenât heard of anything set up to do that. I donât see why it couldnât be done though.
Of course, just because I havenât heard of it being done, doesnât mean it isnât being done.
It would probably be worth the dev time of some pro backup plugins for implementing something to trigger upon notification of a core update. But there would still have to be a consideration in place at core level to give such notification prior to updating, I think.
Something like what was mentioned earlier where the automatic update happened if no confirmation within 6 hours.
But then again, WordPress does when âautoâ update is turned off, still triggers the update notification. So, that could possibly be used to trigger an automatic backup.
Sure wish I was a coder right now. Iâd like to see if I could do it, but I have a long way to go before I could do that.
@tim.kaye: >Basically letting the plugin upload to storage a backup before updating in background.
I am pretty sure the UpdraftPlus plugin has an add-on that does this. It would be great to see something like it built in to CP.
@mte90net: well if we focus also on backup stuff and import them we are doing a clone of a lot of other plugins that do that pretty well creating confusion with users that already use them
as right now is the project better focus on the minimum to work so we have time to do other stuff that have high priority
@jnylen: the biggest issue with adding a backup functionality to ClassicPress is that itâs a lot of work, especially when you get into all the edge cases with different kinds of hosting
so this would need to start as a semi-official plugin that we can recommend
unlikely for v1
I know Iâm not going to have time to work on it
@w.m.slob: Yes, v1 should work soon, no frills. And maybe this is something for v3 or even v4. I just thought in abstraction it could help set us apart.
Also, I think one of the strengths of CP can be (similarly to WP) is that âthereâs a plugin/module for thatâ. A lean, efficient core, but with a properly documented route to help people achieve what they want to do. Maybe similar to developing a skill tree efficiently in a RPG.
@elisabetta.marina.cle: Fact is we have to see things in perspective. Yes v.1 has to be rolled out on time and has to be compatible with WP 4.9.1 for obvious reasons and implementing things like backups now is not an option. But sometimes along the line it will be. Discussing things now gives us time to understand which solution fits with CP values and mission statement best.
@tim.kaye: Certainly wasnât expecting it for v1. Wasnât necessarily expecting it for v2 either. Just a nice thing if it can be done at some point.
@jnylen: Yes, if someone wants to work on a plugin for this, and make it an official ClassicPress ârecommendedâ plugin once it is ready, we will be happy to help with that.
@wpslayer: The fact that CP contributors are willing to listen is a major step in the right direction. I personally think things are already pretty much in place to accomplish the backup solution with a plugin, from my understanding of things.
Documentation is a very big thing. Have fun with that.
@jnylen: OK. I donât think the suggestion to add a core backup solution has been made yet outside of Slack. Can someone create a petition at https://petitions.classicpress.net/ so it doesnât get lost?
ClassicPress Petitions
@pieter: this is kinda similar?
https://petitions.classicpress.net/posts/59/core-support-for-basic-backups
Core support for basic backups ¡ ClassicPress Petitions
but happy to open a separate petition for it
@jnylen: ah
yes, I even commented on that one!
so, thatâs the best place to continue the discussion about that suggestion.
@pieter: ha, yeah you did, and me too 
> so, thatâs the best place to continue the discussion about that suggestion.
probably although that discussion went into quite different directions than what adding core backup solution proposes
@wpslayer: Oh gee⌠I did too. I completely forgot about it.
The issue arises though, when there is a forced update. The option to backup doesnât exist unless core update has been disabled.
@jnylen: Yes, in that case having an officially supported plugin that can do an automatic backup before the upgrade would be a huge benefit.
I am trying not to think too hard about all the potential edge cases there, though, otherwise I might need a drink
@wpslayer: A pub might be nice. Eh?
@jnylen: Eh
@pieter: so we are in agreement that we will use the existing petition to discuss more about it instead of opening a new one?
@jnylen: Iâm happy to discuss here, but thatâs what I would recommend if we have something we want to say and not have it get lost in the backscroll.
And yes, I donât see the need to open a new one.
âBasic backupsâ includes the database as described in the original petition, and also the siteâs files.
@wpslayer: I have contacted the devs of duplicator/pro and asked about the suggestion and the possibility of catching the notification to trigger an automatic backup prior to the forced update.
@jnylen: I have not seen that functionality suggested or implemented before, but itâs a really good idea.
Granted, as I said on the petition, I still think the best way to do backups is via the shell / terminal on the server.
@wpslayer: That would be great, if everyone knew how to do that. And if there was a notification prior to the update.
@jnylen: Yeah. I think my solution is the best one - it works for any site, even if the frontend and backend are completely broken - but I donât think itâs for everyone.
@wpslayer: I think the next best thing would be for a plugin to be able to disable the âautomaticâ update, causing the notification which would trigger the backup, then go ahead and update the site as soon as a successful backup has been accomplished.
@jnylen: A lot of places where that could go wrong, but yes, that would be a pretty excellent experience.
@wpslayer: As with forced updates, a lot of things can go wrong. Thus the need for a solution. IMO
Having said that, automatic backups are accomplished all the time with schedules. I donât see a major issue out of the ordinary. Some fail. However, a notification is sent to the site owner or manager and appropriate action can be taken when a backup fails.
In that case, the notification (indicating an update for CP could not be accomplished due to the backup not successfully completing) can be the trigger for the site owner or manager to manually back the site up and update CP.
I have the logic in my head. It works perfectly⌠