Create own bootable DVD
 

Hi,

I have installed a PIII - 733MHz as a Slackware server for my project in school. It's a database, ftp server with db4o that supports the data and all common files that are used in a java customer application. That's just some intro...

My question now: the whole application and server is developed for a social organisation and they don't have any financial resources for hiring a IT expert or whatever. But like all technologie a server can go down, and it's not my intention to go and fix that server everytime it fails. So I want to create a backup dvd (iso) that can be put in by a member of the organisation and when the system reboots, the entire system will be reloaded exactly the same configurations as it has now...

Is this possible? And if it is, is there any step by step tutorial? I'm not an expert in linux but also certainly not a beginner...

SO I don't want to create a bootable dvd consisting of multiple install-iso's but a bootable dvd with the entire configuartion of my system as it is now...

Thx in advance
GekkeGwuido

Have you tried here?

Only have heard of a full system backup into bootable dvd, from which you can reinstall.

You can backup your /etc dir, cause all settings are there. However, nobody will preserve all your other files (like executable ones) from deletion/corruption.

I'm going to take a look at it...

The /etc is not the most important dir. I need that one too off course, but all my db scripts, backupsn, cronjobs, ftp config etc are the ones that I want to reinstalled from scratch; and possible for someone who has never worked with linux...

The pair of programs mindi and mondo say that together they can make a bootable installable backup. I've messed with it a bit, but it didn't fit my needs, as it doesn't seem to be able to play well with dmraid. But, you might give it a try to see if it'll work in your situation. Install both of those programs and then run mondoarchive.

But you must understand that saving only config files won't let you to upgrade packages, because some of new packages could not work with old config files (deprecated functions, new storing paths, etc). What I mean is that restoring only config files without appropiate binaries does not give a guarantee to have a usable system.

And what would u suggest then to make an easy to use repair system for the server?

use dd and write whole data to disc (dvd or external hdd maybe)
when somebody breaks something, you will use same dd to overwrite
you can even create a script for a newbie user
./save_backup.sh
./load_backup.sh

But that is when your server starts up; so when it totally crashes, can't boot anymore, you first have to install slackware again and then restore your clone; or can it be done with a bootable dvd or cd?

With any media where dd is.

You can create live cd with your backup. And then use dd.
Or boot with slackware cd and then use dd to restore backup from another dvd or external hdd.

So basically dd the drive to a image file, and place that on a live CD with the appropriate script to write it back to the drive. You could also do this with something like partimage or G4U/G4L, but I guess that would take more technical knowledge than these users have.

But the part I don't understand here, if you just restore the server to the way it was when you installed it, they are going to lose any data they added to the database. Certainly that is going to be a problem, unless they back that up on the client side?

Finally...not to be too arrogant here, but once the server is setup correctly, there is very little chance that it is ever going to have a problem unless somebody is messing with it. This isn't Windows we are talking about here, were there are apparent random system crashes. The chances that an autonomous Linux server is ever going to have a problem that can't be fixed by a reboot is slim to none. I really wouldn't worry about it.

Lots of information; on your first paragraph, that's waht I'm doing now; I have created an image with dd and copied it into a folder which contains all files to make a bootable dvd... Just not tested it yet;

There will be made a backup every night, and the users have the possibility (read obligation) to copy that backup to a stick or an extrnal storage location; so they can restore there latest backup; all implemented through scripts and java; so that's not really a problem;


I know, I use linux and windows also, and I know the benefits and the "fame" of linux; but say never never; and I don't want to be called for every little problem; so I try to cover myself by creating a robuust system and easy-to-use repair methods...

I've managed to make a .iso file, but now it's way to big (6.7 Gb) to burn on a dvd. With dd I've created a .gz file that is approx 3.6 Gb... How can I burn this to a dvd? Or waht can i delete from the original slackware iso???

get slax frodo and copy your gz

Can I just download slax frodo iso and burn it together with my image to one dvd?

Did you try the automated scripts at http://www.linux-live.org? It will use aufs with lzma compression on the filesystem from which you boot. A compressed iso won’t do any good except for transporting isos from one computer another…

Use Isolinux to create a bootable dvd from SLAX Frodo and your gz file.

Thx all for your suggestions
It works!
For someone who has (or cill have) the same problem, what have I done?
* I mad a clean install of my slackware server with all the applications and my needs installed and running
* Then I made an entire copy (or clone) of my disk with
Off course u have to adapt the paths to your own system (the /home/backup is a second HD in the server used for backups)
* Then I burned the directory vacserver to a dvd with the program k3b (in the directory extra at your slackware dvd or cd)
* I made a live cd using Slax Frodo
* I booted with the live cd and gave in following commands
After all this the system starts up like a charm and most important with exactly the same settings as before...

Again, thx all for the help
GekkeGwuido

Glad to help. Osor suggestion was also good and maybe even better in some cases.