Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I am writing to get some advice regarding a good backup strategy for my code which I will deploy on a remote server.
The situation: I will have access to a VPS/actual server somewhere. It will have some popular flavor of linux on it, probably Ubuntu 9.04. I will have admin rights.
The problem: How should I set up a backup strategy?
The guys who will give me access to the server may not be able to go in and add hard disks as and when I need them and so they have offered to provide more disk space up front than I would need. They will install the linux system, I will not have access to it during the OS installation process.
I think my application will never use more than 1 TB of disk space. The guys at the server farm can install a server with 2 1 TB disks for me. What could be the best way to mirror the primary 1 TB disk onto the 2nd 1 TB disk after the OS has been installed.
Also if there is a standard recovery mechanism to bring back the system based on a mirrored disk, I would really appreciate a pointer.
I have used Google to search and there's tons of articles, petabyte systems and what not. I am not sure how to go about it and hence this post.
You can do it after the install. From what I can remember, the logic is:
-Setup RAID1 partition on second hard disk with first disk 'missing'.
-Create new partition(s) on second hard disk (preferably LVMs).
-Mount the partition(s) and copy all data from original disk to new disk.
-Setup grub on second hard disk.
-Setup new initrd on second hard disk.
-Change your BIOS to boot to one disk or the other.
-Remove the first disk and see if you PC will boot just with the second disk.
-Change boot order on the disks.
-Wipe out what used to be the first disk and add it to the array.
-Configure grub on the new second disk
-Reboot with either disk disabled to verify.
RAID 1 (aka mirror) is NOT a backup soln, it just protects you if one disk dies. If you delete a file (or file tree!) or get a corruption, it will happen to both disks simultaneously. Use rsync to copy files from one disk to the other once a day/week as appropriate.
Also, do an offsite backup so you have protection from site issues and also multiple backups. You may not discover an issue till several days after the fact. Classically you have grandfather/father/son eg
7 daily backups, extract the Fri backup and move it off as a weekly, extract every 4th weekly and save as mthly backup.