Re: one large partition
>But it will skip ordinary files at the top level. Also, any >directories created there without remembering to change the >backup scheme. Agreed. Which is what: ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.* sort of addresses (or, more correctly, hacks around :-). >jon John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: one large partition
On Thu, Nov 09, 2000 at 06:46:40PM -0500, John R. Jackson wrote: > >And I would only be able to backup ALL hda or ALL hdb, but not just > >/usr/bin without getting into GNUTAR exclusions and such...maybe I'm > >wrong... > > You're wrong :-). > > If you put a directory name in your disklist (instead of something like > "hdb" or "/dev/hdb"), that just gets passed to GNU tar as is, so it's > pretty easy to just do a subdirectory. > > Now the problem is if you also list the top level mount point as well. > That would cause it and the subdirectory to both be dumped. That's where > you would need an exclusion to ignore the subdirectory when doing the > whole partition. > > But if you don't have very many subdirectories and list each one by > itself and never mention the top level, it will work just fine. But it will skip ordinary files at the top level. Also, any directories created there without remembering to change the backup scheme. For that coverage, you have to go back to listing the root directory and excluding the individually backed-up subdirs. jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: one large partition
>And I would only be able to backup ALL hda or ALL hdb, but not just >/usr/bin without getting into GNUTAR exclusions and such...maybe I'm >wrong... You're wrong :-). If you put a directory name in your disklist (instead of something like "hdb" or "/dev/hdb"), that just gets passed to GNU tar as is, so it's pretty easy to just do a subdirectory. Now the problem is if you also list the top level mount point as well. That would cause it and the subdirectory to both be dumped. That's where you would need an exclusion to ignore the subdirectory when doing the whole partition. But if you don't have very many subdirectories and list each one by itself and never mention the top level, it will work just fine. >DL John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: one large partition
Hmm! I thought AMANDA only backed up whole "disks" or "partitions"...i.e: [lloy0076] % df /dev/hda /usr /dev/hdb /tmp And I would only be able to backup ALL hda or ALL hdb, but not just /usr/bin without getting into GNUTAR exclusions and such...maybe I'm wrong... DL
Re: one large partition
>... I am not very familiar with the setup you are >talking about. Do you know where I can find some docs and references to >this kind of setup? ... I don't think it's really documented anyplace. The idea is that if your file system is named /some/big/filesystem and it contains sudirectories sub1, sub2 and sub3 that instead of just listing /some/big/filesystem in disklist you would instead enter each one: the-client/some/big/filesystem/sub1 the-dumptype the-client/some/big/filesystem/sub2 the-dumptype the-client/some/big/filesystem/sub3 the-dumptype The idea/hope is that the individual subdirectories are smaller than a tape and so Amanda will not have to split them. Note that if you have "too many" file systems, you may overflow the UDP packet size Amanda uses. That can be changed in the source from 8 KBytes to 64 KBytes in common-src/dgram.h (symbol MAX_DGRAM). You'll need to do a complete rebuild of both client and server. The value is already changed to this at 2.4.2. You might also look at: ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.* for another way of breaking up a large parent area. Note that you have to use GNU tar for this, and that has "issues", like the access time for all backed up files will be altered. You should also probably avoid version 1.13.* as it's known to have lots of problems with Amanda. Use 1.12 and apply the patches at www.amanda.org. >Sherrill John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: one large partition
[snip] > >We are using tape changer, but amanda can't split one > >file. Is there any way to get around this problem? > > The standard solution is to use GNU tar and logically (to Amanda) break > up the partition into individually backed up pieces. There are tricks > to auto-manage this and group things, but they still use this basic plan. > [snip] John, Thanks for the info. I am not very familiar with the setup you are talking about. Do you know where I can find some docs and references to this kind of setup? Thank you vey much. Sherrill ### Sherrill (Peichih) Verbrugge [EMAIL PROTECTED] http://www.gospelcom.net ext. 273 ###
Re: one large partition
>I am trying to backup one (~75GB) partition. Amanda will compress the >entire partition and try to put on the tape. We only have the compressed >50GB tapes. ... Note that you should **not** use both hardware and software compression. Pick one or the other. Trying to put an already (software) compressed image on tape via hardware compression may not even give you the non-compressed capacity listed for the device. >We are using tape changer, but amanda can't split one >file. Is there any way to get around this problem? The standard solution is to use GNU tar and logically (to Amanda) break up the partition into individually backed up pieces. There are tricks to auto-manage this and group things, but they still use this basic plan. >Sherrill John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
one large partition
Hi, I am trying to backup one (~75GB) partition. Amanda will compress the entire partition and try to put on the tape. We only have the compressed 50GB tapes. We are using tape changer, but amanda can't split one file. Is there any way to get around this problem? Any advices will be greatly appreciated. Thanks. Sherrill ### Sherrill (Peichih) Verbrugge [EMAIL PROTECTED] http://www.gospelcom.net ext. 273 ###
