SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Originally posted by kemplej Anyone have good suggestions suggestions to use for a disaster recovery program for slackware servers (non xwindows)? I havent been able to find anything that would work on a command line.
Slackware 9.1's Disk 2 was a live CD that started you with BASH. I'm not sure what disk it is for Slack10.0, though, might be 2, maybe 3 or 4. But either way, that should be able to let you get yourself back on your feet.
I'm not sure how you are defining disaster recovery, because the key features of a carefully designed and well thought out disaster recovery plan will essentially be the same regardless of the OS. Additionally, the implied idea in your post that a disaster recovery effort could be launched from the command line is pretty confusing -- it's not exactly like typing in a couple of commands via the CLI will restore everything to its previous state if your data center has been affected by a disaster such as an earthquake, fire, or tornado.
Generally, a thorough disaster recovery plan involves making and retaining a set of system backups on a continual basis; designating an alternative location where the system can be restored to and run from should your primary site be unusable; a group of personnel with defined duties and roles who have been trained on what needs to be done to achieve a system recovery; a plan for acquiring, installing, and configuring all production hardware and software systems; a communication plan to notify your users, employees, and customers regarding the condition of your system, and many, many other things. Basically it would be way too much to attempt to cover in a few posts here at LQ.
Disaster recovery planning is a huge topic. I'd recommend doing a Google search on it, or to check Amazon for book suggestions about it. Good luck with it. -- J.W.
Sorry for the broad question. I meant a backup type program. I know I could just put my /etc dir on a cd or whatnot but I was kinda wondering if anyone had any suggestions on a program to make it easier.
Can't you tarball the directories that are important, and then have the files burnt onto CD's or DVD's, or even better yet, have a backup partition, so if you have to reformat your system, you can leave the backup files untouched and still on your hard drive?
Hey kemplej this program is non xwindows and wicked if you just want to backup the whole partition... I use it on my system as it only takes about 6 minutes to restore my whole about 2gb slackware partition (Which I keep on another backup partition)
rdiff-backup is a script, written in python(1) that backs up one directory to another. The target directory ends up a copy (mirror) of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves symlinks, special files, hardlinks, permissions, uid/gid ownership, and modification times.
rdiff-backup can also operate in a bandwidth efficient manner over a pipe, like rsync(1). Thus you can use ssh and rdiff-backup to securely back a hard drive up to a remote location, and only the differences will be transmitted. Using the default settings, rdiff-backup requires that the remote system accept ssh connections, and that rdiff-backup is installed in the user's PATH on the remote system. For information on other options, see the section on REMOTE OPERATION.