Hello,
what could be the reason for a very very slow backup?
My backup server is a celeron 500 with 128 MB memory and a tandberg slr 24
tape box.
My network is 100MB switched.
The gamma client is a 800 MHz PIII system.
The dv-02 client is a 1,2 GHz Athlon system.
I have no explanation for this
Nick Danger wrote:
Thanks for the help with the previous problem, I have it backing up all
the non reiserfs partitions just fine now.
How do I get it to back up reiserfs partitions? I tried root-tar, and
comp-root-tar in disklist and neither worked.
FAILURE AND STRANGE DUMP SUMMARY:
[EMAIL PROTECTED] wrote:
what could be the reason for a very very slow backup?
Actually, I have no idea. Just a few remarks.
My backup server is a celeron 500 with 128 MB memory and a tandberg slr 24
tape box.
My network is 100MB switched.
The gamma client is a 800 MHz PIII system.
The dv-02
On Wed, Jan 26, 2005 at 11:24:57AM +0100, Paul Bijnens wrote:
Nick Danger wrote:
Thanks for the help with the previous problem, I have it backing up all
the non reiserfs partitions just fine now.
How do I get it to back up reiserfs partitions? I tried root-tar, and
comp-root-tar in
Ralf,
In addition to what Paul said, I've begun (after advice from amanda-users)
to use amplot, it'll give a good visual that may help to spot the problem.
On Wed, Jan 26, 2005 at 11:43:59AM +0100, Paul Bijnens wrote:
[EMAIL PROTECTED] wrote:
what could be the reason for a very very slow
Jon LaBadie wrote:
It has been a couple of years since I looked at tar,
but IIRC two things that give a return code of 2 are
file changed as we backed it up
file disappeared after we made the list of what to backup
These conditions are common on active file systems.
Both cause the error
Hi,
on Donnerstag, 20. Jänner 2005 at 22:22 I wrote to amanda-users:
SGW This will be added to the docs:
SGW - configure and make as $AMANDAUSER, make install as root
SGW - run ldconfig afterwards.
I edited the install.xml-file today and tried to take care of the
things mentioned in this
On Wed, Jan 26, 2005 at 03:51:33PM +0100, Paul Bijnens wrote:
Jon LaBadie wrote:
It has been a couple of years since I looked at tar,
but IIRC two things that give a return code of 2 are
file changed as we backed it up
file disappeared after we made the list of what to backup
These
I have problem doing incremental backup on mount file. I'm using FC2
systems. The server mount to some files and does incremental backup
everyday. The proplem is the ctime some how got changed when backing
up, so the files endup archived even though it's not been touched. Any idea?
Thanks.
On Wed, 26 Jan 2005 at 2:40pm, Nina Pham wrote
I have problem doing incremental backup on mount file. I'm using FC2
systems. The server mount to some files and does incremental backup
How does the server mount to the files? The canonical way to use amanda
is to install it on the client.
I mount using smbmount
Joshua Baker-LePain wrote:
On Wed, 26 Jan 2005 at 2:40pm, Nina Pham wrote
I have problem doing incremental backup on mount file. I'm using FC2
systems. The server mount to some files and does incremental backup
How does the server mount to the files? The
On Wed, Jan 26, 2005 at 03:38:36PM -0800, Nina Pham wrote:
I mount using smbmount
Don't do that then. Install Amanda on all of the systems that need to
be backed up, and let it work the way it was designed.
The files we are backing up are resigned on more than 1 servers, and we
want to store that archive on the same place. Therefore we need to mount.
Mike Delaney wrote:
On Wed, Jan 26, 2005 at 03:38:36PM -0800, Nina Pham wrote:
I mount using smbmount
Don't do that then. Install Amanda on
Nina Pham wrote:
I have problem doing incremental backup on mount file. I'm using FC2
systems. The server mount to some files and does incremental backup
everyday. The proplem is the ctime some how got changed when backing
up, so the files endup archived even though it's not been touched.
Nina Pham wrote:
The files we are backing up are resigned on more than 1 servers, and we
want to store that archive on the same place. Therefore we need to mount.
Can you explain more? I don't understand that.
Amanda stores all my archives on the same place :-)
--
Paul Bijnens, Xplanation
On Wed, Jan 26, 2005 at 04:26:07PM -0800, Nina Pham wrote:
Mike Delaney wrote:
On Wed, Jan 26, 2005 at 03:38:36PM -0800, Nina Pham wrote:
I mount using smbmount
Don't do that then. Install Amanda on all of the systems that need to
be backed up, and let it work the way it was designed.
On Wednesday 26 January 2005 19:27, Nina Pham wrote:
The files we are backing up are resigned on more than 1 servers, and
we want to store that archive on the same place. Therefore we need
to mount.
Nina: Sorry, but you still need to drop the smbmount as samba itself
does not support ctime, it
On Wed, Jan 26, 2005 at 06:10:19PM -0500, Joshua Baker-LePain wrote:
On Wed, 26 Jan 2005 at 2:40pm, Nina Pham wrote
The proplem is the ctime some how got changed when backing
up, so the files endup archived even though it's not been touched. Any idea?
Amanda uses dump and/or tar to
18 matches
Mail list logo
