2/29/2024 0 Comments Revert drupal coreThe first step to recovery without backups is to find your web server logs and study them, both of which could be challenging steps. You might lose a few hours or days of updates, but that's a lot better than a few months (or years) worth of updates.Įxpert Tip: Even when restoring a backup after a site failure, never completely delete a broken site or its database - always save a copy somewhere, as you might be able to recover it in a development workspace eventually and/or be able to dig through the database to recover recent changes and copy them by hand into the restored website. If you follow this advice, then hopefully the worst you ever have to do is just wipe out the production site and reload the last backup into its hosting space. Make sure that process works before going off and assuming you're going to have good backups when you need them. Either way, test the system to make sure it's actually generating usable backup files (make sure you're getting both the filesystem and the database, too.) After the first scheduled run, locate these backup files, copy them somewhere else and try to bring up a copy of your site with them. For sites that change more infrequently, you might be okay with weekly backups instead. For sites that change daily, daily backups are a good idea. Many hosting services come with backup systems, but you have to make sure the system is turned on and configured to create backups on a regular basis. The typical advice is to always make a backup before doing anything dangerous to your site, like applying patches and updates, but it's often when you don't think your action could be very dangerous that it ends up frying the whole site. In the future, always have an automatic backup generation plan in place. I'll go ahead and get this one out of the way, even though it may be too late at this point to be of any help. What follows are some tips and advice that might get you back in action again without (completely) losing your sanity. While whitescreening is a good security practice (as opposed to the site spewing error messages to the browser that might reveal sensitive details), it's a royal pain when you just want your site to work and you have no idea what's wrong or where to start with fixing it. You'll apply a module update or do some other under-the-hood task and the next thing you know, your Drupal 8 site is no longer responding (often called whitescreening).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |