Am 2016-07-06 um 20:12 schrieb Jean-Louis Martineau:
In the dumptype? disklist?
run: amadmin CONF disklist | grep -i holdingdisk
$ amadmin myconf disklist | grep -i holdingdisk
HOLDINGDISK AUTO
HOLDINGDISK AUTO
HOLDINGDISK AUTO
Am 2016-07-06 um 18:51 schrieb Debra S Baddorf:
Is there room on your holding disk? I noticed earlier that you said the holding
disk "reserve”
was at 40. Since I have nothing but amanda stuff on my holding disk, I set
mine to 02 percent
reserved for incremental type backups.
However, if
Am 2016-07-06 um 19:13 schrieb Jean-Louis Martineau:
It wait for an operator because you set an interactivity. And that's why
it continue to scan the changer, to detect change in it.
I didn't set an interactivity intentionally.
But the config has grown and that setting might come from the
Am 2016-07-05 um 17:21 schrieb Jean-Louis Martineau:
> On 30/06/16 03:06 AM, Stefan G. Weichinger wrote:
>> Am 2016-06-27 um 11:07 schrieb Stefan G. Weichinger:
>>> Am 2016-06-21 um 10:38 schrieb Stefan G. Weichinger:
>>>
>>>> If the admin forgets to ch
Am 2016-07-05 um 16:25 schrieb Stefan G. Weichinger:
> Interesting: I don't have any strategy noinc in that config
>
> $ amadmin myconf config | grep -i noinc
> $
I see where that comes from:
JLM once pointed me at doing this:
define dumptype dle_exclude {
pigz-tar
}
# crontab
5
Am 2016-07-03 um 21:12 schrieb Stefan G. Weichinger:
> In general I would like to know what makes amanda search over and over
> again. Is it possible that the missing changerfile lead to this? As in
> "amanda can't remember it has looked into these slots already" ?
We re-
Am 2016-07-01 um 18:42 schrieb Debra S Baddorf:
I’m pretty sure I’ve deleted the robot contents file* and it refilled itself
whenever it next
read each tape. After that, the barcode reader cues it to which one is in
which particular
slot.
*I deleted the file more than once, I think, when
Am 2016-06-30 um 17:28 schrieb Jason L Tibbitts III:
You don't actually say what kind of library you have so you aren't going
to get any responses like "I have the same one and it works OK for me;
here's my config."
Yes, you are right. For now I can only look at /proc/scsi/ :
Vendor: HP
Am 2016-06-27 um 11:07 schrieb Stefan G. Weichinger:
Am 2016-06-21 um 10:38 schrieb Stefan G. Weichinger:
If the admin forgets to change tapes every week and the next tape to use
is NOT in the library, amanda goes wild and doesn't stop scanning for
the next tape ... it goes through the 8 slots
Am 2016-06-27 um 21:19 schrieb Debra S Baddorf:
(I’ve been on vacation …) But I HAVE had occurrences when the correct tape
isn’t in the library. Amanda will search through my whole library, but only
once.
The parameters you quoted seemed reasonable to me.FWIW, I’m running on
Linux,
Am 2016-06-21 um 10:38 schrieb Stefan G. Weichinger:
> If the admin forgets to change tapes every week and the next tape to use
> is NOT in the library, amanda goes wild and doesn't stop scanning for
> the next tape ... it goes through the 8 slots over and over again and
> even spaw
fellow amanda-users,
at a customer we saw the following happen:
amanda-3.3.5 (we went back as 3.3.9 isn't yet working fine in gentoo
linux), an 8-slot tape library.
As long as the next tape(s) are in the library: everything great
If the admin forgets to change tapes every week and the next
Am 2016-06-13 um 09:11 schrieb Traugott Simon:
> Hello List,
> Hello Stefan,
>
> how did it went out?
the amsamba provided by JLM works fine here so far!
Am 2016-06-09 um 14:11 schrieb Jean-Louis Martineau:
> Attaching it again.
>
> You might need to change the first and the 'use lib' line to match your
> installation.
thanks a lot, the attachment got caught in my spam-filtering.
amcheck looks good now, first amdump test running now.
Am 2016-06-09 um 13:42 schrieb Jean-Louis Martineau:
> On 09/06/16 03:00 AM, Stefan G. Weichinger wrote:
>> Am 2016-05-27 um 09:23 schrieb Traugott Simon:
>>> Hello again,
>>> here you have the full anonymized report from amreport
>>>
>>> http:
Am 2016-06-09 um 09:00 schrieb Stefan G. Weichinger:
> Am 2016-05-27 um 09:23 schrieb Traugott Simon:
>> Hello again,
>> here you have the full anonymized report from amreport
>>
>> http://pastebin.com/MXgVFfb6
>
> I hit this as well with a Debian Jessie
Am 2016-05-27 um 09:23 schrieb Traugott Simon:
> Hello again,
> here you have the full anonymized report from amreport
>
> http://pastebin.com/MXgVFfb6
I hit this as well with a Debian Jessie client.
Any news or fixes ahead for this?
Am 04.05.2016 um 23:00 schrieb Jean-Louis Martineau:
> It's not possible to exclude a DLE
>
> What I would do:
> Add a new empty dumptype (dle_exclude)
> Make the dle you want to exclude inherit from that dumptype
>
> and run: amdump CONF -oDUMPTYPE:dle_exclude:strategy=skip
> the day you do not
Am 2016-04-20 um 09:11 schrieb Stefan G. Weichinger:
> It depends ;-) I think it would be more elegant to not have to use
> "amadmin force". Everything covered by the amanda config, no need to
> remember two things. But that's academic discussion in a way ;-)
additional q he
Am 2016-04-22 um 08:08 schrieb Traugott Simon:
> I have filed a bug report about this at Samba and Debian:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821801
> https://bugzilla.samba.org/show_bug.cgi?id=11854
Thanks for doing that. bug-reports lead to bug-fixing. Sometimes ;)
Am 20.04.2016 um 15:30 schrieb Jean-Louis Martineau:
> It's hard to fix documentation when user don't tell how to improve it.
> Can you tell us the additional stuff?
You are right, sorry.
I just wanted to wait for an example, maybe I misunderstood something etc
My definitions so far, note
Am 2016-04-19 um 01:06 schrieb Debra S Baddorf:
> I forgot to reply — I’ve just started using specific DLEs inside of
> disklist (I had been creating differently named dumptypes inside of
> amanda.conf) so I’ll have to look at that too. But I also use named
> dumptypes inside of other named
Am 2016-04-15 um 11:41 schrieb Tobias Köck:
> Hi there,
>
> as reported before I have the same problem.
>
> I have tried the newest update it didn't work, too.
>
> At the moment I have reverted to Samba version
>
> 4.1.17+dfsg-2
I try to use amsamba-application with amanda 3.3.9 on gentoo.
Am 2016-04-01 um 19:04 schrieb Debra S Baddorf:
> Yes, put a link for the disklist.
> Copy the amanda.conf but change:
>
> dumpcycle 0 # the number of days in the normal ARCHIVE cycle
> tapecycle 9000# some infinite number; always fresh tape for archives
> runtapes 3#
(3rd try, as my mails don't seem to get through to the list)
->
I am asked to come up with an archive setup using WORM tapes (LTO6).
There should be yearly backups written to those tapes and stored away.
Any clever tricks on how to set that up with as little overhead as
possible? I'd like to
Am 2016-01-27 um 00:04 schrieb Uwe Menges:
> On 01/26/16 12:27, Stefan G. Weichinger wrote:
>> fedora tells me to use star:
>>
>> https://fedoraproject.org/wiki/SELinux_FAQ#How_can_I_back_up_files_from_an_SELinux_file_system.3F
>
> I think this is outdated, GNU tar s
Am 2016-01-27 um 21:37 schrieb Jean-Louis Martineau:
> $ man amgtar
>SELINUX
>
>Default "NO". If "YES", gnutar will preserve SELinux extended
>attributes on Linux. This corresponds to the --selinux gnutar
>option. Requires a GNU Tar with nonstandard
greetings ...
after moving place I didn't run my amanda server for some time now.
today I fired it up to test new amanda 3.3.8 and backup my new fedora 23
machine.
unfortunately I hit problems with selinux, it blocks amandad/tar from
accessing stuff.
Aside from the details here, is there a
Am 2016-01-26 um 12:48 schrieb Gerrit A. Smit:
> Stefan G. Weichinger schreef op 2016-01-26 12:27:
>
>>
>>
>> (and no, don't tell me to disable selinux completely, please)
>>
>
> Still a kind of disable:
> switch to 'permissive' and get a better view
Am 2016-01-12 um 10:06 schrieb Tobias Köck:
> There seem to be a similar problem with smbclient 4.33.
>
>
>
> It works with
>
>
>
> smbclient --version
>
> Version 4.1.17-Debian
>
>
>
> Either the smbclient 4.33 has a problem and/or AMANDA cannot handle the
> new smbclient version.
Am 2016-01-12 um 22:13 schrieb Uwe Menges:
> On 12/28/15 12:43, Gene Heskett wrote:
>> In an effort to learn more about how these 4 settings work, it would be
>> advantageous to have an additional number in each DLE's line of the
>> report that tallies how long it has been since the last full
Are there any known issues with using samba-4.x as smbclient within
amanda-DLEs ?
I face failing backups since upgrading one server to fedora 23 which
brings Samba 4.3.3 (in this case as an ADS domain member server if that
matters).
$ amcheck -c daily samba01 carplan_sr
Amanda Backup Client
Am 2015-09-15 um 15:49 schrieb Robert Heller:
> What does this error mean:
>
> frodo /Users lev 0 FAILED [can't switch to incremental dump]
>
> I *want* to do a level 0 backup. Frodo is a MacMini (running MacOSX). I am
> using AMANDA 2.5.0p2 with a CentOS 5 server (with the stock 2.5.0p2
>
On 18.02.2015 19:43, Jean-Louis Martineau wrote:
On 02/18/2015 01:17 PM, Debra S Baddorf wrote:
(a)oops, I didn’t mean to write plural. Just singular.
amadmin config tape
(b) the flag doesn’t work for me.I’m at version 3.3.7.
RedHat; I compiled from a tar ball.
The
Am 18.02.2015 um 19:43 schrieb Jean-Louis Martineau:
On 02/18/2015 01:17 PM, Debra S Baddorf wrote:
(a)oops, I didn’t mean to write plural. Just singular.
amadmin config tape
(b) the flag doesn’t work for me.I’m at version 3.3.7.
RedHat; I compiled from a tar ball.
On 17.02.2015 18:30, Debra S Baddorf wrote:
So maybe nobody does anything clever. I don’t either.
But it occurs to me that I could at least do a cronjob weekly (or whatever
frequency you need),
in case I forget to log in with at least that frequency, to do
mtx -f /dev/changer
On 16.02.2015 10:02, Gour wrote:
Hello, tried with forums, but got no reply, so I'm trying here now...
I'm considering to upgrade my current backup system consisting of Amanda
and LTO-2 drive/tapes.
My needs are to regularly backlup my desktop machine (2X1TB disks in
raid-1) and
Am 15.02.2015 um 12:09 schrieb Eric Björkvall:
Thanks! This patched also fixed the problem with libUtil.dylib that I
had on x86_64-apple-darwin14.1.0 ( Mac OS X 10.10.2 ). Had to install
swig with homebrew first, seems to be working now.
Will this give a new release soon, with the patch
How do you all handle refilling your library's magazines?
It would helpful to be notified when the library holds less than N
reusable tapes (or $tapes for N runs). Not every library holds all the
tapes configured for one config and amanda shouldn't run out of reusable
tapes on saturday ...
Is
On 15.02.2015 17:12, Jean-Louis Martineau wrote:
On 02/15/2015 10:46 AM, Stefan G. Weichinger wrote:
Am 15.02.2015 um 12:09 schrieb Eric Björkvall:
Thanks! This patched also fixed the problem with libUtil.dylib that I
had on x86_64-apple-darwin14.1.0 ( Mac OS X 10.10.2 ). Had to install
swig
On 15.02.2015 21:45, Jean-Louis Martineau wrote:
Stefan,
I made a new 3.3.7p1 release!!!
It also include a new fix for swig-3.0.5.
I appreciate if you can test it before I announce it to mailing list.
The fix in the comment #6 to require swig is not required. The swig
files should be
How are multiple holding disks used?
Do multiple dumpers write to separate holding disks in parallel?
Is it possible to configure this?
thanks, Stefan
Am 17.12.2014 um 15:12 schrieb Jean-Louis Martineau:
On 12/17/2014 01:15 AM, Stefan G. Weichinger wrote:
So the parallel taping is initiated only when there is more data than
that?
yes, amanda always try to fill tapes.
You can lie to amanda and set the tape length to a smaller value.
OK
Another server:
a sendsize process hangs and hangs ... and I can't kill it or
amcleanup -k ... any ideas aside from rebooting?
Stefan
Is it possible to define a behavior like:
always start with dumping this DLE ?
taperalgo only influences taping ... and starttime only decides *if*
to dump the DLE at all ... right?
Any other trick?
A separate run of amdump comes to my mind ... but that's not ideal.
Thanks, Stefan
Sorry, wrong verb - prioritize :-P
In german it's priorisieren ... so priorize sounded familiar.
Am 16.12.2014 um 13:58 schrieb Jean-Louis Martineau:
starttime to is delay the dump of a dle.
There is no way to order the dump of the dles.
What kind or order do you want?
1 - dle A must start the dump after dle B started the dump.
2 - dle A must start the dump after dle B finished
Am 16.12.2014 um 14:42 schrieb Dennis Benndorf:
Hi Stefan,
did you consider using
dumporder T...
in order start with those DLEs which take the longest time?
I *never* really understood that parameter!
If that does the trick ... sure, we will try :-)
Thanks, Stefan
Another config-question I have:
I have a server with 2 LTO-2 drives, configured as:
--
tapetype LTO2-200
tpchanger chg-multi:{/dev/nst0,/dev/nst1}
changerfile chg-multi-state
taper-parallel-write 2
runtapes 2
--
according to
Am 16.12.2014 um 20:43 schrieb Jean-Louis Martineau:
What's the flush* value?
Did it have enough data to fill more than one tape?
Very likely not.
The holding disk is ~200G which is around one tape.
So the parallel taping is initiated only when there is more data than that?
Thanks!
Stefan
Am 28.07.2014 um 19:24 schrieb Stefan G. Weichinger:
Thanks for the script ... I don't have a changer there ... and I would
have to do the erasing before every single amdump ... because if I do it
for all the tapes in one session, there are no valid backups anymore ;-)
Maybe I just keep
Am 15.12.2014 um 13:43 schrieb Jean-Louis Martineau:
On 12/15/2014 05:37 AM, Stefan G. Weichinger wrote:
I was able to relabel the tape after a
mt -f /dev/nst0 setblk 32768
Is that OK?
It is better to set the blocksize to 0 (variable), that way you can
easily change it in amanda.
If you
Am 05.12.2014 um 00:33 schrieb Debra S Baddorf:
I’ve only got a year’s worth of data on LTO2 tape, so this seems worth doing.
I had older yet
SDLT tapes before that, lots of them. Those I won’t try to convert, but
will save the
heroics until someone absolutely requires some old data.
Is there an official package for amanda on opensuse 11.3 ?
I don't have access to that server yet, so I ask in advance.
amanda.org only shows packages for SLES ...
And the customer prefers packages over installing from source, I assume ;-)
Thanks, Stefan
Am 09.12.2014 um 17:32 schrieb Joi L. Ellis:
https://en.opensuse.org/Archive:Package_list_11.3 lists Amanda-2.6.1
as an available package. If that version is new enough, you can
install it with the usual package manager.
phew ... that is *old*
Maybe I can convince them to let me compile the
Am 09.12.2014 um 17:38 schrieb Gerrit A. Smit :: TI:
For OpenSuSE 13.1, Amanda sits in the standard repository, and for 12.2
too, but for 11.3 (old!!!) I don't know.
I checked this on my own system and on software.opensuse.org
I know that 11.3 is old ... but they told me that had to decide
Am 09.12.2014 um 18:32 schrieb Debra S Baddorf:
Compiling from source is really awfully easy! (as long as you have
a compiler on the machine)
I installed the compiler etc right now ;-)
amanda-3.3.6 needs glib = 2.2.0 ... sigh ... and this box only has 2.0.0 !
It feels odd to have to deal
Am 09.12.2014 um 19:26 schrieb Stefan G. Weichinger:
Am 09.12.2014 um 18:32 schrieb Debra S Baddorf:
Compiling from source is really awfully easy! (as long as you have
a compiler on the machine)
I installed the compiler etc right now ;-)
amanda-3.3.6 needs glib = 2.2.0 ... sigh
Am 13.11.2014 um 23:26 schrieb Jean-Louis Martineau:
Did you build in a clean directory?
make distclean
./autogen
./configure ...
make
If it's a build dependencies, you can try 'make -k; make' or 'make
clean; make'
I just gave it another try and skipped using the package/ebuild from
Am 15.11.2014 um 16:17 schrieb Jean-Louis Martineau:
What is your source file?
Which tarball are you using?
amanda-3.3.6.tar.gz
If you have swig 3.02 or newer, do:
touch perl/*/*.swig perl/*/*/*.swg
make
I have swig 3.0.2
Did that:
$ touch perl/*/*.swig perl/*/*/*.swg
touch:
Has anyone tried to compile latest stable amanda with gcc 4.9.x ?
It fails for me on a fresh gentoo installation.
I'd like to add the specific logs ... it's a bit hard to spot.
-
libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I../config -I../common-src -I../common-src
Am 28.10.2014 um 18:46 schrieb Nathan Stratton Treadway:
GNU tar as called normally by Amanda will automatically detect files
with multiple hard links and will add the second-and-later references to
the archive as links to the first name processed. (See
Am 06.10.2014 um 23:51 schrieb Joi L. Ellis:
We have several SANS here. I'm not their manager so I'm not able to
really be specific as to brand or whatnot, but I know one of them is
setup to replicate itself off-site to a backup SAN, so any hosts
storing files on it get those backed up for
If I use amgtar as amanda application, how does it handle hard links?
A customer tells me he has some pictures in a website and does hardlinks
to save space.
When he restores from amanda he gets several copies of one and the same
picture and no hard links created?
Is that expected behavior?
If I use amgtar as amanda application, how does it handle hard links?
A customer tells me he has some pictures in a website and does hardlinks
to save space.
When he restores from amanda he gets several copies of one and the same
picture and no hard links created?
Is that expected behavior?
Am 28.10.2014 um 09:33 schrieb Stefan G. Weichinger:
If I use amgtar as amanda application, how does it handle hard links?
sorry for the double post, my email client seemed to have stuck (and
obviously hasn't ...)
S
Am 28.10.2014 um 12:36 schrieb Jean-Louis Martineau:
gnutar extract hard link.
See http://www.gnu.org/software/tar/manual/html_node/hard-links.html
Yes, been there ;-) That was what I meant by -h and -H.
But as I understand it I have to toggle the switch at backup time which
means I dump X
Am 25.09.2014 um 17:21 schrieb Stefan G. Weichinger:
Additional info:
they can't use the A/ZManda-Windows-Client because the NTFS-share is
shared from a storage/SAN and not from a dedicated MS Windows Server.
So we have to solve that on the side of the linux server, I assume.
Does
Am 24.09.2014 um 20:04 schrieb Stefan G. Weichinger:
Couldn't I use amsamba as application and let its property GNUTAR-PATH
point to the local star-binary?
Would that work?
As far as I tested this naive approach it does NOT work this way.
Different command line options etc.
I will try
Am 25.09.2014 um 16:12 schrieb Jean-Louis Martineau:
Stefan,
The GNUTAR-PATH property of amsamba is used only for creating the
index and when restoring on local machine.
In this case it will be restored on the local machine, but I have to
check back with the guys at the site.
amsamba use
Additional info:
they can't use the A/ZManda-Windows-Client because the NTFS-share is
shared from a storage/SAN and not from a dedicated MS Windows Server.
So we have to solve that on the side of the linux server, I assume.
Stefan
https://forums.zmanda.com/showthread.php?677-NTFS-File-Permissions
tells me that (a) the community edition does not support star for
Windows shares and (b) that GNU-tar does not preserve NTFS permissions?
Is that still true?
Couldn't I use amsamba as application and let its property
Am 24.07.2014 um 09:44 schrieb Stefan G. Weichinger:
It would be great to have amanda test for DLEs being overdue more than X
days and email/warn me.
Might be scripted with amadamin conf due, right, but I assume it would
be better to add it as a feature either to amcheck (run at a specific
Am 05.08.2014 um 11:42 schrieb Stefan G. Weichinger:
Always learning, failing, learning ...
At a second look I found a valid version of the tapelist on a tape from
last week.
S
Is there a way to reconstruct the tapelist from the amanda logs?
I messed up a tapelist and now this config doesn't know about the
available tapes anymore ... unfortunately my amanda-backups from
/etc/amanda only contain ruined versions of tapelist.
Any ideas?
Thanks, Stefan ;-)
Am 05.08.2014 um 11:34 schrieb Olivier Nicole:
Stefan,
I know it doies not answer your question, but after each run of amdump,
I run a script that rsync all amanda files/config/indexes/etc. to a
different server.
I also keep a rotation of 10 backward copies of tapelist.
Plus the whole
At a customer I get this:
$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /mnt/amhold/daily: 592780 MB disk space available, using
589708 MB
slot 1: Device /dev/nst0 use fixed block size of 512 and tapetype use 32768
all slots have been loaded
Taper scan
Am 28.07.2014 11:04, schrieb Stefan G. Weichinger:
At a customer I get this:
$ amcheck daily
Amanda Tape Server Host Check
-
Holding disk /mnt/amhold/daily: 592780 MB disk space available, using
589708 MB
slot 1: Device /dev/nst0 use fixed block size of 512
Am 28.07.2014 17:02, schrieb Jean-Louis Martineau:
mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=64, partition=0.
Tape block size 512 bytes. Density code 0x42 (LTO-2).
Soft error count since last status=0
General status bits on (101):
ONLINE IM_REP_EN
... LTO-2
Am 28.07.2014 17:52, schrieb Jean-Louis Martineau:
What does that mean?
The tape is in fixed 512 bytes block, this is bad.
it should be in variable block size.
I don't know how that comes ... never intentionally set anything here.
Do I have to relabel tapes with amanda 3.3.5 or edit my
Am 28.07.2014 19:13, schrieb Alan Hodgson:
On Monday, July 28, 2014 05:55:40 PM you wrote:
All tapes written with a blocksize smaller than 32K must be rewritten.
They probably needs to be erased before relabeling with a different
block size.
... phew. A bit of a task for a productive
It would be great to have amanda test for DLEs being overdue more than X
days and email/warn me.
Might be scripted with amadamin conf due, right, but I assume it would
be better to add it as a feature either to amcheck (run at a specific
time via cron) or amdump (run after the backups).
This
Am 17.07.2014 12:20, schrieb Jean-Louis Martineau:
Stefan,
amcheck always looked to find only one usable tape.
It could be a good feature to check for more if slots and/or drives are
available.
It's hard to check for more tapes because a tape can become reusable
only after the first is
As far as I remember, amcheck checked all (in my case, 2) drives for
correct tapes when I had runtapes=2 set.
At a customer today we noticed that amcheck only checked/showed the
result for one tapedrive. Is that intentional? Have I missed another
setting here? Shouldn't it check both drives?
Would anyone mind sharing some real world scripts he uses with amanda?
I think of stopping/starting DBs or something like that.
I would appreciate some good templates ;-)
Thanks, Stefan
Am 03.07.2014 14:33, schrieb Stefan G. Weichinger:
Am 03.07.2014 14:27, schrieb Jean-Louis Martineau:
Stefan,
If you have 3.3.5
$ man amanda.conf
eject-volume bool
Default: no. Set to yes if you want the volume to be ejected
after
Amanda wrote data
Am 09.07.2014 16:17, schrieb Stefan G. Weichinger:
Would anyone mind sharing some real world scripts he uses with amanda?
I think of stopping/starting DBs or something like that.
I would appreciate some good templates ;-)
I started playing with the email examples from the docs
Am 09.07.2014 17:13, schrieb Gene Heskett:
On Wednesday 09 July 2014 10:17:03 Stefan G. Weichinger did opine
And Gene did reply:
Would anyone mind sharing some real world scripts he uses with amanda?
I think of stopping/starting DBs or something like that.
I would appreciate some good
Am 09.07.2014 19:06, schrieb John Hein:
I'm not sure about the exact cause of the errors you're seeing, but it
looks like the mailto check will not accept '@' or '.' (or dashes or
underscores or numbers).
To address that, maybe try this patch:
---
Am 09.07.2014 16:17, schrieb Stefan G. Weichinger:
Would anyone mind sharing some real world scripts he uses with amanda?
I think of stopping/starting DBs or something like that.
When I think about this I assume that some sudo-trickery might be
needed, right?
The amanda-user won't
Am 09.07.2014 20:27, schrieb Schlacta, Christ:
Or you could, you know, add Amanda to the sudoers.d folder
Sure, that's what I thought of.
Am 03.07.2014 14:52, schrieb Jean-Louis Martineau:
Read download.php, it tell how to use svn or git.
Follow the link for the development branch in the table, it tell you how
to checkout.
... sorry, my fault, didn't scroll enough.
Thanks, Stefan
Am 02.07.2014 22:12, schrieb Stefan G. Weichinger:
Am 02.07.2014 22:10, schrieb Jean-Louis Martineau:
Better news, it's already in 3.3.1
Check for the eject-volume setting.
pardon? I have 3.3.5 here already.
Looking fwd!
JL, pls provide me what to checkout with svn.
I can't find latest
Am 03.07.2014 14:27, schrieb Jean-Louis Martineau:
Stefan,
If you have 3.3.5
$ man amanda.conf
eject-volume bool
Default: no. Set to yes if you want the volume to be ejected
after
Amanda wrote data to it. It works only with some changer and
Am 29.06.2014 23:27, schrieb Stefan G. Weichinger:
I am currently rewriting my cronjobs to systemd-units and -timers ...
and I do that as well for the daily run of amdump.
Works fine so far.
my question:
It is rather easy to do a mt -f /dev/st0 offl after a successful
amdump
Am 02.07.2014 21:56, schrieb Jean-Louis Martineau:
Stefan,
This feature is already committed for the next major release (3.4).
Wow, I love to hear that!
I assume you could provide a link to the commit?
I'd like to see what you implemented (and maybe comment on that :-) ).
Thanks, regards,
Am 02.07.2014 22:10, schrieb Jean-Louis Martineau:
Better news, it's already in 3.3.1
Check for the eject-volume setting.
pardon? I have 3.3.5 here already.
Looking fwd!
I am currently rewriting my cronjobs to systemd-units and -timers ...
and I do that as well for the daily run of amdump.
Works fine so far.
my question:
It is rather easy to do a mt -f /dev/st0 offl after a successful
amdump, if there is only one tape-device.
I currently use 2 LTO-2 drives
Am 03.04.2014 09:58, schrieb Stefan G. Weichinger:
Am 28.03.2014 10:28, schrieb Stefan G. Weichinger:
Am 28.03.2014 10:17, schrieb Stefan G. Weichinger:
Some DLEs worked for the two problematic hosts, some not:
failed: dumper: [request failed: error sending REQ: write error to:
Broken pipe
Am 07.04.2014 13:35, schrieb Jean-Louis Martineau:
Then you have a different problem, post the client amandad debug files.
Jean-Louis
See one debugfile for a failing amcheck (I think).
If I run amcheck -c daily $onlyonehost it works without problem!
If I run amcheck -c daily I get the
501 - 600 of 1514 matches
Mail list logo
