Am 26.11.19 um 19:58 schrieb Charles Curley:
> I wonder if this would capture complete backups? If you have all level
> 0 (total) backups, this should be fine. But if you have non-level-0
> backups, you need a way to capture and keep until the next level 0
> backup all the non-level-0 backups.
>
Am 26.11.19 um 19:42 schrieb Debra S Baddorf:
> I’ve no particular knowledge of this, so this is just suggestion - until
> somebody with better
> ideas comes along.
yeah, the dozens of amanda-users populating the discussions here ;-)
> I suspect amanda does not like to leave things in her
special need again:
One DLE uses amsamba-application to dump a Windows-share, containing a
specific SQL-Server-export
That dump should go to (a) amanda's vtapes (done already) and (b)
rsynced to some remote server off-site
Now how do I keep the tarballs in the holdingdisk for syncing them
Am 26.11.19 um 12:39 schrieb Stefan G. Weichinger:
>
> Does someone have a working example for an exclude list in combo with
> the amsamba application?
ah, and now it works .. as so often after asking for help ;-)
sorry for the noise
Does someone have a working example for an exclude list in combo with
the amsamba application?
Am 21.11.19 um 08:59 schrieb Olivier:
> Hi,
>
> One of the machine I back-up with Amanda is used by our students to run
> AI, machine learning, etc. Each coming with huge set of data. When I
> know that it will be coming, I may exclude the student's directory, but
> I am not always aware.
Isn't
Am 19.11.19 um 06:12 schrieb Jon LaBadie:
> On Sun, Nov 17, 2019 at 12:16:18PM +0100, Stefan G. Weichinger wrote:
>> Am 15.11.19 um 20:32 schrieb Jon LaBadie:
>>
>>> I was not thinking of any algorithm. Just a weekend crontab entries like:
>>>
>>> am
Am 15.11.19 um 20:32 schrieb Jon LaBadie:
> I was not thinking of any algorithm. Just a weekend crontab entries like:
>
> amadmin ... force ... ; amdump ...
Yes, I understood that. But that "manual force" always disturbs the
schedule built by the amanda algorithm, right?
At least that was
Am 12.11.19 um 15:27 schrieb Stefan G. Weichinger:
> I think that should be pointed out somewhere in the docs ... maybe I
> should write something (or you ;-))
The more I think of this I suggest that the default value of the
property "GNUTAR-LISTDIR"
should be "/var/li
Am 12.11.19 um 14:55 schrieb Nathan Stratton Treadway:
> The danger in your particular case is that the "weekly" run will update
> the level 0 snapshot file for each DLE, and then the any "daily" runs
> that do level 1 dumps the following week will only include files changed
> after that "weekly"
Am 11.11.19 um 22:10 schrieb Debra S Baddorf:
> My alternate config is run once a month, but I think my params would work
> for your
> “every weekend” too.
> dumpcycle 0 # I plan to run it whenever I want to
> tapecycle 9000 # I will always give you a fresh tape. You would say 31.
>
Am 12.11.19 um 00:12 schrieb Jon LaBadie:
> What about a single config incremental only.
>
> Via crontab, force level 0's when you want,
> maybe every other weekend FRI & SAT.
>
> The SAT dump serves as level 0's for the incrementals.
>
> The FRI dump can be used for your archiving as needed.
Am 11.11.19 um 22:10 schrieb Debra S Baddorf:
> runtimes 3# the max you’ll allow to catch all the level-0 backups
that parameter is not recognized here ;-)
Aside from that: thanks a lot for your feedback, Debra
At a customer we try to run 2 configs in parallel.
I discussed this setup here in the past, and bring it back up again ;-)
-
We run a daily config with 58 tapes.
This is run on weekdays 1-4 only.
Until now we had:
dumpcycle 2 weeks
runspercycle 8
Would it be better to have
dumpcycle 8
Am 02.08.19 um 10:56 schrieb Nuno Dias:
> Hi,
>
> Since two days ago I have this error, everytime I try to run amstatus
>
> amstatus: bad status on taper SHM-WRITE (taper): 16 at
> /usr/lib64/perl5/vendor_perl/Amanda/Status.pm line 935, <$fd> line
> 9210.
>
> I can see that the amdump is
What's the current howto here?
I don't see a matching PROPERTY for the device "Tape device" here
https://wiki.zmanda.com/man/amanda-devices.7.html
Customer wishes to have all tapes ejected in the morning.
OK, I could run a cron job, but what if amdump isn't done yet?
something like
amdump
Am 20.07.19 um 14:39 schrieb Nathan Stratton Treadway:
> On Sat, Jul 20, 2019 at 10:54:04 +0200, Stefan G. Weichinger wrote:
>> Does someone have patches in place for this ACCESS_DENIED issue
>> mentioned here:
>>
>> https://github.com/zmanda/amanda/issues/77
>&
Am 18.07.19 um 13:49 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
>> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>>
>>>> Add the same pattern near line 757:
>>
Am 18.07.19 um 13:45 schrieb Stefan G. Weichinger:
> Am 18.07.19 um 10:44 schrieb Diego Zuccato:
>> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>>
>>> Add the same pattern near line 757:
>>> return if $line =~ /^Unable to initialize messaging contex
Am 18.07.19 um 10:44 schrieb Diego Zuccato:
> Il 17/07/19 19:04, Jean-Louis Martineau ha scritto:
>
>> Add the same pattern near line 757:
>> return if $line =~ /^Unable to initialize messaging context/;
> Tks! Applied. Hope it gets included in next update!
>
Am 17.07.19 um 19:04 schrieb Jean-Louis Martineau:
> Add the same pattern near line 757:
> return if $line =~ /^Unable to initialize messaging context/;
Oh, Jean-Louis, nice to read you!
thanks for the missing line, yes, now my first test dump is free of that
error.
Do we have a PR somewhere
Am 16.07.19 um 10:07 schrieb Stefan G. Weichinger:
> Am 16.07.19 um 09:14 schrieb Diego Zuccato:
>> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>>
>>> I never figured out the correct patch ;-)
>>> Pls show your change, I want to give it another try.
>
Still believing in filing issues:
https://github.com/zmanda/amanda/issues/109
Am 16.07.19 um 09:14 schrieb Diego Zuccato:
> Il 16/07/19 08:46, Stefan G. Weichinger ha scritto:
>
>> I never figured out the correct patch ;-)
>> Pls show your change, I want to give it another try.
> Here it is.
> -8<--
> # diff -u amsamba.ori amsamba
> --- a
Am 10.07.19 um 14:17 schrieb Diego Zuccato:
> Too bad the patch given here:
> http://www.backupcentral.com/forum/14/292396/smbclient_usage_fails_with__unable_to_initialize_messaging_context_
> is not in packaged version (3.5.1) yet.
>
> Adding the two lines, in my case, fixes the amcheck issue.
After upgrading a gentoo server to amanda-3.5.1 I get this for a
specific (and very old) amanda-client:
Amanda Backup Client Hosts Check
ERROR: linux4: selfcheck request failed: Can't bind a socket to connect
to linux4
Client check: 1 host checked in 10.015
Am 24.06.19 um 22:06 schrieb Debra S Baddorf:
> You can also use “dd” to get the whole dump off tape. You would have to
> “glue” together
> any partial files; I don’t know how to do that (I’ve specified no partial
> files).
>
> “dd” still needs a reasonably correct block size.
thanks for
I stil have issues here:
amrestore --config abt -b 2097152 /dev/nst0 jupi smb_revision
Restoring from tape ABT-401 starting with file 1.
amrestore: 1: skipping split dumpfile: date 20190607213002 host juno
disk vm182 part 1/UNKNOWN lev 0 comp N program /bin/tar
[..]
amrestore: 12:
Am 19.06.19 um 19:30 schrieb Stefan G. Weichinger:
>
> I get
>
> $ amrestore --config abt /dev/nst0 jupi smb_revision
> ERROR: Error reading Amanda header: block size too small
>
> $ amrestore --config abt -b 32768 /dev/nst0 jupi smb_revision
> ERROR: Error reading A
I get
$ amrestore --config abt /dev/nst0 jupi smb_revision
ERROR: Error reading Amanda header: block size too small
$ amrestore --config abt -b 32768 /dev/nst0 jupi smb_revision
ERROR: Error reading Amanda header: block size too small
I don't have to say that I need these restores ...
(bump)
I need a solution ... that DLE does not dump ok
Am 15.06.19 um 16:05 schrieb Stefan G. Weichinger:
>
> amanda-3.5.1, samba-4.8.6
>
> amcheck fails, messages tell me:
>
> "
> Jun 15 16:04:06 mail Amsamba[17632]: Use of uninitialized value
> $regex_match in
amanda-3.5.1, samba-4.8.6
amcheck fails, messages tell me:
"
Jun 15 16:04:06 mail Amsamba[17632]: Use of uninitialized value
$regex_match in pattern match (m//) at
/usr/libexec/amanda/application/amsamba line 92.
Jun 15 16:04:07 mail Amsamba[17633]: Use of uninitialized value
$regex_match in
We now received 40 new tapes for a new config "weekly": it should be run
on friday and maybe saturday and do only FULL backups.
Maybe someone wants to doublecheck my config and suggest improvements ->
I set:
dumpcycle 1 weeks
runspercycle 1
and
flush-threshold-dumped 100
Am 07.06.19 um 10:50 schrieb Stefan G. Weichinger:
>
> I have to backup a share that is only reachable via SMB2:
>
> server ~ # smbclient -L 192.168.160.1 -U user%pw
> protocol negotiation failed: NT_STATUS_CONNECTION_RESET
>
> server ~ # smbclient -L 192.168.160.1 -U use
I have to backup a share that is only reachable via SMB2:
server ~ # smbclient -L 192.168.160.1 -U user%pw
protocol negotiation failed: NT_STATUS_CONNECTION_RESET
server ~ # smbclient -L 192.168.160.1 -U user%pw -m SMB2
Domain=[ANLAGEN-SERVER] OS=[] Server=[]
[..]
ADMIN$
>> CI pipeline? CI is a new acronym to me, Stefan.
Continuous Integration
for example automated test builds to keep the code in a state that
actually compiles.
GitHub provides Travis CI to run tests etc everytime a commit is pushed
to the repo.
I already have a (rather big) docker image here
Am 12.05.19 um 00:46 schrieb Charles Curley:
> I am making progress on building amanda from the git repo. I have buit
> a new machine and populated it as needed.
>
> So far, my build process is:
>
> ./autogen
> ./configure
> packaging/deb/buildpkg
...
I am playing with a Debian Stretch Docker
Am 10.05.19 um 02:20 schrieb Chris Hassell:
> That's pretty bonkers. There's nothing in the setup that I know of
> that's been changed. Never happened to me.
>
> Try a "pstree -phul" to see if you can find wth it was trying to do.
> Did htop show something spinning ... or a specific
Am 06.04.19 um 01:57 schrieb Chris Hassell:
> [Chris Hassell]
> I could look into spinning up a Debian v7 setup, but I bet I could get it to
> work.
>
> I'm going to push a branch to the github repo that can be merged (or ignored
> as people like) to add the buildfix stuff by merging with it.
Am 22.01.19 um 18:50 schrieb Stefan G. Weichinger:
>
> I might have written about that already some years(?) ago, but anyway:
>
> I have a small shell-script to ask "amadmin config tape --days X" for
> the next tapes to put into the magazines.
>
> That sc
Am 25.03.19 um 22:53 schrieb Chris Hassell:
> Hi all,
>
> Actually here at BETSOL I'm tasked with getting changes from
> github-git converted into SVN commits.
>
> Git at Github should be the main repo AFAIK. It's been a bit quiet
> too long to treat it like the back end of the master-slave.
Am 20.03.19 um 18:53 schrieb Gene Heskett:
> The sudden silence from JLM did beg for the question to be asked, and I'm
> fairly famous for that, so it was mentioned. I hope you are well these
> days Dustin. I had to have a pacemaker installed back in January. I
> guess its a sign of the 84
Am 17.10.18 um 22:37 schrieb Ashwin Krishna:
>> So is Jean-Louis still involved or not? Employed by Betsol or ...
>> ?
>
> Jean Louis is not with BETSOL. He is part of the community though.
> The previous call was to understand the pain points of the community
> in general for governance and
Am 18.03.19 um 19:20 schrieb Ryan:
> Amanda 3.5.1 (RHEL7 community RPM) has been terribly buggy for us, and
> most of it shows itself in the planner.
pls also inform
amanda-hack...@amanda.org
and file an issue at github:
https://github.com/zmanda/amanda/issues
Unfortunately the project
Am 05.03.19 um 18:54 schrieb Stefan G. Weichinger:
> Am 04.03.19 um 12:35 schrieb Stefan G. Weichinger:
>
>> amanda-client host runs docker.service
>>
>> amdump starts, estimates ok, dump proceeds ... hangs at ~99%
>>
>> If I stop docker.service, amdum
Am 04.03.19 um 12:35 schrieb Stefan G. Weichinger:
> amanda-client host runs docker.service
>
> amdump starts, estimates ok, dump proceeds ... hangs at ~99%
>
> If I stop docker.service, amdump finishes OK.
Addon: if I stop the portainer container, amdump works OK ...
Sol
Am 26.02.19 um 16:44 schrieb Charles Curley:
> On Tue, 26 Feb 2019 13:56:35 +0100
> "Stefan G. Weichinger" wrote:
>
>> Do I understand correctly:
>>
>> with "auth ssh" amanda only uses ssh for auth and transport of data?
>>
>> So port
Am 26.02.19 um 16:26 schrieb Jose M Calhariz:
>
> My plan is for Debian 11, current is 9, to make ssh authentication
> the default. I will not disable bsd authentication, only harder to
> setup.
>
> In attach is the Readme.Debian that I have created.
thanks
What I wonder and what IMO is not
Am 25.02.19 um 20:15 schrieb Stefan G. Weichinger:
>> dump runs but hangs at 99,99% ... oh my.
>
> I get data timeout for that one test DLE.
>
> And I assume it will be the same for the other DLEs tonight.
>
> I now stopped docker .. reran amdump, and it is throu
Am 25.02.19 um 19:11 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 17:51 schrieb Stefan G. Weichinger:
>
>>> another client dumps fine via ssh already
>>>
>>> do all clients have to have ssh-access to the server as well?
>>
>> estimate calcsize does n
Am 25.02.19 um 17:51 schrieb Stefan G. Weichinger:
>> another client dumps fine via ssh already
>>
>> do all clients have to have ssh-access to the server as well?
>
> estimate calcsize does not work with ssh for me
>
> estimate server ... starts dumping after the
Am 25.02.19 um 17:09 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 16:36 schrieb Charles Curley:
>> On Mon, 25 Feb 2019 08:12:21 +0100
>> "Stefan G. Weichinger" wrote:
>>
>>> on my way. amcheck ok, amdump not. seems to still run via inetd.
>>>
Am 25.02.19 um 16:36 schrieb Charles Curley:
> On Mon, 25 Feb 2019 08:12:21 +0100
> "Stefan G. Weichinger" wrote:
>
>> on my way. amcheck ok, amdump not. seems to still run via inetd.
>>
>> I assume I should disable inetd on the client ... does not help so
Am 25.02.19 um 07:48 schrieb Stefan G. Weichinger:
> Am 25.02.19 um 00:08 schrieb Jose M Calhariz:
>> On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger
>> wrote:
>>>
>>> does anyone see estimates fail on a updated Debian 9.8 amanda
>>> client
Am 25.02.19 um 00:08 schrieb Jose M Calhariz:
> On Thu, Feb 21, 2019 at 04:50:25PM +0100, Stefan G. Weichinger
> wrote:
>>
>> does anyone see estimates fail on a updated Debian 9.8 amanda
>> client server?
>>
>> update: seems that my new docker daemon o
Am 21.02.19 um 16:50 schrieb Stefan G. Weichinger:
>
> does anyone see estimates fail on a updated Debian 9.8 amanda client server?
>
> update: seems that my new docker daemon on the client closes the
> iptables for amanda
>
> does anyone have a snippet for me?
as soon a
does anyone see estimates fail on a updated Debian 9.8 amanda client server?
update: seems that my new docker daemon on the client closes the
iptables for amanda
does anyone have a snippet for me?
I read
https://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda and
loaded that
I might have written about that already some years(?) ago, but anyway:
I have a small shell-script to ask "amadmin config tape --days X" for
the next tapes to put into the magazines.
That script is run via cron and emails the local admin at the customer
with the requested tapes.
A bit ugly
Am 22.01.19 um 18:30 schrieb Debra S Baddorf:
> The first block is a text description of the dump and how to use it.
>
> dd if=tapeOrFilename of=whatever bs=YourBlockSize count=1
>
> should show that first block.Use skip=1 for put the actual dump to a
> useable file.
>
> (DD command
Am 17.01.19 um 12:10 schrieb Stefan G. Weichinger:
> The idea is to let the normal runs write to storage "daily" and
> additionally keep the dumped files in the holdingdisk.
>
> After having all DLEs there I want to do something like:
>
> amflush daily -o storage=a
New thread, trying to summarize what I try to achieve here.
amanda-3.5.1 on a gentoo linux server
1x LTO6 tape drive, 8 slot tape library
around 12 TB data to dump
More or less enough holding disk to keep a full lev0 of all the DLEs.
-
The normal schedule (let's call it amanda config
Am 10.01.19 um 20:41 schrieb Debra S Baddorf:
>
>
>> On Jan 10, 2019, at 10:32 AM, Stefan G. Weichinger wrote:
>>
>> Am 30.11.18 um 19:40 schrieb Debra S Baddorf:
>>
>>> IFF you have the holding disk space, you might want these params:
>>>
>
Am 30.11.18 um 19:40 schrieb Debra S Baddorf:
> IFF you have the holding disk space, you might want these params:
>
> flush-threshold-dumped300 # (or perhaps only 150) ## I have NOT
> tested this one
> flush-threshold-scheduled 100#
> ###However, all dumps will be flushed;
Am 08.01.19 um 13:37 schrieb Stefan G. Weichinger:
> filed a bug at gentoo:
>
> https://bugs.gentoo.org/674864
Just in case someone is interested:
I made some progress there, there seems to be some bug around barcodes.
Am 08.01.19 um 10:30 schrieb Stefan G. Weichinger:
> Am 06.01.19 um 10:59 schrieb Stefan G. Weichinger:
>
>>> /usr/libexec/amanda/amcheck-device
>>>
>>> fails with
>>>
>>> traps: amcheck-device[11133] trap invalid opcode ip:7fc29a5d33b
Am 06.01.19 um 10:59 schrieb Stefan G. Weichinger:
>> /usr/libexec/amanda/amcheck-device
>>
>> fails with
>>
>> traps: amcheck-device[11133] trap invalid opcode ip:7fc29a5d33bc
>> sp:7fffb73c7770 error:0 in libamanda-3.5.1.so[7fc29a5ad000+7e000]
>>
&
Am 24.12.18 um 16:55 schrieb Stefan G. Weichinger:
>> Maybe someone could take a look here:
>>
>> https://oc.oops.co.at/nextcloud/index.php/s/pfTRE34c3aqPyDZ
>
>
>
> /usr/libexec/amanda/amcheck-device
>
> fails with
>
> traps: amcheck-device[11133
Am 05.01.19 um 00:31 schrieb Uwe Menges:
> On 1/4/19 7:51 PM, Stefan G. Weichinger wrote:
>> I couldn't find a way to exclude/ignore such messages from smbclient
>> within amsamba. And browsing the script itself it wasn't clear to me
>> non-coder how and where to add th
Am 03.01.19 um 09:56 schrieb Uwe Menges:
> On 1/2/19 8:19 PM, Stefan G. Weichinger wrote:
>>> at first: happy new year to all you amanda-users!
>
> Happy new year as well!
thank you ;)
> I don't use smb or amsamba, so I don't know what it does in depth.
> But I don't ye
Am 02.01.19 um 11:19 schrieb Stefan G. Weichinger:
at first: happy new year to all you amanda-users!
--
Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails
to amcheck/amdump:
Amanda Backup Client Hosts Check
HOST backup ERROR: smbclient
at first: happy new year to all you amanda-users!
--
Today I noticed that one server running Debian 9.6 and Samba-4.8.8 fails
to amcheck/amdump:
Amanda Backup Client Hosts Check
HOST backup ERROR: smbclient: Unable to initialize messaging context
HOST backup
Am 22.12.18 um 09:36 schrieb Stefan G. Weichinger:
> Am 21.12.18 um 19:01 schrieb Stefan G. Weichinger:
>> Am 18.12.18 um 14:29 schrieb Stefan G. Weichinger:
>>>
>>> I get this error with amcheck:
>>>
>>> ERROR: amcheck-device terminated with signal 1
Am 21.12.18 um 19:01 schrieb Stefan G. Weichinger:
Am 18.12.18 um 14:29 schrieb Stefan G. Weichinger:
I get this error with amcheck:
ERROR: amcheck-device terminated with signal 11
I now updated and rebooted the library as well.
Maybe someone could take a look here:
https://oc.oops.co.at
Am 17.12.18 um 10:18 schrieb Stefan G. Weichinger:
I switch over configs (and in consequence tapes) this week: instead of
running normal "daily" config, I now run "archive" to a separate set of
tapes now ... same disklist, other amanda.conf
The plan is to let that conf
Am 18.12.18 um 14:29 schrieb Stefan G. Weichinger:
>
> I get this error with amcheck:
>
> ERROR: amcheck-device terminated with signal 11
>
> amanda-3.5.1 ... completely rebuilt, perl stuff updated etc
>
> I can load various tapes via amtape, no
I get this error with amcheck:
ERROR: amcheck-device terminated with signal 11
amanda-3.5.1 ... completely rebuilt, perl stuff updated etc
I can load various tapes via amtape, no problem.
dmesg says:
[27652194.798451] amcheck-device[668]: segfault at 8 ip 7f094b6ed6e6
sp
Am 30.11.18 um 19:40 schrieb Debra S Baddorf:
> Well, from comp sci courses 20 years ago, the best algorithm to fill the
> tapes (or the “Bag” in CS class)
> is the Greedy Method. Which is also the most obvious one.
> taperalgo=largestfit
> I.E. Pick the biggest thing that will still fit
Am 12.12.18 um 19:38 schrieb Gene Heskett:
On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
Am 12.12.18 um 17:32 schrieb Gene Heskett:
On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
I only recently reconfigure some older servers to use the
application
Am 12.12.18 um 17:32 schrieb Gene Heskett:
> On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
>
>> I only recently reconfigure some older servers to use the application
>> amgtar instead of "GNUTAR"
>>
>> Now my old exclude lists are
I only recently reconfigure some older servers to use the application
amgtar instead of "GNUTAR"
Now my old exclude lists aren't read anymore and the manpages aren't as
informative as I would need them ;-)
How to configure an exclude-list for amgtar, per DLE?
I tried:
define dumptype global
Am 05.12.18 um 04:11 schrieb Uwe Menges:
> On 10/17/18 10:37 PM, Ashwin Krishna wrote:
>> The previous call was to understand the pain points of the community
>> in general for governance and contributions. Based on the feedback
>> from those who attended, we have come up with the action plan as
Am 30.11.18 um 19:40 schrieb Debra S Baddorf:
> Well, from comp sci courses 20 years ago, the best algorithm to fill the
> tapes (or the “Bag” in CS class)
> is the Greedy Method.
[..]
a quick thanks for now ... quite busy here, I will report back when I
find the time to try that.
Stefan
Am 28.11.18 um 20:24 schrieb Debra S Baddorf:
> Not sure if these paragraphs are still in the example config files or not;
> I’ve hung onto them because they
> were so useful.In case they help you:
[..]
thanks for sharing that, this somehow corresponds to a task I am
starting over the
I know it was topic here already ... long ago, maybe someone knows a
solution to this already:
I have files owned by root that get correctly amdump-ed but throw ugly
errors/warnings when I run my daily amcheck via cron (to remind admins
to change tapes if necessary).
So I get for
Am 28.11.18 um 15:47 schrieb Chris Nighswonger:
> So why won't amanda dump and tape at the same time?
It does normally, that is what the holding disk is for.
More details might lead to better suggestions.
Show your amanda.conf etc
Am 16.11.18 um 18:53 schrieb Chris Hoogendyk:
I've found it encouraging to see all the activity on the Amanda users
list recently.
Same here, nice to see the communication/cooperation.
Am 13.11.18 um 13:02 schrieb Jose M Calhariz:
On Tue, Nov 13, 2018 at 11:10:03AM +0100, Stefan G. Weichinger wrote:
man amrecover says:
"The GNU readline library is used to provide command line history and
editing if it was built in to amrecover."
I am unsure if that means we s
man amrecover says:
"The GNU readline library is used to provide command line history and
editing if it was built in to amrecover."
I am unsure if that means we should have command completion as well
within amrecover?
I get history via arrow keys, but no completion for paths or filenames.
Am 09.11.18 um 06:19 schrieb Nathan Stratton Treadway:
> So, you were following the the instructions found in the "Using the new
> chg-disk:' section of the How_To:Set_Up_Virtual_Tapes wiki page that
> Stefan mentioned earlier in this thread, right?
>
>
Am 08.11.18 um 21:01 schrieb Gene Heskett:
> On Thursday 08 November 2018 12:50:46 J Chapman Flack wrote:
>
>> On 11/8/18 12:27 PM, Gene Heskett wrote:
>>> I certainly don't have any objections, and I wasn't aware there were
>>> anywhere near that many choices. Can you PM me a list?
>>
>> In
Am 08.11.18 um 22:55 schrieb Stefan G. Weichinger:
Am 08.11.18 um 22:52 schrieb Stefan G. Weichinger:
manpage says:
exclude [ list | file ][[optional][append][ string ]+]
Default: file. Exclude is the opposite of include and specifies files
that will be excluded from the backup. The format
Am 08.11.18 um 22:52 schrieb Stefan G. Weichinger:
manpage says:
exclude [ list | file ][[optional][append][ string ]+]
Default: file. Exclude is the opposite of include and specifies files
that will be excluded from the backup. The format of the exclude
expressions depends
Am 08.11.18 um 22:49 schrieb Stefan G. Weichinger:
Am 08.11.18 um 22:06 schrieb Debra S Baddorf:
Ah, good! What does “file” do in your include line?
exactly
include file ...
means "read include regex(es) from that file
you want
include "./[a-g]*"
and not "includ
Am 08.11.18 um 22:06 schrieb Debra S Baddorf:
Ah, good! What does “file” do in your include line?
exactly
include file ...
means "read include regex(es) from that file
you want
include "./[a-g]*"
and not "include file"
see manpage
Am 08.11.18 um 18:52 schrieb Chris Miller:
> Hi Stefan,
>
>
>
> *From: *"Stefan G. Weichinger"
> /etc should contain only config
> In my case, I will have a set of config -- pro
Am 08.11.18 um 19:11 schrieb Nathan Stratton Treadway:
> On Thu, Nov 08, 2018 at 09:40:37 -0800, Chris Miller wrote:
>> bash-4.2$ ls -l /net/nas1/d0/Mail.TCLC.org/
>> :
>> -rwxr-xr-x. 1 amandabackup disk 1110 Nov 8 09:12 state
>> drwxr-xr-x. 2 amandabackup disk 0 Nov 5 10:17 vtape.00
>> :
>>
Am 08.11.18 um 18:11 schrieb Chris Nighswonger:
> Thu Nov 8 05:27:11 2018: thd-0x1c8f200: sendbackup: Nothing found to
> include for disk /netdrives/CAMPUS/sz
"nothing found"
Am 08.11.18 um 13:56 schrieb Chris Nighswonger:
> Why not form a document git repo to house just Amanda docs?
Sure, why not ... I just want to avoid creating something noone
contributes to. Let's collect some opinions, decide and then collect
knowhow ;-)
Am 08.11.18 um 12:46 schrieb Gene Heskett:
> On Thursday 08 November 2018 05:02:30 Stefan G. Weichinger wrote:
>
> For those who might be interested, the link on my web page that leads
> to "Genes-os9-stf", now has a new readme for GenesAmandaHelper, and a
> fresh b
Am 07.11.18 um 18:25 schrieb Chris Miller:
> Hi Austin,
>
> Thanks very much. Your comments have been very helpful, and I appreciate
> the obviously considerable amount of time you spent to help me. I'm much
> farther along on this project as a result. I have no idea how I'm going
> to verify
201 - 300 of 1516 matches
Mail list logo
