All,
I have posted a 2.5.0b1 test report on the Amanda forums here:
http://forums.zmanda.com/showthread.php?p=9
Anyone else using 2.5.0 beta, please post your test results, so we can smash
any bugs before the final release.
Cheers,
--Ian
On Sunday 27 November 2005 10:48 pm, Broderick Wood wrote:
ie. I want to change the name from amanda to backup or some other ID
but runtar seems to have the id amanda hard coded into it.
That is correct. At the moment, Amanda has its username compiled-in.
Therefore, if you want to use a
Tom,
What OS and dump version was the data backed up from? What OS and dump version
are you trying to restore to?
In general, the dump type (xfsdump, vdump, etc.) and sometimes even the
version must be the same for backup and restore. This is an unfortunate
consequence of Amanda's use of
and i can confirm that even on the server that did the backup i get the
same garbage when trying to restore - Is the dump version difference the
issue do you think?
Well, if you're getting this issue on the original server, then version
differences are probably not the problem.
Amrecover
:
http://forums.zmanda.com/showthread.php?p=20
Sincerely,
--Ian Turner
(Amanda developer)
--
Forums for Amanda discussion: http://forums.zmanda.com/
Gene,
On Saturday 10 December 2005 02:33 pm, Gene Heskett wrote:
The patch itself may be great, Kevin, BUT Bzip2 isn't anywhere near as
dependable as gzip.
That is because bzip2, by default, uses a much larger block size than gzip.
Gzip's default block size is a mere 32k, whereas bzip2 uses a
On Saturday 10 December 2005 10:50 pm, Gene Heskett wrote:
Go grab a linux kernel src in bz2 format from kernel.org, make yourself
about 10 directories to play in, and do a tar xjf /path/to/.bz2 file
in each of them, and then compare trees.
On my system, I extracted the latest Linux kernel 11
Hello all,
It seems that the amcheck manpage is presently a lie. It reads:
-w Enables a DESTRUCTIVE check for write-protection on the tape
(which would otherwise cause the subsequent amdump to fail). If
the tape is writable, this check causes all data after the
On Saturday 07 January 2006 12:38 pm, Tony van der Hoff wrote:
WARNING: tapecycle (6) = runspercycle (6).
What this means, is that if a dump ever fails (bad tape, network problems,
etc.), there is a chance that you will have no backup at all.
If tapecycle == dumpcycle, then you are overwriting
On Saturday 07 January 2006 01:17 pm, Tony van der Hoff wrote:
I am certainly not overwriting my last dump; in fact I have 5 generations
of dump :)
If you are doing a full dump everyday, then set your dumpcycle to 1 day, and
your runspercycle to 1.
If you are doing a full dump once a week
On Tuesday 10 January 2006 12:24 pm, Graeme Humphries wrote:
As a followup, the planner started segfaulting when it *wasn't* compiled
with -O2, so I had to go back to -O2 for most things. Really strange. :)
If you set your ulimit (for amdump) to allow core dumps, then if any of the
amanda
On Tuesday 17 January 2006 06:10 am, you wrote:
You're making unwarranted assumptions about other people's situations,
and telling them what to do without even understanding their needs.
Even if you do understand, the policy choice is theirs to make. Some
people have data that doesn't have
Hello,
Is anyone out there using chg-scsi instead of chg-mtx or chg-zd-mtx? If so,
can you tell me why? I've been testing it quite a bit, but there seem to be a
large number of problems -- the code is ridden with bad device references,
fixed buffer overflows, and the like. I'm more than happy
Sebastian,
On Monday 23 January 2006 08:18 am, Sebastian Marten wrote:
I have a small fileser at home and I'm looking for a brackup software.
I found amanda, and i think it can be the right thing for my server.
But I don't have a taper. I only habe a DVD-Writer with DVD-RAM support.
Can I
Eric,
On Wednesday 25 January 2006 02:22 pm, Eric Schnoebelen wrote:
NetBSD and FreeBSD do have very functional changer management
command line tools and system call interfaces, and both the
command line and system call interfaces are very stable.
MTX works on all the BSDs, as far as I
On Sunday 29 January 2006 10:28 am, Omer wrote:
... which produce three distinct files on the tape. How can I merge the
label and the tar file so I can restore it with:
You have to write the entire file at once. Anytime you close the file
descriptor (that is, a program exits), the system will
On Sunday 05 February 2006 10:40 am, Stefan G. Weichinger wrote:
AFAIK I recommended to use separate disks for vtapes and holdingdisk.
Why even use a holding disk at all with vtapes? It's not like you're going to
keep the hard disk streaming.
--
Forums for Amanda discussion:
On Sunday 05 February 2006 03:14 pm, Salvatore Enrico Indiogine wrote:
Question: since we have a autoloader/medium changer, besides mt-tools
do I also need to install mtx?
I recommend it. You can use the chg-zd-mtx script with the MTX distributed
with Fedora. The alternative is to use the
Brett,
Today, Amanda has extremely limited support for database and other application
backups. You can't use the API interface, but you can create scripts to dump
the database somewhere, and then back up that dumped file. Alternatively,
with some databases you can just backup the raw data
On Thursday 23 February 2006 22:38, Jon LaBadie wrote:
The actual complaint is often a big help to those answering.
$(man_MANS): %: $(MANPAGEDIR)/%.proc.xml xslt/man.xsl
$(XSLTPROC) --path xslt/ --output $@ man.xsl $
Now, it's been a while since I wrote Makefiles, but I must
On Friday 24 February 2006 12:07, Jon LaBadie wrote:
What make's do and don't support static patterns?
Is it a candidate for a configure check?
I have no idea, but again, it's not a big enough deal, unless there is also
some make out there that supports static patterns and chokes on wildcard
I'm surprised to hear you say that it fails with gmake too, since that's what
I use. What version of GNU make?
Sorry, it's been too long since I did this.
You shouldn't need to apply the patch manually; if you take the attachment and
pipe it into the patch program, it will make the change
On Wednesday 01 March 2006 09:44, Jon LaBadie wrote:
amtapetype: The tape is already used, use -o to overwrite the tape
Uhh, yeah, I used it for a tar. And you used it after that for
the -c check. But you didn't complain for the -c check.
I dunno what to say. It's the exact same test both
On Thursday 02 March 2006 10:26, Geert Uytterhoeven wrote:
I meant individual file size, not file system size.
Ah. In that case, FAT32's limit is 4 GB. But that is a non-issue; you can get
around it by specifying the chunksize or tape_splitsize options for
holding-disks and vtapes,
On Thursday 02 March 2006 12:08, Jon LaBadie wrote:
Wish there were a reasonably universal, reasonably
featured, reasonably secure FS type other than FAT.
UDF?
--
Forums for Amanda discussion: http://forums.zmanda.com/
On Thursday 02 March 2006 12:31, you wrote:
Does UDF support a modern permissions system though? I thought it
didn't, because it was designed for optical media...
Yes. It is designed to be a superset of all common filesystems, feature-wise.
So it has support for NT ACLs, POSIX ACLs, UNIX
On Friday 03 March 2006 04:13, Geert Uytterhoeven wrote:
That sounds actually good to me...
- disk capacity is increasing a lot,
- disk transfer speeds are also increasing, but less compared to
capacity, - disk latency (seek times) is improving very slowly.
All of this is true, but the
Anthony,
On Thursday 02 March 2006 21:30, Anthony Valentine wrote:
When I run amverify, I get errors at the beginning and the end of the
status mail, however it shows the complete tape listing in the middle.
Here it the output, edited for length (let me know if you want to see
the entire
Oliver,
Amanda should already buffer things and stream things properly to tape. If you
find that your tape drive is not going as fast as you think it should, you
should start by checking that you have enough holding disk space. If you need
more help, you could start by attaching the report
On Monday 06 March 2006 15:29, Anthony Valentine wrote:
I tested another amverify, this time doing a rewind first, and got the
same errors. Also, I am only backing up 10GB to a 40/80GB tape, so I
don't think that I am running out of space.
As another test, I created a new config using
On Wednesday 08 March 2006 06:34, Dave Ewart wrote:
In summary: when a directory is *renamed* the files underneath it are
not considered to have changed
Usually, I would say that this is a limitation of the UNIX filesystem. A
directory's modification time can change anytime you add or remove a
On Wednesday 08 March 2006 06:34, Dave Ewart wrote:
In summary: when a directory is *renamed* the files underneath it are
not considered to have changed
This does not appear to happen with CVS tar in listed-incremental mode. Please
try upgrading your tar and check if you still see this
On Thursday 16 March 2006 08:55, listrcv wrote:
That is what I was looking for, a description of the disklist format.
But I'm lacking the manpage:
If you installed amanda with --prefix, then the manpages will also be
installed in that --prefix, which may not be in your manpath.
On my system,
On Friday 24 March 2006 16:47, you wrote:
amtape: scanning all 34 slots in tape-changer rack:
This is a bug. I have opened a sourceforge bug here:
https://sourceforge.net/tracker/index.php?func=detailaid=1458291group_id=120atid=100120
Cheers,
--Ian
--
Zmanda: Open Source Data Protection and
On Saturday 25 March 2006 16:49, Nathanel wrote:
MAILER=/usr/bin/Mail
Is this correct for your system?
--Ian
--
Zmanda: Open Source Data Protection and Archiving.
http://www.zmanda.com
Attention all Amanda users (or potential users) in Long Island:
I will be giving a talk at LILUG (Long Island Linux Users Group) tonight
(4/11) on Amanda features and installation. The talk does not assume any
Amanda knowledge, but will be of use to experienced users as well.
The meeting is at
On Monday 17 April 2006 14:23, Pavel Pragin wrote:
START planner date 20060417
FINISH planner date 20060417 time 0.003
What does your disklist look like? How about the output of amcheck?
--
Forums for Amanda discussion: http://forums.zmanda.com/
Tom,
No guarantees, but you might try something like:
mt -f /dev/nst0 rewind
mt -f /dev/nst1 rewind
while dd if=/dev/nst0 of=/dev/nst1 bs=32k; do done;
In general, if you want Amanda to write two copies of your data, you should
use the RAIT driver.
Cheers,
--Ian
On Monday 17 April 2006
On Wednesday 19 April 2006 09:01, Filip Rembiałkowski wrote:
broken syntax. maybe you meant do true; done; ? why not just a short
cantrip dd if=/dev/nst0 of=/dev/nst1 bs=32k
I did mean do : done. But you must use a loop because a single run of dd will
only copy the first file on the tape. When
On Wednesday 26 April 2006 10:30, McGraw, Robert P. wrote:
1) The above log seems to show that the tape_splitsize is 10G and not the
30G that I indicated in the tape_splitsize. Is this correct? Other than the
tape_splitsize what other parameter do I need.
No, the tape_splitsize used was only
On Wednesday 26 April 2006 11:31, McGraw, Robert P. wrote:
For now I do have a holding disk space greater than 300GB that I can use.
If I set the size greater then 300GB this it should use this space rather
then shared memory?
I think you are confusing mmap'd memory and shared memory. Shared
Use chg-zd-mtx. Chg-scsi seems to work well on some systems, and crash and die
horribly on others.
On Monday 01 May 2006 14:49, Carl Holzhauer wrote:
I seem to be having an awful time with configuring chg-scsi:
-bash-3.00$ amlabel dailyset dailyset0 slot 0
changer: got exit: 2 str: error
On Tuesday 09 May 2006 11:06, Jon LaBadie wrote:
My autoloader is on /dev/st0 and tape are defined on /dev/nst0
I don't think so.
st0 and nst0 are the same device handled differenly on close.
The changer is probably on /dev/sg0 or /dev/sg1.
--
Wiki for Amanda documentation:
and Announcements
7:00 PM - 9:30 PM Main Presentation
---
Topic: The AMANDA Open Source Enterprise Backup System
---
Speaker: Ian Turner
Zmanda http
On Friday 19 May 2006 12:08, Pavel Pragin wrote:
Your changerfile paremeter should be set to
/etc/amanda/DailySet1/changer.conf if DailySet1 is the config you are
using.
This is one of the most common gotchas with chg-zd-mtx. The changerfile
parameter should be set to
On Friday 19 May 2006 13:09, James Wilson wrote:
FAILURE AND STRANGE DUMP SUMMARY:
amanda.transolutions.net /etc RESULTS MISSING
dumper: FATAL must be run setuid root to communicate correctly
dumper: FATAL must be run setuid root to communicate correctly
dumper: FATAL must be run
Jon,
There is no good short-term solution to this problem. Sorry. :-( Tape spanning
helps, but is not a panacea.
This is one of the limitations of the vtape API that I was talking about -- it
tries to reimplement tape semantics on a filesystem, even when that doesn't
make sense.
When the
On Wednesday 24 May 2006 06:38, Anthony Worrall wrote:
However you might want to add an option to allow amanda to overwrite the
tape if there is enough holding disk space for it to first read all the
dumps that need to be retained off the tape.
This is a process called Migration, and while it
On Monday 26 June 2006 04:53, silpa kala wrote:
Suppose if I want to eliminate the sockets for the
security reason (because of the port no) How can I
approach . Please provide me the details.
Probably the simplest way to secure Amanda sockets would be just to instruct
xinetd to only accept
Marilyn,
Amanda's tape selection policy is as follows.
Consider the set of tapes T. We can partition the set into two disjoint
subsets A (the set of active tapes) and I (the set of inactive tapes).
Assuming I is nonempty, there exists a subset P of I, called the set of
preferred tapes. Note
On Tuesday 08 August 2006 11:01, Jon LaBadie wrote:
One thing still up in the air (to me anyway) is final tape selection
from within the tapelist and physical tape changer. Your description
gets to which tapes are eligible to be selected, but not which tape
(or runtape number of tapes) among
On Tuesday 08 August 2006 12:11, Jon LaBadie wrote:
Just to be clear, suppose I have a large tape library with functioning
barcode reader and associated changer database.
I neglected to mention that if there is a barcode reader, Amanda will start by
loading the least recently used reusable
On Tuesday 08 August 2006 14:29, Jon LaBadie wrote:
-- The most recently used tapecycle number of tapes is in A.
-- Any remaining tapes are in I. The single least recently used
of these is also in P.
When I first read it, I was in a mindset of # tapes in rotation
matches tapecycle and
On Tuesday 08 August 2006 14:32, Jon LaBadie wrote:
From this discussion, your and my observations also, it appears the
order of tapes listed in the tapelist file is immaterial.
I'm not sure about this, but I think the definition of least recently used
is based on the order in the tapelist
Toomas,
GNU tar 1.13 should be good; The real troublemaker is tar 1.14, which will
silently corrupt your archives and throw away data. Unfortunately, some
distributions patch their tar with other code, so some versions of tar 1.13
are problematic, whereas some versions of tar 1.14 are
On Saturday 02 September 2006 16:21, Phil Howard wrote:
It would not need to be separate for each OS. The idea of using a
partition table isn't even the only approach.
The tradeoff here is that if you don't use real partitions, then you (again)
need this tool for restore. At present the only
On Tuesday 05 September 2006 10:18, Chuck Amadi Systems Administrator wrote:
Is it possible to set the AMANDA_DBGDIR directory (usually /tmp/amanda)
to some thing else example /usr/tmp/amanda .
Yes, but you have to compile from source. When you configure the compilation,
use
On Tuesday 05 September 2006 05:21, Phil Howard wrote:
On Mon, Sep 04, 2006 at 11:01:20PM -0400, Ian Turner wrote:
| On Saturday 02 September 2006 16:21, Phil Howard wrote:
| It would not need to be separate for each OS. The idea of using a
| partition table isn't even the only approach
On Wednesday 06 September 2006 04:23, Geert Uytterhoeven wrote:
So my ideal backup solution would be Amanda, with support for incrementally
storing backups at a remote location :-)
Well, Amanda does that, via incremental backups. What it doesn't do (because
of tool support) is incremental
On Friday 08 September 2006 07:08, Ronan KERYELL wrote:
First I would say it is possible to mkfs the disk before each new usage to
have clean data structures with less overhead (no fragmentation...).
Not really necessary; on any modern filesystem (and a few very old ones),
emptying the
On Monday 11 September 2006 01:48, Stephen Carville wrote:
I've been using Amanda for about five years now. The only problems I've
ever had are because a single dumps has to fit on a single tape.
If you upgrade to Amanda 2.5.x, then you can instruct Amanda to split dumps
across tapes; so you
On Friday 08 September 2006 17:03, you wrote:
A few years ago I was doing a forensics security review for a client that
had data that needed to be erased VERY reliably. The determination was
that because even IDE disks did remapping internally, it would be possible
for previously written data
On Friday 15 September 2006 11:21, Jon LaBadie wrote:
I scanned throught the 2.4.4 code and found no indication it is used
by any code there. It is unlikely sst gets used more in later amanda
releases.
A quick grep of 2.5.1 suggests it's not in use there either. I say we ditch
it.
--Ian
--
On Thursday 28 September 2006 11:54, Geert Uytterhoeven wrote:
Amanda only keeps track of what was written to `tape'. You cannot restore
from the holding disk without resorting to a manual restore.
This was true a long time ago, but no more. Today you can restore from the
holding disk using
On Wednesday 11 October 2006 16:32, Alan Jedlow wrote:
Is possible to configure AMANDA to use a specific
interface for data transfer?
Since Amanda only listens via inetd, if your inetd supports listening only on
a particular interface, then you can use that configuration with Amanda.
Xinetd
On Tuesday 17 October 2006 14:00, Steven Settlemyre wrote:
in my existing amanda setup, i have /usr and /usr/local in the disklist
for the same machine. They are separate disks (or partitions at least).
Is this correct, or does /usr include /usr/local?
Amanda does not cross filesystem
On Thursday 09 November 2006 16:12, Brett Marlowe wrote:
I've been implementing amanda 2.5.0p2 in our very heterogeneous
environment. One of the clients is AIX 5.2. It compiles correctly but
sendsize always dumps core. It appears to be related the addition of the
AMANDATES_FILE macro. Does
Hello all,
I'll be giving a presentation on Amanda, its user and development communities,
and the ways that all three have interacted with the growth of Zmanda as a
company and as a central provider of commercial support.
The talk will be this Friday, November 17, at 5:30 PM as part of the
Julien,
The problem is that the changer script needs to update some files to work,
which it can't do if the disk is full. The solution is to temporarily disable
the changer (unset tpchanger) and tape the files you are interested in
manually.
Cheers,
--Ian
On Thursday 16 November 2006 06:00,
Chris,
From my research on MIC technology about a year ago, it appears the drive will
automatically take advantage of the information if you issue an ASF and ASB
mt system calls. The MIC information allows the drive to seek directly to the
file or block requested, but this feature is
On Monday 12 March 2007 11:26, James Brown wrote:
1) The wiki says RAIT with tape changers is not
supported. Is this true?
Actually, I think these days you can use the chg-rait changer. The main
restriction is that you have to have the same number of slots assigned to
each drive, with the
On Saturday 05 May 2007 09:13, Donofrio, Lewis wrote:
Do I still have to use another tty to change tapes with amanda 2.5.x?
Amrestore only supports one tape at a time, so you can change tapes with the
same TTY.
Amrecover and amfetchdump know how to use the changer now, so you don't need
On Monday 21 May 2007 13:54, Chris Hoogendyk wrote:
Jordan Desroches wrote:
I'm trying to figure out how to set backup retention, and was
wondering if it was as simple as making sure the number of tapes a
configuration has to use allows it to cycle through N times, or if
there is an
for the freeze was
committed to the trunk.
Wiki Changes:
* Taper scan algorithm was supplemented with additional text, mostly by
Chris Hoogendyk, with some additional contributions from Ian Turner.
* The new Coding Guidelines portal, mostly written by Dustin Mitchell,
provides information useful
On Tuesday 26 June 2007 11:58:00 Weber, Philip wrote:
Is it possible to have 2 configs using 2 separate drives in a tape
robot, i.e. can they share the changer interface? I don't mean use of
RAIT.
The answer to your question is yes, but you must ensure that only one instance
of mtx is
, as suggested by a
community user.
In the background, Jean-Louis Martineau continues work on the Application API,
and Ian Turner is putting the finishing touches on the Device API. Look for
large patches with these changes in the coming months.
Sincerely,
--Ian Turner
--
Zmanda: Open Source Backup
On Thursday 27 September 2007 11:57:53 Dustin J. Mitchell wrote:
To summarize the levels of functionality for restore:
OS, Amanda, Config, Logs, Indices: use amrecover
OS, Amanda, Config, Logs: use amfetchdump
OS, Amanda: use amrestore[1], or use inventory to recover the logs
and then use
On Tuesday 02 October 2007 11:46:32 Jon LaBadie wrote:
In the old days you could do a silly command like taking some existing
file and cat'ting it on to the end of itself.
cat foobar foobar
These days (GNU coreutils 5.97) you can still do
$ cat foobar foobar
Though, of course, there
Tom,
What is runtapes set to?
--Ian
On Wednesday 31 October 2007 00:31:53 Tom Hansen wrote:
BACKGROUND INFO: I have Amanda 2.5.2p1 running on Ubuntu linux 6.10,
configured to backup several large (300Gb +) filesystems spanning
several tapes. I have a robot changer, LTO1 tapes (100Gb
release.
--Ian
On Wednesday 31 October 2007 14:31:44 Tom Hansen wrote:
Ian Turner wrote:
Tom,
What is runtapes set to?
--Ian
The runtapes parameter is set to 25.
-Tom
On Wednesday 31 October 2007 00:31:53 Tom Hansen wrote:
BACKGROUND INFO: I have Amanda 2.5.2p1 running on Ubuntu
On Thursday 01 November 2007 11:34:43 Krahn, Anderson wrote:
Is there anyway of changing the default blocksize for writing to tape
(LTO3) from 32k to 2MB without re-compiling?
Use the 'blocksize' tapetype parameter in amanda.conf.
--Ian
--
Zmanda: Open Source Backup and Recovery.
Don,
The easiest way is to lower the priority of the amandad daemon that runs on
the client. If you are using xinetd, you can just add a nice entry to the
amandad service. If you are using BSD inetd, you can use the nice program;
change the command from amanda dgram udp wait
amandabackup
On Thursday 01 November 2007 13:41:46 Jean-Francois Malouin wrote:
what happens with the previously written tapes?
can they still be read?
It should not be a problem. Reading tapes with a smaller blocksize should
never cause trouble. Reading tapes with a larger blocksize than that
specified
only one dump at a time will run over a given
network connection.
Hope that helps.
Cheers,
--Ian Turner
On Thursday 01 November 2007 15:12:24 Krahn, Anderson wrote:
How is it possible in Amanda to ensure the best network usuage?
For instance I have 2 interfaces on for qa and prd both are 100MB
Greg,
It's a serious annoyance, a violation of both etiquette and protocol. Summary
list removal (with notice) is indicated, but the main thing is that someone
needs to step up to the plate and volunteer to take care of this task.
--Ian
On Friday 28 December 2007 14:12:58 Greg Troxel wrote:
On Tuesday 01 January 2008 22:08:45 Jeremy Mordkoff wrote:
Does anyone have any suggestions for an OS to put on a boot disk for
doing restores? I am thinking of using flash drives, but CD is an option
also.
I have had good success with SystemRescueCD, which includes a wide variety of
useful
On Monday 14 January 2008 14:42:44 Gene Heskett wrote:
That test run was successfull, but I had to consult my scripts log to see
if amcheckdump was actually ran, which it did. I'm used to getting an
email from it and did not. Does it send one if it fails?
Amcheckdump does not send any
On Friday 18 January 2008 13:11:35 Stefan G. Weichinger wrote:
Any suggestion for the new parameter device_output_buffer_size,
especially with the DLT8000?
There are a lot of factors involved in the choice of this parameter (speed and
latency of CPU, memory, system bus, holding disk, scsi bus,
Stephan,
The main thing that I can recommend is to give the new beta release a try. It
features a near-complete rewrite of taper, including all the device-buffering
code. Amongst other things, the tapebufs parameter is deprecated in favor of
a new device_output_buffer_size parameter, which is
Douglas,
Are there any details regarding this issue in the /tmp/amanda debug files for
this dumper?
--Ian
On Monday 09 June 2008 17:11:51 Douglas K. Rand wrote:
Once or twice a week my amanda backups are failing when a dumper exits
on signal 6, SIGABRT:
Jun 5 23:27:38 scotch kernel:
On Friday 13 June 2008 15:13:13 Chris Hoogendyk wrote:
I will still need to know whether
there is a clean and recommended way to tell Amanda to terminate
operations immediately (accepting that ufsdumps will probably just hang).
In recent (~last year?) versions of amanda, amcleanup will also
Johan,
Your problem is here:
On Wednesday 18 June 2008 11:15:32 Johan Booysen wrote:
chg-manual contains:
firstslot=1
lastslot=1
You'll need to have more than one slot if you want to use multiple tapes.
Just increase 'lastslot' to 2 (or even to the total number of tapes you
possess), and
The default is 1 GB, but specifying 0 will just compute a size based on
INT_MAX. I don't think there is any way to specify unlimited chunksize, but
you could specify whatever your filesystem limit actually is. (2 TiB for ext2
with 4KiB blocks)
Just out of curiosity, why do you care?
On
Jeremy,
What do you mean when you say that amdump always fails. Do you get an error
message?
--Ian
On Thursday 10 July 2008 09:28:39 Jeremy Mordkoff wrote:
Hi --
I have a working setup running on fedora core 7/8/9. On my server, I am
running
amanda-2.5.1p3-3.fc7
102404844 1024004 1% /dev
devshm 1024048 0 1024048 0% /dev/shm
lrm1024048 38684985364 4%
/lib/modules/2.6.24-19-generic/volatile
-Original Message-
From: Ian Turner [mailto:[EMAIL PROTECTED]
Sent
0
0
0
0
0
0
-Original Message-
From: Ian Turner [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 2:13 PM
To: Jeremy Mordkoff
Cc: amanda-users@amanda.org
Subject: Re: debian client
Do I understand that there is nothing in /var/log/amanda/client on
cuttingroom? What
On Monday 14 July 2008 22:01:21 [EMAIL PROTECTED] wrote:
I am trying to backup a remote host's /boot and / mount points.
I don't have a tape drive, so I am backing up host to a disk on the
server.
When I use hard-disk-dump, /boot seems to backup fine, but / doesn't.
When I use hard-disk-tar,
Doyle,
This appears to be a bug in Amanda. I can't reproduce it on my end, though; is
there any chance you can run amcheck in a debugger with these options and see
what you get? If you break on get_int and generate a backtrace from there, it
may provide some clues as to what is going on.
Jon,
I thought you were in Princeton. Did you move?
--Ian
On Friday 25 July 2008 14:03:52 Jon LaBadie wrote:
On Fri, Jul 25, 2008 at 01:18:40PM -0400, Brian Cuttler wrote:
We have a Solaris E250 amanda server backing up two T1000 servers,
also Solaris, hosting Lotus Notes.
Over time,
Mtrento,
There are a few different issues here:
1. Setting tape_splitsize affects the way dumps are broken up when writing to
tape, but does not affect they way they are stored on the holding disk. So
dumps will still be done directly if they are larger than the holding disk,
even if you have
1 - 100 of 108 matches
Mail list logo
