Re: Dump command on Debian
john, you say gtar and dump work on the sun boxes, but only state that dump fails on the debian boxes (which is probably correct, since it only dumps ext2 filesystems). did you try gtar? it should work.. :-) regards, -rodi. On Sat, 2004-07-10 at 17:07, John Bossert wrote: Adding a pair of Debian(woody) clients to a Solaris shop... Amanda is working just fine with both gtar and dump on the Sun boxes. Trying to dump filesystems, failed. Discovered that there's no dump on the debian boxes... All the filesystems are jfs, yet the dump package I find at debian.org (0.4b27-4) appears oriented towards ext2. What package do I want to install on these clients to play nice with Amanda? Thx.
Amanda Backup
In My office amanda does a full backup regularly for 3 days but why is it not switching over to a incremental backup after the full backup is run for first time any help -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. Tel : +91-22-22881326/27 Fax : +91-22-22881318 Cell : +91-9820367783
Re: Amanda Backup
Kaushal Shriyan wrote: In My office amanda does a full backup regularly for 3 days but why is it not switching over to a incremental backup after the full backup is run for first time any help Now we can only guess, like you told her so, or because she has a mind of her own. It would help us if post more info, like the e.g. configuration. (At least if you're not talking about Amanda, the secretary in Your office)). -- 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: Error /bin/tar got signal 13
Hi! Here's a little bit more information: - In /var/log/messages (see attachment schatten_messages) just above the sendbackup-entry I get strange error messages about connecting to an ldap-server. We're using LDAP at our site, but I can see no significant reason, why gtar needs this, since all users used by Amanda are local in /etc/passwd and /etc/group. nsswitch.conf is configured correctly (file before ldap). LDAP is required because the user-/group-numbers are resolved to names through it. But a manually started gtar --create --file - --directory . --one-file-system --sparse --ignore-failed-read --totals . | /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' doesn't reproduce this failure and doesn't create an equivalent syslog entry like during backup. Hope, somebody is able to help me! Bye, Simon -- Simon Frettloeh Institute AIFB (Applied Computer Science and Formal Description Methods) University of Karlsruhe Engler Str. 11 - 76128 Karlsruhe - Germany
GNUTAR, mount points symbolic links ???
Does Amanda/GNUTAR _follow_ all mount points and symbolic links in a DLE? Everytime that I setup Amanda clients, I get confused on these issues. If this is covered in the FAQ-O-Matic, then I do not see it. If it has been covered on the mailing list countless times, then my searches are too lame. Hopefully, this post, including this subject line, will make this easier to find for those who come after ; If I am right, by default, Amanda/GNUTAR _does_ follow follow mount points contained within a DLE, but does _not_ follow symbolic links. This makes a difference regarding deploying exclude files. What do you think? -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: Dump command on Debian
Gtar works fine (and I use it for my Dailies.) Here, I'm trying to establish a bare metal restore process. With Solaris, if _really bad things_ happen, I can take my ufs dumps and rebuild a machine fairly directly. Is the best practice in the Debian world to just use gtar for this? How do others manage this? Thx. -john R.M. Evers wrote: john, you say gtar and dump work on the sun boxes, but only state that dump fails on the debian boxes (which is probably correct, since it only dumps ext2 filesystems). did you try gtar? it should work.. :-) regards, -rodi. On Sat, 2004-07-10 at 17:07, John Bossert wrote: Adding a pair of Debian(woody) clients to a Solaris shop... Amanda is working just fine with both gtar and dump on the Sun boxes. Trying to dump filesystems, failed. Discovered that there's no dump on the debian boxes... All the filesystems are jfs, yet the dump package I find at debian.org (0.4b27-4) appears oriented towards ext2. What package do I want to install on these clients to play nice with Amanda? Thx. -- La thiorie, c'est quand on sait tout et que rien ne fonctionne. La pratique, c'est quand tout fonctionne et que personne ne sait pourquoi. Ici, nous avons riuni thiorie et pratique : Rien ne fonctionne... et personne ne sait pourquoi! [Einstein]
Re: GNUTAR, mount points symbolic links ???
On Mon, Jul 12, 2004 at 03:13:24PM -0500, Michael D Schleif wrote: Does Amanda/GNUTAR _follow_ all mount points and symbolic links in a DLE? Everytime that I setup Amanda clients, I get confused on these issues. If this is covered in the FAQ-O-Matic, then I do not see it. If it has been covered on the mailing list countless times, then my searches are too lame. Hopefully, this post, including this subject line, will make this easier to find for those who come after ; If I am right, by default, Amanda/GNUTAR _does_ follow follow mount points contained within a DLE, but does _not_ follow symbolic links. This makes a difference regarding deploying exclude files. What do you think? Amanda merely starts the backup program, in this case gnutar. Thus the gnutar manpage/reference doc is your best source for information. A guess here, gnutar does not cross mountpoints unless an option is used (of course the opposite may be true, i.e., will cross mountpoints unless an option is used). Whichever, the gnutar options used are recorded in the debug log files in (by default) /tmp/amanda. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: all estimate failed
Gene, thanks for your help. I finally seem to be on the track of fixing the problem. I completely nuked amanda and let Gentoo rebuild it from scratch, after providing the ebuild with the proper env vars. This didn't help, but it gave me a clean slate. After that, I rewrote my amanda.conf and disklist files for the affected configs using the templates provided with the current version of amanda (my old configs have been in use for about 5 years, through several versions of amanda, and were somewhat hacked and outdated). I'm not sure exactly which parameter(s) made the difference, but a backup of the main local system seems to be proceeding well. I note that the Gentoo build defaults to 'localhost' for the server address, which should _always_ be 127.0.0.1, and hence unambiguous. I trust the Gentoo devs implicitly. IMHO, they're right up there with the Debian package maintainers in knowledge and experience. I did, however, use the FQDN for the server in the ebuild, which I prefer in any event. -- Lindsay Haisley | Everything works| PGP public key FMP Computer Services | if you let it | available at 512-259-1190 |(The Roadie) | http://www.fmp.com/pubkeys http://www.fmp.com| |
Re: all estimate failed
On Mon, Jul 12, 2004 at 05:21:40PM -0500, [EMAIL PROTECTED] enlightened us: I note that the Gentoo build defaults to 'localhost' for the server address, which should _always_ be 127.0.0.1, and hence unambiguous. I trust the Gentoo devs implicitly. IMHO, they're right up there with the Debian package maintainers in knowledge and experience. I did, however, use the FQDN for the server in the ebuild, which I prefer in any event. It is not unambiguous since *every* machine is localhost with an address of 127.0.0.1. Unfortunately that's a problem with binary packages and amanda in that yes, backing up with localhost/127.0.0.1 will always work, but it can fail at restore time and can cause other crazy problems occasionally. It is the same situation in the redhat packages, which is why I always grab the source rpm and rebuild with the right options for my server. Sounds like that's what you did and is IMHO the best way to do it if you want to keep the tracking of packages while using amanda in the best manner. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: all estimate failed
On Monday 12 July 2004 18:21, [EMAIL PROTECTED] wrote: Gene, thanks for your help. I finally seem to be on the track of fixing the problem. I completely nuked amanda and let Gentoo rebuild it from scratch, after providing the ebuild with the proper env vars. This didn't help, but it gave me a clean slate. After that, I rewrote my amanda.conf and disklist files for the affected configs using the templates provided with the current version of amanda (my old configs have been in use for about 5 years, through several versions of amanda, and were somewhat hacked and outdated). I'm not sure exactly which parameter(s) made the difference, but a backup of the main local system seems to be proceeding well. I note that the Gentoo build defaults to 'localhost' for the server address, which should _always_ be 127.0.0.1, and hence unambiguous. I trust the Gentoo devs implicitly. IMHO, they're right up there with the Debian package maintainers in knowledge and experience. I did, however, use the FQDN for the server in the ebuild, which I prefer in any event. The huge majority of the amanda users here, and even Jean-Louis, will re-iterate about not using localhost because its not a unique name. The problem being that the data can be taken to any machine that is also localhost and installed. This is, among other things, a huge security hole. I'm not sure how the ebuilder works, but from the tarballs unpacking, to a fully installed update here is not more than 5 to 6 minutes unless you use the checkinstall utility to install it on an rpm based system. Checkinstall can be handy in that you do the standard routine of unpack, cd to the unpacked directory, ./configure; make, doing this as the user amanda, then revert to root or become root, and do the make install or the checkinstall. Checkinstall takes the packages built directory, makes a binary rpm out of it, and then installs the rpm. One can then remove an errant package with the rpm -e command should it become required. Configureing the tarball to make it can be confusing, and error prone if you don't have a photographic memory, so I only do these steps to build and install it: (1) tar xzvf name_of_tarball (2) cp gh.cf name_of_tarball/ (3) chown -R amanda:disk name_of_tarball (4) become the user 'amanda' (5) cd name_of_tarball(minus the tar.gz of course) (6) ./gh.cf (which configures it with my std config options, then 'make's it) (7) become root (8) cd name_of_tarball (9) make install (10) become user amanda (11) amcheck configname (to error check the install) Steps 1-9 take about 5 minutes here. Here is that gh.cf file: #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make --- I didn't sanitize it any, that hostname won't resolve more than 100 feet away in my woodshop, as my firewall is bulletproof in practice. Adjust your changer device if required. -- Cheers, Gene There are 4 boxes to be used in defense of liberty. Soap, ballot, jury, and ammo. Please use in that order, starting now. -Ed Howdershelt, Author Additions to this message made by Gene Heskett are Copyright 2004, Maurice E. Heskett, all rights reserved.
Amanda Through firewall
Can I allow amanda backup server to talk through firewall for accessing amanda client host, Is there any way out Any help -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. Tel : +91-22-22881326/27 Fax : +91-22-22881318
Re: Amanda Through firewall
There is an excellent how-to about this in the Amanda Faq-O-Matic : http://amanda.sourceforge.net/cgi-bin/fom?_highlightWords=10080file=139 HTH Bert De Ridder PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be http://www.mobileware.be Kaushal Shriyan [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 13/07/2004 06:48 To [EMAIL PROTECTED] cc Subject Amanda Through firewall Can I allow amanda backup server to talk through firewall for accessing amanda client host, Is there any way out Any help -- Regards, Kaushal Shriyan Technical Engineer Red Hat India Pvt. Ltd. Tel : +91-22-22881326/27 Fax : +91-22-22881318
