turn off --one-file-system when using tar
Hi all, I'm running amanda 2.4.5. on a number of FC4 servers. I'm using gnutar (1.15) Is there an option available to turn the --one-file-system option off in a dumptype config? By default this command line option is parsed to gnutar when running a backup. Is there an easy way to turn this option off in a config file? Thanks! Dennis
Re: Fixed amcheck, one more question (or two)
Jon LaBadie wrote: amlabel creates the tapelist, not amdump and friends. If you want to recreate it by hand do entries of the form: 0 vtape64 reuse 0 vtape63 reuse Reverse order, the first one you want used at the bottom, last at the top. ...or else, just `amlabel' the tapes again when you want to overwrite them. As long as you put the same label on them that is already there, amlabel shouldn't complain. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: turn off --one-file-system when using tar
On Thursday 14 September 2006 04:58, Dennis Ortsen wrote: >Hi all, > >I'm running amanda 2.4.5. on a number of FC4 servers. > >I'm using gnutar (1.15) You'll need to be more specific, 1.15-1, 1.15-91 etc. >Is there an option available to turn the --one-file-system option off >in a dumptype config? By default this command line option is parsed to >gnutar when running a backup. Is there an easy way to turn this option >off in a config file? > >Thanks! > >Dennis -- 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) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
I/O error on labelling
Somebody knows why I receive this error when I label a tape? -sh-3.00$ amlabel mybbookInSite mybbookInSite-10 slot 10 labeling tape in slot 10 (/dev/nst0): rewinding, reading label, not an amanda tape (Input/output error) rewinding, writing label mybbookInSite-10, checking label, done. After that I see that the tape that was previously on slot 10 is on the data transfer element (this is correct, I think). How can I check that the tape has been labeled correctly? Those are the settings in the amanda.conf regarding the tape drive: runtapes 1 tpchanger "chg-zd-mtx" tapedev "/dev/nst0" rawtapedev "/dev/null" changerfile "/etc/amanda/mybbookInSite/changer.conf" changerdev "/dev/sg2" And this is the changer.conf: firstslot=1 lastslot=16 autoclean=0 havereader=1 offline_before_unload=0 poll_drive_ready=10 max_drive_wait=120 unloadpause=20 driveslot=0 Using Amanda 2.5.1. Thanks, -- Fabio Corazza - Engineering NewBay Software, Ltd. Wilson House, Fenian Street, Dublin 2, Ireland Phone: +353 1 634 5490 - e-mail: [EMAIL PROTECTED]
Re: I/O error on labelling
Fabio Corazza wrote: Somebody knows why I receive this error when I label a tape? -sh-3.00$ amlabel mybbookInSite mybbookInSite-10 slot 10 labeling tape in slot 10 (/dev/nst0): rewinding, reading label, not an amanda tape (Input/output error) rewinding, writing label mybbookInSite-10, checking label, done. You mean the `Input/output error'? That is normal; your tape hadn't been used before and amanda tried to read a former tape label off it. Since the tape was emtpy, it couldn't complete that first read. That's normal behaviour for amlabel. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: turn off --one-file-system when using tar
>I'm running amanda 2.4.5. on a number of FC4 servers. > >I'm using gnutar (1.15) You'll need to be more specific, 1.15-1, 1.15-91 etc. tar-1.15.1-11.FC4 >Is there an option available to turn the --one-file-system option off >in a dumptype config? By default this command line option is parsed to >gnutar when running a backup. Is there an easy way to turn this option >off in a config file? Dennis
Resuming interupted dumps
Is there a way to resume a level0 dump wheree it left off, rather than starting all over again, in the even of a client reboot during the dump? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: turn off --one-file-system when using tar
On 2006-09-14 10:58, Dennis Ortsen wrote: Hi all, I'm running amanda 2.4.5. on a number of FC4 servers. I'm using gnutar (1.15) Is there an option available to turn the --one-file-system option off in a dumptype config? By default this command line option is parsed to gnutar when running a backup. Is there an easy way to turn this option off in a config file? You'll have to change the source and recompile or use a wrapper program which removes the --one-file-system option. To get started with a wrapper see: http://wiki.zmanda.com/index.php/Backup_client#Paul_Bijnens.27s_suggestions Curiousity... why would you like/need to do that??? -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: turn off --one-file-system when using tar
On Thu, 2006-09-14 at 14:58 +0200, Paul Bijnens wrote: > On 2006-09-14 10:58, Dennis Ortsen wrote: > > Hi all, > > > > I'm running amanda 2.4.5. on a number of FC4 servers. > > > > I'm using gnutar (1.15) > > > > Is there an option available to turn the --one-file-system option off > > in a dumptype config? By default this command line option is parsed to > > gnutar when running a backup. Is there an easy way to turn this option > > off in a config file? > > You'll have to change the source and recompile or use a wrapper program > which removes the --one-file-system option. > > To get started with a wrapper see: > > http://wiki.zmanda.com/index.php/Backup_client#Paul_Bijnens.27s_suggestions > > Curiousity... why would you like/need to do that??? > to prevent myself from forgetting to add another DLE for a lower mounted filesystem. for instance: I've got a DLE -> jupiter.domain.org/var/wwwtar-med in /var/www I have several directories, one of them has another filesystem mounted underneath (logical volume management), for instance /var/www/rpm As it is now I have to remember to add a new DLE, but whouldn't this imply that instead of having /var/www as a DLE, I need to add /var/www/rpm and all the other directories that are on the same level as /var/www/rpm? Like /var/www/insite, /var/www/wiki, /var/www/othersite? Dennis
Re: turn off --one-file-system when using tar
On Thu, Sep 14, 2006 at 10:58:28AM +0200, Dennis Ortsen wrote:
> Hi all,
>
> I'm running amanda 2.4.5. on a number of FC4 servers.
>
> I'm using gnutar (1.15)
>
> Is there an option available to turn the --one-file-system option off
> in a dumptype config? By default this command line option is parsed to
> gnutar when running a backup. Is there an easy way to turn this option
> off in a config file?
None that I know of.
It sometimes help to know what you are trying to accomplish.
That might allow us to suggest alternatives to the single
approach you are asking about. But I'm going to guess anyway.
My guess is you want one DLE to backup multiple file systems.
Two other approaches:
A gnutar wrapper that checks which DLE is passing through
and turns off the option for those you want it off.
A single DLE with include statements for the two starting
directories. The "one-file-system" option in my testing
(the manpage is deficient here) suggests it does not cross
a mount point. But it can be told to start in multiple
places, each a different file system. Within each it
will not cross, but one archive can contain multiple FS.
I've tried successfully something like this for a single
DLE backing up /opt and /var, each a distinct FS:
host MISC / {# / is above both FS
root-comp-tar # choose your dumptype
include file "./opt"
include file append "./var"
}
My spool directory for mail, print jobs, ... is /var/spool.
It is a separate file system so the above would skip over
the spool file system just as if I had backed up /var by
itself. If I wanted a single DLE to handle /var/spool
and its parent /var I might try this (untested)
host VAR /var { # Or simply "host /var {"
root-comp-tar
include file "."
include file append "./spool"
}
HTH
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: turn off --one-file-system when using tar
On Thu, Sep 14, 2006 at 03:56:55PM +0200, Dennis Ortsen wrote:
> On Thu, 2006-09-14 at 14:58 +0200, Paul Bijnens wrote:
> > On 2006-09-14 10:58, Dennis Ortsen wrote:
> > > Hi all,
> > >
> > > Is there an option available to turn the --one-file-system option off
> > > in a dumptype config? By default this command line option is parsed to
> > > gnutar when running a backup. Is there an easy way to turn this option
> > > off in a config file?
> >
> > Curiousity... why would you like/need to do that???
> >
>
> to prevent myself from forgetting to add another DLE for a lower mounted
> filesystem.
>
> for instance:
>
> I've got a DLE -> jupiter.domain.org /var/wwwtar-med
>
> in /var/www I have several directories, one of them has another
> filesystem mounted underneath (logical volume management), for
> instance /var/www/rpm
>
> As it is now I have to remember to add a new DLE, but whouldn't this
> imply that instead of having /var/www as a DLE, I need to
> add /var/www/rpm and all the other directories that are on the same
> level as /var/www/rpm?
> Like /var/www/insite, /var/www/wiki, /var/www/othersite?
>
Sounds like my guess was pretty close.
If all the extra mounted file systems are like rpm, mounted just
under /var/www, then you might consider a DLE using wildcards
like this (again, untested)
jupiter.domain.org /var/www {
tar-med
include file "./*" # may include several mount points
}
I'd suggest a comment because someone looking at that a year from
now might think "why add the include line, it is redundant".
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: I/O error on labelling
On Thu, Sep 14, 2006 at 12:14:43PM +0100, Fabio Corazza wrote: > Somebody knows why I receive this error when I label a tape? > > -sh-3.00$ amlabel mybbookInSite mybbookInSite-10 slot 10 > labeling tape in slot 10 (/dev/nst0): > rewinding, reading label, not an amanda tape (Input/output error) > rewinding, writing label mybbookInSite-10, checking label, done. > > After that I see that the tape that was previously on slot 10 is on the > data transfer element (this is correct, I think). How can I check that > the tape has been labeled correctly? > man amtape -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Resuming interupted dumps
On Thu, Sep 14, 2006 at 09:10:49AM -0400, [EMAIL PROTECTED] wrote: > > Is there a way to resume a level0 dump wheree it left off, rather than > starting all over again, in the even of a client reboot during the dump? > no -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: turn off --one-file-system when using tar
On Thursday 14 September 2006 07:43, Dennis Ortsen wrote: >> >I'm running amanda 2.4.5. on a number of FC4 servers. >> > >> >I'm using gnutar (1.15) >> >> You'll need to be more specific, 1.15-1, 1.15-91 etc. > >tar-1.15.1-11.FC4 That _should_ be a good one. >> >Is there an option available to turn the --one-file-system option off >> >in a dumptype config? By default this command line option is parsed to >> >gnutar when running a backup. Is there an easy way to turn this option >> >off in a config file? I do not know, but you can turn the debug level up to a much higher level and give the results a good searching to see how its done. I'm not sure I'd want to remove that limitation however as its there for a good reason I'm sure. >Dennis -- 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) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: I/O error on labelling
On Thursday 14 September 2006 07:14, Fabio Corazza wrote: >Somebody knows why I receive this error when I label a tape? > >-sh-3.00$ amlabel mybbookInSite mybbookInSite-10 slot 10 >labeling tape in slot 10 (/dev/nst0): >rewinding, reading label, not an amanda tape (Input/output error) This is normal for a tape that does not already contain a valid label 1st block. >rewinding, writing label mybbookInSite-10, checking label, done. Generally, if it says it did it, it did it ok. >After that I see that the tape that was previously on slot 10 is on the >data transfer element (this is correct, I think). How can I check that >the tape has been labeled correctly? Thats something you should be able to do with the 'mtx' utility, which can cause tapes to be loaded or unloaded and placed back in the rack, usually by its rack position number. Once the tape has been loaded and recognized by the drive as shown by an 'mt -f /dev/ice status returning a 'BOT' (begining of tape) status, then: 'dd if=/dev/ice count=1' should spit out the first block to stdout, your screen. This should contain the tape label amlabel applied followed by about 32,730 bytes of zeros, so it won't look like 32k on screen. Here's this mornings vtape equivalent file: AMANDA: TAPESTART DATE 20060914001000 TAPE Dailys-20 014 The datestamp may be shorter in your version of amanda. There may be other diffs too as the above is from this mornings vtape, not a real physical tape. >Those are the settings in the amanda.conf regarding the tape drive: > >runtapes 1 >tpchanger "chg-zd-mtx" >tapedev "/dev/nst0" >rawtapedev "/dev/null" >changerfile "/etc/amanda/mybbookInSite/changer.conf" >changerdev "/dev/sg2" > >And this is the changer.conf: > >firstslot=1 >lastslot=16 >autoclean=0 >havereader=1 >offline_before_unload=0 >poll_drive_ready=10 >max_drive_wait=120 >unloadpause=20 >driveslot=0 > > >Using Amanda 2.5.1. > > > >Thanks, -- 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) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: turn off --one-file-system when using tar
On 2006-09-14 16:20, Jon LaBadie wrote:
On Thu, Sep 14, 2006 at 03:56:55PM +0200, Dennis Ortsen wrote:
On Thu, 2006-09-14 at 14:58 +0200, Paul Bijnens wrote:
On 2006-09-14 10:58, Dennis Ortsen wrote:
Hi all,
Is there an option available to turn the --one-file-system option off
in a dumptype config? By default this command line option is parsed to
gnutar when running a backup. Is there an easy way to turn this option
off in a config file?
Curiousity... why would you like/need to do that???
to prevent myself from forgetting to add another DLE for a lower mounted
filesystem.
for instance:
I've got a DLE -> jupiter.domain.org /var/wwwtar-med
in /var/www I have several directories, one of them has another
filesystem mounted underneath (logical volume management), for
instance /var/www/rpm
As it is now I have to remember to add a new DLE, but whouldn't this
imply that instead of having /var/www as a DLE, I need to
add /var/www/rpm and all the other directories that are on the same
level as /var/www/rpm?
Like /var/www/insite, /var/www/wiki, /var/www/othersite?
Sounds like my guess was pretty close.
If all the extra mounted file systems are like rpm, mounted just
under /var/www, then you might consider a DLE using wildcards
like this (again, untested)
jupiter.domain.org /var/www {
tar-med
include file "./*"# may include several mount points
}
I'd suggest a comment because someone looking at that a year from
now might think "why add the include line, it is redundant".
This is indeed a far better approach than omitting the option
"--one-file-system".
You could create an enormous backup just by someone having
an automounted directory (/net, /home,...) touched minutes before
Amanda starts or just by having the CWD on such place.
Left in a DVD by accident?, or having your 200 Gbyte external USB
disk still connected -- all included.
Mounted snapshots? All included.
And what if you mount two filesystems in a different place?
So you end up with a fairly large exclude list to avoid all
these exceptions. And then you will need to change the exclude
list when you change your filesystem.
And we're back to the same problem we tried to avoid :-).
Why not write a little script that looks what is mounted, and
alerts with the differences in disklist.
(Hey, maybe that could even be added to amcheck, which could
classify this as warning only, or only test for this when explicitly
asked.)
--
Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: I/O error on labelling
On Sep 14, Gene Heskett wrote: > On Thursday 14 September 2006 07:14, Fabio Corazza wrote: > >rewinding, writing label mybbookInSite-10, checking label, done. > > Generally, if it says it did it, it did it ok. > > >After that I see that the tape that was previously on slot 10 is on the > >data transfer element (this is correct, I think). How can I check that > >the tape has been labeled correctly? > > Once the tape has been loaded and recognized by the drive as shown by an > 'mt -f /dev/ice status returning a 'BOT' (begining of tape) status, then: > 'dd if=/dev/ice count=1' should spit out the first block to stdout, your > screen. This should contain the tape label amlabel applied followed by > about 32,730 bytes of zeros, so it won't look like 32k on screen. Here's > this mornings vtape equivalent file: > > AMANDA: TAPESTART DATE 20060914001000 TAPE Dailys-20 > 014 > To use an amanda tool, you may also use amcheck for this. Among other things the label of the tape and whether it fits in your configuration is checked, too. The dd method may be faster anyway. regards, Andreas Putzo
amtapetype "aborts" on XServe running Yellow Dog Linux 4.1
Here is what I've gotten twice, with hardware compression on and off.
[EMAIL PROTECTED] amanda]# ./sbin/amtapetype -f /dev/tape -e 400g -o
Writing 2048 Mbyte compresseable data: 31 sec
Writing 2048 Mbyte uncompresseable data: 31 sec
Estimated time to write 2 * 409600 Mbyte: 12400 sec = 3 h 26 min
wrote 12320768 32Kb blocks in 94 files in 5655 seconds (short write)
wrote 12386304 32Kb blocks in 189 files in 6025 seconds (short write)
define tapetype unknown-tapetype {
comment "just produced by tapetype prog (hardware compression off)"
length 386048 mbytes
filemark 0 kbytes
speed 67752 kps
}
*** glibc detected *** free(): invalid pointer: 0xf7d9a000 ***
Aborted
Anybody got any ideas? Will this cause a problem, or is it a problem?
Says it aborted, but it gave me a tapetype definition that looks
right (it's lto-3 ultrium which according to the wiki at
http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO_Ultrium_3_with_400.2F800_Gbyte_tapes
for 400G tapes the tape length is 402432 mbytes) Not sure if this is
cause for concern.
Thanks
Nick
--
Nick Jones
University of Iowa
Dept of Neurology
Systems Analyst
319-356-0451
changes to amanda.conf for amanda 2.5.1?
To all, I’ve changed up to Amanda 2.5.1. For some reason, these three parameters that used to work in Amanda.conf didn’t work anymore. diskdir “var/tmp: disksize 25000 MB logfile “/usr/adm/Amanda/test/log” When I ran amcheck it tells me on those lines that "/usr/local/etc/amanda/test/amanda.conf", line 19: configuration keyword expected "/usr/local/etc/amanda/test/amanda.conf", line 19: end of line is expected When I commented out those three parameters, amcheck works just fine. Is there a change in the parameter, or the syntax, that I did not know about? Victor Chan Network Administrator CSI Financial Services 3636 Nobel Drive #215 San Diego, CA 92122 (858)200-9211
Re: changes to amanda.conf for amanda 2.5.1?
Chan, Victor wrote:
> To all,
>
>
>
> I've changed up to Amanda 2.5.1. For some reason, these three
> parameters that used to work in Amanda.conf didn't work anymore.
>
What version were you using?
>
>
> diskdir "var/tmp:
I don't see that in my 2.4.5 or my 2.5 configs. I vaguely recall that
was what the 'holdingdisk' parameter used to be called. Also, you're
missing the closing quote so the parser would choke anyway.
>
> disksize 25000 MB
Same issue as above. You need something like:
holdingdisk name {
use 200 Gb
...
}
>
> logfile "/usr/adm/Amanda/test/log"
The log filenames are compiled in, but there is a logdir option to
specify the directory the logfiles get written into. You might want
to read through the entire amanda.conf man page, as there are many
new options worth considering even if your old config does work.
Frank
>
>
>
> When I ran amcheck it tells me on those lines that
>
>
>
>
>
> "/usr/local/etc/amanda/test/amanda.conf", line 19: configuration keyword
> expected
>
> "/usr/local/etc/amanda/test/amanda.conf", line 19: end of line is
> expected
>
>
>
> When I commented out those three parameters, amcheck works just fine.
>
>
>
> Is there a change in the parameter, or the syntax, that I did not know
> about?
>
>
>
> Victor Chan
>
> Network Administrator
>
> CSI Financial Services
>
> 3636 Nobel Drive #215
>
> San Diego, CA 92122
>
> (858)200-9211
>
>
>
>
--
Frank Smith [EMAIL PROTECTED]
Sr. Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: changes to amanda.conf for amanda 2.5.1?
On Thu, Sep 14, 2006 at 05:18:46PM -0600, Chan, Victor wrote: > To all, > > > > I've changed up to Amanda 2.5.1. For some reason, these three > parameters that used to work in Amanda.conf didn't work anymore. > > > > diskdir "var/tmp: No '/' at start of /var/tmp No '"' at end of string Did you really mean to have a ':' there? Perhaps an email typo, but if not maybe the cause of your troubles. > > disksize 25000 MB > > logfile "/usr/adm/Amanda/test/log" > > > > When I ran amcheck it tells me on those lines that > > > > > > "/usr/local/etc/amanda/test/amanda.conf", line 19: configuration keyword > expected > > "/usr/local/etc/amanda/test/amanda.conf", line 19: end of line is > expected > > > > When I commented out those three parameters, amcheck works just fine. > > > > Is there a change in the parameter, or the syntax, that I did not know > about? > > > > Victor Chan > > Network Administrator > > CSI Financial Services > > 3636 Nobel Drive #215 > > San Diego, CA 92122 > > (858)200-9211 > > > >>> End of included message <<< -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
