Amanda-Users

Re: Problem: Failed backups overwrite good backups

2003-03-11 15:08:51
Subject: Re: Problem: Failed backups overwrite good backups
From: Jonathan Swaby <jfs10 AT bnext.stucen.gatech DOT edu>
To: amanda-users AT amanda DOT org
Date: Tue, 11 Mar 2003 13:31:17 -0500 (EST)
> 
> On Tue, Mar 11, 2003 at 09:15:10AM -0500, Jonathan Swaby wrote:
> >  
> >  I am using Amanda 2.4.3b3 on a Linux RH 7.2 box to dump several
> >  windows clients to disk. I discovered a problem yesterday with my
> >  process. I run all of the backup jobs from a script. Each backup is a
> >  full backup. When one job completes, the next job runs. This all works
> >  correctly if the backup server is able to access the machine. If it is
> >  not able to connect to the machine, prehaps the machine is off, the
> >  existing backup files are overwritten. Does anyone know of a way to
> >  prevent this from happening? If it fails, I want it to leave the
> >  existing backup files.
> 
> Others may have additional ideas, but what about not having a tape available
> and only backing up to the holding disk.  Then once (or thrice) a day
> run amdump to collect the held backups.  IIRC amdump only uses a tape if
> it first determines there are directories to flush.
I will look into this thanks.

My programming skills are not great, but the idea I have been toying
with is to use the output of amcheck to determine whether or not to
proceed with the backup. Now my backup script looks like this:
su -c "amdump machine1" operator
su -c "amdump machine2" operator

If I can figure out how to do what I want it might look lie this:

returncode = someprogram machine1
if (returcode==0)
  su -c "amdump machine1" operator

Ideally "someprogram" would take the output from amcheck and scan it for
errors or warnings like time-out and return value indicating whether
or not to proceed with the backup.  


> 
> >  The dumpcycles are set to 0 and the number of tapes is 1. I am just
> >  getting the system going, and I did not have a good feel for how much
> >  drive space was going to be consummed by the backups.
> >  
> >  If any one cares, this is how the system works.
> 
> It is amazing how flexible the amanda system can be.
> 
> The above arrangement (flush separately from dumps) might also let you
> have the users select a time to backup as your scheme "tried" to do.
> 
My users do not want the responsibility of having to backup their own
data. I guess more importantly, my boss suggested that I not give them
this responiblity.

Thanks 
Jonathan Swaby

>   [[ interesting scheme snipped ]]
> 
> jl
> -- 
> Jon H. LaBadie                  jon AT jgcomp DOT com
>  JG Computing
>  4455 Province Line Road        (609) 252-0159
>  Princeton, NJ  08540-4322      (609) 683-7220 (fax)
>