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.
General backup solutions are a different sort of thing. Scan through http://www.linuxquestions.org/bookmarks/tags/backup, and you will find examples of both. Amanda is my choice for general network backup of multiple machines. If you're dealing with a smaller situation, you might want something different, say, rsnapshot or backuppc or . . .
It's surprising that Ubuntu does not come up with a decent backup and recovery tool -- probably the greatest shortcoming of Ubuntu at this time. I have successfully created system recovery discs with remastersys, but the software is flaky (limited to 4 gb) and sparsely documented.
Another option (which I have not yet installed) is bubakup.
Personally, I just use tar to back up my system, but that's probably not kind of solution you're looking for.
Quote:
Originally Posted by libssd
It's surprising that Ubuntu does not come up with a decent backup and recovery tool -- probably the greatest shortcoming of Ubuntu at this time. I have successfully created system recovery discs with remastersys, but the software is flaky (limited to 4 gb) and sparsely documented.
Another option (which I have not yet installed) is bubakup.
Thanks a lot guys!I can't imagine there are many replies from my question in such a short time!
choogendyk, thanks for your recommendation on partimage and Clonzilla.But isn't it that the system must be rebooted and boot from the cd/dvd to do the backup? I just want a software which will do the backup without booting from cd/dvd.
I mentioned Ubuntu only because I didn't have personal experience with Slackware, although the OP suggests that Slackware, like most (all?) Linux distros doesn't come with a pre-packaged backup solution. Backing up data is pretty straightforward, but restoring a trashed system from a recovery image is more challenging (and essential). Typical situation is, "Help! I just upgraded to XXX, and now my computer won't boot."
Choogendyk, thank you so much for the pointer to Clonezilla, which seems to be exactly what I've been looking for. Especially nice that their documentation consists of a video tutorial.
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Posts: 1,197
Rep:
Quote:
Originally Posted by Swift&Smart
choogendyk, thanks for your recommendation on partimage and Clonzilla.But isn't it that the system must be rebooted and boot from the cd/dvd to do the backup? I just want a software which will do the backup without booting from cd/dvd.
(a bit long and tutorial like, but hopefully useful and informative)
Although most sysadmins can't afford the downtime (or to be there in the middle of the night all the time) and don't follow the recommendation, the official line on backing up an OS is that you should at least take it down to single user to run backups. You'll find this in Sun's documentation for ufsdump, for example. The reason is that a running OS and running applications can have data in memory that hasn't been flushed to disk at the instant that the backup software wants to read that portion of disk. In itself that might not be an issue, but there may be different pieces of data at different points in time and position on the disk that end up not being backed up in a consistent way because of lack of coordination between the live OS, live applications, and the backup software. This is particularly an issue with database software like Oracle or MySQL, which have their own procedures for locking tables/transactions and dumping data.
When a backup runs over a lengthy period of time, the exposure to inconsistencies increases. The use of snapshots radically reduces (but does not eliminate) exposure to inconsistencies. Using LVM snapshots, or Solaris fssnap with ufsdump, or ZFS snapshots, can reduce the exposure to seconds. They make it feasible to shut down an application, take the snapshot, restart the application, and then backup the snapshot. This kind of procedure is routinely incorporated into backup software like Amanda. However, it's not foolproof. I've been doing this with Amanda for years. I don't often have to recover an OS. Usually, I'm recovering someone's lost or corrupted file. Of the times when I have had to recover an OS, I have had one that simply would not boot after the recovery. The backup seemed to be good, and the recovery went without any complaints, but the system would not boot. I did an update install over the top of the recovered system and it was alright. But that is the risk that is taken backing up live systems.
This problem with inconsistencies in an OS backup is one of the reasons for keeping multiple backups or using multiple methods of backup. For example, you might use something like clonzilla to backup the OS (and do it from a system booted off CD/DVD), and then run regular data backups using something else that runs off cron on the live system. If you need to recover the OS, do it from the clonzilla backup and then recover data files from the other backup system.
Another alternative that a lot of people have adopted is to simply backup partitions that will have data in them (e.g. /home, /var, /usr/local, and /etc), and don't bother with the OS. If there is a problem with the OS and it needs to be restored, just reinstall it and then recover the data partitions.
Whatever method is used, databases need particular attention. Look up specifics on the support sites for the particular database engine. Oracle has RMAN. MySQL has it's own methods - http://dev.mysql.com/doc/refman/5.0/...-recovery.html, and can have a completely integrated backup using ZRM for MySQL - http://www.zmanda.com/backup-mysql.html. Database backups can then be pushed to tape if desired by something like Amanda.
Bottom line is that while you might want to run backups of your data on a regular (daily) basis, something like clonzilla is intended for periodic use after a fresh install or a significant update. The inconvenience of taking the system down should be infrequent, but it should provide some level of confidence that the OS backup is consistent and good.
Thank you for the pointer to Bacula; it looks promising and well documented. No matter what I tried, I could not get Clonezilla to backup to the device of my choosing. Bubakup doesn't support grub2, and aa1backup (which is very small and elegant) doesn't support ext4.
Reading the Bacula docs, I especially appreciate this:
Quote:
The old bare metal recovery project is essentially dead. One of the main features of it was that it would build a recovery CD based on the kernel on your system. The problem was that every distribution has a different boot procedure and different scripts, and worse yet, the boot procedures and scripts change from one distribution to another. This meant that maintaining (keeping up with the changes) the rescue CD was too much work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.