SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I am in the process of installing a file server for a client. They would like to have some kind of real time backup configured for it. Which one would be the best option
1. Setup raid.
2. Install on the first hard disk, use dd command and clone it on the second hard disk and then use cp command or some kind of mirroring software on a regular basis
3. Do backups using normal CD/DVD's and use some kind of cloning software to clone the 2nd hard disk once a week or so.
You can also have a look at "rsnapshot". This is a backup solution based on rsync which creates backup snapshots of your computer(s). You can make several snapshots per day if you want. The method is very disk space efficient because of the use of hardlinks. Here is an article I wrote sometime ago: http://alien.slackbook.org/dokuwiki/...inux:rsnapshot
At home, I have a rsnapshot solution running based on a small Linksys NSLU2 "NAS" running custom software (uNSLUng) with an external 1 TB USB hard drive.
For a business server I would suggest both: RAID and a backup plan.
I set up a straightforward automated rsnapshot system for myself. Basically I use two rsnapshot setups. One to backup important configuration and user files every three hours. Because rsnapshot uses rsync, the disk space requirements are nominal after the first few backups. I have two internal hard drives and I backup those important files to the second drive and to a different partition. The second part of my backup strategy requires a full backup to a hard drive I store in a small fire-proof safe. The second part is manual for me, but could be automated for a nominal cost.
1. Install on primary harddisk
2. mirror it on a secondary harddisk
3. use normal cp command to copy user files from primary hard disk to the secondary backup hardiisk
Only questions is, how to make the secondary harddisk bootable?
1. Install on primary harddisk
2. mirror it on a secondary harddisk
3. use normal cp command to copy user files from primary hard disk to the secondary backup hardiisk
Only questions is, how to make the secondary harddisk bootable?
Any suggestions/comments
Thanks
Jay
I can see this causing some problems down the road.
For starters, there is no redundant disk. If the primary disk goes bad, the system goes offline. Since you plan on mirroring a drive anyway, why not use RAID-1? It's easy to configure, always in sync, and easy to recover when a drive fails. (you can boot from either drive)
Both primary and secondary disks are connected to same machine. What if your disk controller goes bad and corrupts both disks? For this reason, you should backup the system configuration and other important directories to a different media or workstation. Like the others in this thread, I recommend a rsync-based solution. Tar is also a good option if you plan on burning backups.
For example, you could use the following command to rsync your data to a server named "failsafe" over ssh (pubkey auth):
rsync -av -e "ssh -i /path/to/private_key" /important/directory username@failsafe:/backups/
It might not be a bad idea to burn off some critical files for safe keeping elsewhere:
tar -cvzf /path/to/output.tar.gz /path/to/important/directory
Then burn the output file to a disc using whatever method you feel comfortable with.
Both of these tasks are easy to script and place on cron, which makes life easy.
System configuration is easy, as this is just a file server, so configuring it wont be a problem, once i have setup the system i can backup the conf files. Its the user data which is more important here. So i thought of the above procedure.
Regardless of what you are backing up, your methods mentioned above fall short in a few categories.
1. You will be wasting time and space with cp.
2. Your data will not be protected by physical separation.
3. Your data will not be protected by physical separation. (sic)
I like to keep important data in three different places. You may think I'm paranoid, but I don't like taking risks. Especially when my pay check is involved.
a. Primary server with RAID
b. Backup server
c. Offsite (tape/DVD)
Distribution: Ubuntu, Slackware, Gentoo, Fedora, Red Hat, Puppy Linux
Posts: 370
Rep:
Quote:
Originally Posted by granth
Regardless of what you are backing up, your methods mentioned above fall short in a few categories.
1. You will be wasting time and space with cp.
2. Your data will not be protected by physical separation.
3. Your data will not be protected by physical separation. (sic)
I like to keep important data in three different places. You may think I'm paranoid, but I don't like taking risks. Especially when my pay check is involved.
a. Primary server with RAID
b. Backup server
c. Offsite (tape/DVD)
These allow you to insert an OEM hard drive into the system, perform your back and remove the hard disk to a safe off-site location. With the cost of 500 GB SATA II hard drives now under $60 you can now backup instantly without having to fuss with DVD drives which may or may not write correctly and may get lost.
A single disk can be used to store files, tarballs or database backups.
Just a thought. We use these for daily backups to backup more than 250 GB of data and have no problems.
Last edited by AuroraCA; 12-22-2008 at 02:53 PM.
Reason: Clarification added
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.