to be the same as on
clients. You can continue using the existing clients.
--
Toomas Aas
of dumps, you
could delay writing dumps to tape until enough of them have gathered
on the holding disk to fill a tape. That is what I am doing here.
Relevant parameters in my amanda.conf:
flush-threshold-dumped 100
flush-threshold-scheduled 100
taperflush 100
autoflush yes
--
Toomas Aas
Tartu
To add an example to Eric's excellent summary:
% /usr/bin/uname -rms
FreeBSD 10.1-RELEASE-p1 amd64
--
Toomas Aas
Tartu linnakantselei arvutivõrgu peaspetsialist
tel 736 1274
mob 513 6493
.
--
Toomas Aas
Tartu linnakantselei arvutivõrgu peaspetsialist
tel 736 1274
mob 513 6493Wed Jan 14 13:31:35 2015: thd-0x803422e00: selfcheck: pid 94228 ruid 1002 euid
1002 version 3.3.6: start at Wed Jan 14 13:31:35 2015
Wed Jan 14 13:31:35 2015: thd-0x803422e00: selfcheck: version 3.3.6
Wed Jan
--
that is the holding disk smooths out the 'bumps' in the actual
backup process.
AFAIK, when writing directly to tape - even virtual tape - only one
client can be dumped simultaneously. When dumping to holding disks,
several dumps can run in parallel.
--
Toomas Aas
solution that I'm missing. So,
if anyone has a success story about backing up filesystem ACLs on
FreeBSD 10 amd64 (with Amanda, of course), I'm all ears :)
Regards,
--
Toomas Aas
separate tape libraries
or drives, just tapes labelled with different labelstr.
By this I don't mean to imply that two separate configs are the best
solution for OP.
--
Toomas Aas
extract tool. On Unix-like systems this is usually done with
dd. I don't have much experience with such things on Windows, but
something similar surely exists.
HTH,
--
Toomas Aas
1500
gbytes and that my tape drive uses LEOM.
For a real life data point, on my LTO4 tape drive with HW compression
enabled I get 900 GB to 1.1 TB.
--
Toomas Aas
to server
run at normal speed (20 MB/s), also scp'ing files from server to
client seems to work normally.
I looked at amandad.timestamp.debug on the server and
amrecover.timestamp.debug on the client, but there are no obvious
errors.
How to troubleshoot this issue?
--
Toomas Aas
Tartu
simultaneously with dumping
these DLEs that are later in the queue.
If it matters, this is Amanda 3.2.0 using vtapes with chg-disk.
--
Toomas Aas
the current behaviour of taper sitting idle much of the time
is caused by combination of 'dumporder sssS' and 'taperalgo first'
that I currently have in my config.
--
Toomas Aas
bug in 3.2.0:
https://forums.zmanda.com/showthread.php?3168-lev-1-FAILED-can-t-dump-in-degraded-mode
I configured a temporary holdingdisk and the problem is solved. Sorry
for the noise.
--
Toomas Aas
: searching oldest reusable volume 'TAPE32'
Sat Nov 24 08:26:21 2012: taper: Amanda::Taper::Scan::traditional
result: 'TAPE32' on file:/backup/drive1 slot 2, mode 2
Sat Nov 24 08:26:29 2012: taper: pid 39920 finish time Sat Nov 24
08:26:29 2012
--
Toomas Aas
On Thu, 11 Oct 2012 Toomas Aas wrote:
On Wed, 10 Oct 2012, Charles Curley wrote:
I believe running amcheck during an amdump run is a harmless error.
It doesn't probably do any harm, but it turns out that in this case
the mail report is still sent, containing these warnings:
WARNING
or amflush seem to be running
WARNING: if they are not, you must run amcleanup
--
Toomas Aas
. However, in case the disk has actually been
repaced on time, the early morning amcheck run might coincide with
amdump in progress. Can this have any bad effects?
--
Toomas Aas
is not that bad. Besides, even
when rsyncing to swappable disks, someone still has to swap these
disks, and rsync does not, AFAIK, have a 'rsynccheck' which could yell
at the operator in a way amcheck does ;)
--
Toomas Aas
the traces of this commented-out host I could
find on the server.
--
Toomas Aas
with Amanda's
scheduling, unless you configure Amanda to do full backups only. Most
of us don't have enough resources to do that...
--
Toomas Aas
where I would set it. I imagine it would be
possible to do it with a cronjob, but I haven't set up anything like
this.
The next scheduled amdump run is tonight at 22:15. I've set up an 'at'
job to make a copy of info file at 22:14, to see if command is still
set to 0.
--
Toomas Aas
BACKUP unforce kuller.raad.tartu.ee /storage/lists
amadmin: no force command outstanding for
kuller.raad.tartu.ee:/storage/lists, unchanged.
How do I get these DLEs out of the 'force' state?
BTW, my Amanda server version is 3.2.2
--
Toomas Aas
affected backup of /, as
indicated by Nathan above.
--
Toomas Aas
34425972 9515844 2215605230%/storage/lists
--
Toomas Aas
9120 MB). Then I looked at the index file of /storage DLE on
server for that day's amdump run, and noticed that all files in the
/storage/lists directory were listed there.
--
Toomas Aas
could still see, and back-up, the masked files.
Tar should be using file system semantics, but like I said, grasping.
I just double-checked and I'm pretty sure I did delete the original
files from the directory. When I umount /storage/lists, the directory
appears empty.
--
Toomas Aas
--listed-incremental
/var/amanda/client/gnutar-lists/kuller.raad.tartu.ee_storage_1.new
--sparse --ignore-failed-read --totals .
1337197794.439383: runtar: pid 34403 finish time Wed May 16 22:49:54 2012
--
Toomas Aas
Tue, 01 May 2012 kirjutas Paul Crittenden paul.critten...@simpson.edu:
What is the proper way of removing a failed tape from the tape rotation?
amrmtape YourConfig TapeLabel
--
Toomas Aas
N, 19 apr 2012 kirjutas Alan Orth alan.o...@gmail.com:
? /bin/tar: ./homes/[a-d]*: Warning: Cannot stat: No such file or directory
What, exactly, does your entry in the disklist look like?
--
Toomas Aas
this:
localhost /export_homes1 /export/homes {
user-tar
include ./[a-d]*
}
--
Toomas Aas
in mind the leap years).
I myself have two Amanda configurations - one that runs on every
weekday and keeps backups for ca 6 months, and another that runs full
backup of everything twice a year and is kept forever.
--
Toomas Aas
workaround?
--
Toomas Aas
see the tape drive. Otherwise
mulitple, possibly contradicting, SCSI commands arriving from multiple
hosts will completely confuse the drive and as result, no host can
really use it.
This is not an Amanda issue, but rather a lower level issue with SCSI
subsystem on the hosts.
--
Toomas
, you lose
only the holdingdisk, which is probably survivable. With one volume,
you stand a good chance of losing the entire server which is not so
good.
--
Toomas Aas
levels you
have to go through during recovery, the faster you can recover).
Is there a configuation parameter we need to set to change this?
'maxpromoteday' is probably what you're looking for.
--
Toomas Aas
about that one too?
--
Toomas Aas
a lot, looks like this helped. I started an amflush, and it
seems to be running successfully. It's flushing the 4th DLE out of 12
as I type this.
--
Toomas Aas
K, 15 dets 2010 kirjutas Jean-Louis Martineau martin...@zmanda.com:
Toomas Aas wrote:
$AMANDA_COMPONENTS = client amrecover ndmp;
That's the problem, it looks like the server code is installed but
it is not in that line.
I don't know how the FreeBSD port collection works
the backups I'll be making from
now on). But I still think that it should work and would like to
understand why it doesn't.
--
Toomas Aas
(perhaps you forgot
to load Amanda::Xfer::Source::Recovery?) at
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Recovery/Clerk.pm line 544.
Bug or PEBKAC?
--
Toomas Aas
=/usr/local/bin/gtar --without-client --without-gnuplot
--disable-s3-device --prefix=/usr/local --mandir=/usr/local/man
--infodir=/usr/local/info/ --build=amd64-portbld-freebsd8.1
--
Toomas Aas
combo.
--
Toomas Aas
On 25.03.2010 07:42, Toomas Aas wrote:
Upgrading tar to 1.22 seems to have made no difference.
Interestingly, having read tonight's mail report to the end, I see that
the DLE in question is reported as having been backed up fine:
FAILURE DUMP SUMMARY:
kuller.raad.tartu.ee /var lev 0
On 25.03.2010 08:03, Toomas Aas wrote:
So it seems that the FAILURE DUMP SUMMARY is incorrect about
listing this DLE as failed.
As a workaround, I switched this DLE to estimate calcsize. Tonight's run
went fine.
--
Toomas
On 23.03.2010 12:03, Toomas Aas wrote:
FAILURE DUMP SUMMARY:
kuller.raad.tartu.ee /var lev 0 FAILED /usr/local/libexec/amanda/runtar
exited with status 1: see
/tmp/amanda/client/TLV/sendsize.2010031502.debug
Upgrading tar to 1.22 seems to have made no difference. Hoping to see some
: sendsize: errmsg is /usr/local/libexec/amanda/runtar
exited with status 1: see /tmp/amanda/client/TLV/sendsize.2010031502.debug
--
Toomas Aas
on a network to a single large-capacity tape drive
or hard disk partition.
-
Backup to disk is a popular requirement these days, and if we say early in
the README that AMANDA can do that then we may increase our sales ;)
--
Toomas Aas
... I
that
might break in your particular environment.
--
Toomas Aas
khalil_noura wrote:
I labeled the tapes when I created a vtape test envirement. when I run amlabel
I get the message : amlabel: label Backup-012 already on a tape.
my amanda.conf file is configured as this :
tpchanger chg-disk# the tape-changer glue script
tapedev
khalil_noura wrote:
is it ok if I send you a copy of my amanda.conf file? I am not sure if
I am missing something on the config file.
If you post it to the list, it is quite likely that someone can point out
whether there is anything wrong with it. Just to make sure, does /dev/nst0
actually
Topper wrote:
head -1 /usr/libexec/amanda/application/abas-stop
#! /bin/sh
That space between ! and / looks terribly suspicious...
--
Toomas Aas
... Like I said before, I never repeat myself!
Sunday 01 March 2009 04:59:54 kirjutasid sa:
Toomas Aas wrote at 11:04 +0200 on Feb 28, 2009:
I have a single-machine (client==server) setup which has been working
well for quite a long time. It's running Amanda 2.5.1p3 on FreeBSD 6.4.
Yesterday I added a new disk to the machine
problem. After adding the new DLE,
the total number of DLEs is now 13. Bad luck?
--
Toomas Aas
way to achieve this.
- Can I specify when not to run any backup process? I would like backs
to run only during system idle time. So is there any setting that can
be done in Amanda?
See above.
--
Toomas Aas
... Show respect to age. Drink good scotch.
Gene Heskett wrote:
I can't find anything in the latest amanda, but tar-1.20's NEWS file says it
now has a --no-check-device configuration option.
Unforch:
[EMAIL PROTECTED] tar-1.20]$ ./configure --no-check-device
configure: error: unrecognized option: --no-check-device
Try `./configure
Friday 07 November 2008 09:38:55 kirjutas peter7:
1. I want to store the backup on-site (on NAS) and then copy it to tapes to
take off-site. Does Amanda support it? How would the restoration from tapes
work if NAS went down?
I've never done something like this, but one topic which is
Brian Bruns wrote:
Here is, I think, the relevant log file from the client machine:
[EMAIL PROTECTED] DailySet1]# tail sendbackup.20080808140957.debug
sendbackup-gnutar: time 0.001: pid 8298: /bin/gzip --fast
sendbackup-gnutar: time 0.002: doing level 0 dump as
listed-incremental to
the tape.
--
Toomas Aas
first, but I
don't have that kind of equipment so I haven't tried.
--
Toomas Aas
Steve Newcomb wrote:
How do I get off this list?
The instructions are below. They are for another list, but this list works
exactly the same:
http://lists.herald.co.uk/pipermail/lois-bujold/2007-December/006849.html
--
Toomas
... It's not an optical illusion. It just looks like one.
[EMAIL PROTECTED] wrote:
Can the clients be upgraded after the server or should it all be done
simultaneously ?
Probably you don't need to upgrade everything at once. My current setup
which works well here is:
Server: 2.5.0p2
Client1: 2.4.4p4
Client2: 2.5.1p3
Client3: 2.4.5
--
Toomas Aas
Gil Vidals wrote:
I'm new to Amanda and I'm preparing to rotate tapes for the first time.
I have an autoloader that holds 10 tapes all under the amanda.conf as
DailySet1. And I just ordered 10 more (new) tapes, but I'm not clear as
to when do I pull out tapes and put in the new ones???
I
. Maybe someone on this list has one, and can point me to some
online docs?
I assume that it is basically a standard SCSI DLT drive and should work
fine with non-Sun server, right?
--
Toomas Aas
... Would a fly without wings be called a walk?
Toomas Aas wrote:
So, it seems very likely that all my problems were caused by this one
corrupt library. I went on and installed the latest available version
from FreeBSD ports, which is 2.5.1p3. We'll see how tonight's run goes.
Tonight's run was fine, except that I had failed to specify
regarding *why* the backup was not done.
Can anyone provide any recommendations based on this vague description?
--
Toomas Aas
--
... If it wasn't for C, we'd be using BASI, PASAL and OBOL!
K, 27 juuni 2007 kirjutas Toomas Aas [EMAIL PROTECTED]:
My Amanda setup is 2.5.1p2 on a single FreeBSD 6.2 server backing up
only itself to vtapes using GNU tar 1.15.1. It has been running well
for over 6 months, but then I screwed things up by splitting up a large
DLE into two smaller ones
by backup:wheel ('backup' is my Amanda user). If I su to backup, I
can manually create files in this directory and walk down to this directory
from / with chdir. /var partition has 25 GB free space. So where's the problem?
--
Toomas Aas
.
--
Toomas Aas
) is about 20 MB/s.
Dumping speed varies greatly, but for level 0s of larger DLEs I see up
to 11 MB/s if using software compression and up to 25 MB/s if not using
software compression).
--
Toomas Aas
of
not having a proper/correct verion gtar ?
This is a well known indication of bad version of GNU tar.
--
Toomas Aas
.
--
Toomas Aas
Steven Settlemyre wrote:
I am looking to restore a disk from one of my machines and am having a
little trouble understanding which report to believe. Using amadmin
find, I see there was a level 0 on 4/12 and again on 4/19.
When I look at the daily reports I see on 4/12:
pop:/files1.0
blocksize 0).
--
Toomas Aas
backup
/usr/local/libexec/amanda/amidxtaped amidxtaped -auth=bsd amdump amindexd
amidxtaped
--
Toomas Aas
Gene Heskett wrote:
On Wednesday 31 January 2007 01:27, Toomas Aas wrote:
Hello!
First, the system details:
FreeBSD 6.2-RELEASE
Amanda 2.5.1p2
GNU tar 1.16
All DLEs use GNU tar for backup
I noticed a strange problem today with this rather new Amanda setup.
Yesterday, a level 0 backup
Gene Heskett wrote:
I wonder if that version of tar is biting us again. Can you back up to
1.15-1 and give that a try?
Some googling found this, which seems related. Looks like downgrading tar
is the way to go. How I miss the good old days of 1.13.25!
Hello!
First, the system details:
FreeBSD 6.2-RELEASE
Amanda 2.5.1p2
GNU tar 1.16
All DLEs use GNU tar for backup
I noticed a strange problem today with this rather new Amanda setup. Yesterday,
a level 0
backup was done of one particular DLE. This DLE is ca 50 GB in size, which
compresses
to
= 0
taper: blocksize= 32768
=== end of file ===
Thanks for any ideas,
--
Toomas Aas
Please ignore my previous message. I shouldn't have killed the terminal
from which I started amdump! Amanda is still in testing on the new
server so amdump doesn't run from cron yet. I started another amdump and
it's happily taping now (until I manage to kill it again).
--
Toomas Aas
Hello!
It's me again with taking my vtapes based config from old Amanda 2.4.4
server to new Amanda 2.5.1p2 server. I have my tapetype definition set
so that one 160 GB partition is divided into 5x50GB vtapes. This is done
considering that on most nights Amanda doesn't really fill the vtape so
the same kind of automation can be
achieved with chg-disk.
--
Toomas Aas
|arvutivõrgu peaspetsialist | head specialist on computer networks|
|Tartu Linnakantselei | Tartu City Office |
skype: toomas_aas
the christmas-time dumps from the holding disk, it hit EOT
at approximately 52 GB. Your data is different from mine, of course, but I
do think that being able to tape this 53128750 kB dump with 40 GB tape
drive and hardware compression cannot be taken for granted.
--
Toomas Aas
Gene Heskett wrote:
On Thursday 30 November 2006 08:19, Uwe M. Kaufmann wrote:
(brought to you by Amanda 2.4.5)
SuSE Linux 10.0
Humm, and why is SuSE serving up such an old version of amanda?
IIRC that version does not support vtapes (but somebody will correct me
I'm sure), so I'm
server's partition table
every day. It also seems to me that such functionality would need to be
programmed separately for each OS - quite a bit of work.
--
Toomas Aas
they were considered as
being out of window by the firewall. Note that the port numbers and timestamps
in these two logs match.
--
Toomas Aas
Aug 24 03:32:57 2006
sendbackup: time 6268.139: 117: strange(?): sendbackup: index tee cannot write
[Broken pipe]
sendbackup: time 6268.140: 93: normal(|): DUMP: Broken pipe
sendbackup debug
--
Toomas Aas
Hello!
I'm planning to upgrade my Amanda server (currently 2.4.5) to 2.5.0p2.
I'm wondering whether GNU tar 1.13.25 is still officially considered a
good version, or is it absolutely required to upgrade to 1.15.1?
I noticed that when installing Amanda from FreeBSD ports, the
installation
Ian Turner wrote:
On Friday 18 August 2006 11:35, Toomas Aas wrote:
BTW, I currently use dump for backups, so gtar is only used for indexes.
No, Amanda will even use dump to generate indices. So actually you don't need
tar at all.
Of course, what was I thinking.
Joe Donner (sent by Nabble.com) wrote:
dumpcycle 0 (to force a full backup on every run, because all our data fit
comfortably onto a single tape every night, and amdump only runs for 4.5
hours)
Lucky you :)
runspercycle 5 days (to do an amdump each day Monday to Friday)
tapecycle 21 tapes
John Clement wrote:
I can't find any documentation on getting the client working on BSD so
started going by all the information I've gleened troubleshooting the
Linux machines here.
Getting the client working on FreeBSD is nothing special :) Just install
the client (I understand that's
/
--with-index-server=amandaServerName
--with-tape-server=amandaServerName --with-tape-device=/dev/nst0
--with-portrange=850,859 --with-udpportrange=850,859
I believe the TCP portrange should be unprivileged (ports above 1024).
--
Toomas Aas
was set to more
than 1 in your config file. But every single DLE had to fit on one tape.
--
Toomas Aas
|arvutivõrgu peaspetsialist | head specialist on computer networks|
|Tartu Linnakantselei | Tartu City Office
with their
defaults and set the maxpromotedays for some larger DLEs to 2.
--
Toomas Aas
this '3' actually influence the planner?
--
Toomas Aas
' changer using chg-manual.
--
Toomas Aas
Hello!
Just curious - what are people's experiences with different brands of LTO2
media? I've lost two HP LTO2 tapes within last two months due to the drive
reporting 'media write errors'. Should I switch to some other manufacturer?
--
Toomas Aas
, thus amanda should know that it
needs to go back to 1 after 5 and I have labelled all of them at the
beginning using amlabel.
If the label on vtape 1 were correct, that's exactly what would happen.
--
Toomas Aas
Jon LaBadie wrote:
How are current users sizing their vtapes and what has
been their experience in disk usage?
I've divided my ~160GB removable disks into 5 vtapes each. I have a total of
8 DLEs, two of which are 40 GB (after compression) and the rest are no
larger than 2 GB. On the days
Joshua Kuperman wrote:
While I have no problem dumping the files on
the solaris machine; I can't seem to figure out what is in them. Except
for a few text characters on the tape label I'm stumped. the dd command
works as expected. I don't remember the order, etc and I don't have the
there's no
reason to worry.
--
Toomas Aas
|arvutivõrgu peaspetsialist | head specialist on computer networks|
|Tartu Linnakantselei | Tartu City Office |
- +372 736
1 - 100 of 189 matches
Mail list logo
