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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
1. there are many... most people I know use rsync or bacula
2. not necessarily
3. this is going to depend allot on the hardware and what distrobution of Linux you choose. Never seems an ambiguous term. I do know of many Linux servers that have been running for more than 5 years with out ever being rebooted though.
1. there are many... most people I know use rsync or bacula
2. not necessarily
3. this is going to depend allot on the hardware and what distrobution of Linux you choose. Never seems an ambiguous term. I do know of many Linux servers that have been running for more than 5 years with out ever being rebooted though.
A: Anything/everything you could possibly imagine And then some
A: For example, if you ask how people back things up, you'll get LOTS of different answers...all of them right (for the people using them), and all of them wrong (for each other).
A: there are many
Quote:
1>what method is used?
<= THERE IS NO SINGLE "BEST" METHOD!
And whatever you learn today, might be irrelevant tomorrow
Whatever one employer uses, another will use something different
2>does it required separate machine for that?
<= "It depends"
3>will the backup server never crashed?
<= Similarly, "what if the backup media becomes corrupt?"
A: *Think* about it.
Think about what kinds of things can "go wrong".
Don't stop until you come up with 3 (you can easily come up with 30!)
Now think about what you can do to *mitigate* these eventualities
And remember:
Quote:
A backup procedure that hasn't been tested, cannot be trusted
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
Posts: 3,233
Rep:
not directly related to the 3 questions posed but common sense with backup that is often ignored, as an assistant tech who has been in the field a few times one common mistake i see people doing is they religiously keep backups on dvd/tapes/floppies etc.. only to keep the only copy of the backup media on the shelf next to the server
think about that for a minute and ask yourself why this is wrong
answer:
if the location is physically destroyed (name your natural disaster, sprinkler system malfunction, fire, etc..) and your ownly backup is physically on location it will be destroyed as well
of course if a company can't financially withstand the destruction of their building this is moot but i have heard of at least one company going under after the 9/11 attacks on the wtc because the backup tapes for all their databases were in the trunk of a car in the parking lot under the building
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Posts: 1,197
Rep:
When you come in with such general basic questions, it indicates you need to do a bit of research, reading and learning. Then you might have some specific questions that would get more useful answers.
You could start with the book "Backup and Recovery" by W. Curtis Preston, or check out the companion website, Backup Central. Be aware that it is a broad and deep subject.
Those should make it clear that there are many answers to your questions. My answers would be that I use a variety of backup tools depending on the situation. My departmental backups use Amanda. I use rsync to replicate certain directories such as radmind across departments. I use a variant of rsync to replicate between machines at home. I have used Retrospect in the past but am disinclined to use it anymore. Sometimes I have a backup server that is separate, and sometimes I have separate machines backing each other up. I often have multiple methods and copies. And while you would like to have all your servers never fail, you can't ever count on it. Plan for failures and have procedures to follow when they happen. Test those procedures. And, of course, always test to see that you can recover using your backups. Recover a file, recover a partition. Test on a regular basis.
If anybody takes anything from this discussion, this should be it:
Quote:
Plan for failures and have procedures to follow when they happen. Test those procedures. And, of course, always test to see that you can recover using your backups. Recover a file, recover a partition. Test on a regular basis.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.