in/gzip" UNCOMPRESS_PATH="/bin/gzip"
>> planner: LPRCMD=UNDEF MAILER=UNDEF
>> planner: listed_incr_dir="/opt/amanda-3.3.0/var/amanda/gnutar-lists"
>> planner: defs: DEFAULT_SERVER="edgar" DEFAULT_CONFIG="charm"
>> planner:
On Mon, 3 Aug 2009, Dustin J. Mitchell wrote:
On Mon, Aug 3, 2009 at 10:36 AM, wrote:
However, one of the filesystems still failed to back up. Furthermore, it
used 3 different virtual tapes for this run, even though I set:
It looks like it only used one tape -- what makes you think it used
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
#x27;s now the server, and it's been backing up fine
> with just amandad in there. I just uncommented restarted inetd, but now I
> get the following:
>
> AMRECOVER Version 2.5.0p2. Contacting server on ns1.pil.net ...
> 220 ns1 AMANDA index server (2.5.0p2) ready.
> 200 Acce
I've restored amanda file systems in the past from tape using amrestore.
However, I switched from tapes to vtapes several months ago and am trying
to restore a file system.
According to the FAQs and posts I saw searching various archives, one
wants to use amrecover intead of amrestore for vtapes.
e used as the "prefix" for...what? Tape names? In the
wiki above, they show this example:
changerfile "/home/amanda/test/chg-disk-status"# status files prefix
But no example contents for that file.
> Also, chg-disk needs a "tapedev" which points to the root
I'm switching from a DLT backup system to a disk-based backup system with
occasional tapes for offsite backups. I followed the instructions at:
http://www.amanda.org/docs/howto-filedriver.html
and was able to get the first backup, but I seem confused about how to do
a "virtual tape" rotation.
Responding to my own post...is it possible that this dump taking place
over 2 different dates be an issue? Does it matter what date is in the
tapelist when you flush it?
If so, I could rename files or the folder...
On Fri, 15 Sep 2006 [EMAIL PROTECTED] wrote:
>
> I make a special amanda config
I make a special amanda config with a one tape tapelist to just dump this
one large filesystem on a remote network that didn't make the last backup
due to an interuption. After nearly 24 hours, it made it to the local
holding disk on the server, but had a tape error trying to get it to tape.
The
On Thu, 14 Sep 2006, Frank Smith wrote:
> Chan, Victor wrote:
> > To all,
> >
> > I've changed up to Amanda 2.5.1. For some reason, these three
> > parameters that used to work in Amanda.conf didn't work anymore.
> >
>
> What version were you usi
Is there a way to resume a level0 dump wheree it left off, rather than
starting all over again, in the even of a client reboot during the dump?
TIA,
James Smallacombe PlantageNet, Inc. CEO and Janitor
[EMAIL PROTECTED]
Sorry for all the whining...it turned out the "host down" was the same
reverse DNS problem that the other amanda client was returning, but since
the error message was totally different, it baffled. I hooked the server
back up to the old network and it worked fine.
2 more minor is
r/log/messages about amanda(d).
>
> Inetd doesn't normally log unless you start it with a debug option.
> In your case, since a debug file is created then inetd is working
> so you may not need to check further on that.
> Post the debug file on the client and maybe we can see at
On Wed, 13 Sep 2006, Frank Smith wrote:
> [EMAIL PROTECTED] wrote:
> > Replying to my own post (sorry, but I'm getting desperate here), I took
> > the advice of the FAQ-O-Matic and installed lsof and ran this command:
> >
> > su-2.05b# lsof -uamanda
> >
> > There was no output. Should there have
Replying to my own post (sorry, but I'm getting desperate here), I took
the advice of the FAQ-O-Matic and installed lsof and ran this command:
su-2.05b# lsof -uamanda
There was no output. Should there have been? Does this mean that amandad
is not running? This is what I have in my /etc/inetd.
On Wed, 13 Sep 2006, Toomas Aas wrote:
> [EMAIL PROTECTED] wrote:
>
> > The server is reporting that client down, so I checked and noticed that
> > the FBSD port for the amanda-client did not install amindexd or
> > amidxtaped, although it did install amandad. Are all 3 needed for a
> > client?
>
Hi:
I've been using amanda for years, but I just reconfigured and updated some
servers using the latest everything and updated the disklists for the
newer format (integer/spindle).
>From FreeBSD ports, I just installed amanda-2.4.5 on the amanda server and
amanda-2.5.0p2 on the client (the ports
On Wed, 21 Jun 2006, Jon LaBadie wrote:
> On Wed, Jun 21, 2006 at 08:23:57AM -0400, Joshua Baker-LePain wrote:
> > On Tue, 20 Jun 2006 at 10:59pm, [EMAIL PROTECTED] wrote
> >
> > >Here's the complete report, now that it finally finished:
> > >
> > >su-2.05a$ amtapetype -f /dev/nrsa0
> > >Writing 2
On Tue, 20 Jun 2006, Joshua Baker-LePain wrote:
> On Tue, 20 Jun 2006 at 4:27pm, [EMAIL PROTECTED] wrote
>
> > On Tue, 20 Jun 2006, Joshua Baker-LePain wrote:
> >>
> >> I'd start by using amtapetype to test your new drive, both for hardware
> >> compression and native speed. I'd also look at addi
curious is this:
>
> Yes, it would affect all the clients. All the (already) compressed data
> going to tape would be hardware "compressed" by the drive, making it
> expand and take up more tape space. Therefore, even though amanda only
> saw ~25GB go to tape, on tape it took up
On Mon, 19 Jun 2006, Joshua Baker-LePain wrote:
> On Mon, 19 Jun 2006 at 6:45pm, [EMAIL PROTECTED] wrote
>
> > taper: tape FULL0 kb 24499968 fm 9 writing file: short write
> >
> *snip*
> >
> > define tapetype DLT7000 {
> >
> >comment "DEC/Quantum DLT7000 tape drive, hardware compression turne
Hi:
It's been many years since I needed help with Amanda, but I'm stuck on
this one. I've had a client+server and a client only box set up for
years, backing up no problem (running amanda-2.4.4). I switched from a
DLT4000 to a DLT7000 several months ago, as the former was we
22 matches
Mail list logo