[DOCS-1296] Comment on: "manual/tutorial/backup-databases-with-filesystem-snapshots.txt": filenames and remote/local compression/decompression. Created: 25/Mar/13  Updated: 03/Nov/17  Resolved: 25/Mar/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: auto Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Not important.

Location: http://docs.mongodb.org/manual/tutorial/backup-databases-with-filesystem-snapshots/
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22
Screen Resolution: 1366 x 768
repo: docs
source: tutorial/backup-databases-with-filesystem-snapshots


Participants:
Days since reply: 10 years, 47 weeks, 2 days ago

 Description   

Hi,

some comments on 'http://docs.mongodb.org/manual/tutorial/backup-databases-with-filesystem-snapshots/':

  • section 'Backup and Restore Using LVM on a Linux System', subsection 'Archive a Snapshot', I am reading 'dd if=/dev/vg0/mdb-snap01 | gzip > mdb-snap01.tar.gz': why .tar ? This is not a tar file, should we not read 'dd if=/dev/vg0/mdb-snap01 | gzip > mdb-snap01.gz' instead ?
  • section 'Backup and Restore Using LVM on a Linux System', subsection 'Restore a Snapshot': same as above for 'gzip -d -c mdb-snap01.tar.gz | dd of=/dev/vg0/mdb-new', and if not fixed for some reason, you might want to update 'Uncompresses and unarchives the mdb-snap01.gz into the mdb-new disk image.' which correctly refer to a file without '.tar'.
  • section 'Backup and Restore Using LVM on a Linux System', subsection 'Remote Backup Storage': same as above.
  • section 'Backup and Restore Using LVM on a Linux System', subsection 'Remote Backup Storage': the procedures described in this section use lot of bandwidth, is it done on purpose (remove CPU usage on the server serving the database) ? A note might be welcome to explain the trade-off between doing local and remote compression/decompression.

Feel free to contact me fore more information.

Best regards,

Jean-François Gagné
jean.francois.gagne.1977@gmail.com



 Comments   
Comment by Sam Kleinman (Inactive) [ 25/Mar/13 ]

Fixed the file extension.

It doesn't make sense to compress locally and then offload to (ssh automatically compresses it's operations,) so compression locally would be redundant, and take even more resources from a presumably production system. I think the decision to create the gzip file depends on available space which is mentioned and other considerations that are beyond the scope of this file.

I'm going to close this ticket for now, but feel free to comment or reopen if you think we need to do more work.

Cheers,
sam

Comment by auto [ 25/Mar/13 ]

Author:

{u'date': u'2013-03-25T18:02:51Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1296 correcting file extensions
Branch: master
https://github.com/mongodb/docs/commit/16532b3816e864948508debce3464e9d4d3700e5

Comment by auto [ 25/Mar/13 ]

Author:

{u'date': u'2013-03-25T18:02:51Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1296 correcting file extensions
Branch: v2.2
https://github.com/mongodb/docs/commit/8838c91739d214d692bdff7876b54a492ad1049b

Generated at Thu Feb 08 07:40:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.