http://drupal.org/upgrade/backing-your-site-command-line
Hi;
Just working through using this document with Drupal 7.x and found a couple of things that should be noted on the page.
Under "Back up your Drupal database with MySQL" :
1. The drush command line :
The drush command line should probably be shown with parameter to specify the destination file for the backup similar to the mysqldump command just above it. At least that is the parameter that I had to go find when I tried to use it.
Change
drush sql-dump
to
drush sql-dump --result-file=drupaldatabasebackupfile.sql
Note: drupaldatabasebackupfile.sql can contain a path to the file.
The drush command works with Drupal 7.x
2. The drupalsqldump.sh command line :
I have been using the drupalsqldump.sh script to backup my Drupal 6.x site quite successfully.
When I tried to use the drupalsqldump.sh script to backup my Drupal 7.x site, I found that it returned an error regarding a -h parameter. At that point I switched to the drush command.
Maybe the document should identify that the drupalsqldump.sh script work with Drupal prior to version 7.0.
Maybe a link to a current version of the drupalsqldump.sh script or information on how to get the script would be a good idea.
Comments
Comment #1
batigolixthe whole backup section (http://drupal.org/node/22281) could use a review. feels like things are being repeated over and over
i cannot edit http://drupal.org/upgrade/backing-your-site-command-line due to not allowed input formats for my role, maybe?
Comment #2
skrossa commentedI was going to volunteer to give it some love, too, but I can't edit it, either. (Perhaps it is the dreaded last edited with an input filter we mere mortals aren't allowed to use issue? ;-)
I think it would be good to have an intro on each of the different backup method pages re-iterating the needed general steps.
For that matter, the main backup page (http://drupal.org/node/22281) could use a decent summary intro listing what needs backing up to backup a site, and a bit of reorganizing. (I don't think that a core vs. non-core division makes the most sense for the non-database files.) Happily, that page I can edit.
[I'm still new to this issue queue stuff -- should I start a new issue for http://drupal.org/node/22281 and/or the intros for other backup method pages?]
Comment #3
batigolixthe page http://drupal.org/upgrade/backing-your-site-command-line is editable now
Comment #4
batigolixfirst revision done: http://drupal.org/node/61740 . this revision includes all the suggestions above. furthemore i simplified the structure and uncluttered the text.
i left the postgres part as it was
@SKRossa: i think we can use this issue to discuss improvements to the handbook section. i already modified the title
Comment #5
batigolixchanged status
Comment #6
batigolixthe main handbook page on backups (http://drupal.org/node/22281) contains large chunks of text with sometimes patronizing remarks ...
it also contains information that is covered elsewhere. the whole part under backup files and backup database is also covered under the child pages "backup with command line" and "backup with gui". they re just the same info ordered differently
we should further clean up this main page, shorten it and remove duplicate information
@SKrossa : I see you already started with this. will you continue further improving this main page?
Comment #7
skrossa commentedYes, I am continuing to work on the main page. I will be moving a lot of stuff to the appropriate sub-pages.
Some specific feedback on the tone --particularly the tone of the General backup best practices points, which I've rearranged but not yet tackled editing the prose-- would be welcome. We need to give enough info for the completely new to backing up people (which should include the whys) without being patronizing.
Once we've got a good general page with info on what needs to be backed up, we'll also want to review all the sub pages again and make sure they give the specific details for how to do each of those steps by the relevant method.
(I'm having fun with this :-)
Comment #8
arianek commentedtags
Comment #9
batigolixi propose to compress all information in the child pages under http://drupal.org/node/22281 into 4 pages: 1 parent page and 3 child pages
* parent: "backing up a site" : overview & recommendations
** child 1: "backing up the DB"
** child 2: "backing up files"
** child 3: "backing up a drupal 6 site": container for D6 only information
let me know if i can proceed with this
Comment #10
quietone commentedThis for D7 documentation and D7 is End of Life.