On Tuesday 02 November 2004 16:12, Jerry Feldman wrote:

On Tuesday 02 November 2004 9:45 am, David Sexton wrote:

...

Hi I am running suse 9.1 and wish to come up with some type of backup system. How ever I don't know what I should backup. I was thinking that /home and /etc should be backed up. Can any one give me some suggestions on what to backup? I was thinking I could use yast they have a nice backup tool. to make tar files.

I would agree that /home is always a good one to backup. I only backup a few files from /etc since most are easily recreated via YaST. In general, backup strategies are based on how you use your system.

If you got the diskspace to make backups, then take a look at Storebackup.. (on SuSE Cd's)... IMHO... It's the best backup system around... Jerry

-- Jerry Feldman Partner Technology Access Center (contractor) (PTAC-MA) Hewlett-Packard Co. 550 King Street LKG2a-X2 Littleton, Ma. 01460 (978)506-5243

Jerry, On Tuesday 02 November 2004 07:32, Jerry Westrick wrote:

...

If you got the diskspace to make backups, then take a look at Storebackup.. (on SuSE Cd's)...

IMHO... It's the best backup system around...

That's good to know, since I've yet to find a Linux backup "solution" I like, having been quite spoiled by Retrospect on the Mac and Windows. However, this software seems a little pushy. I installed it yesterday when your message came through but did not immediately start working on it. This morning, I had my first failed status report on overnight cron jobs. It came from an invalid invocation of storeBackup. (That, or a valid invocation of an unconfigured setup.) To wit: -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- ... SCRIPT: logrotate, OK. SCRIPT: storebackup exited with RETURNCODE = 255. SCRIPT: output (stdout && stderr) follows no source directory specified! This program copies trees to another location. ... -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- The installation RPM creates a template configuration file which is not acceptable to use to run the program but which is used by the cron script ("/etc/cron.daily/storebackup") simply by virtue of being where it is, in "/etc/storebackup.d/". The cron script does not even discriminate files in that directory based on some kind of name pattern. It just assumes every file there is a well-formed storeBackup configuration file that should be used to run a daily backup.

Jerry

Randall Schulz

Jerry, On Wednesday 03 November 2004 08:13, Jerry Westrick wrote:

...

...

The installation RPM creates a template configuration file which is not acceptable to use to run the program but which is used by the cron script ("/etc/cron.daily/storebackup") simply by virtue of being where it is, in "/etc/storebackup.d/". The cron script does not even discriminate files in that directory based on some kind of name pattern. It just assumes every file there is a well-formed storeBackup configuration file that should be used to run a daily backup.

...

Jerry

Randall Schulz

Well it works over here... did you modify the file /etc/storebackup.d/storebackup.config ? there you need to define what should be back-up, to where and how many versions to keep...

Huh? What did I say? Did I say it didn't work? I said that simply installing it and leaving it as installed leads to the diagnostic from the cron job. I fully understand the situation, it's just that some users could perceive this as a problem (I'd call it a bug, at least in the packaging of the software). I figured it would be worthwhile to give other potential users of this software a heads-up that if they install this software and don't configure it before they go to bed that day, they'll wake up to an error report from cron.

Jerry

Randall Schulz