inparallel setting

Amanda is taking a very long time to write the dumps. My inparallel setting is set to 50. Amanda has all data waiting to be backed up in /hold. What are other people running inparallel at? If I got 500gb 8hours in /hold whats a reasonable setting to set inparallel at ? Thanks.

don't want files to be divided up on holding disk

Hi, I recently upgraded form Amanda 2.4.4 to 2.6.0. I used to have chunksize commented out altogether for my holding disks to avoid having things divided up. Since the upgrade, it is defaulting to a cnunksize of 1G. Do I simply set it to 0 to not use multiple files? Thanks, Paul

Reading label

Hello, I'm searching for the command to read the label of the currently inserted tape. Can somebody give me a hint? Regards Sebastian

Re: inparallel setting

On Wed, Jul 2, 2008 at 2:25 PM, Mike Fahey [EMAIL PROTECTED] wrote: Amanda is taking a very long time to write the dumps. My inparallel setting is set to 50. Amanda has all data waiting to be backed up in /hold. What are other people running inparallel at? If I got 500gb 8hours in /hold

Re: inparallel setting

On Wed, Jul 2, 2008 at 4:07 PM, Mike Fahey [EMAIL PROTECTED] wrote: I am not using a tape drive, I am dumping to a raid 5 array with 1TB of storage. It is currently dumping one server and in amstatus it shows waiting for dumping for several other servers. Are there any tweaks to increase

Re: Reading label

On Wed, Jul 2, 2008 at 3:18 PM, Sebastian Henrich [EMAIL PROTECTED] wrote: I'm searching for the command to read the label of the currently inserted tape. Can somebody give me a hint? What Amanda version? The closest you can get to $ amreadlabel CONF CONF-012 is $ amtape S3 current slot

Re: don't want files to be divided up on holding disk

On Wed, Jul 2, 2008 at 3:05 PM, Paul Yeatman [EMAIL PROTECTED] wrote: Hi, I recently upgraded form Amanda 2.4.4 to 2.6.0. I used to have chunksize commented out altogether for my holding disks to avoid having things divided up. Since the upgrade, it is defaulting to a cnunksize of 1G. Do I

Re: don't want files to be divided up on holding disk

The default is 1 GB, but specifying 0 will just compute a size based on INT_MAX. I don't think there is any way to specify unlimited chunksize, but you could specify whatever your filesystem limit actually is. (2 TiB for ext2 with 4KiB blocks) Just out of curiosity, why do you care? On

speeding up estimates

I'm having trouble making backups because the estimates are taking too long. I inherited an amanda backup setup and my predecessor had already increased the etimeout to 1800. I doubled it to 3600 and I was still getting timeout warnings at the top of the email when I did an amdump. So I doubled

Re: don't want files to be divided up on holding disk

Okay, I guess I'll just set a large chunksize, then. Thanks! To answer Ian's question, I am simply accustomed to the default being not to divide backup files up. Before now, I always thought of chunksize as only being used if needed and, when not needed and thus not set, essentially disabled

Re: speeding up estimates

John Heim wrote: I'm having trouble making backups because the estimates are taking too long. I inherited an amanda backup setup and my predecessor had already increased the etimeout to 1800. I doubled it to 3600 and I was still getting timeout warnings at the top of the email when I did an