Amanda-Users

"preventing dump on (host) as directed"??

2009-08-03 11:55:40
Subject: "preventing dump on (host) as directed"??
From: up AT 3 DOT am
To: amanda-users AT amanda DOT org
Date: Mon, 3 Aug 2009 10:36:56 -0400 (EDT)

Hi:

I have amanda 2.5.1p3 running on a server and amanda 2.6.1p1 on the client in this case. I set up 3 "virtual tapes" on disk with a 3 week "dumpcycle" and a 3 tape "tapecycle". I then saw somewhere that you should have one more tape in your tapecycle than in your dumpcycle, so I added one.

I am doing level 0 full backups only, but not yet on a regular basis for these hosts. Because I had a failure the first time, I added this to my amanda.conf:

usetimestamps   yes     # allow more than one run per day

However, one of the filesystems still failed to back up. Furthermore, it used 3 different virtual tapes for this run, even though I set:

runtapes 1            # number of tapes to be used in a single run

Here was the report:

These dumps were to tape NS3_4.
The next tape Amanda expects to use is: NS3_1.

FAILURE AND STRANGE DUMP SUMMARY:
  ns3.pil.net  /dev/mirror/gm0s1g  lev 0  FAILED [dump to tape failed]


STATISTICS:
                          Total       Full      Incr.
                        --------   --------   --------
Estimate Time (hrs:min)    0:02
Run Time (hrs:min)         1:20
Dump Time (hrs:min)        1:12       1:12       0:00
Output Size (meg)        1830.7     1830.7        0.0
Original Size (meg)      4943.6     4943.6        0.0
Avg Compressed Size (%)    37.0       37.0        --
Filesystems Dumped            3          3          0
Avg Dump Rate (k/s)       436.8      436.8        --

Tape Time (hrs:min)        1:18       1:18       0:00
Tape Size (meg)          1830.7     1830.7        0.0
Tape Used (%)               3.1        3.1        0.0
Filesystems Taped             5          5          0

Chunks Taped                  0          0          0
Avg Tp Write Rate (k/s)   402.7      402.7        --

USAGE BY TAPE:
  Label       Time      Size      %    Nb    Nc
  NS3_4       1:18  1874624k    3.1     5     0

NOTES:
  planner: tapecycle (4) <= runspercycle (21)
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1a on tape NS3_0 overwritten in 4 runs. planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1g on tape NS3_3 overwritten in 2 runs.
  planner: Preventing bump of ns3.pil.net:/dev/mirror/gm0s1g as directed.
planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1e on tape NS3_0 overwritten in 4 runs. planner: Last full dump of ns3.pil.net:/dev/mirror/gm0s1f on tape NS3_2 overwritten in 3 runs. driver: ns3.pil.net /dev/mirror/gm0s1g 0 [dump to tape failed, will try again]
  taper: tape NS3_4 kb 1874720 fm 5 [OK]


DUMP SUMMARY:
DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS KB/s -------------------------- ------------------------------------- ------------- ns3.pil.net -ror/gm0s1a 0 2478757 923072 37.2 34:31 445.7 34:32 445.5 ns3.pil.net -ror/gm0s1e 0 2436963 907008 37.2 35:06 430.7 35:07 430.5 ns3.pil.net -ror/gm0s1f 0 146506 44544 30.4 1:55 388.1 1:56 385.2 ns3.pil.net -ror/gm0s1g 0 FAILED --------------------------------------------

(brought to you by Amanda version 2.5.1p3)
---------------------

What's the best way to straighten out this mess, and have each backup dump to one tape and back up everything?

Thanks,

James Smallacombe                     PlantageNet, Inc. CEO and Janitor
up AT 3 DOT am                                                      http://3.am
=========================================================================

<Prev in Thread] Current Thread [Next in Thread>