I will eventually start doing some further searching on this, and I may very well have found some info in the past in previous searches, but I thought I might as well just ask the folks here on Drupal.org for suggestinos.

I have a couple of sites currently running on Drupal 6, and one on Drupal 7 which I just totally took down when the major security announcement came out mentioning backdoors to sites. Since I built those sites, my time has been extremely limited, not that I had tons of time in the past to work on the sites.

I like the idea of Drupal in how it is structured, and as far as I can tell, I like the Drupal 8 overall design better (site/folder structure and such).

My question is really about 3 different possibilities, but at the same time, I can see where the answers could be actually wrapped up in one product or method or reference point.

So here are my scenarios that I'd like to consider:

  1. Active Drupal 6 Sites - What are some of the best options/tools/methods for backing up site content in such a way that I could then create a new site in Drupal 8 once stable, not Beta, and more or less import the content? I'm not so much concerned with details like author and publish date, but more or less just the content that is typically visible to the end user audience. It'd be good to discuss back-end/maintenance type data if it's handled separately, but primarily just what the end user sees on a site.
  2. For a Drupal 7 site - if I maintained a backup, I'm sure I have at least a couple that I didn't delete with the way I backup so much - I backup my backups. :) I'd like to know - are there any good ways to extract the content easily from say the database backups and/or site backups. I suppose it would have to be MySQL queries assuming that is the database used, but are there any good tools/options out there along those lines?
  3. For a Drupal 8 Beta site, What good methods are there to back up the content between releases, then export, and re-import into new sites? Would the Backup and Migrate Module(s) be all that I would need? Would something like that break between Drupal minor version upgrades/re-installs? The reason I ask is that the couple times I've attempted a minor version update on a test Drupal 8 site, every attempt has failed. I've ended up just scrapping what I did, and starting over. It's not the end of the world at this point, but it s disheartening, since I don't have all the time in the world to repeat, repeat, repeat, and repeat my efforts at testing a new site build.

My question is more so for front-end developers, I suppose, as I do not have time with my non-drupal, non-web deisgn, responsibilities to get much farther into it. I do hope one day to look into scripting methods such as using Drush (which I did look at, prior to Drupal 7), and get more familiar with those. That seems to really be the way to go in order to cut down on some of the monotony for some tasks.

Thanks in advance for any thoughts or suggestions.

Comments

VM’s picture

Considering that Drupal 8 is still in beta expectations for upgrade paths should be tempered until such time as it is considered a stable release.

kjv1611’s picture

Definitely understood. I'm thinking more-so of at least backup the content. I guess only way to see if it works for now is to try it out. The Backup and Migrate module has versions in dev for D8. So maybe I'll try that soon - see if I can get it to install. My past install attempts at 3rd party modules have not been so great.

Thanks for the comment

VM’s picture

you can backup the database with your server database tools.

kjv1611’s picture

True - Thanks. That's where all the content is, then if necessary, I can just build queries to get the data out either in phpMyAdmin or link to it with MS Access as one tool I'm very accustomed to.

Mindblowing’s picture

I make drupal site back up simply:
STEP 1 - backup all web site files.
Backup all the files and folders inside the Drupal directory. You can do that by downloading them via your favourite FTP client.

STEP 2 - Backup/Export database
Then, you have to export your Drupal database. You can do that by using PHPMyAdmin. Just make sure that you choose the correct database, which your Drupal application uses!!!
If you are unsure about the Drupal database name, you will be able to find it in the drupal_folder/sites/default/settings.php file. You can view this file through cPanel -> File manager.

That's it)

kjv1611’s picture

Thanks for the thoughts

couturier’s picture

Because work appears to have stalled for Backup and Migrate 8.x (last update was January 17, 2015), developers who cannot backup via the command line (due to access permissions for certain server situations) can alternately try a simplified version of the Backup and Migrate which is under current development for 8.x, Backup Database maintained by swim.