Re: Is there a log that tells me the block size of a Backup Job

I am only backing up one file, an iso image, which is about 2.6 gigabytes in size. Maybe that is why I get an error after 2.5 gigs. The tapes The LTO4 tape drive I am using is has a capacity of 800 gigabytes uncompressed and 1.6 terabytes compressed. I have tarred to that drive at speeds of

RE: Amrecover error

Hi Looks a firewall of networking issue. What happenes if you do this on server? Any other clients it works on? And a look in the amanda log files for clues - normally /tmp/amanda. -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 -Original

Re: sizeof error for 2.6.0p1 compile

Dustin J. Mitchell [EMAIL PROTECTED] writes: On Wed, Jul 23, 2008 at 3:52 PM, McGraw, Robert P [EMAIL PROTECTED] wrote: I tried to compile amanda-2.6.0p1 on a Sparc Solaris 9 10 host and get the following error: The actual error in config.log (sent privately) is configure:49348:

Re: Is there a log that tells me the block size of a Backup Job

Doyle Collings wrote: [..] I have tarred to that drive at speeds of 5.5 gigabtyes a minute. A good method to find out how fast your tapedrive could work in your current environment is to write a scratch tape with the amtapetype command like: amtapetype -e 800g /dev/nst0 Takes a few

Checking for GLIB error

Solaris 10 SPARC Amanda 2.6.0p1 My configure looks like ./configure \ PKG_CONFIG=/opt/csw/bin/pkg-config \ CC=/pkgs/$GCCVERSION/bin/gcc \ LDFLAGS='-R/opt/csw/lib' \ PERL=/opt/csw/bin/perl \ --prefix=/local/Amanda/$AMANDAVERSION \ --without-client \ --with-user=amanda \ --with-group=operator \

Re: Checking for GLIB error

On Thu, Jul 24, 2008 at 11:22 AM, McGraw, Robert P [EMAIL PROTECTED] wrote: I assume that this is not working because of the compile error. I assume that the invalid option is the -mt. I am not sure what is causing this option in be inserted. Any suggestions.

Re: Is there a log that tells me the block size of a Backup Job

I entered the following with following results: fs2:/etc/amanda/fullback # amtapetype -o -t LTO4 -e 800g -b 2048k -f /dev/nst0 Writing 4096 Mbyte compresseable data: 48 sec Writing 4096 Mbyte uncompresseable data: 44 sec Estimated time to write 2 * 819200 Mbyte: 17600 sec = 4 h 53 min wrote

RE: Checking for GLIB error

Don't you hate it when folks do this? As you install each dependency be sure and read the description because sometime each dependency has it own dependencies which must be installed. Paul Crittenden Computer Systems Manager Simpson College Phone: 515-961-1680 Email: [EMAIL PROTECTED]

amrecover, almost done but...

Hello, I'm trying to recover some file using VERSION=Amanda-2.5.0p2 on CentOS5. I'm stuck at the last step where amanda ask me again and again a tape that is already loaded. I'm pretty sure my tape reader works since i'm doing dump everyday with it. Any idea where this could come from ?

Parameters problem

Hello, I want to offer to users the ability to recover any file (or version of file) for 10 days. What parameters are best suited for doing the trick ? Regards JP Pozzi

Re: Is there a log that tells me the block size of a Backup Job

On Thu, Jul 24, 2008 at 4:44 PM, Doyle Collings [EMAIL PROTECTED] wrote: What do I need to do next to troubleshoot a misconfiguration or hardware problem. If I am using a bad installation, I am not averse to wiping the machine clean of Amanda and re-installing from source.. Try setting up a

howto fix over-write email information

All, As you can see below, I am getting bad readings because the MM:SS and KB/s are overwriting eachother. Is there a way to fix this? Also I would rather have numbers expressed in MB/s (not Mb/s), if possible! Thanks!!! Amanda user wrote: These dumps were to tape lightlife1104. The next