Re: amgtar application: exclude lists
On Wednesday 12 December 2018 14:31:06 Stefan G. Weichinger wrote:
> Am 12.12.18 um 19:38 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
> >> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> >>> On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> >>>> I only recently reconfigure some older servers to use the
> >>>> application amgtar instead of "GNUTAR"
> >>>>
> >>>> Now my old exclude lists aren't read anymore and the manpages
> >>>> aren't as informative as I would need them ;-)
> >>>>
> >>>> How to configure an exclude-list for amgtar, per DLE?
> >>>>
> >>>> I tried:
> >>>>
> >>>>
> >>>> define dumptype global {
> >>>>
> >>>> program "APPLICATION"
> >>>> application "app_amgtar"
> >>>> # yes, I also defined that application above
> >>>>
> >>>> [..]
> >>>>
> >>>> }
> >>>>
> >>>> #disklist
> >>>>
> >>>> main root / {
> >>>> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> >>>>
> >>>> [..]
> >>>>
> >>>> }
> >>>>
> >>>> Maybe that glob has to be on the client? manpage only says:
> >>>>
> >>>> "EXCLUDE-LIST-GLOB
> >>>> A filename containing exclude glob expression for the restore
> >>>> command."
> >>>>
> >>>> whoa, "for restore" ... what about dump time?
> >>>
> >>> It has been specified in the dumptype, I think since before I
> >>> started useing it it the late '90's. I tend to keep my named
> >>> exclude lists in my /GenesAmandaHelper-0.61 directory. Clutters it
> >>> some, but it seems handier to have a fixed location, but it is on
> >>> a per client basis, so the excludes are unique to the client,
> >>> achieved in the dumptype, which is unique to that client,
> >>> sometimes 4 or more per client as os stuff is on the install cd if
> >>> the disk should choke and die.
> >>
> >> example?
> >>
> >> still the "exclude list" parameter? IMO the manpage doesn't tell
> >> the exact syntax here.
> >
> > Perhaps the thing glossed over is that in the file the list points
> > to, insufficient emphasis is placed on the format of a line, it
> > needs an anchor point of ./ so that it only applies to that file, or
> > dir and below it if the name is a directory.
> >
> > As for an example:
> >
> > define dumptype shop-tar-comp {
> > global
> > compress client best
> > exclude list "/GenesAmandaHelper-0.61/excludes"
> > }
> >
> > And that excludes list files content:
> >
> > ./*.iso
> > ./.gvfs
> > ./Ksocket-gene
> > ./orbit-gene
> > ./init
> > ./lock
> > ./run
> > ./rpc_pipefs
> >
> >
> > The filename itself is I think immaterial as long as its matched.
> > "excludes" above could both be one of the Kardashians. ;-)
>
> I had it exactly like that and it seemed to have stopped working with
> amgtar. Rechecked it, a single DLE test run looks good now. Thanks to
> you, Gene.
I'm going to have to quit this, everybody will think I am an expert. ;)
Copyright 2018 by Maurice E. Heskett
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: amgtar application: exclude lists
Am 12.12.18 um 19:38 schrieb Gene Heskett:
On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
Am 12.12.18 um 17:32 schrieb Gene Heskett:
On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
I only recently reconfigure some older servers to use the
application amgtar instead of "GNUTAR"
Now my old exclude lists aren't read anymore and the manpages
aren't as informative as I would need them ;-)
How to configure an exclude-list for amgtar, per DLE?
I tried:
define dumptype global {
program "APPLICATION"
application "app_amgtar"
# yes, I also defined that application above
[..]
}
#disklist
main root / {
property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
[..]
}
Maybe that glob has to be on the client? manpage only says:
"EXCLUDE-LIST-GLOB
A filename containing exclude glob expression for the restore
command."
whoa, "for restore" ... what about dump time?
It has been specified in the dumptype, I think since before I
started useing it it the late '90's. I tend to keep my named exclude
lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
it seems handier to have a fixed location, but it is on a per client
basis, so the excludes are unique to the client, achieved in the
dumptype, which is unique to that client, sometimes 4 or more per
client as os stuff is on the install cd if the disk should choke and
die.
example?
still the "exclude list" parameter? IMO the manpage doesn't tell the
exact syntax here.
Perhaps the thing glossed over is that in the file the list points to,
insufficient emphasis is placed on the format of a line, it needs an
anchor point of ./ so that it only applies to that file, or dir and
below it if the name is a directory.
As for an example:
define dumptype shop-tar-comp {
global
compress client best
exclude list "/GenesAmandaHelper-0.61/excludes"
}
And that excludes list files content:
./*.iso
./.gvfs
./Ksocket-gene
./orbit-gene
./init
./lock
./run
./rpc_pipefs
The filename itself is I think immaterial as long as its matched.
"excludes" above could both be one of the Kardashians. ;-)
I had it exactly like that and it seemed to have stopped working with
amgtar. Rechecked it, a single DLE test run looks good now. Thanks to
you, Gene.
Re: amgtar application: exclude lists
On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> >> I only recently reconfigure some older servers to use the
> >> application amgtar instead of "GNUTAR"
> >>
> >> Now my old exclude lists aren't read anymore and the manpages
> >> aren't as informative as I would need them ;-)
> >>
> >> How to configure an exclude-list for amgtar, per DLE?
> >>
> >> I tried:
> >>
> >>
> >> define dumptype global {
> >>
> >> program "APPLICATION"
> >> application "app_amgtar"
> >> # yes, I also defined that application above
> >>
> >> [..]
> >>
> >> }
> >>
> >> #disklist
> >>
> >> main root / {
> >> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> >>
> >> [..]
> >>
> >> }
> >>
> >> Maybe that glob has to be on the client? manpage only says:
> >>
> >> "EXCLUDE-LIST-GLOB
> >> A filename containing exclude glob expression for the restore
> >> command."
> >>
> >> whoa, "for restore" ... what about dump time?
> >
> > It has been specified in the dumptype, I think since before I
> > started useing it it the late '90's. I tend to keep my named exclude
> > lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
> > it seems handier to have a fixed location, but it is on a per client
> > basis, so the excludes are unique to the client, achieved in the
> > dumptype, which is unique to that client, sometimes 4 or more per
> > client as os stuff is on the install cd if the disk should choke and
> > die.
>
> example?
>
> still the "exclude list" parameter? IMO the manpage doesn't tell the
> exact syntax here.
The man page has been squashed, needs help, so use your amanda.conf, its
all explained in there.
Copyright 2018 by Maurice E. Heskett
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: amgtar application: exclude lists
On Wednesday 12 December 2018 12:11:57 Stefan G. Weichinger wrote:
> Am 12.12.18 um 17:32 schrieb Gene Heskett:
> > On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> >> I only recently reconfigure some older servers to use the
> >> application amgtar instead of "GNUTAR"
> >>
> >> Now my old exclude lists aren't read anymore and the manpages
> >> aren't as informative as I would need them ;-)
> >>
> >> How to configure an exclude-list for amgtar, per DLE?
> >>
> >> I tried:
> >>
> >>
> >> define dumptype global {
> >>
> >> program "APPLICATION"
> >> application "app_amgtar"
> >> # yes, I also defined that application above
> >>
> >> [..]
> >>
> >> }
> >>
> >> #disklist
> >>
> >> main root / {
> >> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
> >>
> >> [..]
> >>
> >> }
> >>
> >> Maybe that glob has to be on the client? manpage only says:
> >>
> >> "EXCLUDE-LIST-GLOB
> >> A filename containing exclude glob expression for the restore
> >> command."
> >>
> >> whoa, "for restore" ... what about dump time?
> >
> > It has been specified in the dumptype, I think since before I
> > started useing it it the late '90's. I tend to keep my named exclude
> > lists in my /GenesAmandaHelper-0.61 directory. Clutters it some, but
> > it seems handier to have a fixed location, but it is on a per client
> > basis, so the excludes are unique to the client, achieved in the
> > dumptype, which is unique to that client, sometimes 4 or more per
> > client as os stuff is on the install cd if the disk should choke and
> > die.
>
> example?
>
> still the "exclude list" parameter? IMO the manpage doesn't tell the
> exact syntax here.
Perhaps the thing glossed over is that in the file the list points to,
insufficient emphasis is placed on the format of a line, it needs an
anchor point of ./ so that it only applies to that file, or dir and
below it if the name is a directory.
As for an example:
define dumptype shop-tar-comp {
global
compress client best
exclude list "/GenesAmandaHelper-0.61/excludes"
}
And that excludes list files content:
./*.iso
./.gvfs
./Ksocket-gene
./orbit-gene
./init
./lock
./run
./rpc_pipefs
The filename itself is I think immaterial as long as its matched.
"excludes" above could both be one of the Kardashians. ;-)
Copyright 2018 by Maurice E. Heskett
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Re: amgtar application: exclude lists
Am 12.12.18 um 17:32 schrieb Gene Heskett:
> On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
>
>> I only recently reconfigure some older servers to use the application
>> amgtar instead of "GNUTAR"
>>
>> Now my old exclude lists aren't read anymore and the manpages aren't
>> as informative as I would need them ;-)
>>
>> How to configure an exclude-list for amgtar, per DLE?
>>
>> I tried:
>>
>>
>> define dumptype global {
>>
>> program "APPLICATION"
>> application "app_amgtar"
>> # yes, I also defined that application above
>>
>> [..]
>>
>> }
>>
>> #disklist
>>
>> main root / {
>> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
>>
>> [..]
>>
>> }
>>
>> Maybe that glob has to be on the client? manpage only says:
>>
>> "EXCLUDE-LIST-GLOB
>> A filename containing exclude glob expression for the restore
>> command."
>>
>> whoa, "for restore" ... what about dump time?
>
> It has been specified in the dumptype, I think since before I started
> useing it it the late '90's. I tend to keep my named exclude lists in
> my /GenesAmandaHelper-0.61 directory. Clutters it some, but it seems
> handier to have a fixed location, but it is on a per client basis, so
> the excludes are unique to the client, achieved in the dumptype, which
> is unique to that client, sometimes 4 or more per client as os stuff is
> on the install cd if the disk should choke and die.
example?
still the "exclude list" parameter? IMO the manpage doesn't tell the
exact syntax here.
Re: amgtar application: exclude lists
On Wednesday 12 December 2018 10:08:43 Stefan G. Weichinger wrote:
> I only recently reconfigure some older servers to use the application
> amgtar instead of "GNUTAR"
>
> Now my old exclude lists aren't read anymore and the manpages aren't
> as informative as I would need them ;-)
>
> How to configure an exclude-list for amgtar, per DLE?
>
> I tried:
>
>
> define dumptype global {
>
> program "APPLICATION"
> application "app_amgtar"
> # yes, I also defined that application above
>
> [..]
>
> }
>
> #disklist
>
> main root / {
> property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
>
> [..]
>
> }
>
> Maybe that glob has to be on the client? manpage only says:
>
> "EXCLUDE-LIST-GLOB
> A filename containing exclude glob expression for the restore
> command."
>
> whoa, "for restore" ... what about dump time?
It has been specified in the dumptype, I think since before I started
useing it it the late '90's. I tend to keep my named exclude lists in
my /GenesAmandaHelper-0.61 directory. Clutters it some, but it seems
handier to have a fixed location, but it is on a per client basis, so
the excludes are unique to the client, achieved in the dumptype, which
is unique to that client, sometimes 4 or more per client as os stuff is
on the install cd if the disk should choke and die.
Copyright 2018 by Maurice E. Heskett
--
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
amgtar application: exclude lists
I only recently reconfigure some older servers to use the application
amgtar instead of "GNUTAR"
Now my old exclude lists aren't read anymore and the manpages aren't as
informative as I would need them ;-)
How to configure an exclude-list for amgtar, per DLE?
I tried:
define dumptype global {
program "APPLICATION"
application "app_amgtar"
# yes, I also defined that application above
[..]
}
#disklist
main root / {
property "EXCLUDE-LIST-GLOB" "/etc/amanda/root-excludes"
[..]
}
Maybe that glob has to be on the client? manpage only says:
"EXCLUDE-LIST-GLOB
A filename containing exclude glob expression for the restore command."
whoa, "for restore" ... what about dump time?
Re: Common exclude lists
Should I go ahead and create a page 'OS- and application-specific information' on the wiki, link to it from the Configuration and Exclude_and_include_lists pages and then add (mostly empty) pages for some common applications? I just created the page and added some information for Linux. I will add more information about applications later: http://wiki.zmanda.com/index.php/OS-_and_application-specific_information Review of my addition and more OS and application information are welcome. Regards, Johan
Re: Common exclude lists
On Tue, Nov 30, 2010 at 06:00:06AM +0100, Johan Stuyts wrote: man amgtar I don't have the man page on my machines but I found this: http://wiki.zmanda.com/man/amgtar.8.html It does explain exclude patterns and provides a number of examples, but what I am actually looking for are instructions for specific applications. For example (WARNING: just an example. Do not use without review): LINUX Patterns: ./proc ./media ./mnt ./dev SQUID CACHING PROXY Patterns: ./var/spool/squid POSTGRESQL Add the data directories. Example patterns: ./var/lib/postgresql/7.4/main Then backup using one of the following strategies: ... VMWARE Patterns: *.vmem *.vmem.lck *.vmdk *.vmdk.lck Install the Amanda client on each virtual machine. Then change the following settings on the Amanda server to prevent the virtual machines backing up add the same time, slowing down disk reads: ... Collecting exclude schemes and authoring such a document sounds like an excellent project for someone who wishes to contribute to Amanda without coding. -- Jon H. LaBadie j...@jgcomp.com JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Common exclude lists
Collecting exclude schemes and authoring such a document sounds like an excellent project for someone who wishes to contribute to Amanda without coding. I am willing to setup such a resource (I assume the wiki would be the best place for it), but I am not a system administrator so I won't be able to contribute a lot of content. Should I go ahead and create a page 'OS- and application-specific information' on the wiki, link to it from the Configuration and Exclude_and_include_lists pages and then add (mostly empty) pages for some common applications? Regards, Johan
Common exclude lists
Hi,My Amanda backup system has gone live recently. I still have to keep an eye on it and check if everything is alright. It took a while, but it was worth the effort.I use VMWare Server on one of my servers. I get 'strange' results from this server. I already excluded the memory and disk files (because each VM has its own Amanda client) of the VMs. Here is some of the output:...| gtar: ./var/run/acpid.socket: socket ignored| gtar: ./var/run/vmnat.4996: socket ignored| gtar: ./var/run/vmware/proxy-mob: socket ignored| gtar: ./var/run/vmware/proxy-webserver: socket ignored? gtar: ./var/run/vmware/hostd-fifo/wqppollWQ3.C282FA0.19a8: Warning: Cannot stat: No such file or directory| gtar: ./var/run/vmware/root_0/1290854406892367_2793/ha-nfc-fd: socket ignored| gtar: ./var/run/vmware/root_0/1290854406892367_2793/ha-nfcssl-fd: socket ignored| gtar: ./var/run/vmware/root_0/1290854406892367_2793/hostd-vmdb-fd: socket ignored| gtar: ./var/run/vmware/root_0/1290854602573389_5338/ha-nfc-fd: socket ignored| gtar: ./var/run/vmware/root_0/1290854602573389_5338/ha-nfcssl-fd: socket ignored...I am pretty sure I can add '/var/run' and a number of other directories to the exclude file, but I can't seem to find guidelines for exclude patterns for the OS and specific applications. Are there guides/how-tos for exclude patterns and/or backup strategies for applications?Kind regards,Johan Stuyts
Re: Common exclude lists
man amgtar Jean-Louis Johan Stuyts wrote: Hi, My Amanda backup system has gone live recently. I still have to keep an eye on it and check if everything is alright. It took a while, but it was worth the effort. I use VMWare Server on one of my servers. I get 'strange' results from this server. I already excluded the memory and disk files (because each VM has its own Amanda client) of the VMs. Here is some of the output: ... | gtar: ./var/run/acpid.socket: socket ignored | gtar: ./var/run/vmnat.4996: socket ignored | gtar: ./var/run/vmware/proxy-mob: socket ignored | gtar: ./var/run/vmware/proxy-webserver: socket ignored ? gtar: ./var/run/vmware/hostd-fifo/wqppollWQ3.C282FA0.19a8: Warning: Cannot stat: No such file or directory | gtar: ./var/run/vmware/root_0/1290854406892367_2793/ha-nfc-fd: socket ignored | gtar: ./var/run/vmware/root_0/1290854406892367_2793/ha-nfcssl-fd: socket ignored | gtar: ./var/run/vmware/root_0/1290854406892367_2793/hostd-vmdb-fd: socket ignored | gtar: ./var/run/vmware/root_0/1290854602573389_5338/ha-nfc-fd: socket ignored | gtar: ./var/run/vmware/root_0/1290854602573389_5338/ha-nfcssl-fd: socket ignored ... I am pretty sure I can add '/var/run' and a number of other directories to the exclude file, but I can't seem to find guidelines for exclude patterns for the OS and specific applications. Are there guides/how-tos for exclude patterns and/or backup strategies for applications? Kind regards, Johan Stuyts
Re: Common exclude lists
man amgtar I don't have the man page on my machines but I found this: http://wiki.zmanda.com/man/amgtar.8.html It does explain exclude patterns and provides a number of examples, but what I am actually looking for are instructions for specific applications. For example (WARNING: just an example. Do not use without review): LINUX Patterns: ./proc ./media ./mnt ./dev SQUID CACHING PROXY Patterns: ./var/spool/squid POSTGRESQL Add the data directories. Example patterns: ./var/lib/postgresql/7.4/main Then backup using one of the following strategies: ... VMWARE Patterns: *.vmem *.vmem.lck *.vmdk *.vmdk.lck Install the Amanda client on each virtual machine. Then change the following settings on the Amanda server to prevent the virtual machines backing up add the same time, slowing down disk reads: ... Kind regards, Johan Stuyts
using exclude lists
Hello Amanda users,
One of my amanda clients includes a system with (Solaris 10) non-global
zones, because of the file structure of the client, capacity of the
tape on the server, etc, I'm using tar to back up the files under
each of the non-global zones separately.
I find errors such as this in my amdump output.
/-- dorldom1 / lev 1 STRANGE
sendbackup: start [dorldom1:/ level 1]
sendbackup: info BACKUP=/usr/sfw/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/sfw/bin/gtar -xpGf - ...
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? /usr/sfw/bin/gtar: ./dev/fd: file changed as we read it
? /usr/sfw/bin/gtar: ./devices: file changed as we read it
? /usr/sfw/bin/gtar: ./proc: file changed as we read it
? /usr/sfw/bin/gtar: ./core: file changed as we read it
| Total bytes written: 96706560 (93MiB, 1023KiB/s)
sendbackup: size 94440
sendbackup: end
And had moved to a structure like this in my dislist file.
dorldom1 /export/zones/sc1beaz1 {
comp-user-tar
exclude ./root/proc
}
However since I have multiple instances of this issue I thought
I would move to a structure more like this.
dorldom1 /export/zones/sc1beaz1 {
comp-user-tar
exclude list /export/home/amanda/exclude-list
}
Where I have determined that /export/home/amanda directory is
on the specific client system and not the amanda server.
Right ?
Also, I have a question of relative location.
I think the exclude-list should be written
./root/proc
indicating relative location from the location of the head
of the tar ball, not
/export/zones/sc1beaz1/root/proc
which would be absolute from the root of the file system.
Is that correct ?
thank you,
Brian
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
exclude lists
I have defined an exclude list in a dumptype using exclude list /etc/amanda/DailySet1/exclude-list with entries like $ cat /etc/amanda/DailySet1/exclude-list ./dumps ./opt/dell/srvadmin/shared/.ipc I have a couple of questions about the entries. Based on the documentation I've read and the tests I've run, the leading '.' is required which means these are relative paths to the device where these directories live. First, am I correct in thinking the '.' are required? If so, how can Amanda be told to exclude, for example, /dumps on sda1 but still backup /dumps on sda2 other than defining different dumps types with their own exclude list? Thanks. -- Brandon
Re: exclude lists
m == martin...@zmanda.com writes: m The '.' is required, all excludes are relative to the dle you back up. m Brandon Metcalf wrote: m I have defined an exclude list in a dumptype using m mexclude list /etc/amanda/DailySet1/exclude-list m m with entries like m m$ cat /etc/amanda/DailySet1/exclude-list m./dumps m./opt/dell/srvadmin/shared/.ipc m m I have a couple of questions about the entries. Based on the m documentation I've read and the tests I've run, the leading '.' is m required which means these are relative paths to the device where m these directories live. m m First, am I correct in thinking the '.' are required? If so, how can m Amanda be told to exclude, for example, /dumps on sda1 but still m backup /dumps on sda2 other than defining different dumps types with m their own exclude list? m m You can't. Seems like a nice feature would be to allow the DLE to be specified in the exclude list. -- Brandon
Re: exclude lists
Brandon Metcalf wrote: m First, am I correct in thinking the '.' are required? If so, how can m Amanda be told to exclude, for example, /dumps on sda1 but still m backup /dumps on sda2 other than defining different dumps types with m their own exclude list? m m You can't. Seems like a nice feature would be to allow the DLE to be specified in the exclude list. The 'exclude list' can be a relative path to the dle.
Re: exclude lists
The '.' is required, all excludes are relative to the dle you back up. Brandon Metcalf wrote: I have defined an exclude list in a dumptype using exclude list /etc/amanda/DailySet1/exclude-list with entries like $ cat /etc/amanda/DailySet1/exclude-list ./dumps ./opt/dell/srvadmin/shared/.ipc I have a couple of questions about the entries. Based on the documentation I've read and the tests I've run, the leading '.' is required which means these are relative paths to the device where these directories live. First, am I correct in thinking the '.' are required? If so, how can Amanda be told to exclude, for example, /dumps on sda1 but still backup /dumps on sda2 other than defining different dumps types with their own exclude list? You can't. Jean-Louis
Re: exclude lists
m == martin...@zmanda.com writes: m Brandon Metcalf wrote: m m First, am I correct in thinking the '.' are required? If so, how can m m Amanda be told to exclude, for example, /dumps on sda1 but still m m backup /dumps on sda2 other than defining different dumps types with m m their own exclude list? m m m m You can't. m m m Seems like a nice feature would be to allow the DLE to be specified in m the exclude list. m m The 'exclude list' can be a relative path to the dle. So, you're saying I can specify one dumptype with exclude list ./amanda/DailySet1/exclude-list or is it exclude list amanda/DailySet1/exclude-list and have this file exist on each DLE?
Re: exclude lists
Brandon Metcalf wrote: m == martin...@zmanda.com writes: m Brandon Metcalf wrote: m m First, am I correct in thinking the '.' are required? If so, how can m m Amanda be told to exclude, for example, /dumps on sda1 but still m m backup /dumps on sda2 other than defining different dumps types with m m their own exclude list? m m m m You can't. m m m Seems like a nice feature would be to allow the DLE to be specified in m the exclude list. m m The 'exclude list' can be a relative path to the dle. So, you're saying I can specify one dumptype with exclude list ./amanda/DailySet1/exclude-list or is it exclude list amanda/DailySet1/exclude-list Both works. and have this file exist on each DLE? Yes. Jean-Louis
Re: exclude lists
On 2009-05-19 15:35, Brandon Metcalf wrote: m == martin...@zmanda.com writes: m m m Seems like a nice feature would be to allow the DLE to be specified in m the exclude list. m m The 'exclude list' can be a relative path to the dle. So, you're saying I can specify one dumptype with exclude list ./amanda/DailySet1/exclude-list or is it exclude list amanda/DailySet1/exclude-list and have this file exist on each DLE? Specify it as: exclude list optional append .exclude-list And have a file (optionally) in the directory of each DLE, e.g. /.exclude-list (only for the root DLE) /var/.exclude-list (only for the /var DLE) /space/.exclude-list (only for the /space DLE) Have a look in the man page for the exact meaning of optional and append. -- Paul Bijnens, Xplanation Technology ServicesTel +32 16 397.525 Interleuvenlaan 86, B-3001 Leuven, BELGIUM Fax +32 16 397.552 *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ~., * * stop, end, ^]c, +++ ATH, disconnect, halt, abort, hangup, KJOB, * * ^X^X, :D::D, kill -9 1, kill -1 $$, shutdown, init 0, Alt-F4, * * Alt-f-e, Ctrl-Alt-Del, Alt-SysRq-reisub, Stop-A, AltGr-NumLock, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: exclude lists
P == paul.bijn...@xplanation.com writes: P On 2009-05-19 15:35, Brandon Metcalf wrote: P m == martin...@zmanda.com writes: P P m P m P m Seems like a nice feature would be to allow the DLE to be specified in P m the exclude list. P m P P m The 'exclude list' can be a relative path to the dle. P P P So, you're saying I can specify one dumptype with P Pexclude list ./amanda/DailySet1/exclude-list P P or is it P Pexclude list amanda/DailySet1/exclude-list P P and have this file exist on each DLE? P Specify it as: P exclude list optional append .exclude-list P And have a file (optionally) in the directory of each DLE, P e.g. /.exclude-list (only for the root DLE) P/var/.exclude-list (only for the /var DLE) P/space/.exclude-list (only for the /space DLE) P Have a look in the man page for the exact meaning of optional and append. Thanks for the feedback from everyone. -- Brandon
Problem with Exclude Lists
I have several excludelists and most work but one doesn't. Here's
an example of one that works. In amanda.conf:
define dumptype comp-ambiance-home1-tar {
global
exclude list /usr/local/etc/amanda/genepi/home1-excludelist
program GNUTAR
comment user partitions dumped with tar
compress client fast
priority medium
}
Here is home1-excludelist:
./anal2/CVG
Here is another one (this one doesn't work, all files are still
backed up):
define dumptype comp-grandeur-gen13-tar {
global
exclude list /usr/local/etc/amanda/genepi/gen13-excludelist
program GNUTAR
comment user partitions dumped with tar
compress client fast
priority medium
}
Here is gen13-excludelist:
./gen13/coal/r03/noback/
I'm using amanda 2.5.2p1. Is this too deep to exclude? Can anyone
help me debug this?
Thanks,
Steve
--
Steven J. BackusComputer Specialist
University of Utah E-Mail: [EMAIL PROTECTED]
Genetic EpidemiologyAlternate: [EMAIL PROTECTED]
391 Chipeta Way -- Suite D150 Office: 801.587.9308
Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
Re: Problem with Exclude Lists
Steven Backus wrote: Here is gen13-excludelist: ./gen13/coal/r03/noback/ I'm using amanda 2.5.2p1. Is this too deep to exclude? Can anyone help me debug this? I think your exclude will match nothing, you should read gnutar documentation. Use './gen13/coal/r03/noback' or './gen13/coal/r03/noback/*'. Jean-Louis
Re: Problem with Exclude Lists
From Jean-Louis Martineau writes: I think your exclude will match nothing, you should read gnutar documentation. Use './gen13/coal/r03/noback' or './gen13/coal/r03/noback/*'. Thanks very much! I didn't even think of that, it really helps to have someone else look at your problem. Steve -- Steven J. BackusComputer Specialist University of Utah E-Mail: [EMAIL PROTECTED] Genetic EpidemiologyAlternate: [EMAIL PROTECTED] 391 Chipeta Way -- Suite D150 Office: 801.587.9308 Salt Lake City, UT 84108-1266 http://www.math.utah.edu/~backus
Exclude Lists - Amanda 2.5.0
Could somebody please point me to a good explanation of the exclude lists? I am trying to create an exclude list for some windows machines that I back up. Will excludes work on the windows machines (using smbclient backup in Amanda 2.5.0)? If they will work, I would like a good explanation of the syntax of the file, specifically wildcards. i.e. can I specify /*/somedirectory/file???.chk? How about file paths with spaces in them. Do I just put them with the spaces or do I have to use some special syntax for that? I tried searching the net and the wiki but I did not find the answers. I found some references to it, but it did not answer the questions above. Thanks for the help. Regards, Gordon
Re: Exclude Lists - Amanda 2.5.0
Hello, Please take look at this link for information about exclude lists: http://wiki.zmanda.com/index.php/Exclude_and_include_lists Thanks Pavel Pragin Could somebody please point me to a good explanation of the exclude lists? I am trying to create an exclude list for some windows machines that I back up. Will excludes work on the windows machines (using smbclient backup in Amanda 2.5.0)? If they will work, I would like a good explanation of the syntax of the file, specifically wildcards. i.e. can I specify /*/somedirectory/file???.chk? How about file paths with spaces in them. Do I just put them with the spaces or do I have to use some special syntax for that? I tried searching the net and the wiki but I did not find the answers. I found some references to it, but it did not answer the questions above. Thanks for the help. Regards, Gordon
Re: Exclude Lists - Amanda 2.5.0
If your situation permits, you could use an administrator-friendly, rational operating system, such as Linux or Mach, that permits you to backup a working system comprehensively, and, after a disk crash, fire, or other mishap, to quickly restore a *working* system from a *comprehensive* backup image. That would solve a bunch of problems all at once. Of course, your situation may not permit that, but it's something to think about. Gordon J. Mills III [EMAIL PROTECTED] writes: I have a question about Exclude lists. I am finally sick of seeing all of the missed open files for my windows boxes, so I want to put the common ones in an exclude list. First, is there any difference in specifying a directory or a file? Second, how do I specify a path that has spaces in it (in the exclude list file)? And finally, does anyone out there have a generic exclude list for windows servers? If not, I may post mine after I get it working correctly if anyone is interested. Regards, Gordon -- -- Steve Steven R. Newcomb, Consultant Coolheads Consulting Co-editor, Topic Maps International Standard (ISO/IEC 13250) Co-editor, draft Topic Maps -- Reference Model (ISO/IEC 13250-5) [EMAIL PROTECTED] http://www.coolheads.com direct: +1 540 951 9773 main: +1 540 951 9774 fax:+1 540 951 9775 208 Highview Drive Blacksburg, Virginia 24060 USA (Confidential to all US government personnel to whom this private letter is not addressed and who are reading it in the absence of a specific search warrant: You, along with the corrupt and pusillanimous 109th Congress, are co-conspiring to subvert the Constitution that you are sworn to defend. You can either refuse to commit this crime, or you can expect to suffer criminal sanctions in the future, when the current administration of the United States of America has been replaced by one that respects the rule of law. I do not envy you for having to make this difficult choice, but I urge you to make it wisely.)
Exclude Lists - Amanda 2.5.0
I have a question about Exclude lists. I am finally sick of seeing all of the missed open files for my windows boxes, so I want to put the common ones in an exclude list. First, is there any difference in specifying a directory or a file? Second, how do I specify a path that has spaces in it (in the exclude list file)? And finally, does anyone out there have a generic exclude list for windows servers? If not, I may post mine after I get it working correctly if anyone is interested. Regards, Gordon
Re: GNUTAR exclude lists not working in Windows or Linux
I've had no time to work on this lately. I will get back to it soon. On Wed, Jun 15, 2005 at 05:39:54PM +0200, Paul Bijnens wrote: Paul Bijnens wrote on 2 June 2005: OK, I'll jump on this. Any progress on this problem? Can you reproduce the problem with a small setup, that I could duplicate here? -- Paul Bijnens, XplanationTel +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 * *** -- Joe Rhett senior geek meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
Paul Bijnens wrote on 2 June 2005: OK, I'll jump on this. Any progress on this problem? Can you reproduce the problem with a small setup, that I could duplicate here? -- Paul Bijnens, XplanationTel +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: GNUTAR exclude lists not working in Windows or Linux
On Thursday 02 June 2005 23:47, Joe Rhett wrote: Okay, so if it isn't a documentation problem then what do we test now? A test lab just demonstrated what I already knew. On Thu, Jun 02, 2005 at 11:16:18PM +0200, Paul Bijnens wrote: Joe Rhett wrote: In the meantime, can you confirm exclude file versus exclude list ? Someone else reported a different syntax that conflicts with the man page, but actually makes more sense to the naked eye. This may be a documentation problem. The documentation is correct: exclude file ./some*thing this excludes all the files matching name some*thing exclude list /some/file /some/file on the client contains a list of patterns to be excluded I'm curious to see if Joe Rhett made his work last night. With my corrected syntax, my file by file include, overriding the exclude list, appeared to have worked as intended last night. The only puzzlement was that while the amverify output was, as usual, included in the email I got from my wrapper script, backup.sh, I normally get a somewhat nicer formatted email from the amverify run. I did not get that email. So I first installed snapshot 2.4.5-20050603 and re-ran that amverify step for exercise, and did get the email this time. The strange case of the disappearing email strikes again. Odd... -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: GNUTAR exclude lists not working in Windows or Linux
Joe Rhett wrote: Okay, so if it isn't a documentation problem then what do we test now? A test lab just demonstrated what I already knew. You know it, but we don't. And we both would like to know why. Then I would like to have the config of that test: amanda.conf, disklist, the contents of the exclude file, etc. The output of ls -lR of the directory that you tested with. and the corresponding debug files on the client in /tmp/amanda/*.debug The output of ls -lR of the directory that you tested with. Or maybe even a tar.gz of ~amanda/Test completely, including all log files amdump* log.*, info-dir and index-dir? And maybe even the resulting VTape file if not too large? Don't send the large files to the list, send them to me privately. I try to duplicate the problem here. There must be some difference. And until we can understand it, and point it to some specific bug (in the code or in the config), most computer problems look like witchcraft. (That's also why the users see systemadminstrators as wizards.) -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: GNUTAR exclude lists not working in Windows or Linux
On Thursday 02 June 2005 15:50, Joe Rhett wrote:
On Thu, Jun 02, 2005 at 08:02:21AM -0400, Gene Heskett wrote:
And as I noted before, and someone tried to explain away, it
appears that the command line invocation for the exclude list
is wrong (missing an equals) runtar.20050601020202.debug:
running: /bin/tar: gtar --create --file - --directory /
--one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/client-host3__0.new --sparse
--ignore-failed-read --totals --exclude-from
/etc/exclude.gtar .
I don't know what equals sign you feel is missing.
The man page I have for gnutar does not show an equal sign
needed with the --exclude-from option:
My amanda.conf shows that syntax, however my dumptypes that use
this option use it like this:
exclude file /amanda/excludes
Hm. Mine says exclude list, and according to the man page
exclude [ list|file ][[optional][ append ][ string ]+]
Default: file. There is two exclude list exclude file
and exclude list. With exclude file , the string is a
gnutar exclude expression. With exclude list , the
string is a file name on the client containing gnutar
exclude expression.
Does yours work? If so, perhaps it's a documentation problem?
Yes, mine works as intended, very nicely ignoreing about 2.4 GB worth
of FC3 iso's, which are then covered by an individual disklist entry
per iso involved. This gives amanda a chance to spread the load and
balance the amount backed up per nightly run.
The contents of the above file:
./*.iso
./FC3
./FC3-SRPMS
And it works, albeit in an all linux environment with tar-1.15 on
the server, and tar-1.13-25 on my one client.
Does the server version of tar matter for excludes?
In terms of excludes, I do not know. What I do know is that tar-1.13
is totally busted for other file format reasons, 1.13-19 and 1.13-25
work fine, as does 1.15. 1.14 was fairly shortlived as it apparently
broke a lot of stuff.
Can we have the output of a 'tar --version' on each of these
boxes?
tar (GNU tar) 1.13.25
This is fine AFAIK.
[...]
Also, that line of the revelant dumptype that specifys the exclude
file, starting the lookup by consulting the disklist to get the
actual dumptype being used, and showing us a snip of that dumptype
please.
I had supplied these in my original report, and in the latest report
as well.
In my defense, I did want to see them as they existed most recently.
They were removed from the quoted text. Here it is
again:
disklist:
client-host1 /user-tar
I don't think I've ever done this, I've always declared many more as
this gives amanda room to play, adjusting schedules to equalize the
amount of data backed up each night. My disklist defines just short
of 50 entries, 20 some of which are subdirs of /.
I'm not saying thats the problem, but it does tend to make amanda's
schedueling into a nightmare.
You also have skipped over defineing whether or not its a local drive,
and the network interface. Here is two of my disklist entries:
coyote /usr/games coyote-tar 1 local
gene /bin gene-tar2 le0
wheer the 4th argument is the spindle number, set so that amanda won't
thrash the drives seek mechanism by atempting to access two different
file systems on that one drive. The second line shows a different
spindle number, which amanda will then run in parallel. The
local/le0 switch in the last column tells amanda which interface to
use when talking to a client.
I don't believe amanda is married to this hard specification and won't
work without it, but its still good practice.
amanda.conf:
define dumptype global {
index yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
exclude list /etc/exclude.gtar
priority low
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
Humm, user-tar includes root-tar, which includes global. And they seem
to be in the proper order (amanda cannot use an as yet unread
dumptype, eg anything included must have been read previously in
order to stack specs as you have done here (and so do I) So this
looks good AFAICT.
I'd try changing the exclude 'list' above to 'file' just for grins.
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
99.35% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: GNUTAR exclude lists not working in Windows or Linux
Okay, so if it isn't a documentation problem then what do we test now? A test lab just demonstrated what I already knew. On Thu, Jun 02, 2005 at 11:16:18PM +0200, Paul Bijnens wrote: Joe Rhett wrote: In the meantime, can you confirm exclude file versus exclude list ? Someone else reported a different syntax that conflicts with the man page, but actually makes more sense to the naked eye. This may be a documentation problem. The documentation is correct: exclude file ./some*thing this excludes all the files matching name some*thing exclude list /some/file /some/file on the client contains a list of patterns to be excluded -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * *** -- Joe Rhett senior geek meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
Gene Heskett wrote: On Thursday 02 June 2005 17:16, Paul Bijnens wrote: The documentation is correct: exclude file ./some*thing this excludes all the files matching name some*thing exclude list /some/file /some/file on the client contains a list of patterns to be excluded I'd argue that point, I'm using 'file' to specify a file that contains a list, and its working just fine. To settle the argument, we need some proof, and correct the bug in the documentation or correct the bug in your configuration. I would like to see the entries as you have them defined in the disklist, and the output of amadmin TheConfig disklist (the ultimate interpretation by amanda, after resolving all included types) e.g.: My disklist entry in the test configuration: amatest/space/scratch/topdir user-tar And then this command would give the ultimate configuration: $ amadmin test disklist amatest '^/space/scratch/topdir$' line 26: host amatest: interface default disk /space/scratch/topdir: program GNUTAR exclude list /var/opt/amanda/exclude.gtar priority 1 dumpcycle 0 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record NO index YES skip-incr NO skip-full NO Where we can see that the dumptype user-tar somehow has an exclude defined. Moreover, when I specify exclude file /non/existing/file, then amcheck does not complain. However with exclude list /non/existing/file, amcheck complains about the non-existing file, just as expected. -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: GNUTAR exclude lists not working in Windows or Linux
On Friday 03 June 2005 06:23, Paul Bijnens wrote: Gene Heskett wrote: On Thursday 02 June 2005 17:16, Paul Bijnens wrote: The documentation is correct: exclude file ./some*thing this excludes all the files matching name some*thing exclude list /some/file /some/file on the client contains a list of patterns to be excluded I'd argue that point, I'm using 'file' to specify a file that contains a list, and its working just fine. See below, I'm full of it. I'd given up making it work and found a workaround of sorts. And had forgotten about it. Memory, second thing to go you know. :) To settle the argument, we need some proof, and correct the bug in the documentation or correct the bug in your configuration. I would like to see the entries as you have them defined in the disklist, and the output of amadmin TheConfig disklist (the ultimate interpretation by amanda, after resolving all included types) e.g.: My disklist entry in the test configuration: amatest/space/scratch/topdir user-tar And then this command would give the ultimate configuration: $ amadmin test disklist amatest '^/space/scratch/topdir$' line 26: host amatest: interface default disk /space/scratch/topdir: program GNUTAR exclude list /var/opt/amanda/exclude.gtar priority 1 dumpcycle 0 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record NO index YES skip-incr NO skip-full NO Where we can see that the dumptype user-tar somehow has an exclude defined. Moreover, when I specify exclude file /non/existing/file, then amcheck does not complain. However with exclude list /non/existing/file, amcheck complains about the non-existing file, just as expected. Here, the file exists, and if I ran a diff against the two outputs of the above command, one when its says file, and one when it says list, the only diff would be to remove this line: -exclude file /amanda/excludes with: +exclude list /amanda/excludes Here is the output of that command for 'file' against coyote /bin: line 109: host coyote: interface LOCAL disk /bin: program GNUTAR exclude file /amanda/excludes priority 0 dumpcycle 5 maxdumps 4 maxpromoteday 1 bumpsize 10240 bumpdays 1 bumpmult 2.00 strategy STANDARD estimate CLIENT compress NONE auth BSD kencrypt NO holdingdisk YES record YES index YES skip-incr NO skip-full NO and here is that same line after changing it to 'list': line 109: host coyote: interface LOCAL disk /bin: program GNUTAR exclude list /amanda/excludes priority 0 dumpcycle 5 maxdumps 4 maxpromoteday 1 bumpsize 10240 bumpdays 1 bumpmult 2.00 strategy STANDARD estimate CLIENT compress NONE auth BSD kencrypt NO holdingdisk YES record YES index YES skip-incr NO skip-full NO Now, lets see if the files I wanted excluded are in the tarballs. I am indeed wrong! They are as the /usr/FC3 backup at the last level 0 is indeed 2.3 GB. So I am mistaken. But, if indeed it works while using the word 'list', then I should remove those 3 dirs from the disklist, and re-enable the entries for the individual files, one a day until all are enabled again. An interesting observation here, since I was wrong. The 'file' usage in that event would never have had a 'hit' because while the dumptype is specified, thats not the dumptype used to backup the directory that file lives in. And when I started this little exercise this morning, that disklist entry didn't use a dumptype that had the exclude. As a test for tonight, I've used a dumptype that specifies the excludes list, which will exclude the contents of that directory, but then specified just one of the files in that directory with an include directive. So that one then looks like this: line 195: host coyote: interface LOCAL disk /usr/dlds-misc/FC3/FC3-i386-rescuecd.iso: device /usr/dlds-misc/FC3 program GNUTAR exclude list /amanda/excludes include file ./FC3-i386-rescuecd.iso priority 0 dumpcycle 5 maxdumps 4 maxpromoteday 1 bumpsize 10240 bumpdays 1 bumpmult 2.00 strategy STANDARD estimate CLIENT compress NONE auth BSD kencrypt NO holdingdisk YES record YES index YES skip-incr NO skip-full NO Does this look kosher? Actually, I should quit backing this FC3 stuff up, I'll probably never install it, I'll be jumping to FC4 when the final is out, its in
Re: GNUTAR exclude lists not working in Windows or Linux
Joe Rhett wrote: These systems I can test with to my heart's content, unlike those Windows boxes, so tell me what you need to know. OK, I'll jump on this. I can assure you there is at least one configuration in the world where the excludes do work. First some general info needed: Amanda version on server and client (is client the server itself too?) Gnutar version of server and client? And OS version of server and client? To test and experiment with amanda, it's nice to set up a special config for this, and the file-driver is perfect. (we're testing excludes, not tape drives.). Create a new config for amanda, e.g. Test, which has it's own amanda.conf and disklist. Configure the chg-disk driver for this configuration, see: http://www.amanda.org/docs/howto-filedriver.html Now set up a little disklist too, backing up only a small directory where you have complete control (create files or directories with names you need to test. And make sure the amcheck Test works and a basic amdump Test works too. Do not make the disklist too large, so that amadmin Test force followed by amdump Test runs a few minutes at most. Do not add filesystems or directories to the disklist that also are added in the production disklists. And if you really need to, add record no to its disktype, to avoid interference with your production environment. Creating such a setup takes about an hour, but it's very handy to experiment with amanda. I mean, it's not a wasted resource for the future either. Once you have set it up, try to duplicate the problem. I have already done that all here, and I cannot reproduce the problem. That means there must be some difference between your config and mine. We just need to get that nailed down. -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: GNUTAR exclude lists not working in Windows or Linux
On Wed, Jun 01, 2005 at 10:11:07PM -0700, Joe Rhett wrote: On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote: On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote: Okay, last year I had observed that perfectly valid gnutar exclude lists were being ignored by amanda on Windows machines. The best answer anyone could give me was to build my own tar program that does the excludes, and replace runtar. I forget the discussion, but there must have been more than that, A bit more, mostly telling me to use SMB instead, which is nonsense. backing up of windows boxes does not use gnutar but smbclient. Different cmd line syntax for excludes. Every time I talk about Windows, you keep talking about smbclient. Nobody, flat nobody that I know of is stupid enough to run SMB on a public webserver. The windows machines in question are using amanda under cygwin. Gee Joe, I apologize. Somehow I lost track of the point that you use cygwin. It should have been obvious to me since in the past year there was only one posting about cygwin besides yours. I can't imagine why I might have assumed that like 95% of the other posters you were using samba to backup a windows box. And as I noted before, and someone tried to explain away, it appears that the command line invocation for the exclude list is wrong (missing an equals) runtar.20050601020202.debug: running: /bin/tar: gtar --create --file - --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-host3__0.new --sparse --ignore-failed-read --totals --exclude-from /etc/exclude.gtar . I don't know what equals sign you feel is missing. The man page I have for gnutar does not show an equal sign needed with the --exclude-from option: Some versions of tar out there apparently don't work properly without the equals sign. Search for it, or trust me. In any case, I agree that it isn't affecting these linux boxes -- either syntax appears to work. /etc/exclude.gtar $ cat /etc/exclude.gtar ./* ,/ * If I recall the syntax correctly, each entry must begin ./ The first is valid and would exclude everything with the possible exception of dot files (eg .profile). Second and third are invalid. That's fine, I was trying everything possible. Right now with those regexs I'm backing up 60gb a night from that system. Wouldn't that suggest something is wrong? I started with just the first regex and added others when it didn't work, so it isn't due to the bad regexes... Actually I think it somehow is. I ran a few tests with my gtar. The command line was a pipe from one gtar creating an archive to another generating a listing. I wanted to see the effect of various exclude patterns in the file. My commandline was like this: amgtar --create --exclude-from /var/tmp/exclude \ --directory /tmp --file - . | amgtar --list --file - I ran it first without the --exclude-from option, then with the option and an empty file. Same large list of files. When I ran it with the option, but with the exclude file missing I got an error and no archive was created. Next I put a simple pair of patterns in the file: ./s2 ./s4 and the file s2 was excluded, there was no s4 to begin with. The next test was to put in the exclude file a single entry, ./* This resulted in a single line of output, ./ i.e. no files were archived but the directory was noted. Lastly I put in your three patterns, ./* ,/* * The result I got was that nothing was archived, not even . I looked at the last two a little further, collected the result of the gtar creation into a file instead of a pipe. Each command created a file exactly 10K. The one from a single exclude entry (./*) had a little data in the first few hundred bytes, then nulls. The file command recognized this as a tar file. The corresponding 10K file created with your three patterns was simply a file of null bytes. No data and of course it was not recognized by the file command as a tar file. Perhaps running the command by hand like this could help sort out the exclude patterns for you. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: GNUTAR exclude lists not working in Windows or Linux
On Thursday 02 June 2005 01:11, Joe Rhett wrote: On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote: On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote: Okay, last year I had observed that perfectly valid gnutar exclude lists were being ignored by amanda on Windows machines. The best answer anyone could give me was to build my own tar program that does the excludes, and replace runtar. I forget the discussion, but there must have been more than that, A bit more, mostly telling me to use SMB instead, which is nonsense. backing up of windows boxes does not use gnutar but smbclient. Different cmd line syntax for excludes. Every time I talk about Windows, you keep talking about smbclient. Nobody, flat nobody that I know of is stupid enough to run SMB on a public webserver. The windows machines in question are using amanda under cygwin. However, having an identical problem on Linux proves that this isn't related to Windows or Cygwin. I know you've got your head wrapped around smbclient, so let's drop the windows and focus on Linux. Tar isn't honoring the exclude files on Linux. Well now I've enabled my first gnutar linux clients, and they are seeing the exact same problem. /tmp/amanda/sendsize.debug and runtar.debug both show that the exclude list is being passed to tar, but they are ignored. Just to clarify, the entire system (60gb+) is backed up every night. And as I noted before, and someone tried to explain away, it appears that the command line invocation for the exclude list is wrong (missing an equals) runtar.20050601020202.debug: running: /bin/tar: gtar --create --file - --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-host3__0.new --sparse --ignore-failed-read --totals --exclude-from /etc/exclude.gtar . I don't know what equals sign you feel is missing. The man page I have for gnutar does not show an equal sign needed with the --exclude-from option: My amanda.conf shows that syntax, however my dumptypes that use this option use it like this: exclude file /amanda/excludes The contents of the above file: ./*.iso ./FC3 ./FC3-SRPMS And it works, albeit in an all linux environment with tar-1.15 on the server, and tar-1.13-25 on my one client. Some versions of tar out there apparently don't work properly without the equals sign. Search for it, or trust me. In any case, I agree that it isn't affecting these linux boxes -- either syntax appears to work. /etc/exclude.gtar $ cat /etc/exclude.gtar ./* ,/ * If I recall the syntax correctly, each entry must begin ./ The first is valid and would exclude everything with the possible exception of dot files (eg .profile). Second and third are invalid. That's fine, I was trying everything possible. Right now with those regexs I'm backing up 60gb a night from that system. Wouldn't that suggest something is wrong? I started with just the first regex and added others when it didn't work, so it isn't due to the bad regexes... Can we have the output of a 'tar --version' on each of these boxes? Also, that line of the revelant dumptype that specifys the exclude file, starting the lookup by consulting the disklist to get the actual dumptype being used, and showing us a snip of that dumptype please. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.35% setiathome rank, not too shabby for a WV hillbilly Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: GNUTAR exclude lists not working in Windows or Linux
On Wed, Jun 01, 2005 at 10:11:07PM -0700, Joe Rhett wrote: That's fine, I was trying everything possible. Right now with those regexs I'm backing up 60gb a night from that system. Wouldn't that suggest something is wrong? I started with just the first regex and added others when it didn't work, so it isn't due to the bad regexes... On Thu, Jun 02, 2005 at 02:22:27AM -0400, Jon LaBadie wrote: Actually I think it somehow is. I ran a few tests with my gtar. The command line was a pipe from one gtar creating an archive to another generating a listing. I wanted to see the effect of various exclude patterns in the file. My commandline was like this: amgtar --create --exclude-from /var/tmp/exclude \ --directory /tmp --file - . | amgtar --list --file - I ran it first without the --exclude-from option, then with the option and an empty file. Same large list of files. When I ran it with the option, but with the exclude file missing I got an error and no archive was created. Next I put a simple pair of patterns in the file: ./s2 ./s4 and the file s2 was excluded, there was no s4 to begin with. The next test was to put in the exclude file a single entry, ./* This resulted in a single line of output, ./ i.e. no files were archived but the directory was noted. Lastly I put in your three patterns, ./* ,/* * The result I got was that nothing was archived, not even . I looked at the last two a little further, collected the result of the gtar creation into a file instead of a pipe. Each command created a file exactly 10K. The one from a single exclude entry (./*) had a little data in the first few hundred bytes, then nulls. The file command recognized this as a tar file. The corresponding 10K file created with your three patterns was simply a file of null bytes. No data and of course it was not recognized by the file command as a tar file. Perhaps running the command by hand like this could help sort out the exclude patterns for you. That's nice. Ignore a consistent and repeatable bug report for over a year, then be sarcastic to the reporter. I HAVE run these commands by hand. I sent directly to you the results of running these commands by hand last year, versus the results displayed in the amanda report. And besides, you are making my arguement for me. Your results show that no files should have been backed up with the file as shown, however 62gb was backed up the previous night. Now that your own tests have demonstrated that running the command by hand works, yet amanda is getting something different, would you possibly take an interest in finding out why? -- Joe Rhett senior geek meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
On Thu, Jun 02, 2005 at 08:02:21AM -0400, Gene Heskett wrote:
And as I noted before, and someone tried to explain away, it
appears that the command line invocation for the exclude list is
wrong (missing an equals) runtar.20050601020202.debug:
running: /bin/tar: gtar --create --file - --directory /
--one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/client-host3__0.new --sparse
--ignore-failed-read --totals --exclude-from /etc/exclude.gtar .
I don't know what equals sign you feel is missing.
The man page I have for gnutar does not show an equal sign
needed with the --exclude-from option:
My amanda.conf shows that syntax, however my dumptypes that use this
option use it like this:
exclude file /amanda/excludes
Hm. Mine says exclude list, and according to the man page
exclude [ list|file ][[optional][ append ][ string ]+]
Default: file. There is two exclude list exclude file
and exclude list. With exclude file , the string is a
gnutar exclude expression. With exclude list , the
string is a file name on the client containing gnutar
exclude expression.
Does yours work? If so, perhaps it's a documentation problem?
The contents of the above file:
./*.iso
./FC3
./FC3-SRPMS
And it works, albeit in an all linux environment with tar-1.15 on the
server, and tar-1.13-25 on my one client.
Does the server version of tar matter for excludes?
Can we have the output of a 'tar --version' on each of these boxes?
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
Also, that line of the revelant dumptype that specifys the exclude
file, starting the lookup by consulting the disklist to get the
actual dumptype being used, and showing us a snip of that dumptype
please.
I had supplied these in my original report, and in the latest report as
well. They were removed from the quoted text. Here it is again:
disklist:
client-host1 /user-tar
amanda.conf:
define dumptype global {
index yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
exclude list /etc/exclude.gtar
priority low
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
--
Joe Rhett
senior geek
meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
Thanks for the advice on doing that. I had such an environment set up last year, and was able to replicate it at will on the Windows boxes. I'll set it up again for the linux systems. Working this out on Windows stalled because I was reluctant to toy with these production systems. Windows doesn't need any help to be shaky ;-) In the meantime, can you confirm exclude file versus exclude list ? Someone else reported a different syntax that conflicts with the man page, but actually makes more sense to the naked eye. This may be a documentation problem. On Thu, Jun 02, 2005 at 10:33:23AM +0200, Paul Bijnens wrote: Joe Rhett wrote: These systems I can test with to my heart's content, unlike those Windows boxes, so tell me what you need to know. OK, I'll jump on this. I can assure you there is at least one configuration in the world where the excludes do work. First some general info needed: Amanda version on server and client (is client the server itself too?) Gnutar version of server and client? And OS version of server and client? To test and experiment with amanda, it's nice to set up a special config for this, and the file-driver is perfect. (we're testing excludes, not tape drives.). Create a new config for amanda, e.g. Test, which has it's own amanda.conf and disklist. Configure the chg-disk driver for this configuration, see: http://www.amanda.org/docs/howto-filedriver.html Now set up a little disklist too, backing up only a small directory where you have complete control (create files or directories with names you need to test. And make sure the amcheck Test works and a basic amdump Test works too. Do not make the disklist too large, so that amadmin Test force followed by amdump Test runs a few minutes at most. Do not add filesystems or directories to the disklist that also are added in the production disklists. And if you really need to, add record no to its disktype, to avoid interference with your production environment. Creating such a setup takes about an hour, but it's very handy to experiment with amanda. I mean, it's not a wasted resource for the future either. Once you have set it up, try to duplicate the problem. I have already done that all here, and I cannot reproduce the problem. That means there must be some difference between your config and mine. We just need to get that nailed down. -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * *** -- Joe Rhett senior geek meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
Joe Rhett wrote: In the meantime, can you confirm exclude file versus exclude list ? Someone else reported a different syntax that conflicts with the man page, but actually makes more sense to the naked eye. This may be a documentation problem. The documentation is correct: exclude file ./some*thing this excludes all the files matching name some*thing exclude list /some/file /some/file on the client contains a list of patterns to be excluded -- Paul Bijnens, XplanationTel +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, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
GNUTAR exclude lists not working in Windows or Linux
Okay, last year I had observed that perfectly valid gnutar exclude lists
were being ignored by amanda on Windows machines. The best answer anyone
could give me was to build my own tar program that does the excludes, and
replace runtar.
Well now I've enabled my first gnutar linux clients, and they are seeing
the exact same problem. /tmp/amanda/sendsize.debug and runtar.debug both
show that the exclude list is being passed to tar, but they are ignored.
These systems I can test with to my heart's content, unlike those Windows
boxes, so tell me what you need to know.
And as I noted before, and someone tried to explain away, it appears that
the command line invocation for the exclude list is wrong (missing an equals)
runtar.20050601020202.debug:
running: /bin/tar: gtar --create --file - --directory /
--one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/client-host3__0.new --sparse --ignore-failed-read
--totals --exclude-from /etc/exclude.gtar .
/etc/exclude.gtar
$ cat /etc/exclude.gtar
./*
,/
*
disklist:
client-host3 / user-tar
amanda.conf:
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
exclude list /etc/exclude.gtar
priority low
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
--
Joe Rhett
senior geek
meer.net
Re: GNUTAR exclude lists not working in Windows or Linux
On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote: Okay, last year I had observed that perfectly valid gnutar exclude lists were being ignored by amanda on Windows machines. The best answer anyone could give me was to build my own tar program that does the excludes, and replace runtar. I forget the discussion, but there must have been more than that, backing up of windows boxes does not use gnutar but smbclient. Different cmd line syntax for excludes. Well now I've enabled my first gnutar linux clients, and they are seeing the exact same problem. /tmp/amanda/sendsize.debug and runtar.debug both show that the exclude list is being passed to tar, but they are ignored. These systems I can test with to my heart's content, unlike those Windows boxes, so tell me what you need to know. And as I noted before, and someone tried to explain away, it appears that the command line invocation for the exclude list is wrong (missing an equals) runtar.20050601020202.debug: running: /bin/tar: gtar --create --file - --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-host3__0.new --sparse --ignore-failed-read --totals --exclude-from /etc/exclude.gtar . I don't know what equals sign you feel is missing. The man page I have for gnutar does not show an equal sign needed with the --exclude-from option: SYNOPSIS tar [ - ] A --catenate --concatenate | c --create [ -- atime-preserve ] [ -b, --block-size N ] [ -B, --read-full- ... --confirmation ] [ -W, --verify] [ --exclude FILE ] [ - X, --exclude-from FILE ] [ -Z, --compress, --uncompress ] [ ... -X, --exclude-from FILE exclude files listed in FILE /etc/exclude.gtar $ cat /etc/exclude.gtar ./* ,/ * If I recall the syntax correctly, each entry must begin ./ The first is valid and would exclude everything with the possible exception of dot files (eg .profile). Second and third are invalid. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: GNUTAR exclude lists not working in Windows or Linux
On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote: On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote: Okay, last year I had observed that perfectly valid gnutar exclude lists were being ignored by amanda on Windows machines. The best answer anyone could give me was to build my own tar program that does the excludes, and replace runtar. I forget the discussion, but there must have been more than that, A bit more, mostly telling me to use SMB instead, which is nonsense. backing up of windows boxes does not use gnutar but smbclient. Different cmd line syntax for excludes. Every time I talk about Windows, you keep talking about smbclient. Nobody, flat nobody that I know of is stupid enough to run SMB on a public webserver. The windows machines in question are using amanda under cygwin. However, having an identical problem on Linux proves that this isn't related to Windows or Cygwin. I know you've got your head wrapped around smbclient, so let's drop the windows and focus on Linux. Tar isn't honoring the exclude files on Linux. Well now I've enabled my first gnutar linux clients, and they are seeing the exact same problem. /tmp/amanda/sendsize.debug and runtar.debug both show that the exclude list is being passed to tar, but they are ignored. Just to clarify, the entire system (60gb+) is backed up every night. And as I noted before, and someone tried to explain away, it appears that the command line invocation for the exclude list is wrong (missing an equals) runtar.20050601020202.debug: running: /bin/tar: gtar --create --file - --directory / --one-file-system --listed-incremental /var/lib/amanda/gnutar-lists/client-host3__0.new --sparse --ignore-failed-read --totals --exclude-from /etc/exclude.gtar . I don't know what equals sign you feel is missing. The man page I have for gnutar does not show an equal sign needed with the --exclude-from option: Some versions of tar out there apparently don't work properly without the equals sign. Search for it, or trust me. In any case, I agree that it isn't affecting these linux boxes -- either syntax appears to work. /etc/exclude.gtar $ cat /etc/exclude.gtar ./* ,/ * If I recall the syntax correctly, each entry must begin ./ The first is valid and would exclude everything with the possible exception of dot files (eg .profile). Second and third are invalid. That's fine, I was trying everything possible. Right now with those regexs I'm backing up 60gb a night from that system. Wouldn't that suggest something is wrong? I started with just the first regex and added others when it didn't work, so it isn't due to the bad regexes... -- Joe Rhett senior geek meer.net
Re: confusion about exclude lists
On Mon, Mar 10, 2003 at 07:55:31PM -0500, Jon LaBadie wrote: On Mon, Mar 10, 2003 at 03:53:03PM -0800, Rob Helmer wrote: Is there any way I can have one exclude.gtar for /, and one for /usr/local ? For example, I may want /etc and not /usr/local/etc, or vice versa and the exclude list would look at both as an entry for etc. From amanda.conf: #If a relative pathname is specified as the exclude list, #it is searched from within the directory that is #going to be backed up. Thus, each DLE can have its own exclude file. Oh, ok, so you specify the path to the exclude list relative to the dir specified to be backed up, e.g. /export/home/exclude.gtar /exclude.gtar And have this as a disklist : # hostname diskdevice dumptypespindle interface server / normal 0 server /export/homenormal 0 And each client specified the exclude list in their amanda.conf like so : exclude list ./exclude.gtar Am I reading that correctly? Thank you, Rob Helmer
Re: confusion about exclude lists
On Tue, Mar 11, 2003 at 10:48:01AM -0800, Rob Helmer wrote: On Mon, Mar 10, 2003 at 07:55:31PM -0500, Jon LaBadie wrote: On Mon, Mar 10, 2003 at 03:53:03PM -0800, Rob Helmer wrote: Is there any way I can have one exclude.gtar for /, and one for /usr/local ? For example, I may want /etc and not /usr/local/etc, or vice versa and the exclude list would look at both as an entry for etc. From amanda.conf: #If a relative pathname is specified as the exclude list, #it is searched from within the directory that is #going to be backed up. Thus, each DLE can have its own exclude file. Oh, ok, so you specify the path to the exclude list relative to the dir specified to be backed up, e.g. /export/home/exclude.gtar /exclude.gtar And have this as a disklist : # hostname diskdevice dumptypespindle interface server / normal 0 server /export/homenormal 0 And each client specified the exclude list in their amanda.conf like so : Clients don't have amanda.conf's. But ... exclude list ./exclude.gtar Am I reading that correctly? ... that is correct. If you are doing it as you describe, you could have one global exclude list in the server's amanda.conf. Otherwise I think you can have separate entries in any dumptype. So if there is a special need, like you are forbidden to have any extraneous files in the root dir of an entry, you could have a dumptype for that disklist entry that shows an exclude list file elsewhere. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
confusion about exclude lists
Hello, I am backing up Solaris hosts, and I want to use Amanda and GNUtar to do it, but I am a bit confused about how (in)flexible exclude lists are with GNUtar .. Currently, I have the server set up to back itself up, I have an exclude.gtar file, and I am backing up the / and /usr/local slices. Is there any way I can have one exclude.gtar for /, and one for /usr/local ? For example, I may want /etc and not /usr/local/etc, or vice versa and the exclude list would look at both as an entry for etc. Or am I going about this the wrong way? Thanks, Rob
Re: confusion about exclude lists
On Mon, Mar 10, 2003 at 03:53:03PM -0800, Rob Helmer wrote: Hello, I am backing up Solaris hosts, and I want to use Amanda and GNUtar to do it, but I am a bit confused about how (in)flexible exclude lists are with GNUtar .. Currently, I have the server set up to back itself up, I have an exclude.gtar file, and I am backing up the / and /usr/local slices. Is there any way I can have one exclude.gtar for /, and one for /usr/local ? For example, I may want /etc and not /usr/local/etc, or vice versa and the exclude list would look at both as an entry for etc. From amanda.conf: #If a relative pathname is specified as the exclude list, #it is searched from within the directory that is #going to be backed up. Thus, each DLE can have its own exclude file. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: exclude lists on server
John R. Jackson [EMAIL PROTECTED] wrote:
JRJ Is there any amanda-way to have exclude lists on the server and update
JRJ them on the client before each backup? ...
JRJ I have not tried this, but if you're running 2.4.3 (server and client)
JRJ and don't have an excessive number of exclusions, you can set up a
JRJ dummy dumptype with the information, then inherit it into each real
JRJ dumptype as needed:
JRJ
JRJ define dumptype exclude-stuff {
JRJ exclude file append pattern1
JRJ exclude file append pattern2
JRJ exclude file append pattern3
JRJ exclude file append pattern4
JRJ }
[SKIP]
JRJ And so on. You can, of course, have more than one fake dumptype with
JRJ different sets of exclude patterns. And, since append is used, you
JRJ may reference more than one in a real dumptype -- the entries will be
JRJ merged into a single large list.
JRJ
JRJ As I said, I haven't even faintly tried this. It's just an idea based
JRJ on how I'm pretty sure this all works.
Looks like exactly what I need :) Thanks. I will try it and see if
it'll actually work. Looks OK to me, though :)
--
Best regards,
Leonid Mamtchenkov, RHCE
System Administrator
Francoudi Stephanou Ltd.
Re: exclude lists on server
On Wed, 29 Jan 2003, Joshua Baker-LePain wrote: On Wed, 29 Jan 2003 at 3:13am, Leonid Mamtchenkov wrote Is there any amanda-way to have exclude lists on the server and update them on the client before each backup? I think, it would be easier to manage exlude list from the central location, rather then manually copy them over to all clients every time a change is introduced. Well, you could always set up passwordess ssh and scp them over at the beginning of your backup script. Or put them on a read-only NFS export... Marc
Re: exclude lists on server
On Wed, 29 Jan 2003 at 3:13am, Leonid Mamtchenkov wrote Is there any amanda-way to have exclude lists on the server and update them on the client before each backup? I think, it would be easier to manage exlude list from the central location, rather then manually copy them over to all clients every time a change is introduced. Well, you could always set up passwordess ssh and scp them over at the beginning of your backup script. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: exclude lists on server
Joshua Baker-LePain [EMAIL PROTECTED] wrote: Is there any amanda-way to have exclude lists on the server and update them on the client before each backup? I think, it would be easier to manage exlude list from the central location, rather then manually copy them over to all clients every time a change is introduced. JBL JBL Well, you could always set up passwordess ssh and scp them over at the JBL beginning of your backup script. Yeah, well. It's an option with a 5-10 hosts. I am in a situation with more like a hundred+. With ssh/scp approach, I am forced to have more configuration, less security, and less convinience. While the functionality is still achievable, I'd still prefer to have it as amanda feature. :) Any hope? :) -- Best regards, Leonid Mamtchenkov, RHCE System Administrator Francoudi Stephanou Ltd.
Re: exclude lists on server
Is there any amanda-way to have exclude lists on the server and update
them on the client before each backup? ...
I have not tried this, but if you're running 2.4.3 (server and client)
and don't have an excessive number of exclusions, you can set up a
dummy dumptype with the information, then inherit it into each real
dumptype as needed:
define dumptype exclude-stuff {
exclude file append pattern1
exclude file append pattern2
exclude file append pattern3
exclude file append pattern4
}
define dumptype normal {
program GNUTAR
... other stuff
exclude-stuff
}
define dumptype always-full {
program GNUTAR
dumpcycle 0
strategy noinc
skip-incr yes
... other stuff
exclude-stuff
}
And so on. You can, of course, have more than one fake dumptype with
different sets of exclude patterns. And, since append is used, you
may reference more than one in a real dumptype -- the entries will be
merged into a single large list.
As I said, I haven't even faintly tried this. It's just an idea based
on how I'm pretty sure this all works.
Leonid Mamtchenkov
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
smb exclude lists
Hi all,
I have been through all the documentation I can find, and still don't know if
it's possible to exclude a directory from a windows (smb) backup. I have the
following as my dumptype, and PAGEFILE.SYS is ignored but nothing else:
define dumptype comp-smb {
root-tar
comment Root partitions with compression
compress client fast
exclude ./TuxDownloads
exclude ./Documents and Settings\Casey Scott
exclude ./WINNT\system32\config
exclude ./PAGEFILE.SYS
dumpcycle 0
}
Do I have to name every file that I want to be ignored, or is there just a
syntax mistake with the directory declarations?
Thanks,
Casey Scott
Re: smb exclude lists
Hi,
Two things:
First your syntax is bad, in a dumptype with exclude you can only define one
file to exclude. if you use it multiple times, only the last exclude-line is used.
For more the one file to exclude use the exclude list option. It takes a file
listing the files to exclude.
But with samba you are lost as far as i remember.
With amanda and samba you can only exclude one single file with the exclude command,
as the exclude list command does not work with samba due to limitation of the
dumper api or the smb-tar, i don't rem,ember exactly which of both.
Christoph
Casey Scott schrieb:
Hi all,
I have been through all the documentation I can find, and still don't know if
it's possible to exclude a directory from a windows (smb) backup. I have the
following as my dumptype, and PAGEFILE.SYS is ignored but nothing else:
define dumptype comp-smb {
root-tar
comment Root partitions with compression
compress client fast
exclude ./TuxDownloads
exclude ./Documents and Settings\Casey Scott
exclude ./WINNT\system32\config
exclude ./PAGEFILE.SYS
dumpcycle 0
}
Do I have to name every file that I want to be ignored, or is there just a
syntax mistake with the directory declarations?
Thanks,
Casey Scott
Re: Amanda-2.4.3b4 and tar exclude lists working?
Bonjour Jean-Louis, * Jean-Louis Martineau ([EMAIL PROTECTED]) [20020904 20:21] thus spake: Hi Jean-Francois, The relative exclude list works for me. Could you send me all the log files for an amcheck and amdump run? amandad.*.debug selfcheck.*.debug selfcheck.*.exclude sendsize.*.debug sendsize.*.exclude sendbackup.*.debug sendbackup.*.exclude runtar.*.exclude The *.exclude files should be a copy of your .amanda-gnutar-exclude-list.txt? Tar should be called with --exclude-from followed by the path of the corresponding *.exclude file. You upgrade the client and server to 2.4.3b4? well, I'm ashamed of myself! I sifted through all the debug files (not an easy task as this host is both a client from another amanda server and its own server. Don't ask me why, it's a long story. Yes, I made sure that the amanda service ports do not collide in the 2 configurations by using --with-testing=blah ...) Anyways, turns out that I got bitten yet again by the exclude list syntax! Quiz: what is the difference between the following entries in an exclude list? 1 ./foo 2 ./foo/ 3 ./foo/* case 1 directory ./foo won't be in the backup image case 2 matches nothing (that was my mistake) case 3 directory ./foo will be in the backup image but nothing below it. Works now. I feel so silly! Thanks for the help to Frank and Jean-Louis. One day I'll write a blurb on my setup: STK L40 jukebox with 4 LTO Ultrium tape drives accessed concurrently, one Ecrix 15 slots VXA tape library and a few measly DLT tape drives. I think I'm around 5TB taken care of by Amanda. I'm about to ditch my last propriatery backup software (NetWorker) driving an ADIC library with DLTs... You guys are doing an outstanding job! Thanks again, jf Jean-Louis -- Thought to justify wrong doings, and speech to conceal thoughts.
Re: Amanda-2.4.3b4 and tar exclude lists working?
Hi Jean-Francois, The relative exclude list works for me. Could you send me all the log files for an amcheck and amdump run? amandad.*.debug selfcheck.*.debug selfcheck.*.exclude sendsize.*.debug sendsize.*.exclude sendbackup.*.debug sendbackup.*.exclude runtar.*.exclude The *.exclude files should be a copy of your .amanda-gnutar-exclude-list.txt? Tar should be called with --exclude-from followed by the path of the corresponding *.exclude file. You upgrade the client and server to 2.4.3b4? Jean-Louis On Tue, Sep 03, 2002 at 10:10:18AM -0400, Jean-Francois Malouin wrote: Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. My setup: amandad: version 2.4.3b4-20020829 amandad: build: VERSION=Amanda-2.4.3b4-20020829 amandad:BUILT_DATE=Sun Sep 1 15:21:17 EDT 2002 amandad:BUILT_MACH=Linux blade.bic.mni.mcgill.ca 2.4.9-31 #1 Tue Feb 26 06:53:37 EST 2002 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/opt/amanda_vxa' '--with-user=amanda' '--with-group=disk' '--with-testing=vxa' '--with-tcpportrange=16384,16896' '--with-udpportrange=700,731' '--with-tape-device=/dev/nst0' '--with-changer-device=/dev/changer' '--with-tape-server=blade' '--with-index-server=blade' '--with-config=vxa' regards, jf -- Cats are intended to teach us that not everything in nature has a function. -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Amanda-2.4.3b4 and tar exclude lists working?
Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. My setup: amandad: version 2.4.3b4-20020829 amandad: build: VERSION=Amanda-2.4.3b4-20020829 amandad:BUILT_DATE=Sun Sep 1 15:21:17 EDT 2002 amandad:BUILT_MACH=Linux blade.bic.mni.mcgill.ca 2.4.9-31 #1 Tue Feb 26 06:53:37 EST 2002 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/opt/amanda_vxa' '--with-user=amanda' '--with-group=disk' '--with-testing=vxa' '--with-tcpportrange=16384,16896' '--with-udpportrange=700,731' '--with-tape-device=/dev/nst0' '--with-changer-device=/dev/changer' '--with-tape-server=blade' '--with-index-server=blade' '--with-config=vxa' regards, jf -- Cats are intended to teach us that not everything in nature has a function.
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin [EMAIL PROTECTED] wrote: Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. Do you have an exclude list properly defined in your dumptype? Are you using tar? Is the exclude list file in the top level of the directory you're trying to back up and is it in the correct format? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Amanda-2.4.3b4 and tar exclude lists working?
* Frank Smith ([EMAIL PROTECTED]) [20020903 11:18] thus spake:
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Hello,
I just installed and configured amanda-2.4.3b4-20020829 on a Linux box
with an ecrix tape library and I might be stumbling on some bug and/or
feature: relative path exclude list don't seem to be used at all...
Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see
that this version is supposed to have this fixed... Is this really the
case? I can provide debug files on demand.
Do you have an exclude list properly defined in your dumptype?
Are you using tar?
Is the exclude list file in the top level of the directory you're trying
to back up and is it in the correct format?
I've been using amanda for a few years now and I'm fully aware of all
the quirks in setting up exclude lists. I have 3 other servers running
2.4.2p2 with relative exclude lists with tape libraries (exb-200,
adic-218 and stk-L40) with no problems whatsoever. For this one, I
decided to jump ahead with 2.4.3b4...maybe I'll go back to 2.4.2p2.
Anyways, yes, I'm using tar (GNU tar) 1.13.19.
Here are the dumptypes from amanda.conf:
---
amanda.conf
---
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
priority low
}
define dumptype high-tar-raid-epilepsy {
root-tar
comment partitions dumped with tar
priority high
exclude list .amanda-gnutar-exclude-list.txt
}
---
disklist entry
---
blade /raid/epilepsy high-tar-raid-epilepsy
---
On the host blade (amanda server and client) I created a file called
/raid/epilepsy/.amanda-gnutar-exclude-list.txt:
[root@blade]# cd /raid/epilepsy/
[root@blade]# ls -la .amanda-gnutar-exclude-list.txt
-rw---1 amanda disk 123 Sep 2 08:18
.amanda-gnutar-exclude-list.txt
---
exclude file
---
[root@blade]# cat .amanda-gnutar-exclude-list.txt
./diffusion/
./extra-TLE/
./F_MRI/
./MRI_misc/
./MT/
./neda/
./PREVIOUS/
./relaxo/
./restore/
./samson/
./thalamus/
./TLE/
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Thanks!
jf
--
Cats are intended to teach us that not everything in nature has a function.
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 11:41:29 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
* Frank Smith ([EMAIL PROTECTED]) [20020903 11:18] thus spake:
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Hello,
I just installed and configured amanda-2.4.3b4-20020829 on a Linux box
with an ecrix tape library and I might be stumbling on some bug and/or
feature: relative path exclude list don't seem to be used at all...
Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see
that this version is supposed to have this fixed... Is this really the
case? I can provide debug files on demand.
Do you have an exclude list properly defined in your dumptype?
Are you using tar?
Is the exclude list file in the top level of the directory you're trying
to back up and is it in the correct format?
I've been using amanda for a few years now and I'm fully aware of all
the quirks in setting up exclude lists. I have 3 other servers running
2.4.2p2 with relative exclude lists with tape libraries (exb-200,
adic-218 and stk-L40) with no problems whatsoever. For this one, I
decided to jump ahead with 2.4.3b4...maybe I'll go back to 2.4.2p2.
Anyways, yes, I'm using tar (GNU tar) 1.13.19.
Here are the dumptypes from amanda.conf:
---
amanda.conf
---
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
priority low
}
define dumptype high-tar-raid-epilepsy {
root-tar
comment partitions dumped with tar
priority high
exclude list .amanda-gnutar-exclude-list.txt
}
---
disklist entry
---
blade /raid/epilepsy high-tar-raid-epilepsy
---
On the host blade (amanda server and client) I created a file called
/raid/epilepsy/.amanda-gnutar-exclude-list.txt:
[root@blade]# cd /raid/epilepsy/
[root@blade]# ls -la .amanda-gnutar-exclude-list.txt
-rw---1 amanda disk 123 Sep 2 08:18
.amanda-gnutar-exclude-list.txt
---
exclude file
---
[root@blade]# cat .amanda-gnutar-exclude-list.txt
./diffusion/
./extra-TLE/
./F_MRI/
./MRI_misc/
./MT/
./neda/
./PREVIOUS/
./relaxo/
./restore/
./samson/
./thalamus/
./TLE/
Yes, it looks like you have it set up correctly, maybe it is a 2.4.3b4
thing (I'm still running 2.4.2p2). What issues are you seeing with
the latest version?
Unrelated question:
Doesn't the trailing slash on your exclude list entries mean that only
those directories themselves are skipped and not any subdirectories?
I leave off the slash to prune the directory tree at that point, and
can't think of too many uses for excluding a directory while backing
up its subdirectories. Or possibly my idea of exclude syntax is off.
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Amanda-2.4.3b4 and tar exclude lists working?
* Frank Smith ([EMAIL PROTECTED]) [20020903 12:53] thus spake: [...] --- exclude file --- [root@blade]# cat .amanda-gnutar-exclude-list.txt ./diffusion/ ./extra-TLE/ ./F_MRI/ ./MRI_misc/ ./MT/ ./neda/ ./PREVIOUS/ ./relaxo/ ./restore/ ./samson/ ./thalamus/ ./TLE/ Yes, it looks like you have it set up correctly, maybe it is a 2.4.3b4 thing (I'm still running 2.4.2p2). What issues are you seeing with the latest version? some chunk is way beyond tape capacity, but with the exclude list it should fit nicely. Looking at my logs I see that somehow, when amanda makes the schedule it does not take into account the exclude list, miscalculate the size of the chunk and so complains that it can't be backed up because it's too big: --- amandad debug file contains: --- [...] Amanda 2.4 REQ HANDLE 000-18320808 SEQ 1031029801 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9f00;maxdumps=1;hostname=blade; [...] GNUTAR /raid/epilepsy 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;index;exclude-list=.amanda-gnutar-exclude-list.txt; [...] Amanda 2.4 REP HANDLE 000-18320808 SEQ 1031029801 OPTIONS features=feff9f00; /raid/epilepsy 0 SIZE 35162160 --- sendsize debug file contains: sendsize: debug 1 pid 24383 ruid 33 euid 33: start at Tue Sep 3 01:10:00 2002 sendsize: version 2.4.3b4-20020829 sendsize[24383]: time 0.480: waiting for any estimate child sendsize[24510]: time 0.481: calculating for amname '/raid/epilepsy', dirname '/raid/epilepsy', spindle -1 sendsize[24510]: time 0.481: getting size via gnutar for /raid/epilepsy level 0 sendsize[24510]: time 0.492: spawning /opt/amanda_vxa/libexec/runtar in pipeline sendsize[24510]: argument list: /bin/gtar --create --file /dev/null --directory /raid/epilepsy --one-file-system --listed-incremental /opt/amanda_vxa/var/amanda/gnutar-lists/blade_raid_epilepsy_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude . sendsize[24510]: time 7.731: Total bytes written: 36006051840 (33GB, 4.2GB/s) sendsize[24510]: time 7.732: . sendsize[24510]: estimate time for /raid/epilepsy level 0: 7.240 sendsize[24510]: estimate size for /raid/epilepsy level 0: 35162160 KB sendsize[24510]: time 7.732: waiting for /bin/gtar /raid/epilepsy child sendsize[24510]: time 7.732: after /bin/gtar /raid/epilepsy wait sendsize[24510]: time 7.733: done with amname '/raid/epilepsy', dirname '/raid/epilepsy', spindle -1 sendsize[24383]: time 7.733: child 24510 terminated normally --- Notice above the line Total bytes written: 36006051840 (33GB... --- --- The file from the above output --exclude-from contains my exclude file list: --- [root@blade]# cat /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude ./diffusion/ ./extra-TLE/ ./F_MRI/ ./MRI_misc/ ./MT/ ./neda/ ./PREVIOUS/ ./relaxo/ ./restore/ ./samson/ ./thalamus/ ./TLE/ My exclude list! --- --- runtar output --- [root@blade]# cat /tmp/amanda/runtar.20020903011000.debug runtar: debug 1 pid 24519 ruid 33 euid 0: start at Tue Sep 3 01:10:00 2002 /bin/gtar: version 2.4.3b4-20020829 running: /bin/gtar: /bin/gtar --create --file /dev/null --directory /raid/epilepsy --one-file-system --listed-incremental /opt/amanda_vxa/var/amanda/gnutar-lists/blade_raid_epilepsy_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude . Unrelated question: Doesn't the trailing slash on your exclude list entries mean that only those directories themselves are skipped and not any subdirectories? I leave off the slash to prune the directory tree at that point, and can't think of too many uses for excluding a directory while backing up its subdirectories. Or possibly my idea of exclude syntax is off. I sure don't know! But I suspect that you're right. Actually I shoud rather have something like ./blah/* Thanks for the time, jf Frank -- Thought to justify wrong doings, and speech to conceal thoughts.
problems with GNUTAR exclude-lists
I'm trying to configure an amanda server/client to use GNUTAR with exclude
lists. GNUTAR works great, but the excludes don't!
The basic configuration is like this:
define dumptype global {
comment Global definitions
index yes
compress client best
#maxdump 2
holdingdisk true
record yes
}
define dumptype bugs {
global
comment Backup incremental, remoto, comp best
holdingdisk yes
program GNUTAR
priority medium
exclude list /usr/local/etc/amanda/exclude.gtar
compress client best
dumpcycle 5
}
And the disklist contains this:
bugs /space bugs -1 hme0
in bugs I have the file /usr/local/etc/amanda/exclude.gtar:
martin@bugs:~ cat /usr/local/etc/amanda/exclude.gtar
./pruebas/
./amanda/
martin@bugs:~
But it's not excluding those 2 directories, and the problem is that the dumps
are growing to big.
What can be wrong?
--
Porqué usar una base de datos relacional cualquiera,
si podés usar PostgreSQL?
-
Martín Marqués |[EMAIL PROTECTED]
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
-
Re: problems with GNUTAR exclude-lists
On Thu, 4 Apr 2002 at 7:57am, Martín Marqués wrote martin@bugs:~ cat /usr/local/etc/amanda/exclude.gtar ./pruebas/ ./amanda/ martin@bugs:~ But it's not excluding those 2 directories, and the problem is that the dumps are growing to big. Just a guess (but this is what I use) -- lose the trailing slashes: ./pruebas ./amanda It works for me(TM). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
