change order of hosts to be backed up
Hi all, I'm using AMANDA 2.4.5 I've got a configuration question. I wasn't able to find a similar question with Google. I thought I'd try it on the list. I've got a disklist with a few DLE's in it. At the start of an amdump, AMANDA asks the clients for an estimate. When the server has received all the estimates, the planner starts doing it's work. What I'm interested in, is there any way to specify the exact order in the disklist for the DLE's to be backed up? For example: I have hosts mars venus and jupiter. In alphabetical order that would be: jupiter mars venus Now, what if I wasn't able to use a holding disk for parallel dumping (which means all DLE's are dumped sequentially) and I wanted host venus to be backed up first. Is there any way I can achieve this? Using a holding disk is an option offcourse, but what if I should be able to manage without a holding disk if I could only change the order the hosts are backed up. What can I do to achieve that? Thanks in advance, Dennis
Partial full backup configuration for amanda
Hi, I need some clarification on the usage of the amanda. What parameters need to be congfigured for the partial full backup i.e.,the full backup is divided into according to the dumpcycle and runspercycle. We configured dumpcycle 10 days runspercycle 10 Suppose this is the case, the full backup is divided into 10 parts. That means per day 1/10 of data is to be backed up. But, Instead of Partial full backup ,full backup is happening. Please help me out in this. What parameters need to be configured in amanda.conf file to perform partial full backup. If u provide the example with minimum configurations or amanda.conf then that will be helpful. Thanks Regards, Silpakala __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Partial full backup configuration for amanda
On Wed, 31 May 2006 at 1:50am, silpa kala wrote I need some clarification on the usage of the amanda. What parameters need to be congfigured for the partial full backup i.e.,the full backup is divided into according to the dumpcycle and runspercycle. We configured dumpcycle 10 days runspercycle 10 Suppose this is the case, the full backup is divided into 10 parts. That means per day 1/10 of data is to be backed up. But, Instead of Partial full backup ,full backup is happening. Erm, we just had this discussion. Look in the archives at http://marc.theaimsgroup.com/?l=amanda-users for a (very recent) thread titled How to Partial full backup. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Partial full backup configuration for amanda
On 2006-05-31 10:50, silpa kala wrote: Hi, I need some clarification on the usage of the amanda. What parameters need to be congfigured for the partial full backup i.e.,the full backup is divided into according to the dumpcycle and runspercycle. We configured dumpcycle 10 days runspercycle 10 Suppose this is the case, the full backup is divided into 10 parts. That means per day 1/10 of data is to be backed up. But, Instead of Partial full backup ,full backup is happening. Not exactly 1/10 of the data, but some number for disklist entries with total amount as close to 1/10 of the data as possible. If you got only 1 entry in your disklist, then there is nothing to divide or spread. Also the first time, Amanda tries to dump as much as will fit on a tape. It's only during the next runs, that Amanda can schedule incrementals (lvl 0) instead of a full dumps. You will have to wait at least 1 cycle before you notice the spread of level 0 over the cycle. Please help me out in this. What parameters need to be configured in amanda.conf file to perform partial full backup. I still believe your notion of partial full is different than that of Amanda. If u provide the example with minimum configurations or amanda.conf then that will be helpful. Example configurations are on the wiki: A minimal one: http://wiki.zmanda.com/index.php/Test_environment_with_virtual_tapes -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: change order of hosts to be backed up
On 2006-05-31 10:35, Dennis Ortsen wrote: Hi all, I'm using AMANDA 2.4.5 I've got a configuration question. I wasn't able to find a similar question with Google. I thought I'd try it on the list. I've got a disklist with a few DLE's in it. At the start of an amdump, AMANDA asks the clients for an estimate. When the server has received all the estimates, the planner starts doing it's work. What I'm interested in, is there any way to specify the exact order in the disklist for the DLE's to be backed up? For example: I have hosts mars venus and jupiter. In alphabetical order that would be: jupiter mars venus Now, what if I wasn't able to use a holding disk for parallel dumping (which means all DLE's are dumped sequentially) and I wanted host venus to be backed up first. Is there any way I can achieve this? Using a holding disk is an option offcourse, but what if I should be able to manage without a holding disk if I could only change the order the hosts are backed up. What can I do to achieve that? There is dumporder, which can order dumps by of size, time, or bandwith, but not alfabetically. And there is the dumptype option starttime where you can delay the starttime of some DLE's/hosts. It would help if you specified why you would like a specific order. Are you trying to accomplish something like: http://wiki.zmanda.com/index.php/Filling_a_tape_to_100%25 ? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
RE: Cluster backup
From: Nicola Mauri Sent: 31 May 2006 11:38 We are constantly encountering strange errors whith DLEs that refer to cluster virtual addresses. virtualA /apps/a lev 0 FAILED [data timeout] virtualB /apps/b RESULTS MISSING The disklist contains: node1 /etc full# Physical node 1 node2 /etc full# Physical node 2 virtualA /apps/afull# virtual address A virtualB /apps/bfull# virtual address B Error messages are not predictable and may change every day. They completely disappear if - in the disklist file - we replace the virtual address with the node's physical address which is running the service (and is currently mounting the shared partition we need to backup). Obviously, services and partitions might be relocated to another cluster node, so this approach won't work. I guess this happens because amanda server treats node1, virtualA and virtualB like three distinct hosts, whereas in some situations thay may refer to a single physical host, with a single amanda client instance responding. Can someone suggest how to solve this issues and how to configure Amanda to backup a cluster environment? We had similar behaviour with machines using virtual IP addresses which we eventually tracked down to inconsistent netmasks. Taking cyrus1 as an example ... [EMAIL PROTECTED] amanda]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:11:85:E7:40:75 inet addr:128.240.233.72 Bcast:128.240.255.255 Mask:255.255.0.0 eth0:1Link encap:Ethernet HWaddr 00:11:85:E7:40:75 inet addr:128.240.233.238 Bcast:128.240.233.255 Mask:255.255.255.0 (note difference in netmasks - eth0 is configured via DHCP, eth0:1 is configured statically). When Amanda server (ucsbs2 - also on 128.240.233.x) sends request to cyrus1 the reply comes back to ucsbs2 from cyrus (which is the address configured on eth0:1). I guess this is because the system sees eth0:1 as being more specific. Of course the Amanda server just drops the reply as it know that it didn't ask cyrus for anything. Making the netmasks consistent resulted in replies coming back from the main interface. Of course this doesn't help you as you want replies from the primary machine address for some DLEs and from the floating address for others. One suggestion that we had before we realised the issue was the netmask was to use chbind http://www.solucorp.qc.ca/miscprj/s_context.hc?s1=2s2=6s3=3s4=0full=0prjstate=1nodoc=0 or the interface (aka bind) option in xinetd to run multiple instances of the amanda client each responding on a different address (whether that will actually cause the responses to come from the right IP address I don't know). Paul Paul
Re: incremental backups
Pavel Pragin wrote: Hello, 1. Can you please post the last log file and the amdump.1 file from the /usr/local/amanda/log/teste directory. 2. Can you also run amadmin x version and post that as well. 3. Can you aslo explain in more detail what you are trying to acomplish from this configuration, I might be able to suggest a better solution. I also noticed that your dumpuser is set to root and this is not the correct way to setup amanda. You should be using user amanda Pavel Thanks for now. Im a newbie in Amanda, will try to do this steps and post the suggested files soon as possible. My intention is perfom a backup schema in 6x1 (6 incremental and 1 full backup) using a LTO tape drive (200gb). My target system is a ext3 partition (/home) in a Suse Linux 9.3 box called alpes, with less than 50gb of size (mailserver). Current Im using the tar-excl. -- -- Edson Conceicao da Silva | Analista de Suporte Tecnico Trainee | Incor - Instituto do Coracao | Grupo de Suporte - Divisao de Informatica | Av. Dr. Eneas de Carvalho Aguiar, 44 | CEP 05403-000 Sao Paulo SP Brasil | Ramal: 5551 E-mail: [EMAIL PROTECTED] --
Re: incremental backups
On Wed, 31 May 2006 at 9:45am, Edson wrote My intention is perfom a backup schema in 6x1 (6 incremental and 1 full backup) using a LTO tape drive (200gb). My target system is a ext3 partition (/home) in a Suse Linux 9.3 box called alpes, with less than 50gb of size (mailserver). Current Im using the tar-excl. Using amanda as it's meant to be used means giving up on the traditional *nix thinking about scheduling backups. You let amanda schedule fulls and incrementals, not you. Also, looking at the amanda.conf you posted, there are some fundamental errors. 'dumpcycle 0' forces amanda to do a full dump (level 0) every time you run 'amdump'. Also, tapecycle must be = dumpcycle. Stop. Read the documentation. Understand it. Run more test dumps. Then come on back with any questions you still have. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Disagreements between amplot, amstatus
On Tue, May 30, 2006 at 01:50:21PM -0700, Pavel Pragin wrote: But amplot's Bandwidth Allocated graph shows the line mostly pegged at 0% the entire time. From glancing through the amplot scripts, I'm guessing this should be labeled Bandwidth Free? If you run amstatus again what is the value you have in the field below: network free kps: ? also what is your inparallel and maxdumps set to in amanda.conf? network free kps:189380 inparallel 15 maxdumps 2 I don't think maxdumps will affect much - my DLEs happen to almost always be single spindle boxes. As a result, disks don't happen simultaneously on the same host. That's okay with me though. How is network free kps calulated? I played a little bit yesterday with figuring out how 80 Mbps is related to 189380 but couldn't really come up with anything... -- Ross Vandegrift [EMAIL PROTECTED] The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell. --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
Rif: RE: Cluster backup
Paul, thanks for your suggestions. On our machines, all network masks appear to be consistent. We'll try to configure different client instance on xinetd. Another frequent message error I didn't mention in my first post is: aborted:nak error: amandad busy which may sometimes lead to: driver: (aborted:nak error: amandad busy)(too many dumper retry) virutalA /apps/a RESULTS MISSING Any ideas?
Re: Rif: RE: Cluster backup
On Wed, May 31, 2006 at 03:37:44PM +0200, Nicola Mauri enlightened us: Paul, thanks for your suggestions. On our machines, all network masks appear to be consistent. We'll try to configure different client instance on xinetd. Another frequent message error I didn't mention in my first post is: aborted:nak error: amandad busy which may sometimes lead to: driver: (aborted:nak error: amandad busy)(too many dumper retry) virutalA /apps/a RESULTS MISSING Any ideas? If I had to guess, I'd say that you had for example Server1 which has an IP and also the VirtualA IP. In you disklist you have DLEs for both Server1 and VirtualA. Amanda contacts Server1 to start an estimate/dump. Amanda tries to contact VirtualA to do the same, but amandad is already running on that machine. Sound like a possibility? Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Rif: RE: Cluster backup
On 2006-05-31 16:05, Matt Hyclak wrote:
On Wed, May 31, 2006 at 03:37:44PM +0200, Nicola Mauri enlightened us:
Paul, thanks for your suggestions.
On our machines, all network masks appear to be consistent. We'll try to
configure different client instance on xinetd.
Another frequent message error I didn't mention in my first post is:
aborted:nak error: amandad busy
which may sometimes lead to:
driver: (aborted:nak error: amandad busy)(too many dumper
retry)
virutalA /apps/a RESULTS MISSING
Any ideas?
If I had to guess, I'd say that you had for example Server1 which has an IP
and also the VirtualA IP.
In you disklist you have DLEs for both Server1 and VirtualA.
Amanda contacts Server1 to start an estimate/dump.
Amanda tries to contact VirtualA to do the same, but amandad is already
running on that machine.
Sound like a possibility?
Sounds very reasonable.
I have been thinking about handling more than one amandad by
adding more than one amandad listening, each bound to only
one IP-number.
Asssuming you have two interfaces, or an alias to one interface:
eth0 IP 192.168.0.1/24
eth0:1IP 192.168.0.2/24
You can add some parameters in the xinetd.conf file for the amandad service:
service amandad
{
id = amandad1 # give this entry a unique name
bind = 192.168.0.1# bind to this IP-number
...rest of the params...
}
service amandad
id = amandad2
bind = 192.168.0.2# bind to the other IP-number
...
}
I did not yet have time to test this out...
Any feedback welcome.
--
Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: Data Timeout
On 2006-05-30 10:30, Paul Duncan wrote: Hello, One of our filesystems is failing to get backed up and I am interested in trying to ascertain why. The report entry is: compaqdev2 /export/home lev 0 FAILED [data timeout] In the amdump file I see the following suspicious entries. I get a series of driver-idle: no-diskspace entries which span 3 hours: driver: state time 1737.214 free kps: 254081 space: 2164824 taper: idle idle-dumpers: 1 qlen tapeq: 0 runq: 26 roomq: 0 wakeup: 15 driver-idle: no-diskspace driver: state time 12480.205 free kps: 286720 space: 15482922 taper: writing idle-dumpers: 5 qlen tapeq: 6 runq: 2 roomq: 0 wakeup: 86400 driver-idle: no-diskspace The above means that Amanda did not start up another dumper because the holdingdisk had all space reserved by other dumpers. When a dumper needs more diskspace on the holdingdisk than it reserved in the beginning, it asks driver with a command RQ-MORE-DISK? Do you see that string in the logfile? Then the filesystem dump fails over an hour later: driver: result time 17127.984 from dumper0: FAILED 01-00054 [data timeout] I would have a look in the sendbackup.*.debug file on the client and see if some warning/error message is in there, and verify that the client was still running at that time. Could this also be just another symptom of the problem described here: http://wiki.zmanda.com/index.php/Amdump:_mesg_read:_Connection_reset_by_peer Why does the data timeout occur over an hour after disk space becomes available? The dtimeout parameter in amanda.conf is set to 1800. I think it is because the datatimeout is not triggered by the diskspace but by something else. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Rif: Re: Rif: RE: Cluster backup
use the interface (aka bind) option in xinetd
to run multiple
instances of the amanda client each responding
on a different address
TESTED. Configuring multiple amanda client seems to
solve this issue!
My new /etc/xinet.d/amanda file has three entries:
- The first entry binds to node physical interface.
- The remaining entries bind to every virtual
interface defined in the cluster.
I noticed only one problem: when xinetd starts, some
virtual interfaces may not be defined on machine, as they are assigned
to other cluster members; xinetd won't be listening on non-existent interfaces.
When a service is relocated to the node, along with
its interface, xinetd must be somehow restarted to get it listening also
on the new acquired interface.
Should I schedule a daily '/etc/init.d/xinetd restart'?
(that's not very smart, is it?)
--/etc/xinet.d/amanda---
service amanda
{
disable = no
socket_type
= dgram
protocol
= udp
wait
= yes
user
= amanda
group
= disk
server
= /usr/lib/amanda/amandad
bind = 10.0.10.1
}
service amanda
{
disable = no
socket_type
= dgram
protocol
= udp
wait
= yes
user
= amanda
group
= disk
server
= /usr/lib/amanda/amandad
bind = 10.0.10.5
}
service amanda
{
disable = no
socket_type
= dgram
protocol
= udp
wait
= yes
user
= amanda
group
= disk
server
= /usr/lib/amanda/amandad
bind = 10.0.10.6
}
--/etc/xinet.d/amanda---
Re: Rif: Re: Rif: RE: Cluster backup
On 2006-05-31 17:00, Nicola Mauri wrote: use the interface (aka bind) option in xinetd to run multiple instances of the amanda client each responding on a different address TESTED. Configuring multiple amanda client seems to solve this issue! My new /etc/xinet.d/amanda file has three entries: - The first entry binds to node physical interface. - The remaining entries bind to every virtual interface defined in the cluster. I noticed only one problem: when xinetd starts, some virtual interfaces may not be defined on machine, as they are assigned to other cluster members; xinetd won't be listening on non-existent interfaces. When a service is relocated to the node, along with its interface, xinetd must be somehow restarted to get it listening also on the new acquired interface. Should I schedule a daily '/etc/init.d/xinetd restart'? (that's not very smart, is it?) Can you add that command to the program that relocates the service: kill -HUP `cat /var/run/xinetd.pid` -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Partial full backup configuration for amanda
Hi, Thanks for this information. I gone through the all the threads related to the Partial Full backup configuration for amanda. Partial full backup is happening based on the DLE entries instead of memory occupied for all DLEs.That means If one DLE happens to contain 50% of all data, then one day Amanda must do all that complete DLE at once (and probably not schedule anything else for a full dump). Amanda will not divide the DLE itself. I seen sometime back amstatus is showing the keyword PARTIAL. Is it referring to Partial Full bakup. I forgot what configuration was done. Please check whether the following configuration is proper for Partial Full backup. Ex : Amanda.conf - dumpcycle 4 days runspercycle 4 disklist - sda path user-tar 50% sda0 path user-tar 20% sda1 path user-tar 10% sda2 path user-tar 20% sda is backed up 1 day, sda0 is done 2nd day, sda1 is backed up 3rd day, sda2 is backed up 4th day. After 4 days it will perform the full backup.Is it true. Is there any other configuration parameters is required to perform the partial full backup. I have little confusion whether skip-full, skip-incr or strategy parameters need to be enabled for the partial full backup.Otherwise only dumpcycle and runspercycle is enough. Thanks in advance. Regards, silpakala I seen the amstatus is showing --- Paul Bijnens [EMAIL PROTECTED] wrote: On 2006-05-31 10:50, silpa kala wrote: Hi, I need some clarification on the usage of the amanda. What parameters need to be congfigured for the partial full backup i.e.,the full backup is divided into according to the dumpcycle and runspercycle. We configured dumpcycle 10 days runspercycle 10 Suppose this is the case, the full backup is divided into 10 parts. That means per day 1/10 of data is to be backed up. But, Instead of Partial full backup ,full backup is happening. Not exactly 1/10 of the data, but some number for disklist entries with total amount as close to 1/10 of the data as possible. If you got only 1 entry in your disklist, then there is nothing to divide or spread. Also the first time, Amanda tries to dump as much as will fit on a tape. It's only during the next runs, that Amanda can schedule incrementals (lvl 0) instead of a full dumps. You will have to wait at least 1 cycle before you notice the spread of level 0 over the cycle. Please help me out in this. What parameters need to be configured in amanda.conf file to perform partial full backup. I still believe your notion of partial full is different than that of Amanda. If u provide the example with minimum configurations or amanda.conf then that will be helpful. Example configurations are on the wiki: A minimal one: http://wiki.zmanda.com/index.php/Test_environment_with_virtual_tapes -- Paul Bijnens, xplanation Technology Services Tel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * *** __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Partial full backup configuration for amanda
On Wed, May 31, 2006 at 09:48:07AM -0700, silpa kala wrote: Hi, Thanks for this information. I gone through the all the threads related to the Partial Full backup configuration for amanda. Partial full backup is happening based on the DLE entries instead of memory occupied for all DLEs.That means If one DLE happens to contain 50% of all data, then one day Amanda must do all that complete DLE at once (and probably not schedule anything else for a full dump). Amanda will not divide the DLE itself. I seen sometime back amstatus is showing the keyword PARTIAL. Is it referring to Partial Full bakup. I forgot what configuration was done. Please check whether the following configuration is proper for Partial Full backup. NO, it is NOT proper for a Partial Full Backup This is because, as others have already said, amanda does not do partial full backups Each DLE receives either a full or an incremental backup. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
