I had the same problem, and I solved it with chunks
in my amanda.conf I modified the dumptype I am using and after
thatmodification amanda worked pretty fine:
define dumptype user-tar-span {
global
root-tar
tape_splitsize 20 Gb ---------> THIS IS GOING TO SPLIT THE
INFORMATION
compress client fast
compress client best
comment "tape-spanning user partitions dumped with tar"
exclude list "/etc/amanda/JID-Servers/exclude_list"
priority high
}
Another important parameter I set on my amanda.conf file is the
"runtapes" parameter, if you do not have set "runtapes" amanda will be
using only one tape, so I recommand you must set it equal to the
available tapes, I mean if you set amanda with 10 virtual tapes, set
this parameter with 10:
runtapes 10
Mario
[EMAIL PROTECTED] wrote:
Hi Amanda-users list,
This is my first email, so please forgive any missing info.
We have Amanda amanda-2.5.2p1 running on Solaris 10 x86 (Sun
Microsystems Sun Fire(TM) X2100).
I've tried two configurations both showing up the same issue.. We
backup about 187gig (250gig before compression) of data each night
(fulls only). However we keep getting the below repeated in the amdump;
find diskspace: not enough diskspace. Left with 105696 K
find diskspace: not enough diskspace. Left with 90080 K
find diskspace: not enough diskspace. Left with 44484928 K
find diskspace: not enough diskspace. Left with 26170368 K
find diskspace: not enough diskspace. Left with 19444512 K
find diskspace: not enough diskspace. Left with 10875488 K
find diskspace: not enough diskspace. Left with 7748544 K
find diskspace: not enough diskspace. Left with 7727456 K
find diskspace: not enough diskspace. Left with 6539424 K
find diskspace: not enough diskspace. Left with 3373056 K
find diskspace: not enough diskspace. Left with 1192928 K
find diskspace: not enough diskspace. Left with 22674528 K
find diskspace: not enough diskspace. Left with 14369152 K
find diskspace: not enough diskspace. Left with 11827648 K
find diskspace: not enough diskspace. Left with 2773056 K
find diskspace: not enough diskspace. Left with 2155424 K
##much more..
Even though we have now turned off the holding disk, we still get the
error.
Question 1) With no holding disk configured, should this message still
be showing in the amdump?
Question 2) we have 147gig free on the system, can we have less
holding disk space than the total backup? (my reading suggests that as
long as the two largests dumps fit it should be fine)
Question 3) should we just ignore this error?
Thanks for the help,
Regards,
--
Mario Silva
Systems Administrator
Supreme Court of New Mexico
Judicial Information Division
2905 Rodeo Park Dr. East, Bldg. #5
Santa Fe, NM 87505
Phone: (505) 476-6959 / Mobil: (505) 660-1026
Fax: (505) 476-6952
Website: http://www.nmcourts.gov
mailto: [EMAIL PROTECTED]
LEGAL DISCLAIMER:
The content of this data transmission is not considered as an offer, proposal,
understanding, or agreement unless it is confirmed in a document signed by a
legal representative of Supreme Court of the State of New Mexico or the
Judicial Information Division. The content of this data transmission is
confidential and it is intended to be delivered only to the addresses,
therefore, it shall not be distributed and/or disclosed through any mean
without the original sender's previous authorization. If you are not the
addressee you are forbidden to use it, either totally or partially, for any
purpose.
AVISO LEGAL:
El contenido de este mensaje de datos no se considera oferta, propuesta o
acuerdo, sino hasta que sea confirmado en documento por escrito que contenga
la firma autógrafa del apoderado legal de La Suprema Corte del Estado de Nuevo
Mexico o de la Division de Informatica del Estado. El contenido de este mensaje
de datos es confidencial y se entiende dirigido y para uso exclusivo del
destinatario, por lo que no podrá distribuirse y/o difundirse por ningún medio
sin la previa autorización del emisor original. Si usted no es el destinatario,
se le prohíbe su utilización total o parcial para cualquier fin.
begin:vcard
fn:Mario Silva
n:Silva;Mario
org:Supreme Court of New Mexico;Judicial Information Division
adr:;;2905 Rodeo Park Dr. East, Bldg. #5;Santa Fe;NM;87505;USA
email;internet:[EMAIL PROTECTED]
title:Systems Administrator
tel;work:(505) 476-6959
tel;fax:(505) 476-6952
tel;cell:(505) 660-1026
x-mozilla-html:TRUE
url:http://www.nmcourts.gov
version:2.1
end:vcard
