Re: How to configure Amanda for our backup strategy?

[Jon LaBadie]

On Mon, Oct 01, 2007 at 08:50:59AM -0500, [EMAIL PROTECTED] wrote:
> I'm setting up Amanda for the first time and would like to configure
> it for our existing backup strategy.  We want to do complete backups
> nightly during weekdays, i.e. Monday-Friday night.  Once a week, let's
> say Wednesday, we want to take one tape to an off-site vault and bring
> another tape back, meaning we'd be taking a tape out of the normal
> rotation and bringing another one back into the rotation.  We'd want
> to have a minimum of 4 tapes in rotation (3 here and 1 off-site),
> possibly a few more, but not a huge number of tapes.  All will be
> complete backups, no incrementals.
> 
> What parameters would work best in Amanda for doing this with a
> minimal need for manual "adjustments" during the week?  Is it possible
> to just take a tape out of the rotation for a week and give Amanda a
> different tape than it expects, or does a person have to tell Amanda
> they've done this each time they do it?
> 
> Thanks for any help or tips anyone might have!

Set your dumpcycle and runspercycle to 1.  That will do full dumps
each run.  Set your tapecycle to 1 or 2.  If set to 1, amanda will
use any available tape.  If set to 2 it will not reuse the most
recently used tape.  But all the others will be usable.  If the
tape it would prefer to use is off-site, it will use one of the
other available tapes.  You may get some messages about not being
able to use the tape it wants.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

How to configure Amanda for our backup strategy?

[DavidG]

I'm setting up Amanda for the first time and would like to configure
it for our existing backup strategy.  We want to do complete backups
nightly during weekdays, i.e. Monday-Friday night.  Once a week, let's
say Wednesday, we want to take one tape to an off-site vault and bring
another tape back, meaning we'd be taking a tape out of the normal
rotation and bringing another one back into the rotation.  We'd want
to have a minimum of 4 tapes in rotation (3 here and 1 off-site),
possibly a few more, but not a huge number of tapes.  All will be
complete backups, no incrementals.

What parameters would work best in Amanda for doing this with a
minimal need for manual "adjustments" during the week?  Is it possible
to just take a tape out of the rotation for a week and give Amanda a
different tape than it expects, or does a person have to tell Amanda
they've done this each time they do it?

Thanks for any help or tips anyone might have!

David

Re: trying another idea... the --without-ipv6 config option

[Jean-Louis Martineau]

Craig Dewick wrote:


On 01/10/2007, *Jean-Louis Martineau* <[EMAIL PROTECTED] 
> wrote:


The amdump log file show that one backup was done, the IPv6 problem is
fixed.


That is what I was thinking too.


>   yoda  /dev/dsk/c3t1d0s4  RESULTS MISSING
>   driver: FATAL infofile update failed (yoda,'/dev/dsk/c0t0d0s0')
The latest is a fatal error.
Are you sure the user can read/write to the infofile directory.
It is 'amgetconf ORBnet infofile'.


Yes the infofile directory is /var/adm/amanda/ORBnet and it's owned by 
'amanda' with group 'sys', and is set to 0755 permissions.


11 [EMAIL PROTECTED] #>
/var/adm/amanda/ORBnet/curinfo

13 [EMAIL PROTECTED] #> ls -sal /var/adm/amanda/ORBnet
total 1322
   0 -rw---   1 amanda   sys0 Sep 23 00:45 curinfo.dir
   0 -rw---   1 amanda   sys0 Sep 23 00:45 curinfo.pag
   2 drwxr-xr-x   5 amanda   sys  512 Sep 24 09:36 index

Reconfigure amanda on the server without the '--with-db' option.
Only the text db is working.

Jean-Louis

Re: trying another idea... the --without-ipv6 config option

[Craig Dewick]

On 01/10/2007, Jean-Louis Martineau <[EMAIL PROTECTED]> wrote:
>
> The amdump log file show that one backup was done, the IPv6 problem is
> fixed.


That is what I was thinking too.


> >   yoda  /dev/dsk/c3t1d0s4  RESULTS MISSING
> >   driver: FATAL infofile update failed (yoda,'/dev/dsk/c0t0d0s0')
> The latest is a fatal error.
> Are you sure the user can read/write to the infofile directory.
> It is 'amgetconf ORBnet infofile'.
>

Yes the infofile directory is /var/adm/amanda/ORBnet and it's owned by
'amanda' with group 'sys', and is set to 0755 permissions.

11 [EMAIL PROTECTED] #>
/var/adm/amanda/ORBnet/curinfo

13 [EMAIL PROTECTED] #> ls -sal /var/adm/amanda/ORBnet
total 1322
   2 drwxr-xr-x   4 amanda   sys 1024 Oct  1 00:47 .
   2 drwxr-xr-x   3 amanda   sys  512 Sep 15 18:35 ..
  62 -rw---   1 amanda   sys31578 Oct  1 00:47 amdump.1
 152 -rw---   1 amanda   sys77100 Sep 23 14:36 amdump.10
  62 -rw---   1 amanda   sys31557 Sep 30 00:47 amdump.2
  62 -rw---   1 amanda   sys31527 Sep 29 00:47 amdump.3
 150 -rw---   1 amanda   sys76659 Sep 28 14:49 amdump.4
 150 -rw---   1 amanda   sys76488 Sep 28 02:27 amdump.5
 150 -rw---   1 amanda   sys76523 Sep 27 02:27 amdump.6
 150 -rw---   1 amanda   sys76662 Sep 26 02:27 amdump.7
 150 -rw---   1 amanda   sys76799 Sep 25 02:28 amdump.8
 152 -rw---   1 amanda   sys76926 Sep 24 02:27 amdump.9
   0 -rw---   1 amanda   sys0 Sep 23 00:45 curinfo.dir
   0 -rw---   1 amanda   sys0 Sep 23 00:45 curinfo.pag
   2 drwxr-xr-x   5 amanda   sys  512 Sep 24 09:36 index
  10 -rw---   1 amanda   sys 5060 Sep 24 02:27 log.20070924.0
  10 -rw---   1 amanda   sys 5060 Sep 25 02:27 log.20070925.0
  10 -rw---   1 amanda   sys 5060 Sep 26 02:27 log.20070926.0
  10 -rw---   1 amanda   sys 5060 Sep 27 02:27 log.20070927.0
  10 -rw---   1 amanda   sys 5060 Sep 28 02:27 log.20070928.0
  12 -rw---   1 amanda   sys 5241 Sep 28 14:49 log.20070928.1
   4 -rw---   1 amanda   sys 1924 Sep 29 00:47 log.20070929.0
   4 -rw---   1 amanda   sys 1924 Sep 30 00:47 log.20070930.0
   4 -rw---   1 amanda   sys 1924 Oct  1 00:47 log.20071001.0
   2 drwx--   2 amanda   sys  512 Oct  1 00:47 oldlog

I'm concerned about the 'results missing' errors as well since all those
filesystems are valid and active on the respective client targets.

Craig.

-- 
Craig Dewick ([EMAIL PROTECTED]). http://lios.apana.org.au/~craig
RailZone Australia: http://www.railzone.org ([EMAIL PROTECTED])
The SunShack: http://www.sunshack.org ([EMAIL PROTECTED])
ClassicSaab: http://www.classicsaab.net ([EMAIL PROTECTED])

Re: trying another idea... the --without-ipv6 config option

[Jean-Louis Martineau]

The amdump log file show that one backup was done, the IPv6 problem is 
fixed.


Craig Dewick wrote:


Recompiling with the --without-ipv6 option didn't change anything 
unfortunately, and I noticed in the report email that all of the file 
systems targetted for backup are being reported as:


FAILURE AND STRANGE DUMP SUMMARY:
  jedi  /dev/dsk/c0t0d0s6  RESULTS MISSING

  yoda  /dev/dsk/c3t1d0s4  RESULTS MISSING
  driver: FATAL infofile update failed (yoda,'/dev/dsk/c0t0d0s0')

The latest is a fatal error.
Are you sure the user can read/write to the infofile directory.
It is 'amgetconf ORBnet infofile'.

Jean-Louis