Re: Total tape usage in Amanda report

On 2006-03-24 05:01, Michael Loftis wrote: --On March 24, 2006 10:35:38 AM +0700 Olivier Nicole <[EMAIL PROTECTED]> wrote: Uhm...Yes it does... Just after the STATISTICS section you should have (by default): My mistake, it sure is there, but I never noticed it :( NP...note that those nu

Re: Install of 2.5.0 fails somehow

ow for a >> couple of years, building it as the user amanda, but installing it >> as root. >> >> Running an 'amcheck Daily' as amanda gets me this: >> >> [EMAIL PROTECTED] amanda-2.5.0-20060323]$ amcheck Daily >> amcheck: error while loading shared

Re: Install of 2.5.0 fails somehow

ling it as root. > > Running an 'amcheck Daily' as amanda gets me this: > > [EMAIL PROTECTED] amanda-2.5.0-20060323]$ amcheck Daily > amcheck: error while loading shared libraries: libamserver-2.5.0-20060323.so: > cannot open shared object file: No such file or directory

Install of 2.5.0 fails somehow

ED] amanda-2.5.0-20060323]$ amcheck Daily amcheck: error while loading shared libraries: libamserver-2.5.0-20060323.so: cannot open shared object file: No such file or directory However: [EMAIL PROTECTED] amanda-2.5.0-20060323]$ ls -l /usr/local/lib|grep server -rwxr-xr-x 1 root root 399445 De

Re: Total tape usage in Amanda report

--On March 24, 2006 10:35:38 AM +0700 Olivier Nicole <[EMAIL PROTECTED]> wrote: Uhm...Yes it does... Just after the STATISTICS section you should have (by default): My mistake, it sure is there, but I never noticed it :( NP...note that those numbers are just the amount of successfully ta

Re: Total tape usage in Amanda report

> Uhm...Yes it does... > Just after the STATISTICS section you should have (by default): My mistake, it sure is there, but I never noticed it :( Thank you, Olivier

Re: Total tape usage in Amanda report

Uhm...Yes it does... Just after the STATISTICS section you should have (by default): USAGE BY TAPE: LabelTime Size %Nb CDO801 2:18 34005742k 99.4 546 CDO798 1:33 27109731k 79.217 That'll list the total it got onto the tape. --On March 24, 2006 10

Total tape usage in Amanda report

Hello, Is there a way to have the total tape usage in Amanda report? It happens that sometime Amanda runs out of tape after 50 GB (which is normal for a 50GB SLR100 tape) but sometime only after 8GB which clearly means there is a problem. But Amanda reports do not show any total and I have to com

Release of amanda-2.5.0

Hello, The Amanda core team is pleased to announce the release of Amanda 2.5.0. It is a significant milestone in Amanda project. It can be downloaded from http://sourceforge.net/projects/amanda or http://www.amanda.org Here's a list of the changes for release 2.5.0 (from the NEWS file): Look

Re: dumps always too big to dump

On Thu, Mar 23, 2006 at 03:43:23PM +0100, Thomas Widhalm wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Paul Bijnens wrote: > > On 2006-03-23 12:40, Thomas Widhalm wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> Now I have another problem. I just post it into

Re: Amanda interoperability of different amanda versions

On 3/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello Listers, > > At the moment I am running two machines: a SuSE 9.1 (samba) server with the > (SuSE) amanda-2.4.4p2-49 (client) rpm-package and an amanda backupserver > with the same versions. > > I would like to know if I will face some

dumps always too big to dump

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oh my, god. Mea culpa. The solution was to free just a bit more diskspace. I thought, that the compression would gather enough space to get the backup into the space. Just a few MB smaller than the original. So sorry to have bothered you. - -- **

Re: dumps always too big to dump

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Bijnens wrote: > On 2006-03-23 12:40, Thomas Widhalm wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hello again, >> >> Thank you very much for all your help. Amanda now runs as I expected >> with "maxpromoteday 1" and reassigning

Amanda interoperability of different amanda versions

Hello Listers, At the moment I am running two machines: a SuSE 9.1 (samba) server with the (SuSE) amanda-2.4.4p2-49 (client) rpm-package and an amanda backupserver with the same versions. I would like to know if I will face some interoperability problems when I upgrade my dedicated amanda server

Re: dumps always too big to dump

On Thursday 23 March 2006 06:40, Thomas Widhalm wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >Hello again, > >Thank you very much for all your help. Amanda now runs as I expected >with "maxpromoteday 1" and reassigning hosts to different configs. I >have to wait for another server, till

amrcover and nslookups that resolve hostname to more than one IP_ADDR (multi-homed servers)

Hi guys: I've got my setup working nicely. My 'amdumps' are working lovely and I can log onto *almost* every server to restore. Here is my problem: I've got multi-homed servers straddling half a dozen subnets. So nslookup for me is a bit tricky. In the example presented below - this host resolves

Re: dumps always too big to dump

On 2006-03-23 12:40, Thomas Widhalm wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, Thank you very much for all your help. Amanda now runs as I expected with "maxpromoteday 1" and reassigning hosts to different configs. I have to wait for another server, till I switch to a ne

dumps always too big to dump

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, Thank you very much for all your help. Amanda now runs as I expected with "maxpromoteday 1" and reassigning hosts to different configs. I have to wait for another server, till I switch to a newer amanda version, so I can easily adopt vta