I once posted about german umlauts and the issues in amrecover.
Today I hit that again.
In the amrecover UI I found two files in a specific DLE:
2024-01-15-19-30-02 "SOME & FILE Name �bersicht.xlsx"
2024-01-09-19-30-01 "SOME & FILE Name �bersicht.pdf"
note the quotes around the names
for
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 XFS maybe) and
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
accordingly. Not to
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 years.
So here's
I am assuming you mean something like:
CREATE FUNCTION pg_stop_backup ( ) RETURNS TABLE ( lsn pg_lsn, labelfile
text, spcmapfile text )
AS 'pg_backup_stop'
LANGUAGE internal
STRICT;
CREATE FUNCTION pg_start_backup(label text) RETURNS pg_lsn
AS 'pg_backup_start'
LANGUAGE
Hello Trever,
you may define aliases for this functions with the "old" name like described
here:
https://www.postgresql.org/docs/current/xfunc-internal.html
HTH,
Ingo
Am 21. Dez. 2023, 15:11, um 15:11, "Trever L. Adams"
schrieb:
>So, I am not sure which version started this problem with
So, I am not sure which version started this problem with backing up
PostgreSQL.
| psql stderr: ERROR: function pg_start_backup(unknown) does not exist
| psql stderr: LINE 1: SELECT pg_start_backup('amanda-1703142252')
| psql stderr:^
| psql stderr: HINT: No function
On 12/21/23 07:08, Trever L. Adams wrote:
So, I am not sure which version started this problem with backing up
PostgreSQL.
| psql stderr: ERROR: function pg_start_backup(unknown) does not exist
| psql stderr: LINE 1: SELECT pg_start_backup('amanda-1703142252')
| psql stderr:
On 16.11.23 22:08, Moritz Both wrote:
Greetings,
we use amanda with usb disks and manually change them every day. I
configured udev to create a symlink to /dev/amanda-vtape when the disk
is plugged in.
In /etc/fstab I configured this device so it can be mounted to
/mnt/amanda-vtape by the
Olivier writes:
> Many many years ago, I wrote a changer that could use several vtape
My configuration file mentions 2008!
Hi,
> Nowerdays the people changing the disks frequently work at home. So it
> would be nice to plug in more than one disk and have a tape changer scan
> for more than one disk. I understand there is no changer included in
> amanda which is directly capable of that.
Many many years ago, I
Udev can run shell scripts as an action, use that when device is plugged in
and have smarter symlink naming logic in the script.
On Thu, 16 Nov 2023, 22:10 Moritz Both, wrote:
> Greetings,
>
> we use amanda with usb disks and manually change them every day. I
> configured udev to create a
Greetings,
we use amanda with usb disks and manually change them every day. I
configured udev to create a symlink to /dev/amanda-vtape when the disk
is plugged in.
In /etc/fstab I configured this device so it can be mounted to
/mnt/amanda-vtape by the amanda user. This works for many years
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
Nuno,
Thanks for the reply! And apologies for being not quite clear.
I'm quite sure the offending hosts are powered down, so no chance
of partial response. When I look at the planner..debug log, I
can see sendsize requests going out to the hosts that are powered up and
responsive,
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 refused
From
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 3.5.3, the
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
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
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
>
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
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
>
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
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
I concur with your complaint.
You need to have the Finder show hidden files
(https://www.macworld.com/article/671158/how-to-show-hidden-files-on-a-mac.html)
so you can navigate to /opt/local/bin/gtar and add it to Full Disk Access.
In the Finder dialog that pops up when you click on '+' in
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 the
subversion tree on my main desktop) or out on
That does not seem possible. As far as Security & Privacy -> Full Disk Access
is concerned, /opt/local/bin/gnutar does not exist and there does not seem to
be any way of getting there -- it only gives a limited number of places to
point and click on. (I really *hate* pointy-clicky UIs and
I think you need the program that actually reads the files (in this case,
/opt/local/bin/gtar) added to Full Disk Access.
> On Jun 8, 2023, at 7:40 AM, Robert Heller wrote:
>
>
> It already is there.
>
> At Thu, 8 Jun 2023 08:31:15 -0600 Pieter Bowman
> wrote:
>
>>
>> Unfortunately, I
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 Integrity Protection (SIP).
-- 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 MacOSX 10.15
"amanda_deploy" on github has just seen some significant updates.
(Ansible playbooks and roles to deploy Amanda backup, server and clients)
For example:
-updated ansible syntax (e.g. use loop, ansible.builtin)
-vagrant capability, including script to setup multi or single boxes
-ubuntu 22.04
You can probably skip the labelstr completly and only use autolabeling=no with
manual labeling to assign tapes to each storage pool.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2023-05-19 13:36, ASV wrote:
Wow, I'll go through it as soon as I can.
Thank you very much for now exuvo, very
Wow, I'll go through it as soon as I can.
Thank you very much for now exuvo, very appreciated!
On Thu, 2023-05-18 at 12:13 +0200, Exuvo wrote:
> Here is the relevant part of my config with multiple separated tapes
> (all LTO5 in my case) in the same MSL2024.
> This relies on you having labeled
Here is the relevant part of my config with multiple separated tapes (all LTO5
in my case) in the same MSL2024.
This relies on you having labeled the tapes reasonably as it looks like
labelstr can not match the LTO type.
I do not use autolabeling, only manual labeling with a script i run when i
That's correct, all drives are LTO8, but not all tapes. And no, there
is no definition of any kind for slot positioning of the LTO7 right
now.
Thanks for your reply.
On Tue, 2023-05-16 at 16:48 +0200, Stefan G. Weichinger wrote:
> Am 16.05.23 um 16:34 schrieb ASV:
> > Thanks exuvo, I'll try to
Am 16.05.23 um 16:34 schrieb ASV:
Thanks exuvo, I'll try to dig a bit in that direction even though I was
expecting some built-in functionality for that.
Are the LTO7-tapes always in defined slots?
As far as I understand all *drives* are LTO8, but not all *tapes* ?
Thanks exuvo, I'll try to dig a bit in that direction even though I was
expecting some built-in functionality for that.
On Tue, 2023-05-16 at 12:16 +0200, Exuvo wrote:
> I think the settings you want are two different storage/pools
> sections with a labelstr regex for matching valid tapes for
I think the settings you want are two different storage/pools sections with
a labelstr regex for matching valid tapes for it. I cant see my config from
my phone but its something like that.
On Tue, 16 May 2023, 11:17 ASV, wrote:
> OK! I guess you have no hint for me but thanks anyway for
OK! I guess you have no hint for me but thanks anyway for giving a
sign.
On Tue, 2023-05-16 at 11:01 +0200, Kees Meijs | Nefos wrote:
> Yes.
>
> On 16-05-2023 10:40, ASV wrote:
> > This mailing list seems dead. Is anybody actually still reading it?
>
Someone is reading it. Maybe nobody knows the answer...
Diego
Il 16/05/2023 10:40, ASV ha scritto:
This mailing list seems dead. Is anybody actually still reading it?
___
Hello everyone,
I have an Amanda setup nicely working with a SpectraStack.
The drives are LTO8 but I've just
This mailing list seems dead. Is anybody actually still reading it?
___
Hello everyone,
I have an Amanda setup nicely working with a SpectraStack.
The drives are LTO8 but I've just figured out that there are several
LTO7 too in the library. Now I've both types defined in amanda.conf
Hello everyone,
I have an Amanda setup nicely working with a SpectraStack.
The drives are LTO8 but I've just figured out that there are several
LTO7 too in the library. Now I've both types defined in amanda.conf
however I cannot find a way to tell Amanda that tape labelled XXX or
with the barcode
So, I did some more digging, the problem came because a bad log file
that contains the line:
DONE taper WARNING driver Taper protocol error
This line caused Perl module Catalog.pm to die at line 764 because $str
is empty and Perl cannot apply a regex replace on an empty string.
After I removed
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 have this 2
Hi,
Lately, when trying to do an amrecover I get the following error message:
Got no header and data from server, check in amidxtaped.*.debug and
amandad.*.debug files on server
I could not see anything in amandad.*.debug
In amidxtaed.*.debug I found a number of lines saying:
Warning: no log
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
In an installation with two storage definitions with two POLICY
definitions I often get report lines like this:
planner: Last full dump of samba.some.tld:boot on tape ARC948
overwritten in 3 runs.
As far as I know this means I have less tapes in rotation than
"runspercycle".
It seems
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
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 just-released amanda
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)
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 option: -]
>
The
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
Am 20.03.23 um 07:38 schrieb Kees Meijs | Nefos:
Hi there,
On 19-03-2023 18:37, Stefan G. Weichinger wrote:
Do / did you run fileservers on btrfs?
Yes. There's a back up server (runnning something other then AMANDA)
with a 40-something TB volume with btrfs. Quite often (like every other
Am 27.06.22 um 10:21 schrieb Stefan G. Weichinger:
Am 03.06.22 um 09:13 schrieb Stefan G. Weichinger:
I now at last received credentials to that gcs storage bucket, so I
can start to try ...
Does it make sense to somehow follow
https://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3 ?
Am 17.03.23 um 09:20 schrieb Kees Meijs | Nefos:
Hi Stefan,
I'd recommend against btrfs and go for ZFS instead (also on Linux).
Although I was a (really) great fan of btrfs; it just seemed to have too
much bugs, sometimes even resulting in loss of data.
My experience is different, my
Does anyone successfully use btrfs snapshots with amanda?
Like in doing LVM snapshots pre-amdump etc ?
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
problems would be
On Wed, Mar 08, 2023 at 12:20:00PM +0100, Heiko Schlittermann wrote:
Hi,
Jens Berg (Mi 08 Mär 2023 10:06:34 CET):
She does in the moment a tape (= slot) is re-used.
…
Remember that amanda was initially designed to work with tapes and that
Olivier (Mi 08 Mär 2023 11:46:37 CET):
While the
Ingo Schaefer (Mi 08 Mär 2023 11:15:34 CET):
> Hello Heiko,
>
> I usually used the amrestore command to find out, which tapes I would need
> for restoring a particular point in time.
> So this answers the question, which tapes (=storage) is used for backups of a
> particular DLE.
amrestore
I would also like to add that it is good to have backups from varying dates
around in case the most recent backup is ex after a file was accidentally
deleted and you need to restore it from an older backup.
Anton "exuvo" Olsson
ex...@exuvo.se
On 2023-03-08 12:20, Heiko Schlittermann wrote:
Hi,
Jens Berg (Mi 08 Mär 2023 10:06:34 CET):
> She does in the moment a tape (= slot) is re-used.
…
> Remember that amanda was initially designed to work with tapes and that
Olivier (Mi 08 Mär 2023 11:46:37 CET):
> While the tape/slot could free the level 1 dumps for a-disk, there could be
>
Hi,
> Given a series of dumps like
>
> a-host a-disk 1 1 1 0 1 1
>
> the left most level 1 dumps are worthless, because we already dropped
> the "base" level 0.
While the tape/slot could free the level 1 dumps for a-disk, there could be
some DLE for other disks/hosts that are still valid
Hello Heiko,
I usually used the amrestore command to find out, which tapes I would need for
restoring a particular point in time.
So this answers the question, which tapes (=storage) is used for backups of a
particular DLE.
Yours,
Ingo
Am 8. März 2023, 08:10, um 08:10, Heiko Schlittermann
On 08.03.2023 08:14, Heiko Schlittermann wrote:
- Does amanda delete these files? From the output of `amadmin find` it
does not look as if it does.
She does in the moment a tape (= slot) is re-used.
Remember that amanda was initially designed to work with tapes and that
using disks as
Hi,
if I understand and observed well, then for a disk based backup we have the
chunks as
single files in the slot* directories.
Given a series of dumps like
a-host a-disk 1 1 1 0 1 1
the left most level 1 dumps are worthless, because we already dropped
the "base" level 0.
- Does
Hi,
is there a way to find the storage that is used for a particular DLE?
I didn't find anything that's easy.
Using `amadmin info` seems to include the recent backups per level only.
I can try iterating over the output of `amadmin find` and use the known
chunk size and the number of chunks, but
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:
Am 05.02.23 um 15:39 schrieb Uwe Menges:
Hi,
I just updated my backup server from Fedora 35 to 37.
After the upgrade, I tried to run amflush.
The session running amflush was killed by systemd-oomd as per these
lines in the journal:
systemd[1]: session-5.scope: systemd-oomd killed some
Hi,
I just updated my backup server from Fedora 35 to 37.
After the upgrade, I tried to run amflush.
The session running amflush was killed by systemd-oomd as per these
lines in the journal:
systemd[1]: session-5.scope: systemd-oomd killed some process(es) in this unit.
systemd-oomd[7544]:
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
Am 18.01.23 um 14:09 schrieb Pablo Venini:
This is the amanda.conf
org "monitoreo10_diario" # your organization name for
reports
dumpuser "amandabackup" # the user to run dumps under
mailto "xxx...@y.zz" # space separated list of operators at
your site
dumpcycle
Am 18.01.23 um 14:12 schrieb Pablo Venini:
Yes, I was also thinking about installing 3.5.1; I installed 3.5.2 from
RPM so I thought it was ok (I was reinstalling an old server wich ran
3.3.9).
I tried your suggestion and if I run amdump for each DLE, the dumps are ok
Why don't you just set
Yes, I was also thinking about installing 3.5.1; I installed 3.5.2 from
RPM so I thought it was ok (I was reinstalling an old server wich ran
3.3.9).
I tried your suggestion and if I run amdump for each DLE, the dumps are ok
El 18/1/2023 a las 06:23, Stefan G. Weichinger escribió:
Am
This is the amanda.conf
org "monitoreo10_diario" # your organization name for reports
dumpuser "amandabackup" # the user to run dumps under
mailto "xxx...@y.zz" # space separated list of operators at
your site
dumpcycle 1week # the number of days in the normal
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 of
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 # the
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 amdump run, but that
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
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:
define dumptype sm-encrypt-compress {
gui-base
comment "SM dumptype with compression and encryption"
compress client fast
encrypt client
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
> errors. However when I
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 other ones
Am 05.12.22 um 19:41 schrieb Jose M Calhariz:
I wasn't aware that doing this "resets history" ... I just want to have lev0
runs only on that day
It blocks incremental backups to run until a lev0 is run sucessfully.
Now I only do a "amdmin force " when I know I have lost the previous
lev 0 or
On Mon, Dec 05, 2022 at 03:20:08PM +0100, Stefan G. Weichinger wrote:
> Am 05.12.22 um 15:03 schrieb Jose M Calhariz:
> > On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote:
> > >
> > > I have an installation where I didn't add or remove DLEs for a long time.
> > >
> > > But
Am 05.12.22 um 15:03 schrieb Jose M Calhariz:
On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote:
I have an installation where I didn't add or remove DLEs for a long time.
But now an then amanda seems to "forget" a DLE and come up with something
like:
samba.intra rootfs lev
On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote:
>
> I have an installation where I didn't add or remove DLEs for a long time.
>
> But now an then amanda seems to "forget" a DLE and come up with something
> like:
>
> samba.intra rootfs lev 0 FAILED [dumps too big, 42606931
Am 05.12.22 um 06:47 schrieb Nathan Stratton Treadway:
On Thu, Dec 01, 2022 at 10:18:03 +0100, Stefan G. Weichinger wrote:
I have an installation where I didn't add or remove DLEs for a long time.
But now an then amanda seems to "forget" a DLE and come up with
something like:
samba.intra
On Thu, Dec 01, 2022 at 10:18:03 +0100, Stefan G. Weichinger wrote:
>
> I have an installation where I didn't add or remove DLEs for a long time.
>
> But now an then amanda seems to "forget" a DLE and come up with
> something like:
>
> samba.intra rootfs lev 0 FAILED [dumps too big, 42606931
If you had to restore the whole disk from backup, it now looks like a new
un-backed up disk. Something about the backed-up bit for each file having been
altered? Or any other procedure which could alter all/most of the backup
bits?
Deb Baddorf
On Thursday, December 1, 2022, 06:26:31
I have an installation where I didn't add or remove DLEs for a long time.
But now an then amanda seems to "forget" a DLE and come up with
something like:
samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot
incremental dump new disk]
The DLE is NOT new. Where does
The tool is not optimal but from what I understand its purpose exactly
matches my use case, and it had worked before. It's just that it broke
at some point (or maybe I broke it somehow?)
I've read through the thread you suggested. Thanks for pointing that
out. However, it doesn't seem to fit
Am 22.11.22 um 17:13 schrieb Christian:
Hello,
I'm running a very small amanda installation to create regular backups
of local files and also involves archiving at some point. For archiving
files, I run a full backup that ends up in holding and then I run
amvault twice to write the backup
1 - 100 of 46668 matches
Mail list logo
