Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
No, that's not possible, as a snapshot is not new disk space, but existing areas of that LV which are not modified. Instead all new data is put onto space with the VG, and all the while the size of changes between the snapshot and the current data is less than the size allocated to the snapshot, it will be valid. You can take a small snapshot and then dd it to a seperate location if that's what you want to achieve.
snapshot space needs to be reserved within each VG, as above, you can't snap to somewhere else, as there is no data actually written anywhere. the point of a snapshot is to freeze a copy in time, so you would, assuming your tape is fast enough, write directly from the snap to the tape. you do not need intermediary disk space if you can write to tape before the snap invalidates itself, which for a database, depends entirely on how it's used during that time. I think you'd do well to do some formal study of LVM and what technologies actually back up the concept of an LVM snapshot, and it should fall into place much better.