ome LAN -- I have 6 ARM SBCs that I want to make automated daily
> > >> backups of. I have used Amanda in the past, but Amanda is now
> > >> broken, so I need to find a replacement.
> > >
> > > I have heard good things about bacula. It is available for Debia
;> home LAN -- I have 6 ARM SBCs that I want to make automated daily
> >> backups of. I have used Amanda in the past, but Amanda is now
> >> broken, so I need to find a replacement.
> >
> > I have heard good things about bacula. It is available for Debian 12
>
Am 05.08.24 um 20:01 schrieb Charles Curley:
On Mon, 5 Aug 2024 11:04:59 -0400 (EDT)
Robert Heller wrote:
I *need* an automated network-based backup system, at least for my
home LAN -- I have 6 ARM SBCs that I want to make automated daily
backups of. I have used Amanda in the past, but
On Mon, 5 Aug 2024 11:04:59 -0400 (EDT)
Robert Heller wrote:
> I *need* an automated network-based backup system, at least for my
> home LAN -- I have 6 ARM SBCs that I want to make automated daily
> backups of. I have used Amanda in the past, but Amanda is now
> broken, so I ne
The original debs were build *without* the man pages due to a missing build
dep. I have rebuild the arm64 deps and I will rebuild the amd64 tonight.
At Sat, 3 Aug 2024 20:35:56 -0400 (EDT) Robert Heller
wrote:
>
> Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-De
Amanda 3.5 no longer works -- its support for Amazon S3 is non-functional.
Amanda 3.3.3 won't build with Debian 12 without major rewriting. Amanda 3.3.3
does properly support Amazon S3, at least on older operating systems (eg
CentOS 7 -- now EOL).
I *need* an automated network-based b
eally expect it to work ...
> >
> > The community edition simply seems to be neglected for years now.
> >
> > Sad, but true.
> >
> > I have issues on github that are many years open and unresolved, 52 open
> > issues right now. They simply don't care
At Mon, 5 Aug 2024 07:43:14 +0200 li...@xunil.at wrote:
>
> Am 04.08.24 um 18:51 schrieb Robert Heller:
> > Amazon S3 still does not work :-(
>
> I didn't really expect it to work ...
>
> The community edition simply seems to be neglected for years now.
>
> Sad, but true.
>
> I have issues
Am 04.08.24 um 18:51 schrieb Robert Heller:
Amazon S3 still does not work :-(
I didn't really expect it to work ...
The community edition simply seems to be neglected for years now.
Sad, but true.
I have issues on github that are many years open and unresolved, 52 open
issues right now. The
Amazon S3 still does not work :-(
At Sun, 4 Aug 2024 18:09:12 +0200 sgw wrote:
>
> Am 04.08.24 um 02:35 schrieb Robert Heller:
> > Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/
> >
> > Amanda 3.5.4 built for Debian 12 (bookworm) for
Has *anyone* managed to *successfully* use Amanda 3.5.4 with a Amazon S3 based
tape changer?
It is still not working.
I am thinking of getting the sources for Amanda 3.3.3 (which does work with
Amazon S3 based tape changers -- I had it working just fine with CentOS 7).
The error in the
Am 04.08.24 um 02:35 schrieb Robert Heller:
Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/
Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64
(aarch64)
Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed
(qemu-system-x86_64) on
Files available at http://files.deepsoft.com/Other/Amanda-3.5.4-Debian12/
Amanda 3.5.4 built for Debian 12 (bookworm) for amd64 (x86_64) and arm64
(aarch64)
Built using a x86_64 vm with a vanila Debian 12 (bookworm) installed
(qemu-system-x86_64) on a Rpi 5 host, running Debian 12 (bookworm
On 2/14/24 15:33, Winston Sorfleet wrote:
Glad to see you're still alive and kicking Gene. While hardly
Amanda-specific, given you're likely to be doing a lot more writes
(backups) than reads (restores), you probably want to give some thought
your file system choice (I'd think
Glad to see you're still alive and kicking Gene. While hardly
Amanda-specific, given you're likely to be doing a lot more writes
(backups) than reads (restores), you probably want to give some thought
your file system choice (I'd think XFS maybe) and operating parameters
accor
Greetings All;
Due to the simultainious failure of a pair of 2T seacrates, spinning
rust, which p'd me off so bad there is now only one spinning rust drive
left here at the Heskett Ranchete's 8 or 9 machine network.
So I've been out of the amanda users category for a couple ye
Jose,
Indeed I would be interested! Certainly worth a try.
Thanks,
Lou
On 2023-07-25 9:34 a.m., Jose M Calhariz wrote:
Hi,
If I understand well your problem I found it in 3.5.1 and I have a
patch that fix it, from the previous owner of amanda. The patch is
the machine was powered up and responsive but actively refused the
connection for some reason.
I'm puzzled by another thing: we're using the same version of
amanda (3.5.3) and I run backups to disk, no tape drive involved, but
I've never seen the error you mention in Apri
Hi Lou,
I'm using the same version as you, although in Fedora 37
amanda-3.5.3-1.fc37.x86_64 and I don't see that behaviour, I have some
machines that are down and the rest of the backups were made.
In my case I have this
planner: ERROR Request to MACHINE failed: Connection refu
Folks,
I've been using amanda for several years on a simple home network.
Hosts are often powered down. Up through amanda 3.5.2, this worked like
a charm. If the host didn't respond, it was simply skipped. Hosts that
responded were properly backed up.
With amanda
At Sat, 10 Jun 2023 08:25:45 -0600 Orion Poplawski wrote:
>
> On 6/10/23 06:13, Robert Heller wrote:
> > At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf
> > wrote:
> >
> >>
> >> ÃÂïÃÂûÃÂÿTime Machine is built into current Mac OSes. It
> >> wants its own disk, which should be a b
On 6/10/23 06:13, Robert Heller wrote:
At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf wrote:
Time Machine is built into current Mac OSes. It wants its own disk, which
should be a bit (or a lot) bigger than the one you are backing up. I
don’t think it can backup to another machine
At Fri, 9 Jun 2023 23:35:23 -0400 Deb Baddorf wrote:
>
> Time Machine is built into current Mac OSes. It wants its own disk,
> which should be a bit (or a lot) bigger than the one you are backing up. I
> donâÂÂt think it can backup to another machine. It works well, since
> itâÂÂ
Time Machine is built into current Mac OSes. It wants its own disk, which
should be a bit (or a lot) bigger than the one you are backing up. I don’t
think it can backup to another machine. It works well, since it’s baked in.
Deb
> On Jun 8, 2023, at 10:36 PM, Robert Heller wrote:
> I know
On 6/9/23 00:51, Hauke Fath wrote:
On Thu, 8 Jun 2023 20:57:38 -0400 (EDT), Robert Heller wrote:
I know nothing about "Time Machine". Will it backup to a Linux machine?
We use Time Machine at work to back up Macs to a Samba share, so yes.
It is user-operable, and you can restore from the re
At Thu, 8 Jun 2023 21:31:50 -0600 Charles Curley
wrote:
>
> On Thu, 8 Jun 2023 20:57:38 -0400 (EDT)
> Robert Heller wrote:
>
> > I know nothing about "Time Machine". Will it backup to a Linux
> > machine?
>
> Yes. You need Apple networking so the Linux machine will fake a Mac. On
> Debi
On Thu, 8 Jun 2023 21:31:50 -0600
Charles Curley wrote:
> However, if you encrypt the backup, the files on the Linux machine are
> opaque, meaning you can't extract a file on the Linux machine. I have
> not experimented with an unencrypted backup.
Or maybe not. Take a look at the Debian package
On Thu, 8 Jun 2023 20:57:38 -0400 (EDT), Robert Heller wrote:
> I know nothing about "Time Machine". Will it backup to a Linux machine?
We use Time Machine at work to back up Macs to a Samba share, so yes.
It is user-operable, and you can restore from the rescue system for
desaster recovery.
On Thu, 8 Jun 2023 20:57:38 -0400 (EDT)
Robert Heller wrote:
> I know nothing about "Time Machine". Will it backup to a Linux
> machine?
Yes. You need Apple networking so the Linux machine will fake a Mac. On
Debian, that would be the netatalk package. That also pulls in avahi
(bonjour impleme
I know nothing about "Time Machine". Will it backup to a Linux machine?
At Thu, 8 Jun 2023 17:39:47 -0600 Orion Poplawski wrote:
>
> On 6/8/23 09:50, Robert Heller wrote:
> >
> > Already doing that.
> >
> > I'm beginning to think that I need to find some other way of backing up this
> >
On 6/8/23 09:50, Robert Heller wrote:
>
> Already doing that.
>
> I'm beginning to think that I need to find some other way of backing up this
> machine, or maybe just not back it up at all (it is just a build box and has
> nothing on it that is not available either elsewhere on my LAN (eg th
+' in Full Disk Access,
type 'Command' + 'Shift' + '.' (simultaneously) then navigate to the root of
your filesystem containing /opt and from there you can get to the gtar
application and add it to applications allowed Full Disk Access.
Backing up Macs as par
-0600 Pieter Bowman
> > wrote:
> > >
> > >>
> > >> Unfortunately, I have retired, so don't have access to systems running
> > >> amanda on macOS/MacOSX.
> > >>
> > >> However, I can suggest that the problem you are se
AM, Robert Heller wrote:
> >
> >
> > It already is there.
> >
> > At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman
> > wrote:
> >
> >>
> >> Unfortunately, I have retired, so don't have access to systems running
> >> aman
>>
>> Unfortunately, I have retired, so don't have access to systems running
>> amanda on macOS/MacOSX.
>>
>> However, I can suggest that the problem you are seeing is because of
>> System Integrity Protection (SIP). You will need to add the executable
It already is there.
At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman wrote:
>
> Unfortunately, I have retired, so don't have access to systems running
> amanda on macOS/MacOSX.
>
> However, I can suggest that the problem you are seeing is because of
> System In
-- resend as i forgot reply all --
Those errors seem like normal permission errors, if you su to amanda can you
access those files?
If not i think you need to edit amanda-security.conf and uncomment some of the
tar lines so tar runs as root with access to the files you want to backup.
Anton
-- resend as i forgot reply all --
Oh also check that the relevant executables have SGID bit set and correct users
(user root, group amanda). Mine is under /usr/lib/amanda/application/amgtar but
probably different location for you.
I have SGID set for amgtar ambsdtar amstar in that directory
Is there some "trick" to getting Amanda (3.5.1) to run properly under MacOSX
10.15? I recently added a new (to me) machine to my LAN and want to be able
to take regular backups of it. I is an older model MacBook Pro (mid 2012
vintage), running Amanda (3.5.1) to run properly under Ma
The empty man pages is because someone forgot to build the man pages when
making the rest of the package.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2023-04-28 15:44, Nuno Dias wrote:
Hi,
After upgrading amanda from amanda-3.5.1 to amanda-3.5.3 using the rpm
from Fedora, I h
Hi,
After upgrading amanda from amanda-3.5.1 to amanda-3.5.3 using the rpm
from Fedora, I have this 2 problems, every man page of amanda is empty
for example ...
-
$ man amanda.conf
DUMMY
Manual page amanda.conf(5) line 1/2 (END) (press h for help or q to
quit)
--
The
On 23.03.2023 14:47, Charles Curley wrote:
# property "CHECK-DEVICE" "YES"
If you have DLEs on external (USB) drives I strongly recommend to set
this to "NO".
The property translates to the --check-device option of tar (on by
default) what makes tar consider the device number when creati
Nathan Stratton Treadway writes:
> I have had Amanda running for over a decade, yesterday I had no issue at
> all but last night, my backups for Ubuntu machines started crashing
> consistently with the error:
> strange(?): runtar: error [runtar invalid option: -]
>
> The ju
On Thu, 23 Mar 2023 13:02:33 +0700
Olivier wrote:
> I have had Amanda running for over a decade,
I have also been running Amanda for a long time. When I implemented the
proposed work-around, I found I had no definition of amgtar.
Is there a preferred canonical (no wordplay intended) definit
On Thu, Mar 23, 2023 at 2:07 AM Olivier wrote:
> Hello,
>
> I have had Amanda running for over a decade, yesterday I had no issue at
> all but last night, my backups for Ubuntu machines started crashing
> consistently with the error:
> strange(?): runtar: error [runtar invalid
Hello,
I have had Amanda running for over a decade, yesterday I had no issue at
all but last night, my backups for Ubuntu machines started crashing
consistently with the error:
strange(?): runtar: error [runtar invalid option: -]
That even happens on a machine that is currently unused.
The
On March 12, I moved the home of the mailing lists (behind the
scenes) and messed up one of the steps, so mail in past few days to the
amanda lists ended up being silently blackholed. I've corrected this
and adjusted my procedures so it won't happen again and it this or other
problem
Am 22.01.23 um 09:25 schrieb Stefan G. Weichinger:
Just in case this hasn't yet been noticed by anyone upstream:
https://github.com/MaherAzzouzi/CVE-2022-37704
https://github.com/MaherAzzouzi/CVE-2022-37705
https://github.com/zmanda/amanda/issues/192
PRs on their way, as it seems:
Just in case this hasn't yet been noticed by anyone upstream:
https://github.com/MaherAzzouzi/CVE-2022-37704
https://github.com/MaherAzzouzi/CVE-2022-37705
https://github.com/zmanda/amanda/issues/192
ators at
your site
dumpcycle 1week # the number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7 # the number of amdump runs in dumpcycle days
define changer my_vtapes {
tpchanger "chg-disk:/backups/amanda/vtape/diarios/moni
t set up a small holding disk?
I understand the intention to make it work without but I don't see the
advantage of doing so.
Amanda is designed to use a holding disk, it's just recommended and best
practice ;-)
18.01.23 um 01:47 schrieb Pablo Venini:
Hi Stefan, sorry for the delay in answering. This is a backup of the
amanda server itself (configs, etc.), there is less than 100MB of
information. What worries me is that if I use a holding disk without
correcting the problem the dumps will go there instead of
e number of days in the normal dump cycle
tapecycle 8 # the number of tapes in rotation
runspercycle 7 # the number of amdump runs in dumpcycle days
define changer my_vtapes {
tpchanger "chg-disk:/backups/amanda/vtape/diarios/monitoreo10_diario/"
property "num-s
Am 18.01.23 um 01:47 schrieb Pablo Venini:
Hi Stefan, sorry for the delay in answering. This is a backup of the
amanda server itself (configs, etc.), there is less than 100MB of
information. What worries me is that if I use a holding disk without
correcting the problem the dumps will go there
Am 18.01.23 um 01:43 schrieb Pablo Venini:
Hi Nathan, do you know if there is any setting to cause amanda to be
more verbose?
Another weird thing is that the report says:
NOTES:
planner: tapecycle (7) <= runspercycle (7)
However the config is like this:
tapecycle 8 # the number
Hi Stefan, sorry for the delay in answering. This is a backup of the
amanda server itself (configs, etc.), there is less than 100MB of
information. What worries me is that if I use a holding disk without
correcting the problem the dumps will go there instead of going to the
vtapes.
Pablo
Hi Nathan, do you know if there is any setting to cause amanda to be
more verbose?
Another weird thing is that the report says:
NOTES:
planner: tapecycle (7) <= runspercycle (7)
However the config is like this:
tapecycle 8 # the number of tapes in rotation
runspercycle 7 #
On Fri, Dec 30, 2022 at 11:34:14 -0300, Pablo Venini wrote:
> amcheck doesn't report errors
Hmmm.
As Stefan said, the key question is why Amanda is going into degraded
mode. Normally when I have that happen it's because the target tape
wasn't available at the start of the am
Hi,
On 05-01-2023 12:06, Stefan G. Weichinger wrote:
* your tapetype defines a tape with 5 GB
Would your DLEs each fit onto one vtape?
I think you should use a larger vtape ... and make sure that the full
backup of each DLE fits onto one vtape.
Please note the length of vtapes is only used
Am 30.12.22 um 15:34 schrieb Pablo Venini:
Hi Nathan,
no, (as far as I'm aware) I'm not using a holding
disk as this is a vtape backup, the dumptype is as follows:
You could fix that by defining and using a holding disk.
Then a "degraded mode backup" should work.
The qu
st
encrypt client
client_encrypt "/usr/sbin/amcryptsimple"
}
amcheck doesn't report errors
amcheck monitoreo10_diario
Amanda Tape Server Host Check
-
slot 1: volume 'monitoreo10_diario-1' is still active and cannot be
overwritten
slot 2
On Thu, Dec 29, 2022 at 17:17:56 -0300, Pablo Venini wrote:
> Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
> with vtapes. I've setup the vtapes directories, created the job and
> added the dlc, checked permissions, then run amcheck and it shows no
>
Hi, I'm setting up a new backup server with amanda 3.5.2 on CentOS 7
with vtapes. I've setup the vtapes directories, created the job and
added the dlc, checked permissions, then run amcheck and it shows no
errors. However when I run amdump, only one of the dlc gets backed up,
the
On 9/30/22 02:32, Stefan G. Weichinger wrote:
Am 29.09.22 um 02:03 schrieb Nathan Stratton Treadway:
On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:
On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
I received:
"Your message to chris.hass...@betsol.co
Am 29.09.22 um 02:03 schrieb Nathan Stratton Treadway:
On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:
On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
I received:
"Your message to chris.hass...@betsol.com couldn't be delivered.
Chris.Hassell wasn't
On Tue, Sep 13, 2022 at 16:11:15 -0400, Nathan Stratton Treadway wrote:
> On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
> > I received:
> >
> > "Your message to chris.hass...@betsol.com couldn't be delivered.
> >
> > Chris.Hassell wasn't found at betsol.com."
>
> (I just tr
ed 3d printer.
Gene, I don't know where you get port 5000. According to /etc/services,
IANA has assigned amanda ports 10080-10083 inclusive. And amanda uses
those only if you don't run amanda over ssh.
root@hawk:~# grep amanda /etc/services
amanda 10080/tcp
't know where you get port 5000. According to /etc/services,
IANA has assigned amanda ports 10080-10083 inclusive. And amanda uses
those only if you don't run amanda over ssh.
root@hawk:~# grep amanda /etc/services
amanda 10080/tcp # amanda backup service
inter.
I expect its changeable, and I've done it to Octoprint just for test,
works fine. But is that a potential
problem if octoprint is sitting idle on a client at the time amanda
gets fired up? Something to check
out I think, Stefan. Thanks.
Where do you see that port 5000?
Not w
done it to Octoprint just for test,
works fine. But is that a potential
problem if octoprint is sitting idle on a client at the time amanda gets
fired up? Something to check
out I think, Stefan. Thanks.
Where do you see that port 5000?
I grep through the sources and I am not sure ...
my install
Am 16.09.22 um 16:55 schrieb gene heskett:
On 9/16/22 07:28, Stefan G. Weichinger wrote:
I might rebuild later if needed, just wanted to share asap. Right now
I am quite busy with X things.
.
I agree, Wayland in place of X needs all the help it can get.
I didn't mean X11 ;-) .. wanted to s
vant error:
automake: error: cannot open < config/amanda/file-list: No such file
or directory
autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '
vant error:
automake: error: cannot open < config/amanda/file-list: No such file
or directory
autoreconf: automake failed with exit status: 1
find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path
'*/.hg/*' -o -path '*/.bzr/*' -o -path '
Am 02.08.22 um 17:26 schrieb Jose M Calhariz:
I am not doing progress in solving the autotools problems.
I copied debian directory from official Debian 3.5.1, refresh patches,
and "debuild". I fails with alot of warnings and this relevant error:
automake: error: cannot open <
On 9/15/22 03:08, Diego Zuccato wrote:
Il 14/09/2022 19:00, gene heskett ha scritto:
Waiting for 2T SSD's to become affordable, if they ever do.Depends on
your definition of "affordable".
I bought 2 2TB NVMes at about 300€ each... But SSDs and NVMes have a
quite "limited" life. Look at TBW n
Il 14/09/2022 19:00, gene heskett ha scritto:
Waiting for 2T SSD's to become affordable, if they ever do.Depends on your definition of
"affordable".
I bought 2 2TB NVMes at about 300€ each... But SSDs and NVMes have a
quite "limited" life. Look at TBW numbers. Many SSDs and NVMes have some
lable packages from them.
.
That hasn't happened in a mailing list like time frame yet, typically a
month or so.
That says amanda is nowhere near the front burner at Betsol. As an
amanda user since
about the late 1998 time frame, I lament the day that the University of
Maryland sold it
all those
On Wed, Sep 14, 2022 at 13:32:08 +0200, Stefan G. Weichinger wrote:
> Am 13.09.22 um 22:11 schrieb Nathan Stratton Treadway:
>
> >(I just tried sending email to this email address. My message was
> >accepted for delivery by the Betsol mail server, and I haven't received
> >any bounce message back
Am 13.09.22 um 22:11 schrieb Nathan Stratton Treadway:
(I just tried sending email to this email address. My message was
accepted for delivery by the Betsol mail server, and I haven't received
any bounce message back [after waiting a few minutes]. So hopefully the
bounce you saw was just a tem
On Tue, Sep 13, 2022 at 17:29:41 +0200, Stefan G. Weichinger wrote:
> I received:
>
> "Your message to chris.hass...@betsol.com couldn't be delivered.
>
> Chris.Hassell wasn't found at betsol.com."
(I just tried sending email to this email address. My message was
accepted for delivery by the Be
Am 13.09.22 um 14:14 schrieb Stefan G. Weichinger:
@Chris ... any news? Could you pls provide packages, for example for
Debian 11.x ?
thanks
I received:
"Your message to chris.hass...@betsol.com couldn't be delivered.
Chris.Hassell wasn't found at betsol.com."
Am 24.08.22 um 14:10 schrieb Stefan G. Weichinger:
Am 02.08.22 um 20:31 schrieb Nathan Stratton Treadway:
On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:
And where do I get the debian approved versions of 3.5.2?
That's what Jose is attempting to create now... (So watch this thread
Am 02.08.22 um 20:31 schrieb Nathan Stratton Treadway:
On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:
And where do I get the debian approved versions of 3.5.2?
That's what Jose is attempting to create now... (So watch this thread
for news.)
We are :-)
Tried another build in my
On Tue, Aug 02, 2022 at 12:30:07 -0400, gene heskett wrote:
> And where do I get the debian approved versions of 3.5.2?
That's what Jose is attempting to create now... (So watch this thread
for news.)
Nathan
--
tester.
Me too, but its been a while and this is a fairly fresh bullseye
install, and autogen
complains mightily, and quickly.
gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
* gettext macros
* gnulib
* libtool files
..creating file
eryone,
> > > >
> > > > We at Zmanda are pleased to announce the 3.5.2 release of Amanda
> > > > Community.
> > >
> > > Nice to hear ...
> > >
> > > anyone touched that yet?
> > >
> > > Looking forward to t
, count me in as a beta tester.
> > > >
> > >
> > > Me too, but its been a while and this is a fairly fresh bullseye
> > > install, and autogen
> > > complains mightily, and quickly.
> > >
> > > gene@coyote:~/src/amanda-tag-community-3.5.2$ ./auto
mightily, and quickly.
gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for instructions on updating:
* gettext macros
* gnulib
* libtool files
..creating file lists
..aclocal
config/amanda/libs.m4:160: warning: macro 'AM_PATH_GLIB_2_0' not found
in library
Am 02.08.22 um 10:06 schrieb Stefan G. Weichinger:
pressing SEND now, my build is still running
hitting https://github.com/zmanda/amanda/issues/184
Am 02.08.22 um 09:44 schrieb gene heskett:
On 8/2/22 01:40, Winston Sorfleet wrote:
Much appreciated José, count me in as a beta tester.
Me too, but its been a while and this is a fairly fresh bullseye
install, and autogen
complains mightily, and quickly.
gene@coyote:~/src/amanda-tag
Am 29.07.22 um 04:11 schrieb Pavan Raj:
Hello Everyone,
We at Zmanda are pleased to announce the 3.5.2 release of Amanda Community.
URL: http://www.amanda.org/download.php
<http://www.amanda.org/download.php>
https://www.zmanda.com/downloads/
lists packages for Debian-9.9 (for e
On 8/2/22 01:40, Winston Sorfleet wrote:
Much appreciated José, count me in as a beta tester.
Me too, but its been a while and this is a fairly fresh bullseye
install, and autogen
complains mightily, and quickly.
gene@coyote:~/src/amanda-tag-community-3.5.2$ ./autogen
See DEVELOPING for
,
We at Zmanda are pleased to announce the 3.5.2 release of Amanda
Community.
Nice to hear ...
anyone touched that yet?
Looking forward to that release packaged for Debian (most of my
amanda-servers run Debian Linux).
Give me sometime to prepare non oficial Debian source packages for
Debian 11
On Mon, Aug 01, 2022 at 06:50:15PM +0100, Jose M Calhariz wrote:
> On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:
> > Am 29.07.22 um 04:11 schrieb Pavan Raj:
> > > Hello Everyone,
> > >
> > > We at Zmanda are pleased to announce the 3.5
On Mon, Aug 01, 2022 at 10:55:40AM +0200, Stefan G. Weichinger wrote:
> Am 29.07.22 um 04:11 schrieb Pavan Raj:
> > Hello Everyone,
> >
> > We at Zmanda are pleased to announce the 3.5.2 release of Amanda
> > Community.
>
> Nice to hear ...
>
> anyone to
Am 29.07.22 um 04:11 schrieb Pavan Raj:
Hello Everyone,
We at Zmanda are pleased to announce the 3.5.2 release of Amanda
Community.
Nice to hear ...
anyone touched that yet?
Looking forward to that release packaged for Debian (most of my
amanda-servers run Debian Linux).
On gentoo I am
Hello Everyone,
We at Zmanda are pleased to announce the 3.5.2 release of Amanda Community.
URL: http://www.amanda.org/download.php
What's New
Experience enhanced tape handling capabilities with the new Amanda.
The 3.5.2 version of Amanda will prevent unintentional deletions of data on
recursion. Removing that appears to have
fixed the dump.
Still seems like there is an issue with amanda not cleaning up properly
from the timeout condition though.
On Wed, Jun 15, 2022 at 09:50:11AM -0600, Orion Poplawski wrote:
On 6/15/22 09:38, Orion Poplawski wrote:
Recently the backup
rite out the name of the directory to
> > amgtar:
> >
> > root 11321 11315 33 Jun14 ?03:55:46 /usr/bin/tar --create
> > --verbose --verbose --block-number --file - --directory
> > /export/backup/rufous
> > --no-check-device --listed-incremental
> > /va
> --no-check-device --listed-incremental
> /var/lib/amanda/gnutar-lists/saga_export_backup_rufous_0.new
> --ignore-failed-read --totals --exclude-from
> /var/log/amanda/amgtar._export_backup_rufous.20220614211711.exclude .
> root 11432 11427 42 Jun14 ?03:57:48 /usr/bin/t
1 - 100 of 4138 matches
Mail list logo
