Re: LVM snapshots

On 2006-07-08 12:44, Josef Wolf wrote: On Fri, Jul 07, 2006 at 11:13:44PM +0200, Paul Bijnens wrote: There are two approaches (maybe even many more -- I'm not the specialist here). One approach is to let the snapshot mechanism understand the filesystem and work on that level. That is how xfs

dumper, chunker and amandad communication

Hi, I need some clarification on Amanda Internals. Driver will initiate the chunker process and driver will provide some information to the chunker process like name of the file for holding disk, hostname, level, datastamp etc., How the driver will send the information to the chunker? either

communication between the amanda, dumper

Hi, Please clarify me the below statements amandad: try_socksize: send buffer size is 65536 amandad: try_socksize: receive buffer size is 65536 amandad: time 4.786: bind_portrange2: trying port=778 amandad: time 4.786: stream_server: waiting for connection: 0.0.0.0.778 amandad: try_socksize:

Re: communication between the amanda, dumper

On 2006-07-10 10:31, silpa kala wrote: Hi, Please clarify me the below statements amandad: try_socksize: send buffer size is 65536 amandad: try_socksize: receive buffer size is 65536 amandad: time 4.786: bind_portrange2: trying port=778 amandad: time 4.786: stream_server: waiting for

Disapearing amanda label

`ESSDUMP08', date `20060627' slot 2: read label `ESSDUMP09', date `20060701' slot 3: not an amanda tape slot 4: read label `ESSDUMP11', date `20060708' slot 5: read label `ESSDUMP12', date `20060710' slot 6: read label `ESSDUMP13', date `20060520 On the last weekend the backup worked fine. I think

Re: communication between the amanda, dumper

[ Please keep the information on the list -- other people may help too. ] On 2006-07-10 11:56, silpa kala wrote: Hi, I need some clarification on Amanda Internals. Driver will initiate the chunker process and driver will provide some information to the chunker process like name of the file

using amflush

Dear all, in my Amanda test lab, while trying to sort out my issues with hardware vs. software compression, amdump didn't run on 5 July last week (I subsequently put Amanda on hold to prevent amdump from running throughout the rest of the week). So now I have a directory on the holding disk

amrecover failures

Hello, I have recently configured Amanda to backup our data. I am now trying to restore some of the data that I have backed up, and I am having problems doing so. The client and server are the same machine. I have chg-manual configured so that the first and last slot are both 1. I am running

Re: LVM snapshots

Just to be clear on the original question, xfs_freeze is not an lvm command. It's part of the xfs package xfsprogs. - toby bluhm philips medical systems, cleveland ohio [EMAIL PROTECTED] 440-483-5323 [EMAIL PROTECTED] wrote on 07/10/2006

Re: communication between the amanda, dumper

[[ !!! PLEASE PLEASE -- KEEP THE CONVERSATION ON THE LIST It is not my job to answer these questions. Other more knowledgeable people on the list might jump in, and, they may even point out mistakes in my answer! ]] On 2006-07-10 15:54, silpa kala wrote: Hi, Thanks for ur information.I

Re: amrecover failures

Jerlique Bahn wrote: Hello, I have recently configured Amanda to backup our data. I am now trying to restore some of the data that I have backed up, and I am having problems doing so. The client and server are the same machine. I have chg-manual configured so that the first and last slot

port NNNN not secure(newbie)

I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our firewall work fine. 2. Our tape server is on the NATed side of firewall. 3. Backups through the firewall fail when I run AMCHECK. The error message is port not secure. I have attempted to research the

Re: port NNNN not secure(newbie)

On Mon, Jul 10, 2006 at 10:33:27AM -0700, Mike Allen wrote: I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our firewall work fine. 2. Our tape server is on the NATed side of firewall. 3. Backups through the firewall fail when I run AMCHECK. The error

Re: port NNNN not secure(newbie)

Jon LaBadie wrote: On Mon, Jul 10, 2006 at 10:33:27AM -0700, Mike Allen wrote: I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our firewall work fine. 2. Our tape server is on the NATed side of firewall. 3. Backups through the firewall fail when I

Re: port NNNN not secure(newbie)

On Mon, Jul 10, 2006 at 02:38:31PM -0700, Mike Allen wrote: Jon LaBadie wrote: On Mon, Jul 10, 2006 at 10:33:27AM -0700, Mike Allen wrote: I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our firewall work fine. 2. Our tape server is on the NATed side of

Re: port NNNN not secure(newbie)

Jon LaBadie wrote: On Mon, Jul 10, 2006 at 02:38:31PM -0700, Mike Allen wrote: Jon LaBadie wrote: On Mon, Jul 10, 2006 at 10:33:27AM -0700, Mike Allen wrote: I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our

Re: port NNNN not secure(newbie)

Mike Allen wrote: Jon LaBadie wrote: On Mon, Jul 10, 2006 at 02:38:31PM -0700, Mike Allen wrote: Jon LaBadie wrote: On Mon, Jul 10, 2006 at 10:33:27AM -0700, Mike Allen wrote: I'm using Amanda 2.4.5 with FreeBSD 5.4. 1. Backups on the NATed side of our firewall work

Re: amrecover failures

Jerlique Bahn wrote: Jerlique Bahn wrote: I have recently configured Amanda to backup our data. I am now trying to restore some of the data that I have backed up, and I am having problems doing so. The client and server are the same machine. I have chg- manual configured so that the

Slow recover speeds was amrecover failures

Hi Frank, ## This is from the changer.debug MT - /usr/local/amanda/sbin/ammt -f DD - /usr/local/amanda/sbin/amdd Args - -slot next - rewind /dev/nsa0 /dev/nsa0 rewind failed: Permission denied Looks like this is your main problem, you don't have permissions to the tape drive.