Re: amrecover question

Jon LaBadie wrote: On Sat, Jul 29, 2006 at 12:49:26AM +1000, Jeff Allison wrote: I have just upgraded my client using the binarys at zmanda.com and when I try a recover I get [EMAIL PROTECTED] xinetd.d]# amrecover homes -s dalston.blackshaw.dyn.dhs.org AMRECOVER Version 2.5.1b1. Contacting

amrecover question

I have just upgraded my client using the binarys at zmanda.com and when I try a recover I get [EMAIL PROTECTED] xinetd.d]# amrecover homes -s dalston.blackshaw.dyn.dhs.org AMRECOVER Version 2.5.1b1. Contacting server on dalston.blackshaw.dyn.dhs.org ... NAK: amindexd: invalid service any idea

amrecover: Could not read features from control socket

Hi all I've killed my disk list... So I've created a new disklist with the entry for my backupservers root partition fired up amrecover and added /etc/amanda/homes/disklist to the extraction list and I get the subject error when I try to extract [EMAIL PROTECTED] ~]# amrecover homes -s dals

empty active tapes

OK I now appear to be able to backup my DLE again after applying the patch posted and rejigging the DLE sizes. But I now have a number of tapes marked as active but empty [EMAIL PROTECTED] _home_jeff]$ amadmin homes info|grep homes 0 20051030 homes_03 13 2932134 1343891 5377

re spanning tapes

[EMAIL PROTECTED] wrote on 01/11/2005 02:13:48 PM: > On Monday 31 October 2005 15:45, Jeff Allison wrote: > >On Mon, 2005-10-31 at 09:18 -0400, Gene Heskett wrote: > >> On Monday 31 October 2005 07:13, Jeff Allison wrote: > >The biggest DLE is /home/samba which is 11GB

Re: spanning tapes

On Mon, 2005-10-31 at 09:18 -0400, Gene Heskett wrote: > On Monday 31 October 2005 07:13, Jeff Allison wrote: > >Does anyone know how to switch off the tape spanning functionallity in > >2.4.5 I've recently updated from 2.4.2 to 2.4.5 and now my backups > never > >comp

spanning tapes

r/local/bin" sbindir="/usr/local/sbin" libexecdir="/usr/local/libexec" mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/" DUMP="/sbin/dump" RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF SAMBA_CLIENT="/usr/bin/smbclient" GNUTAR="/usr/local/bin/amtar" COMPRESS_PATH="/bin/gzip" UNCOMPRESS_PATH="/bin/gzip" LPRCMD="/usr/bin/lpr" MAILER="/usr/bin/Mail" listed_incr_dir="/usr/local/var/amanda/gnutar-lists" defs: DEFAULT_SERVER="dalston.blackshaw.dyn.dhs.org" DEFAULT_CONFIG="DailySet1" DEFAULT_TAPE_SERVER="dalston.blackshaw.dyn.dhs.org" DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" =-=-=-=-=-=-=-=-=-=-=-=-=-=- Jeff Allison [EMAIL PROTECTED] ICQ 8142658 Messenger [EMAIL PROTECTED] Yahoo Jeff Allison Mobile +44 410 502 702

Some Questions about holding disks and compression

Hi All I've got Amanda running at home quite well now as a test prior to using it at work but I still have a couple of questions... Most of the disk that I back up are on the same server that the backups are running on, I'm using comp user tar for most of them, I only have a small holding