The labelstr setting changed in 3.4
$ man amanda.conf
labelstr string | MATCH-AUTOLABEL
Default: MATCH-AUTOLABEL. The tape label constraint regular
expression. All tape labels generated (see amlabel(8)) and
used by
this configuration must match the
Hi All,
The attached patch fix amsamba in 3.4.1 to works with newer version of
samba.
In 3.3.9 you also need the patch from
https://github.com/zmanda/amanda/commit/585b2139153f8d4a93ccc796983eedfa5a38e6ce
Jean-Louis
On 06/01/17 09:08 AM, Jean-Louis Martineau wrote:
On 06/01/17 07:18 AM
Steve,
The amanda-client can be run with any user.
The user is compiled in, but it doesn't need to be the same on the
amanda server and amanda-client.
What was the problem?
Jean-Louis
On 09/01/17 02:41 PM, Steve Wray wrote:
For what its worth, this creates problems with inter-operability
Jose,
Thanks for the patch.
I committed the attached patch.
Jean-Louis
On 08/01/17 01:35 PM, Jose M Calhariz wrote:
> I am reviewing the patches used by Debian to build amanda 3.3.9 and
> updating them for amanda 3.4.1. I think some of them are not specific
> to Debian. My plan is to present
On 08/01/17 04:56 PM, Jon LaBadie wrote:
> On Sun, Jan 08, 2017 at 06:35:39PM +, Jose M Calhariz wrote:
>> I am reviewing the patches used by Debian to build amanda 3.3.9 and
>> updating them for amanda 3.4.1. I think some of them are not specific
>> to Debian. My plan is to present the
On 06/01/17 01:47 PM, Stefan G. Weichinger wrote:
Am 2017-01-06 um 19:42 schrieb Jean-Louis Martineau:
3.3.9 will not work with newer samba, you must use 3.4.1
The amsamba patch is in the 3_3 branch, you can get it from svn or git.
This server runs
amanda-3.4.1
samba-3.4.5
You point me
On 06/01/17 12:29 PM, Stefan G. Weichinger wrote:
Am 2017-01-06 um 15:08 schrieb Jean-Louis Martineau:
If setting an environment variable is required, try setting it in the
amsamba script before all exec call
$ENV{'LANG'} = 'en_US.UTF-8'
I edited amsamba accordingly, test failed again
On 06/01/17 12:29 PM, Stefan G. Weichinger wrote:
Am 2017-01-06 um 15:08 schrieb Jean-Louis Martineau:
If setting an environment variable is required, try setting it in the
amsamba script before all exec call
$ENV{'LANG'} = 'en_US.UTF-8'
I edited amsamba accordingly, test failed again.
On 06/01/17 07:18 AM, Mike Höhn wrote:
> Am Freitag, 6. Januar 2017, 11:40:44 schrieb Stefan G. Weichinger:
>> Anyone using smbclient for backups with late amanda?
>> If yes, which version of samba?
> Stefan,
>
> I've had the same problems with samba 4.4.5 and amanda 3.3.9 on Slackware.
> I had
Automatically dumping the amanda configuration is complicated
* output of 'amgetconf build.config_dir' # default to /etc/amanda
* /etc/amanda/security.conf # in 3.4.2: output of 'amgetconf
build.security_file'
* Must check all includefile directive from $config_dir/amanda-client.conf
Jose,
The patch is good and I committed it.
Thanks for reporting the issue.
Jean-Louis
On 03/01/17 02:51 PM, Jose M Calhariz wrote:
> A user of amanda on Debian have sent me a patch to fix a problem in
> amanda 3.3.8. I do not know enough perl to validate the patch. But a
> quick look to the
On 17/12/16 12:27 PM, Jean-Francois Malouin wrote:
* Jean-Louis Martineau <jmartin...@carbonite.com> [20161216 12:10]:
On 16/12/16 10:33 AM, Jean-Francois Malouin wrote:
This config has 'taper-parallel-write' set to 2 and during the amdump
run both tape drives were in use at the sam
On 16/12/16 10:33 AM, Jean-Francois Malouin wrote:
This config has 'taper-parallel-write' set to 2 and during the amdump
run both tape drives were in use at the same time at some point. Could
this explain the discrepancy between both outputs?
yes, amtoc print the dump in the order they are
Jean-Francois,
amtoc was not fixed for the new log file format in 3.4
Try the attached patch.
Jean-Louis
On 15/12/16 02:46 PM, Jean-Francois Malouin wrote:
Hi,
Still getting acquainted with amanda-3.4.1 new feature but for the
moment I'm having problems correctly generating table-of-content
Can you run 'amcheck -c DS1 cyber' on the server (mums.jgcomp.com)?
Jean-Louis
On 15/12/16 10:23 PM, Jon LaBadie wrote:
I have finally gotten amdump_client "trying" to work.
Had to modify the systemd amanda@.service unit file.
Of the three amdump_client commands, list works, check
fails
On 09/12/16 12:24 PM, Jon LaBadie wrote:
On Fri, Dec 09, 2016 at 09:48:17AM +0100, Heiko Schlittermann wrote:
Hello,
Jon LaBadie (Do 08 Dez 2016 19:36:07 CET):
Is amservice a client-side program or server-side?
In Fedora packages it does not come in with the client package.
On 08/12/16 01:36 PM, Jon LaBadie wrote:
Is amservice a client-side program or server-side?
In Fedora packages it does not come in with the client package.
Playing with amanda_client I get this error:
amdump_client: open3: exec of /usr/sbin/amservice -f /dev/null \
-s
On 08/12/16 03:56 AM, Heiko Schlittermann wrote:
Jon LaBadie (Do 08 Dez 2016 06:05:17 CET):
I'm thinking of systems, like laptops, that are booted
irregularly and are unlikely to be running during the
normal backup time period.
…
You're looking for amdump_client, aren't you?
On 04/12/16 02:27 AM, Jon LaBadie wrote:
My first contact with this config file. If I properly
understand its purpose I think the comment section has
an error.
# If a program and symbolic name is not listed, then the #
# configured binary is allowed to be run as root. #
On 29/11/16 03:33 AM, Stefan G. Weichinger wrote:
Am 2016-11-28 um 15:16 schrieb Jean-Louis Martineau:
Are you running with the aggregate-slots.diff patch I already sent?
Can you send me your amanda.conf and the changer state files?
ah, I seem to have found it, although I don't know how
On 28/11/16 08:46 AM, Stefan G. Weichinger wrote:
Am 2016-11-28 um 14:28 schrieb Jean-Louis Martineau:
On 26/11/16 10:25 AM, Stefan G. Weichinger wrote:
$ amtape vtape inventory
slot 1:1: label vtape-002-001 (vtape-004) [retention-no]
It is strange that the meta label is vtape-004
On 26/11/16 10:25 AM, Stefan G. Weichinger wrote:
Am 2016-11-26 um 14:08 schrieb Jean-Louis Martineau:
Are you sure amanda can reuse one of those tapes?
The 'amtape vtape inventory' command should list the retention of each
tape.
$ amtape vtape inventory
slot 1:1: label vtape-002-001 (vtape
-Louis Martineau
On 26/11/16 05:54 AM, Stefan G. Weichinger wrote:
Am 2016-11-25 um 15:23 schrieb Jean-Louis Martineau:
What is the result of 'amtape vtape show'?
Any error in the debug files?
$ amtape vtape show
mount: UUID=5a5a9927-995f-4f0f-98ff-d222561f84ff kann nicht gefunden werden
scanning all 20 slots
What is the result of 'amtape vtape show'?
Any error in the debug files?
On 25/11/16 09:03 AM, Stefan G. Weichinger wrote:
Am 2016-11-25 um 14:29 schrieb Jean-Louis Martineau:
Stefan,
Try the attached aggregate-slots.diff patch.
applied, does not change behavior:
ERROR: No acceptable
Stefan,
Try the attached aggregate-slots.diff patch.
Jean-Louis
On 25/11/16 03:29 AM, Stefan G. Weichinger wrote:
Am 2016-11-24 um 17:52 schrieb Jean-Louis Martineau:
But amcheck fails:
$ amcheck vtape -t
Amanda Tape Server Host Check
-
mount: can't find UUID
On 24/11/16 05:19 AM, s...@amanda.org wrote:
compiled 3.4.1 on three machines today, works fine on 2 of them, on
the third I have an issue with my vtapes on the external disks.
I run an aggregated changer combining 2 external disks with 20 vtapes
each.
define changer disk1 {
-Louis Martineau
works even if the client is behind a NAT
Jean-Louis Martineau
Thanks for reporting the problem,
The attached patch fix it.
Jean-Louis
On 10/02/16 02:56 PM, Jose M Calhariz wrote:
In preparation for a new amanda 3.3.8 in Debian I created a preview
package for jessie that I testing on my backup machine.
I found that I can't backup some DLE. Looking into
and modifiable only by root.
o On restore, check the restore_by_amanda_user setting if not run
by root.
Jean-Louis Martineau
M Calhariz wrote:
On Wed, Feb 03, 2016 at 05:05:03PM -0500, Jean-Louis Martineau wrote:
On 03/02/16 04:54 PM, Jose M Calhariz wrote:
On Wed, Feb 03, 2016 at 04:40:09PM -0500, Jean-Louis Martineau wrote:
$ rm common-src/amcrc32chw.lo
As a workaround, add '-msse4.2' to the 'CFLAGS =' line in
RRORS -MT
amcrc32chw.lo -MD -MP -MF .deps/amcrc32chw.Tpo -c -o amcrc32chw.lo amcrc32chw.c
$ make
$ cd ..
$ make
Jean-Louis
On 03/02/16 04:11 PM, Jose M Calhariz wrote:
On Wed, Feb 03, 2016 at 03:52:45PM -0500, Jean-Louis Martineau wrote:
The compilation flag do not have the -msse4.2 flag as expecte
SSH-AGENT Wed Feb 03 21:28:15
CWD=~/source.amanda/amanda/amanda-3.3.8/common-src
cal@picard[3592]>
On Wed, Feb 03, 2016 at 04:21:22PM -0500, Jean-Louis Martineau wrote:
It correctly detect it must use the -msse4.2 flags, but why it doesn't use
it??
Can you try to manually comp
A-Za-z]msse4.2[^0-9A-Za-z]' 2>&1
Jean-Louis
On 03/02/16 03:36 PM, Jose M Calhariz wrote:
On Wed, Feb 03, 2016 at 02:43:49PM -0500, Jean-Louis Martineau wrote:
Hi,
Which gcc version? 4.3 and above should have theses instructions.
$ gcc --version
gcc --version
gcc (Debian 4.9.2-10) 4.9
On 03/02/16 04:54 PM, Jose M Calhariz wrote:
On Wed, Feb 03, 2016 at 04:40:09PM -0500, Jean-Louis Martineau wrote:
$ rm common-src/amcrc32chw.lo
As a workaround, add '-msse4.2' to the 'CFLAGS =' line in
common-src/Makefile
Does -msse4.2 means it is needed a relatively recent i386 CPU
Hi,
Which gcc version? 4.3 and above should have theses instructions.
$ gcc --version
Jean-Louis
On 03/02/16 02:20 PM, Jose M Calhariz wrote:
Hi,
I am trying to compile amanda 3.3.8 on Debian but I get some errors
during linking phase. Both on Debian sid or jessie.
The error is:
/bin/sh
On 27/01/16 03:06 PM, Stefan G. Weichinger wrote:
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,
On 27/01/16 11:47 AM, jflack wrote:
On 01/26/2016 05:51 PM, Jean-Louis Martineau wrote:
What is the taperalgo setting?
largestfit
man amanda.conf:
largestfit
The largest dump image that will fit on the current tape.
The full dump is too large to fit on the tape, so
Hi,
You can also use 'amadmin CONF find' to list all available dump.
On 26/01/16 03:45 PM, jflack wrote:
Hi,
First time -users question, I have inherited an amanda installation.
My question might be a FAQ.
I notice that if I run 'amadmin daily info' after a daily run,
I see a bunch of
Hello,
The Amanda core team is pleased to announce the release of Amanda 3.3.8.
Source tarballs are available from
* http://www.amanda.org
* https://sourceforge.net/project/showfiles.php?group_id=120
Binaries for many systems are available from
*
On 13/01/16 05:47 PM, Focus1 IT wrote:
I have run amdump with our configuration file numerous times, results
are the same.
My director did supply me with a helpful clue he uncovered this
afternoon, it appears that amdump is trying to backup incorrect
directories... For example, instead of
: 01865 617697 ext: 17697
*From:*Jean-Louis Martineau [mailto:martin...@zmanda.com]
*Sent:* 10 December 2015 16:51
*To:* David Simpson <david.simp...@eng.ox.ac.uk>; amanda-users@amanda.org
*Subject:* Re: failed to change dir (error from selfcheck / amcheck)
On 10/12/15 11:45 AM, David Simpson
Tel: 01865 617697 ext: 17697
*From:*Jean-Louis Martineau [mailto:martin...@zmanda.com]
*Sent:* 10 December 2015 16:17
*To:* David Simpson <david.simp...@eng.ox.ac.uk>
<mailto:david.simp...@eng.ox.ac.uk>; amanda-users@amanda.org
<mailto:amanda-users@amanda.o
On 10/12/15 10:37 AM, David Simpson wrote:
Hi
I’m seeing this from an amcheck /Config/ at the moment. If I comment
the DLE it warns about, it’ll happen on the next one too.
/service selfcheck: selfcheck: Failed to
chdir(/export/some/directory/): Permission denied/
/Do the amanda user
Road Campus Research Building
Oxford, OX3 7DQ
Tel: 01865 617697 ext: 17697
*From:*Jean-Louis Martineau [mailto:martin...@zmanda.com]
*Sent:* 10 December 2015 16:17
*To:* David Simpson <david.simp...@eng.ox.ac.uk>; amanda-users@amanda.org
*Subject:* Re: failed to change dir (error from sel
On 18/11/15 11:35 AM, David Simpson wrote:
Hi Deb, Jon
Hopefully this will cover both responses. Thanks again...
Holdingdisk is already configured as 2000GB that as much as I can do on that
server.
Chunksize I have already set to 500MB
Advice on 1/4 of tape size for max DE noted.
Archive
On 18/11/15 05:54 AM, Chris Lee wrote:
Hi All,
As I read this thread and think of the many others I have seen with
people talking of multiple configs in order to make things work I
think maybe there is scope for a feature request for an enhanced
holding disk config:
A holding disk system
On 05/11/15 02:01 AM, Dennis Benndorf wrote:
Hello,
I am facing a bug when running amfetchdump like this:
/usr/local/sbin/amfetchdump --exact-match -lan -O /dir config
client dle timestamp/
Error message is:
/ERROR: -p is not compatible with -n/
But -p is not set and in the
ne 206/207 (amanda3.3.7p1) to
usage("-p is not compatible with -n")
if ($opt_pipe and $opt_no_reassembly);
fixes it, because -p and $opt_pipe goes together
Could you please commit the patch?
Regards,
Dennis
Am 05.11.2015 um 13:53 schrieb Jean-Louis Martineau:
On 05/11/15
Hi Orion,
I appreciate that you post your scripts, it allow me to see how user use
amanda and how I can improve it.
On 03/11/15 06:22 PM, Orion Poplawski wrote:
In case anyone finds these useful:
https://git.nwra.com/nwra-it/amanda/tree/master
This repository contains various scripts in
On 03/11/15 11:12 AM, Steven Backus wrote:
It can only be done by monitoring the system and only you can do it.
Can you give me some advice how to do this? And sorry there wasn't
enough information.
Do any processes use CPU? (ps, top command)
What are they doing? (strace command)
Do the index
Chris,
You can use the following command to list all amanda dump in holding disk:
$ amadmin CONFIG holding list -l
What's in the holding (with the 'ls' command), it looks you have a lot
of files not recognized by amanda.
Jean-Louis
On 30/10/15 01:14 PM, Chris Nighswonger wrote:
No
When reporting a problem, can you at least report which version you are
using.
We also need a way to reproduce the issue, the minum it hat case is the
amlabel command line argument and all setting related to the changer.
Bug get fixed a lot faster when enough information to reproduce the
Steven,
Maybe your disk was corrupted before that backup was done, and the
backup is corrupted.
Try to restore from an older backup.
Jean-Louis
On 08/10/15 12:09 PM, Steven Backus wrote:
I'm having a problem with a restore:
/local/sbin/amrecover gen2 -oauth=local
AMRECOVER Version 3.3.7.
On 06/10/15 09:20 AM, Gene Heskett wrote:
Greetings all;
I have been following the recomendations spit out by amcheck as I am
needing to restore a machine after the machine in that spot failed.
I am now down to this error, and apparently something in the installer
did setup the amanda-client
Gunnar,
Do the number by DLE always differ?
Are you using a holding disk?
Can you monitor the server to find some bottleneck, memory, cpu,
network, disk I/O, ...
Jean-Louis
On 03/09/15 02:49 PM, Gunnarsson, Gunnar wrote:
Hi,
See below slow down in avg tp write rate after having upgraded
systemd (which you probably already run) replace xinetd.
Most services are already started by systemd.
We just need systemd configuration files for amanda.
Jean-Louis
On 26/08/15 08:47 PM, Gene Heskett wrote:
Heads up in case yopu haven't heard it yet.
From a comment I just read on another
Jose,
See https://lists.gnu.org/archive/html/bug-tar/2014-09/msg6.html
It is a known bug in gtar-1.27 and 1.28
The bug is already fixed but is not released yet.
Downgrade to gtar-1.26 or compile gtar from the git repository.
Jean-Louis
On 20/08/15 10:25 AM, Jose M Calhariz wrote:
Hi,
On 31/07/15 02:51 AM, harpingon wrote:
Hello
This is probably a stupid question, but I'm not finding the answer by searching
I'm backing up a SPARC/Solaris 11 server with amzfs-sendrecv via pfexec , and I do get my
dumps okay. They show up on the amanda server tape files as ZFS shapshot
On 01/08/15 03:35 AM, Jon LaBadie wrote:
When replying to Gene H's thread I quoted the
amanda.conf(5) manpage
estimate [ client | calcsize | server ]+
I thought I knew the meaning of the + at the
end of parameter specifications -- the final
term can be repeated. But now I'm not certain.
2:28 PM, Jean-Louis Martineau wrote:
Chris,
Amanda should continue to do the backup to holding disk while it wait
for a new tape, this is constructive work.
You could remove the interactivity setting if you don't what its
behaviour.
What can be done is to add a timeout to the intertivity
Chris,
Amanda should continue to do the backup to holding disk while it wait
for a new tape, this is constructive work.
You could remove the interactivity setting if you don't what its behaviour.
What can be done is to add a timeout to the intertivity plugin to abort
if there is no tape
man ampgsql
Konsole output
STATEDIR
Directory for saving state about backups already made. The
default
is set when Amanda is built by the --with-gnutar-listdir
configure
option.
ampgsql to not use the gnutar_list_dir from amanda-client.conf
You must set
Look for error in the debug file.
Jean-Louis
On 21/06/15 09:01 AM, Kamil Jońca wrote:
When I try to execute:
--8---cut here---start-8---
sudo -u backup amrmtape --cleanup --erase -v alfa alfa-6-100
--8---cut
man amanda.conf
Konsole output
exclude [ list | file ][[optional][append][ string]+]
Konsole output
For GNU-tar, exclude expressions must always be specified as
relative to the top-level directory of the DLE, and must
start with
./. See the manpages for individual
Chris,
Define a new changer and set tpchanger to that changer.
If you don't already define a changer, then also define one for the old
changer.
I would also use a different labeling scheme.
See: man amanda-changers
Jean-Louis
On 16/06/15 02:41 PM, Chris Hoogendyk wrote:
This ought to be a
On 05/26/2015 02:20 AM, Alan Murrell wrote:
OK, so by way of an update I can't seem to make this work. By way
of test, I have tried the following in my DLE for the Windows server:
exclude list /etc/amanda/DailySet1/excludes-server_data
in which I made the following entries:
./Accounting
amrecover can remove everything in the directory you restore to, so it
must not be /, it should always be an empty directory.
Debra, what you say doesn't make sense, if the dle is /var then the /var
path is not in the backup so it can't be restored.
But if the dle is / with and include or
On 05/07/2015 04:50 PM, Gene Heskett wrote:
Thats odd Paul. I was sitting in /home/gene/linucxcnc, and it created a
gene/linuxcnc directory for the recovery. when i asked it to recover the
linuxcnc subdir of /home/gene.
Which dle are you restoring, what is the path inside the dle?
Are you
Jason,
Which taperscan are you using?
The default 'traditional' read all slots.
Try the 'lexical' or 'oldest'.
Jean-Louis
On 04/02/2015 02:20 PM, Jason L Tibbitts III wrote:
I'm running 3.3.6 (but could easily upgrade if it would help). For a
long time I've been wondering about amanda's
release.
Jean-Louis
On 03/30/2015 01:25 PM, Debra S Baddorf wrote:
On Mar 30, 2015, at 11:33 AM, Jean-Louis Martineau martin...@zmanda.com wrote:
On 03/30/2015 04:05 AM, Michael Schmitz wrote:
Hi all,
I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
installed FC21 server
On 03/30/2015 04:05 AM, Michael Schmitz wrote:
Hi all,
I've been using Amanda v2.5 for years an switched to v3.3.6 on freshly
installed FC21 server and all clients (SLES11) a few days ago. My
configuration contains the definition
define dumptype my-dump {
global
auth ssh
it can be because a subprocess write garbage to the socket.
Check the debug files.
Jean-Louis
On 03/30/2015 02:18 PM, Glen Eustace wrote:
A number of weeks ago, I posted a query regarding the failure of one
of our servers with the error
ERROR Request to x failed: tcpm_recv_token:
Greg,
I committed that patch.
amanda should print:
error opening device 'tape:/dev/nst0': Device type tape is not known
Jean-Louis
On 03/24/2015 10:37 AM, Greg Troxel wrote:
Thanks very much for the hint.
It would be nice if instead of that error message one got you tried to
use a tape:
Greg,
Looks like your amanda does not support tape device.
Check for the configuration log file (config.log) to find why.
Maybe some required package are not installed.
Jean-Louis
On 03/24/2015 09:20 AM, Greg Troxel wrote:
I've been quiet, mostly because our amanda installs have been working
What is setgid?
There should be nothing setgid when running amrecover/amidxtaped.
Jean-Louis
On 03/20/2015 01:10 PM, Schlacta, Christ wrote:
So Running an amrecover after following the 15 minute guide gives me a
strange error, and I'm unable to recover..
summary:
Add files to backup using
--src-timestamp 20150208180002 --fulls-only --dst-changer
vtapes-on-spool
--label-template VTAPE-%%% daily
and the “from” changer was the main one in the configuration.
Deb Baddorf
Fermilab
On Dec 5, 2014, at 8:27 AM, Jean-Louis Martineau martin...@zmanda.com wrote:
It is a lot easier
Debra,
The Dle must be in the disklist to be vaulted.
You can keep them in the disklist with 'strategy skip' so that new
backup are not done.
Jean-Louis
On 03/05/2015 07:09 PM, Debra S Baddorf wrote:
I’m testing out AMVAULT for eventually copying some LTO2 tapes to LTO5
(with VTAPES in
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 flag is completely ignored.
I wonder what makes
://sourceforge.net/project/showfiles.php?group_id=120
Documentation can be found at
* http://wiki.zmanda.com
Jean-Louis Martineau
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 with homebrew first, seems to be working now.
Will
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 correctly generated this time.
You can download it
On 02/12/2015 11:05 AM, Stefan G. Weichinger wrote:
How are multiple holding disks used?
Do multiple dumpers write to separate holding disks in parallel?
yes
Is it possible to configure this?
no, it is always done.
thanks, Stefan
Why upgrade to an old version? You should upgrade again.
It's hard to say something because you didn't posted enough information.
I will guess is that amanda need more tape space to do the backup
according to your configuration, you should increase runtapes.
Jean-Louis
On 02/03/2015 03:07
Lozitskiy
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Wednesday, February 04, 2015 9:38 AM
To: dmitry.lozits...@asparona.com; amanda-users@amanda.org
Subject: Re: amanda 2.6.1p2-8 issue
Why upgrade to an old version? You should upgrade again.
It's hard
On 01/25/2015 10:27 PM, Jason L Tibbitts III wrote:
My amanda server has a really large holding disk, because disk is cheap
and because lots of disk striping generally equals better write
performance.
The usual restore operation I have to do is pulling things off of last
night's backup, which
Jens,
Try the attached patch.
Jean-Louis
On 01/26/2015 10:00 AM, Jens Berg wrote:
Hi list,
I compiled amanda 3.3.7 from source which completed successfully.
However, each time I run a command which utilizes libUtil.so, e.g.
amlabel or amcheck I get the following error message:
/usr/bin/perl:
You get error at estimate or at backup time?
Look at the time in the sendsize and sendbackup debug file to find which
one is slow.
On 01/21/2015 02:40 PM, Chris Hoogendyk wrote:
Folks,
I have an Ubuntu 14.04 LTS system running Amanda 3.3.6 server backing
up a Solaris 10 system with Amanda
Older server always do the decompression.
In newer version (3.3.x), server compression is decompressed on the
server and client compression is decompressed on the client.
This bug is fixed in 3.3.6
Jean-Louis
On 01/21/2015 03:41 AM, Schoepflin, Markus wrote:
Hello,
I'm facing an odd
I didn't knew about this new authorization mechanism.
I will add it to amanda, one of the next amanda version will have it.
Jean-Louis
On 01/15/2015 05:49 AM, Dominik Schips wrote:
Hi,
I use Amanda 3.3.6 (Community Edition) with a CentOS 6.6 host (x86_64).
Never had any problems with the use
On 01/14/2015 06:34 AM, Toomas Aas wrote:
I just installed a new Amanda server, version 3.3.6 on FreeBSD 10.1
amd64. There seems to be a cosmetic issue during selfcheck, client
tries to execute something called /usr/bin/sw_vers, which does not
exist (snippet of selfcheck.debug attached).
On 12/19/2014 05:28 PM, Jon LaBadie wrote:
On Fri, Dec 19, 2014 at 03:20:09PM -0500, Jean-Louis Martineau wrote:
On 12/19/2014 02:39 PM, Jon LaBadie wrote:
Following and researching Debra Baddorf's thread raised some questions
in my mind. In one posting, JLM said:
On Wed, Dec 17, 2014 at 01
On 12/19/2014 02:39 PM, Jon LaBadie wrote:
Following and researching Debra Baddorf's thread raised some questions
in my mind. In one posting, JLM said:
On Wed, Dec 17, 2014 at 01:16:32PM -0500, Jean-Louis Martineau wrote:
...
It autoflush is set, they should be flushed first.
All flush
On 12/17/2014 01:15 AM, Stefan G. Weichinger wrote:
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
On 12/17/2014 12:48 PM, Debra S Baddorf wrote:
Expounding on Jon’s ideas: how about, after all the backups are done and
finished for the day.
Then, I run another job
amdump config —no-taper dumphost all-its-DLEs
This would leave them sitting on the holding disk, waiting for tonight’s
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 the dump.
3 - dle A must start the dump after dle B
What's the flush* value?
Did it have enough data to fill more than one tape?
On 12/16/2014 02:05 PM, Stefan G. Weichinger wrote:
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
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 set it to fixed block size, then amanda must use the
It is a lot easier if you can plug the LTO2 tape drive directly on the
machine B, that way you can use amvault to copy the dump directly from
the LTO2 tapes to the LTO5 tapes.
You can do it from both machines:
- run amvault on machine A to copy the dump to vtapes
- transfer the vtapes to
201 - 300 of 1694 matches
Mail list logo