-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, 22.08.2005 at 22:53 -0400, Jason 'XenoPhage' Frisvold wrote:
[ ... some are new mail messages coming in ... ]
I've often wondered about this. I back up the mail spools in /var/mail
of the appropriate server and occasionally get a
I have a problem with the backup of two
windows
shares. At the beginning, always works fine: I do
a
full backup of the shares (they have the same
contents). After, I add a file of 255 kb in the
two
shares. I do an incremental backup and I've got a
problem: one of the share
My coworker have lebelled a tape with an incorrect label (he has inserted an
incorrect progressive number).
Now, my tapelist is something like this:
20050822 backup08 reuse
20050819 backup07 reuse
20050818 backup06 reuse
20050817 backup05 reuse
20050805 backup04 reuse
20050804 backup99 reuse -
Dave Ewart wrote:
3. Copy in a robust fashion from the mail spools to a temporary location
prior to the backup job, so that these copies of the spools will not
change; then backup the copies rather than the 'live' spools. The
robust fashion would work in a similar way to how locking mail
Montagni, Giovanni wrote:
My coworker have lebelled a tape with an incorrect label (he has inserted an
incorrect progressive number).
Now, my tapelist is something like this:
20050822 backup08 reuse
20050819 backup07 reuse
20050818 backup06 reuse
20050817 backup05 reuse
20050805 backup04 reuse
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to data timeout. I didn't even
know there was a dtimeout value to be specified in amanda.conf. I have
learnt that it is an idle time measured against the disks in question.
My question is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, 23.08.2005 at 11:01 +0200, Paul Bijnens wrote:
3. Copy in a robust fashion from the mail spools to a temporary
location prior to the backup job, so that these copies of the spools
will not change; then backup the copies rather than the
Dave Ewart wrote:
The server in question is a fairly generic Debian/Sarge mail server,
RAID setup for disks, 2.6 kernel. And /var/mail is on its own ext3
partition.
You mention that it works with LVM. Do snapshots *require* LVM?
I create snapshots with lvcreate --snapshot ..;, so, yes
On Tue, Aug 23, 2005 at 09:16:03AM +0100, Dave Ewart wrote:
On Monday, 22.08.2005 at 22:53 -0400, Jason 'XenoPhage' Frisvold wrote:
[ ... some are new mail messages coming in ... ]
I've often wondered about this. I back up the mail spools in /var/mail
of the appropriate server and
On Tue, Aug 23, 2005 at 10:23:56AM +0200, tanguy yoann wrote:
After, the login and the password are take in the file
amandapass. There is no problem on that.
The problem is that I have the same data on the two
shares and the backup are different.
The level 0 is the same but the level 1 is
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to data timeout. I didn't even
know there was a dtimeout value to be specified in amanda.conf. I have
learnt that it is an
I still have a data timeout error for a DLE in my amanda log this morning.
This is the second time this happens and this DLE is very important
for us. It has to be backed up correctly.
I've looked in the sendbackup.debug files on the client side and there
is no error for this DLE.
I asked the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, 23.08.2005 at 09:23 -0400, Jon LaBadie wrote:
1. Just put up with it: spools that are changing will result in a
backup which is probably not of any use once in a while. This is
probably fine, unless there is a large amount of mail
So my sturdy HP Ultrium 1 (LTO) tape drive just ate a tape and bit the big
one 2 months after the warranty expired. They want $3,500 for a refurb with a
90-day warranty.
I've been wanting a rackmount unit for a while now, and this gives me a good
excuse to get one :-)
I was looking at the
On Tue, 2005-08-23 at 09:38 -0400, Jon LaBadie wrote:
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to data timeout. I didn't even
know there was a dtimeout value to
--- Jon LaBadie [EMAIL PROTECTED] a écrit :
On Tue, Aug 23, 2005 at 10:23:56AM +0200, tanguy
yoann wrote:
After, the login and the password are take in the
file
amandapass. There is no problem on that.
The problem is that I have the same data on the
two
shares and the backup are
On Tue, Aug 23, 2005 at 05:04:02PM +0200, Erik P. Olsen enlightened us:
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to data timeout. I didn't even
know there was
On Tue, Aug 23, 2005 at 05:04:02PM +0200, Erik P. Olsen wrote:
On Tue, 2005-08-23 at 09:38 -0400, Jon LaBadie wrote:
I may be totally wrong here, but I don't think it is tracking idle time.
I believe it is total time to dump. This would take care of stuck or
runaway dump scenarios.
Jon LaBadie wrote:
The documentation says: dtimeout int Default: 1800 seconds. Amount of
idle time per disk on a given client that a dumper running from within
amdump will wait before it fails with a data timeout error.
Glad I said I may be totally wrong :(
Even though
Jon LaBadie wrote:
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a failure due to data timeout. I didn't even
know there was a dtimeout value to be specified in amanda.conf. I have
tanguy yoann wrote:
Perhaps on the one system something other than
amanda/samba
prevents (or causes) this archive bit to flip. That
You need administrator privilege on the PC to be able
to reset the archive bit. (At least I think so.
Great ignorance of ms windows here too :-)
would
be
I'm having more weird problems backing up the server I mentioned
yesterday (where amstatus was dying). I came in this morning, and
discovered that last night's incremental backup job is still running,
and that it seems to be because 4 dumper threads to that server are
stalled out.
amstatus
I have a Fedora Core 3 amanda server. I have specified an nfs mounted
directory for one of the holding disks. Does anyone know why amcheck finds
much less space available on this drive than a command like 'df' does?
We are currently experiencing the below issue using
amlabel. I have tried with and without a tape loaded, with and
without a slot specified etc.. All chg-zd-mtx tests described in
the script notes have been confirmed to work..
amlabel: could not load slot 1: no slots available
On Tue, 2005-08-23 at 11:24 -0400, Matt Hyclak wrote:
On Tue, Aug 23, 2005 at 05:04:02PM +0200, Erik P. Olsen enlightened us:
On Tue, Aug 23, 2005 at 11:19:59AM +0200, Erik P. Olsen wrote:
I have recently added a set of disks (file systems) to my back-up set
and that ended up with a
On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote:
We are currently experiencing the below issue using
amlabel. I have tried with and without a tape loaded, with and
without a slot specified etc.. All chg-zd-mtx tests described in
the script notes have been
-Original Message-
3. Copy in a robust fashion from the mail spools to a temporary
location prior to the backup job, so that these copies of the spools
will not change; then backup the copies rather than the 'live'
spools. The robust fashion would work in a similar way to how
27 matches
Mail list logo
