Hi,
I also posted this on the forum, but I am not sure whether that was
the right place to go.
I don't understand the message mailed to me regarding the amount of
disk space taken up by the test backups to files. Actually we plan to
run amanda with backup to files anyway, so this is an
If your situation permits, you could use an administrator-friendly,
rational operating system, such as Linux or Mach, that permits you to
backup a working system comprehensively, and, after a disk crash,
fire, or other mishap, to quickly restore a *working* system from a
*comprehensive* backup
Frank Smith wrote:
Thanks to Jean-Louis for the reply on my amcheck issues.
I got some really strange results from my first amdump run last
night after my upgrade.
I updated my home Amanda server and clients (Debian etch
packages) from 2.5.0p2-2.1 to 2.5.1p1-2, and tar from 1.15.91-2 to
Hi List
I have a Daily Config and Monthly archive Config (Last Friday of every
month script) backup running using SuSE SLES 9, Amanda version 2.4.4p2
on the DAT 4MM*150MM tape server and 4 clients but version 2.5 on a new
client I added to the DLE.
Anyway I for now dont want to update my main
I've googled and otherwise searched for an answer, but I'm not finding
out one disables the chunker from executing gzip --fast when writing
to a tape dev. I don't want compression for my virtual tapes since its
on a DataDomain box and any compression on my end defeats the better
compression to be
Ian R. Justman wrote:
Hello.
Tried using includes again, and still I'm having the same problem. It's
backing up nothing. In fact, one item was still using the exclude
method and it still backed up everything.
And for what it's worth, the version of GNU tar that's running on that
machine
On Wednesday 15 November 2006 07:50, René Kanters wrote:
I've added the list back, please use 'reply all' when replying to any
mailing list. That way, the list archives can be searched with a very
high probability of finding an answer to the problem you have because
someone else already had it
Hi there,
* Ian R. Justman [EMAIL PROTECTED] [20061115 12:39]:
Ian R. Justman wrote:
Hello.
Tried using includes again, and still I'm having the same problem. It's
backing up nothing. In fact, one item was still using the exclude
method and it still backed up everything
On Wed, Nov 15, 2006 at 08:58:07AM -0800, Joe Little wrote:
I've googled and otherwise searched for an answer, but I'm not finding
out one disables the chunker from executing gzip --fast when writing
to a tape dev. I don't want compression for my virtual tapes since its
on a DataDomain box and
On Fri, Nov 10, 2006 at 02:43:13PM -0500, René Kanters wrote:
I backup a small directory (/home/rene at about 2.1MB) and when I run
amdump I get messages with (excerpts):
[snip]
i.e., the full size of my (compressed) /home/rene
You're running up against Amanda being too smart!
Since it
Hello,
Upgrading from 2.4.5 to 2.5.1p1 and 2.5.1p2 I've noticed that if a DLE
has a diskname with an underscore in it then amcheck will complain
that the index and info files do no exit and amanda will then schedule
a full backup for those DLEs the first time the new version runs. Not
nice when
Jean-Louis Martineau wrote:
It's a tar bug that it cross filesystem boundaries, you will have to use
exclude as workaround.
OK, I've added to my excludes the secondary drives and NFS mounts, but I
see this causing problems in the future when Debian flips the testing
distribution to stable
This was for the tapedev specification, and not the dumptype. It may
be the index gzip as mentioned..
On 11/15/06, Paddy Sreenivasan [EMAIL PROTECTED] wrote:
Please set compress none in amanda.conf. See
http://wiki.zmanda.com/index.php/Amanda.conf#DUMPTYPE_SECTION
for more information.
Paddy
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
14 matches
Mail list logo
