Rodrigo Ventura wrote:
Alexander Jolk wrote:
Ahm, sorry, I don't quite follow you there. Your sendbackup.* files
are empty, zero bytes?
Yeah, zero bytes.
Barring an installation problem that others have suggested, could you
tell us whether there are any files of nonzero size in /tmp/amanda/?
Hi, Joshua,
on Freitag, 13. Mai 2005 at 01:54 you wrote to amanda-users:
JBL On Thu, 12 May 2005 at 9:34pm, Rodrigo Ventura wrote
Alexander Jolk wrote:
Once again, your syntax seems right to all of us, but nobody really
seems to be actively using `include' right now. I know for certain
Jon == Jon LaBadie [EMAIL PROTECTED] writes:
Jon Is your runtar (and several other amanda programs) set-uid'ed
Jon root?
-rwsr-x---1 root backup 50972 Feb 19 16:57 runtar
among others. It seems amanda is properly installed, as far as
setuid's are concerned.
Hi guys,
This is my first post in this mailing list, I hope you can help me
answer my questions
I have installed amanda to backup all of our servers. The first run of
amdump, all directories I specified on my disklist was backed up. Then I
added three more directories from other host on my
The amdump I'm doing right now is looking good: the sendsize.*.include
files for the var/spool/imap/user is non-zero (and its contents make
sense). I guess the problem was that the directory var/spool/imap/user
was not readable by amanda. Although gnutar is performed as root, and
therefore there
Greets,
I'm running Amanda 2.4.4p4 on Linux Slackware box.
After one of recent samba upgrades, all dumps
are being marked as STRANGE in AMANDA MAIL REPORT.
This makes reports cluttered and hinders reading.
Current Samba version - 3.0.13, tar (GNU tar) 1.15.1
Is there any way to fix it?
--
Filip
Ryan Pagquil wrote:
Then I
added three more directories from other host on my disklist, and amdump
run again. Then I checked the status of my backup and amstatus reported
that my newly added directories to backup are in a status of wait for
dumping, and didn't get backed up.
`Wait for dumping' is
Lei Zhong wrote:
Hi guys,
Thank you all very much for the help. I finally figured out my problem.
It was that I didn't remove the tape label properly. I didn't run
amrmtape before I ran amlabel on the same tape.
Do you mean that was the error message that amanda put in the mail
report? While
My amdump has just finished, and the report looks good:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
omni /
On Fri, 13 May 2005 at 2:12pm, Rodrigo Ventura wrote
During the run, I noticed a process called gzip --best being used by
amanda, however I have a compress none directive. I want to switch
Amanda compresses the index files -- that's the gzip.
to gzip in the future -- change compress to
Hello,
If I want to exclude all mp3 files from my home folders backup.
can I use :
./*.mp3
is it recursive ?
I am editing config.site for the client install. Are the following
lines correct? Dont know the reason of having NO_SERVER_MODE
twice. Thanks, lei
NO_SERVER_MODE --without-server
# Default: false
# if true, disables building server
stuff.
NO_SERVER_MODE=true
On Fri, May 13, 2005 at 02:12:57PM +0100, Rodrigo Ventura enlightened us:
My amdump has just finished, and the report looks good:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
If I backup the root (/) disk with the DUMP program, I know it will
not backup mounted file systems under /.
But if I use GNUTAR ? Is it intelligent enough to skip mounted file systems ?
Otherwise, I don't see how I could backup a root file system with
gnutar without having to exclude all
On Fri, May 13, 2005 at 11:23:12AM +0100, Rodrigo Ventura wrote:
The amdump I'm doing right now is looking good: the sendsize.*.include
files for the var/spool/imap/user is non-zero (and its contents make
sense). I guess the problem was that the directory var/spool/imap/user
was not readable
On Fri, May 13, 2005 at 10:05:54AM -0400, Guy Dallaire wrote:
If I backup the root (/) disk with the DUMP program, I know it will
not backup mounted file systems under /.
But if I use GNUTAR ? Is it intelligent enough to skip mounted file systems ?
Otherwise, I don't see how I could backup
On Fri, 13 May 2005 at 10:05am, Guy Dallaire wrote
If I backup the root (/) disk with the DUMP program, I know it will
not backup mounted file systems under /.
But if I use GNUTAR ? Is it intelligent enough to skip mounted file systems ?
Yes -- amanda runs tar with the --one-file-system
On Fri, May 13, 2005 at 10:05:54AM -0400, Guy Dallaire enlightened us:
If I backup the root (/) disk with the DUMP program, I know it will
not backup mounted file systems under /.
But if I use GNUTAR ? Is it intelligent enough to skip mounted file systems ?
Otherwise, I don't see how I
I created user:amanda under group: disk. When I su amanda,
ran make, I got Permission denied error. Amanda is the owner of
/root/amanda-2.4.5/.
Making all in config
make[1]: Entering directory `/root/amanda-2.4.5/config'
make all-am
make[2]: Entering directory
Hi, Matt,
on Freitag, 13. Mai 2005 at 16:03 you wrote to amanda-users:
MH If you are using software to disable compression, and you are using DDS
MH tapes, you will want to look in the archives for Gene Heskett's script that
MH rewrites tapes...DDS stores compression on/off flags on the tape
Hi, Guy,
on Freitag, 13. Mai 2005 at 16:05 you wrote to amanda-users:
GD But if I use GNUTAR ? Is it intelligent enough to skip mounted file systems
?
Yes.
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
It would be great if we could tell amanda that all subdirectories of a
specific root were to be treated as individual disk list entries. i.e.
balance all sub directories across backups.
This would help in cases like my home system where I have a few user
directories.
These are mostly static in
Stefan G. Weichinger wrote:
Hi, Matt,
on Freitag, 13. Mai 2005 at 16:03 you wrote to amanda-users:
MH If you are using software to disable compression, and you are using DDS
MH tapes, you will want to look in the archives for Gene Heskett's script that
MH rewrites tapes...DDS stores compression
--On May 13, 2005 6:20:33 PM +0100 Chris Lee [EMAIL PROTECTED]
wrote:
It would be great if we could tell amanda that all subdirectories of a
specific root were to be treated as individual disk list entries. i.e.
balance all sub directories across backups.
This would help in cases like my home
On Friday 13 May 2005 10:20 am, Chris Lee wrote:
It would be great if we could tell amanda that all subdirectories of a
specific root were to be treated as individual disk list entries. i.e.
balance all sub directories across backups.
This would help in cases like my home system where I have
Guy Dallaire wrote:
The default setting for the netusage parameter is 600 kbps.
Correct me if I'm wrong, but a 100 Mbps ethernet interface is 10 000
kbps (roughly)
The 'netusage' parameter is not as important as you may think it is.
This parameter is only used when Amanda decides whether or not to
Hi, Chris,
on Freitag, 13. Mai 2005 at 19:20 you wrote to amanda-users:
CL It would be great if we could tell amanda that all subdirectories of a
CL specific root were to be treated as individual disk list entries. i.e.
CL balance all sub directories across backups.
I don't want to sound lazy,
On Fri, May 13, 2005 at 10:44:15AM -0400, Lei Zhong wrote:
I created user:amanda under group: disk. When I su amanda, ran make, I
got Permission denied error. Amanda is the owner of
/root/amanda-2.4.5/.
but who owns everything under it?
are it, and the directories under it writable by
On Fri, May 13, 2005 at 09:36:27PM +0200, Stefan G. Weichinger wrote:
Hi, Chris,
on Freitag, 13. Mai 2005 at 19:20 you wrote to amanda-users:
CL It would be great if we could tell amanda that all subdirectories of a
CL specific root were to be treated as individual disk list entries. i.e.
--On Friday, May 13, 2005 21:36:27 +0200 Stefan G. Weichinger [EMAIL
PROTECTED] wrote:
Hi, Chris,
on Freitag, 13. Mai 2005 at 19:20 you wrote to amanda-users:
CL It would be great if we could tell amanda that all subdirectories of a
CL specific root were to be treated as individual disk
--On May 13, 2005 3:21:29 PM -0500 Frank Smith [EMAIL PROTECTED] wrote:
I just have a DLE for the top level, and that directory contains an
exclude file containing the subdirs that I back up as separate DLEs.
That way I won't miss any new subdirs that are created. This won't work
as well for
Hi, Jon,
on Freitag, 13. Mai 2005 at 16:14 you wrote to amanda-users:
Let me strongly suggest that a paragraph explaining that the base
directory in the DLE *must* be readable by amanda, so that it can
build the include file.
JL Absolutely. I think it is only needed for include, not for
--On Friday, May 13, 2005 14:54:33 -0600 Michael Loftis [EMAIL PROTECTED]
wrote:
--On May 13, 2005 3:21:29 PM -0500 Frank Smith [EMAIL PROTECTED] wrote:
I just have a DLE for the top level, and that directory contains an
exclude file containing the subdirs that I back up as separate
Hi, Jon,
on Freitag, 13. Mai 2005 at 21:58 you wrote to amanda-users:
PAW
(according to Jon LaBadie this means
Stefan G. Weichinger writes : Patches Always Welcome)
;-)
JL I thought we decide on APAW (Applicable PAW).
APAWACCVST.
Applicable Patches Against Current CVS Tree.
;-)
On Fri, May 13, 2005 at 09:36:27PM +0200, Stefan G. Weichinger wrote:
Hi, Chris,
on Freitag, 13. Mai 2005 at 19:20 you wrote to amanda-users:
CL It would be great if we could tell amanda that all subdirectories of a
CL specific root were to be treated as individual disk list entries. i.e.
CL
Hi, Frank,
on Freitag, 13. Mai 2005 at 22:21 you wrote to amanda-users:
Find all the dirs under dle-root-dir, compare them to a list of
already existing DLEs, if something is new, add DLE to disklist.
FS The problem I see with this approach is that you need to run the script
FS on the client
--On Friday, May 13, 2005 23:27:20 +0200 Stefan G. Weichinger [EMAIL
PROTECTED] wrote:
Hi, Jon,
on Freitag, 13. Mai 2005 at 16:14 you wrote to amanda-users:
Let me strongly suggest that a paragraph explaining that the base
directory in the DLE *must* be readable by amanda, so that it can
Dear all,
I am trying to install a decent backup solution at a site where the
server to be backed-up runs its filesystems over LVM (not my install,
the LVM is actually redundant but it can't be reinstalled):
/dev/mapper/vg1-home197G 157G 31G 84% /home
--On May 14, 2005 3:20:55 AM +0200 Arrigo Triulzi
[EMAIL PROTECTED] wrote:
My plan of action is to edit /etc/lvm.conf to alter the umask parameter
to 027 so that the /dev/mapper files are group readable. Then I was
planning to change them to be group backup so that Amanda can read them.
Does
That works fine as long as your'e using dump, but you'll need to have
a backup device with media atleast 158Gb in size, and as your larger
filesystem fills, a device capable of storing 450+Gb AMANDA
currently can't split DLEs across tapes, dumpe2fs is also potentially
unreliable and quite
40 matches
Mail list logo
