Backup of the backup machine
I want to have one of the disks in the disklist be on the server that does the backup. However, I can't get amandad (or anything else) running with xinet.d on the amanda service. My guess would be that it's really a conflict between the client and the server running on the same machine, both taking the same port out of /etc/services. Is there a way around this? Thank you for any information in advance.
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi I added the files amanda and amandaix to /etc/xinetd.d enable running chkconfig -s xinetd 345 and run /etc/init/xinet.d restart shutdown SuSE internal firewall. server:~ # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* server:~ # lsof | grep amanda xinetd5774 root5u IPv4 8186UDP *:amanda xinetd5774 root8u IPv4 8188TCP *:amandaidx (LISTEN) server:~ # Also in /var/lib/amanda/.amandahosts I have my client setup as below #localhost amanda server.domain.co.uk /etc comp-root-tar I have had a look at by amanda logs /tmp/dbglogs but I haven't anything for that is meaning full. My /var.log/messages ay 10 12:38:16 server xinetd[5118]: removing chargen May 10 12:38:16 server xinetd[5118]: removing chargen May 10 12:38:16 server xinetd[5118]: removing printer May 10 12:38:16 server xinetd[5118]: removing daytime May 10 12:38:16 server xinetd[5118]: removing daytime May 10 12:38:16 server xinetd[5118]: removing echo May 10 12:38:16 server xinetd[5118]: removing echo May 10 12:38:16 server xinetd[5118]: removing netstat May 10 12:38:16 server xinetd[5118]: removing rsync May 10 12:38:16 server xinetd[5118]: removing servers May 10 12:38:16 server xinetd[5118]: removing services May 10 12:38:16 server xinetd[5118]: removing systat May 10 12:38:16 server xinetd[5118]: removing time May 10 12:38:16 server xinetd[5118]: removing time May 10 12:38:16 server xinetd[5118]: removing vnc1 May 10 12:38:16 server xinetd[5118]: removing vnc2 May 10 12:38:16 server xinetd[5118]: removing vnc3 May 10 12:38:16 server xinetd[5118]: removing vnchttpd1 May 10 12:38:16 server xinetd[5118]: removing vnchttpd2 May 10 12:38:16 server xinetd[5118]: removing vnchttpd3 May 10 12:38:16 server xinetd[5118]: removing ftp Run socklist and amanda isnt using any ports server:/tmp/amanda-dbg # socklist type port inode uidpid fd name tcp 10082 10472 0 51188 xinetd tcp803 5303 0 31665 ypbind tcp111 4749 0 28804 portmap tcp631 8470 0 31420 cupsd udp 32768 8060 26 38244 postmaster udp800 5298 0 31664 ypbind udp827 10158 0 31666 ypbind udp 10080 10471 0 51185 xinetd udp111 4748 0 28803 portmap udp631 8471 0 31422 cupsd cd /tmp/amanda-debug less amcheck.20050509150302.debug amcheck: debug 1 pid 6923 ruid 150 euid 0: start at Mon May 9 15:03:02 2005 amcheck: dgram_bind: socket bound to 0.0.0.0.673 amcheck: pid 6923 finish time Mon May 9 15:03:32 2005 My /etc/services file # 10009-10079 Unassigned amanda 10080/tcp # Amanda amanda 10080/udp # Amanda amandaidx 10082/tcp amidxtape 10083/tcp But I still get WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Any other areas to checkover I have gone through this with a fine tooth comb. Cheers -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
On Tue, May 10, 2005 at 12:52:32PM +0100, Chuck Amadi enlightened us: Also in /var/lib/amanda/.amandahosts I have my client setup as below #localhost amanda server.domain.co.uk /etc comp-root-tar This is wrong. you've put a disklist entry in amandahosts. amandahosts should contain host username pairs, one per line. Run socklist and amanda isnt using any ports It shouldn't be until a client connects. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpXzTuId8H81.pgp Description: PGP signature
Re: Backup of the backup machine
On Tue, May 10, 2005 at 12:16:11PM +0100, Jens Theisen wrote: I want to have one of the disks in the disklist be on the server that does the backup. However, I can't get amandad (or anything else) running with xinet.d on the amanda service. My guess would be that it's really a conflict between the client and the server running on the same machine, both taking the same port out of /etc/services. Is there a way around this? If it is a standard install - whatever that means :) then your described arrangement is so common I'd call it the norm. Server backs itself up - by amanda definition, the same host is also a client. I'd look elsewhere than client/server conflict - unless you've made changes to the normal setup. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: force backup on a specific tape
You could force amanda to forget that its written the tape, but doing so throws the schedule for the successful partitions out of wack and as amanda will not append to the tape, it will overwrite the tape, you may make recovery of something else difficult/impossible. Don't you have enough tapes in the tape pool to run the job again on the next volume ? On Mon, May 09, 2005 at 02:19:36PM -0800, LaVonna Sydow wrote: You could manually edit the tapelist file so that the tape is on the last line with the oldest date - or remove its line all together. LS FM wrote: Hello, My monthly backup failed (not completely) this week-end because of electric problem. How can I force my backup to use this monthly tape again ? Thanks ! --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Backup of the backup machine
Hi, Jens, on Dienstag, 10. Mai 2005 at 13:16 you wrote to amanda-users: JT I want to have one of the disks in the disklist be on the server that JT does the backup. However, I can't get amandad (or anything else) running JT with xinet.d on the amanda service. My guess would be that it's really a JT conflict between the client and the server running on the same machine, JT both taking the same port out of /etc/services. JT Is there a way around this? Proper configuration. Follow the installation-instructions, this is a very common setup. Check your xinetd.d-entries and your /etc/services, make sure that the daemons (like amandad) are really located where your files point to. Also check for typos again. Does xinetd start? What do its logfiles say? It would also help if you could provide more detail on what symptoms you see. Just can't get it running isn't enough to enable us to help you in more detail. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi, Chuck, on Dienstag, 10. Mai 2005 at 13:52 you wrote to amanda-users: CA Hi I added the files amanda and amandaix to /etc/xinetd.d CA enable running chkconfig -s xinetd 345 and run /etc/init/xinet.d restart CA shutdown SuSE internal firewall. CA server:~ # netstat -a | grep -i amanda CA tcp0 0 *:amandaidx *:* CA LISTEN CA udp0 0 *:amanda*:* CA server:~ # lsof | grep amanda CA xinetd5774 root5u IPv4 8186UDP CA *:amanda CA xinetd5774 root8u IPv4 8188TCP CA *:amandaidx (LISTEN) CA server:~ # Ok. CA Also in /var/lib/amanda/.amandahosts I have my client CA setup as below CA #localhost amanda CA server.domain.co.uk /etc comp-root-tar Not OK. Should contain: server.domain.co.uk root server.domain.co.uk amanda CA I have had a look at by amanda logs /tmp/dbglogs CA but I haven't anything for that is meaning full. CA My /var.log/messages CA ay 10 12:38:16 server xinetd[5118]: removing chargen CA May 10 12:38:16 server xinetd[5118]: removing chargen Is xinetd running? Should be concerning the netstat-output. CA Run socklist and amanda isnt using any ports AMANDA isn't running now. This is OK. CA cd /tmp/amanda-debug CA less amcheck.20050509150302.debug CA amcheck: debug 1 pid 6923 ruid 150 euid 0: start at Mon May 9 15:03:02 CA 2005 CA amcheck: dgram_bind: socket bound to 0.0.0.0.673 CA amcheck: pid 6923 finish time Mon May 9 15:03:32 2005 CA My /etc/services file CA # 10009-10079 Unassigned CA amanda 10080/tcp # Amanda CA amanda 10080/udp # Amanda CA amandaidx 10082/tcp CA amidxtape 10083/tcp Fine so far. CA But I still get WARNING: server.domain.co.uk: selfcheck request timed CA out. Host down? CA Any other areas to checkover I have gone through this with a fine tooth CA comb. Correct your .amandahosts first. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Is gnu tar as safe as dump ?
I plan to use gnu tar instead of dump to take my amanda backups. Is it as stable/safe as dump/ufsdump ? I need to be able to exclude files, that's why I use gnu tar. Also, when I'm done testing amanda, I guess there is some way to reinitialize it's database of tapes and dumps/indexes ? Where should I look in the documentation ? Thanks
Should I worry: ? gtar: ./oradata/WIXP/rbslm1.dbf: file changed as we read it
I know some files are bound to be growing when I back them up. In this case, this is an oracle database file and I'm only testing. When I put amanda in place for good, I will stop oracle and move the database files somewhere else before backing them up, and exclude the live files. But for other type of files: ex: web server logs, will the partly backed up file be restorable ? I know I'm gonna miss the end of it (it is written sequentially) but will it be resotrable ? When errors/warnings of this type happen, is the tape still usable ? Thanks
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down? -Fixed!
I got a bit further I had forgot to add - server.domain.co.uk root as well as server.domain.co.uk amanda. Here's my advance I will sort this alot out as it's self explanatory. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 137244996 KB disk space available, that's plenty ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting a new tape) NOTE: skipping tape-writable test Server check took 120.453 seconds Amanda Backup Client Hosts Check ERROR: server.domain.co.uk: [GNUTAR program not available] Client check: 1 host checked in 10.140 seconds, 1 problem found So I am slowly getting there!. I hope Cheers Chuck On Tue, 2005-05-10 at 15:25 +0200, Stefan G. Weichinger wrote: server.domain.co.uk root -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
amrecover: no index records for host
I added 'index yes' in the dumptype Comp-root-tar. I ran amdump using that dumptype with no error reporting. When I use amrecover C myconfig name, I still got the same errorno index records for host. amandaidx service is enabled in xinetd. Please help. Thank you, lei
Re: Backup of the backup machine
Stefan G. Weichinger wrote:
It would also help if you could provide more detail on what symptoms
you see. Just can't get it running isn't enough to enable us to help
you in more detail.
That's what xinetd's log says in debug mode:
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {main_loop} select returned 1
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {svc_suspend} Suspended service
amanda
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {server_start} Starting service
amanda
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {main_loop} active_services = 0
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {main_loop} active_services = 0
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {main_loop} select returned 1
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {check_pipe} Got signal 17 (Child
exited)
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {child_exit} waitpid returned = 20147
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {server_end} amanda server 20147
exited
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {drain} UDP socket should be empty
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {svc_resume} Resumed service amanda
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {child_exit} waitpid returned = -1
05/5/[EMAIL PROTECTED]:52:34: DEBUG: 20048 {main_loop} active_services = 1
In the usual log there is nothing. In the service specific log, I get
05/5/[EMAIL PROTECTED]:52:34: START: amanda pid=20147 from=192.168.1.135
05/5/[EMAIL PROTECTED]:52:34: FAIL: amanda address from=192.168.1.135
and I have
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /home/amanda/sillytest
log_type= FILE /root/amanda/amanda.log
}
in my xinetd.conf file. The sillytest is just a dummy to see wether it
gets called or not. I doesn't. So this isn't really an amanda problem.
lsof is telling me xinetd is really listening on service amanda, but
it's doesn't call my test script (or even amandad)
The access right are definitely correct.
Sorry to bother you with this; my knowledge about these things is really
limited.
Jens
Re: Is gnu tar as safe as dump ?
On Tue, May 10, 2005 at 09:31:46AM -0400, Guy Dallaire wrote: I plan to use gnu tar instead of dump to take my amanda backups. Is it as stable/safe as dump/ufsdump ? I need to be able to exclude files, that's why I use gnu tar. There are those who believe that tar is safer than dump, at least when running under Linux/ext2fs. Linus Torvalds is one of them, although there are plenty of others who say that there's no significant difference either way.
Keeping backups on holding disk after writing to tape
Hi all, i want the backed up files from a nightly amdump-run to remain on the holding disk (after they were successfully written to tape!) at least for one day. So it would be possible to do faster and more comfortable restores the next day. Is there an option to acomplish that? And if there is one, is it possible to force amanda to remove that data after a defined period of time? Many thanks in advance and best regards, Christoph
Re: Is gnu tar as safe as dump ?
On Tue, May 10, 2005 at 10:03:44AM -0500, Dave Sherohman wrote: On Tue, May 10, 2005 at 09:31:46AM -0400, Guy Dallaire wrote: I plan to use gnu tar instead of dump to take my amanda backups. Is it as stable/safe as dump/ufsdump ? I need to be able to exclude files, that's why I use gnu tar. There are those who believe that tar is safer than dump, at least when running under Linux/ext2fs. Linus Torvalds is one of them, although there are plenty of others who say that there's no significant difference either way. I could be very wrong, I'm just asking... I'd understood that the OS native dump could handle correctly certain types of files that tar couldn't. Not an issue of binaries but rather other types of special files. Is this or was this true ? Even if it is, I have never had issues with tar vs dump for non-boot partitions. I have a preference for dump for user partitions but its an end-user preference rather than a performance or safety one, we often use the dump -i interactive switch to help us select the files to extract and being able to walk the tree is not a feature of tar, though if you are building an index for amrecover to use it may be a non-issue (we haven't done this at our site). --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down? -Fixed!
Hi, Chuck, on Dienstag, 10. Mai 2005 at 15:57 you wrote to amanda-users: CA Here's my advance I will sort this alot out as it's self explanatory. and CA Amanda Backup Client Hosts Check CA CA ERROR: server.domain.co.uk: [GNUTAR program not available] Install gnutar. Re-run configure as amanda, make and make install as root so you get fresh new binaries that know about the location of your new gnutar-binary. Watch out for WARNINGs at the configure-step, there should be no warnings requesting gnutar ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: Keeping backups on holding disk after writing to tape
SND wrote: Hi all, i want the backed up files from a nightly amdump-run to remain on the holding disk (after they were successfully written to tape!) at least for one day. So it would be possible to do faster and more comfortable restores the next day. Is there an option to acomplish that? And if there is one, is it possible to force amanda to remove that data after a defined period of time? Many thanks in advance and best regards, Not that I know the answer, but when I think about it I totally agree with this being a great function. I would immediatly configure my system to leave the last nights backups on disk until the next job starts, then it could purge yesterdays data if it was successfully written to tape. /Andreas
Re: Keeping backups on holding disk after writing to tape
It sounds like a good feature - if you have enough holding area you could even hold files for a configurable number of days. You'll need a way to differentiate held files from ones that didn't properly flush though, perhaps moving to a subdirectory of the holding area, MMDD-HELD or modifying the file name somehow. On Tue, May 10, 2005 at 07:06:48PM +0200, Andreas Sundstrom wrote: SND wrote: Hi all, i want the backed up files from a nightly amdump-run to remain on the holding disk (after they were successfully written to tape!) at least for one day. So it would be possible to do faster and more comfortable restores the next day. Is there an option to acomplish that? And if there is one, is it possible to force amanda to remove that data after a defined period of time? Many thanks in advance and best regards, Not that I know the answer, but when I think about it I totally agree with this being a great function. I would immediatly configure my system to leave the last nights backups on disk until the next job starts, then it could purge yesterdays data if it was successfully written to tape. /Andreas --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
amanda 2.4.5 rpm on RH ES3
Has anybody been able to build an srpm of 2.4.5 on a redhat enterprise server 3 system? Or does anybody know of a site that has an rpm?
Re: Is gnu tar as safe as dump ?
Brian Cuttler on Tue 10/05 11:18 -0400: I'd understood that the OS native dump could handle correctly certain types of files that tar couldn't. Not an issue of binaries but rather other types of special files. Is this or was this true ? Well POSIX 1.e ACLs are one of them. Why GNU tar doesn't support ACLs when star has supported them for ages, is quite a mystery (possibly, so they don't break the tar format).
Re: Is gnu tar as safe as dump ?
On Tue, May 10, 2005 at 11:07:18AM -0700, Scott Mcdermott wrote: Brian Cuttler on Tue 10/05 11:18 -0400: I'd understood that the OS native dump could handle correctly certain types of files that tar couldn't. Not an issue of binaries but rather other types of special files. Is this or was this true ? Well POSIX 1.e ACLs are one of them. Why GNU tar doesn't support ACLs when star has supported them for ages, is quite a mystery (possibly, so they don't break the tar format). Well, this is the wrong list for it but... tar should include a protocal version number in its header so that you could interchange files with different versions and be upwardly compattible. But I shouldn't start that thread here - and for all I know (and I know nothing about tar internals) it already has a protocal number as part of its spec. --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: amanda 2.4.5 rpm on RH ES3
On Tue, May 10, 2005 at 01:59:39PM -0400, McDonagh, Joe enlightened us: Has anybody been able to build an srpm of 2.4.5 on a redhat enterprise server 3 system? Or does anybody know of a site that has an rpm? You can grab my SRPM from http://www.math.ohiou.edu/mirror/casit/redhat/EL3 It depends on the autoconf259 package I put together, which is in the same directory. You can use the binary autoconf259 packages, but the amanda SRPM will have to be rebuild since my servernames have been defined. When you rebuild it, you can pass the following options: defconfig - name of the default config. Defaults to DailySet1 indexserver - fqdn of your indexserver. Defaults to localhost (which is bad) tapeserver - fqdn of the tapeserver. Defaults to indexserver. You can define them on the command line like the following: rpmbuild --rebuild --define defconfig Dailies --define indexserver amanda.example.com amanda-EL3.spec (all one line of course) As soon as I get some time, I'd like to really go through the .spec file and make some cleanups. If this is something more people would be interested in, I'll try to move it up in priority on my list of things to do. Hope that helps, Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpiBl5cjlOuQ.pgp Description: PGP signature
Re: amanda and solaris 10 smf
I rebooted the server and now amandad is fine. Amcheck and amdump run fine. To answer your questions: no errors from inetconv This is the companion CD install and I agree that smf examples would have made sense. Thanks for everyone's thoughtful input. Now on to the next problem. LS Jon LaBadie wrote: On Mon, May 09, 2005 at 02:17:57PM -0700, Mike Delaney wrote: On Mon, May 09, 2005 at 11:13:01AM -0800, LaVonna Sydow wrote: I am trying to configure amanda on a Solaris 10 server that will backup only itself. When I run amcheck, I get: selfcheck request timed out. Host down? svcs shows: online 11:05:10 svc:/network/amidxtape/tcp:default online 11:05:10 svc:/network/amandaidx/tcp:default maintenance 11:07:05 svc:/network/amanda/udp:default svcs -x shows: svc:/network/amanda/udp:default (amanda) State: maintenance since Fri May 06 12:12:48 2005 Reason: Restarter svc:/network/inetd:default gave no explanation. See: http://sun.com/msg/SMF-8000-9C Impact: This service is not running. Two possibilities come to mind: a.) Something in the service definition for svc:/network/amanda/udp is broken. Check and compare the output from running inetadm -l against the three services. b.) You've discovered a bug in the new inetd implementation. Follow the instructions in the URL above and chase it down with Sun. If this: http://forum.sun.com/thread.jspa?threadID=24302 is you, then I don't see anything obvious wrong with the service definition. Does a pre-packaged version of amanda come on the Sol 10 companion CD? Possibly installing in /opt/sfw/... I ask thinking that if they do, they might also have smf definitions for amanda that you can compare to your own.
Re: Backup of the backup machine
Jens Theisen wrote: Stefan G. Weichinger wrote: It would also help if you could provide more detail on what symptoms you see. Just can't get it running isn't enough to enable us to help you in more detail. Problem sorted, was actually quite simple. :) I am really clueless...
What tapes can I send off-site ? How do I implement this backup strategy ?
We use a nice GUI program to do that, but the product is outdated and buying a new licence is too costly. Amanda seems good, and we use more and more open source software here so we decided to try it out. Our current method of backup is the traditional incrementals Mon, Tue, Wed, Thu, and Friday we do a Full backup. No backups on week end. The tapes are stored in a locked cabinet outside the server room. After 3 business days on site, the tapes are sent to a remote location. This permits to have the tape handy if we have to restore a file that was modified and deleted in the last 2 days. Monthly tapes (Full backup) are kept forever for archiving/financial regulation pupose. I'm having a hard time figuring out how to do something similar with amanda. I'm not familiar with backup levels. It's a concept I always had a difficulty to grasp. If I send the tapes older than 3 days to the remote site, will the tapes of the last three days ALWAYS contain the file modified in the last 3 days ? How can I manage to do full backups of every server each FRIDAY ? I know I should create a new config specifying always full and an infinite tapecylce and run it on fridays, and run the regular schedule on the other days. One last question: Is there an easy way with amanda to do an ad hoc backup ? I mean, say I have to backup a group of directories on a server, do I have to create a new config, a new disklist, etc... ? There must be an easier way ? I'm reading the documentation, but there is a lot of doc, and not enough samples and use-cases IMHO. Thanks
Re: Keeping backups on holding disk after writing to tape
On Tue, 10 May 2005, Brian Cuttler wrote:
It sounds like a good feature - if you have enough holding area
you could even hold files for a configurable number of days.
You'll need a way to differentiate held files from ones that didn't
properly flush though, perhaps moving to a subdirectory of the
holding area, MMDD-HELD or modifying the file name somehow.
Would it be possible to replace taper by a wrapper that uses `cp -l' to create
a hardlinked copy of the backup data first?
On Tue, May 10, 2005 at 07:06:48PM +0200, Andreas Sundstrom wrote:
SND wrote:
i want the backed up files from a nightly amdump-run to remain on the
holding disk (after they were successfully written to tape!) at least for
one day. So it would be possible to do faster and more comfortable
restores
the next day.
Is there an option to acomplish that? And if there is one, is it possible
to
force amanda to remove that data after a defined period of time?
Many thanks in advance and best regards,
Not that I know the answer, but when I think about it I totally agree
with this being a great function. I would immediatly configure my system
to leave the last nights backups on disk until the next job starts, then
it could purge yesterdays data if it was successfully written to tape.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
Re: What tapes can I send off-site ? How do I implement this backup strategy ?
On Tue, May 10, 2005 at 03:45:57PM -0400, Guy Dallaire enlightened us: We use a nice GUI program to do that, but the product is outdated and buying a new licence is too costly. Amanda seems good, and we use more and more open source software here so we decided to try it out. Our current method of backup is the traditional incrementals Mon, Tue, Wed, Thu, and Friday we do a Full backup. No backups on week end. The tapes are stored in a locked cabinet outside the server room. After 3 business days on site, the tapes are sent to a remote location. This permits to have the tape handy if we have to restore a file that was modified and deleted in the last 2 days. Monthly tapes (Full backup) are kept forever for archiving/financial regulation pupose. I'm having a hard time figuring out how to do something similar with amanda. You'll need to keep dumpcycle worth of tapes on site. If you set dumpcycle to 1 week, and runspercycle to 5 (M-F), then you'll need to keep the latest 5 tapes to be able to do those quick restores. What a lot of people will do with enough tapes is have 4 sets of tapes. In your case you might have something like the following: * Tape1, Tape2, Tape3, Tape4, Tape5 - current set that backups are performed on * Tape6, Tape7, Tape8, Tape9, Tape10 - most recent set from last week, stored in your locked cabinet * Tape11, Tape12, Tape13, Tape14, Tape15 - set stored offsite * Tape16, Tape17, Tape18, Tape19, Tape20 - in transit back onsite to become next weeks current Depending on how accessible your offsite location is, you can probably get away with 3 sets I'm not familiar with backup levels. It's a concept I always had a difficulty to grasp. If I send the tapes older than 3 days to the remote site, will the tapes of the last three days ALWAYS contain the file modified in the last 3 days ? Backup levels work like this: Level 0 contains every file Level 1 contains every file that has changed since the last Level 0 Level 2 contains every file that has changed since the last Level 1 Level n contains every file that has changed since the last Level n-1 For a simple example, let's consider some directory foo. foo contains the files a, b, c, and d. * Monday - Level 0 - contains a,b,c and d - User edits file b * Tuesday - Level 1 - contains b - User edits file c * Wednesday - Level 1 - contains b and c - User edits file a * Thursday - Level 2 - contains a So the idea is that if you need to restore an entire directory, you use the latest-dated of each level, in this case Monday, Wednesday and Thursday's tapes. Amanda uses the bump* variables to decide when to increase to the next level. Above it seems that the level was bumped arbitrarily from 1 to 2, but what happened for example was that b and c were both extremely large files, and a was very small. It wouldn't make much sense to use tape for those large files when the only change is the small a file, so it bumps the level up. How can I manage to do full backups of every server each FRIDAY ? I know I should create a new config specifying always full and an infinite tapecylce and run it on fridays, and run the regular schedule on the other days. It is generally not recommended to do so. Why do you feel it necessary to only do full dumps on Friday? Let amanda even out the schedule and you will find good usage accross tapes, and fairly consistent backup runtimes. One last question: Is there an easy way with amanda to do an ad hoc backup ? I mean, say I have to backup a group of directories on a server, do I have to create a new config, a new disklist, etc... ? There must be an easier way ? The host would have to be in the disklist, but you can do individual backups. amdump takes optional host and disk parameters, so if a machine was offline during the backup, the next morning you can bring it up and run something like: amdump CONFIGNAME missinghost /backupdir I'm reading the documentation, but there is a lot of doc, and not enough samples and use-cases IMHO. I hope my examples helped. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpuEy3ZZ3Uuh.pgp Description: PGP signature
Anyone got this script ?
In the amanda docs, this link is mentionned: ftp://gandalf.cc.purdue.edu/pub/amanda/gtartest-exclude It is supposed to lead to some soprt of script that checks if gnutar excludes are working the way they should. I cannot connect top the site, been trying for 2 days Anyone has the script and the documentation that comes with it ? Thanks !
Re: Is gnu tar as safe as dump ?
On Tue, May 10, 2005 at 11:07:18AM -0700, Scott Mcdermott wrote: Brian Cuttler on Tue 10/05 11:18 -0400: I'd understood that the OS native dump could handle correctly certain types of files that tar couldn't. Not an issue of binaries but rather other types of special files. Is this or was this true ? Well POSIX 1.e ACLs are one of them. Why GNU tar doesn't support ACLs when star has supported them for ages, is quite a mystery (possibly, so they don't break the tar format). dump/restore, in all its various flavors, is FS-type and/or OS-type specific. It thus can include features specific to those FS/OS. ACL features are not consistant in what and how they are implemented; they too are FS/OS specific. Thus, dump/restore can handle them. Tar, OTOH, is intended to be FS/OS non-specific. Thus it handles a subset of all possible FS/OS features, namely those common to all and present since the early days of unix. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amrecover: Unexpected end of file
I'm not finding any information that has helped me on this one either: bash-3.00# /opt/sfw/sbin/amrecover -C Daily -s pollock (also tried amrecover -C Daily -s pollock -t pollock) AMRECOVER Version 2.4.4. Contacting server on pollock ... amrecover: Unexpected end of file, check amindexd*debug on server pollock bash-3.00# cat /tmp/amanda/amrecover.20050510135806.debug amrecover: debug 1 pid 1252 ruid 0 euid 0: start at Tue May 10 13:58:06 2005 amrecover: stream_client_privileged: connected to 134.10.176.15.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.834
Re: What tapes can I send off-site ? How do I implement this backup strategy ?
How can I manage to do full backups of every server each FRIDAY ? I know I should create a new config specifying always full and an infinite tapecylce and run it on fridays, and run the regular schedule on the other days. Instead of having cron run amdump directly, you could have it run a script like: set -- `date` case $1 in Fri) su backup /local/sbin/amdump Full ;; *) su backup /local/sbin/amdump Daily ;; esac
gpg with amanda
I had a link for using gpg with amanda, but can't find it. Does anyone have the URL handy? Thanks, -- Eric Dantan Rzewnicki | Systems Administrator Technical Operations Division | Radio Free Asia 2025 M Street, NW | Washington, DC 20036 | 202-530-4900 CONFIDENTIAL COMMUNICATION This e-mail message is intended only for the use of the addressee and may contain information that is privileged and confidential. Any unauthorized dissemination, distribution, or copying is strictly prohibited. If you receive this transmission in error, please contact [EMAIL PROTECTED]
RE: amrecover: Unexpected end of file
I've had similar problems in the past for unknown reasons. In several instances running amverify config on the tape in question has been enough to correct the problem and allow me to restore. Good luck. -- Dave Hull Networking and Telecommunications Services A Division of Information Services The University of Kansas -Original Message- From: [EMAIL PROTECTED] on behalf of L Sydow Sent: Tue 5/10/2005 5:07 PM To: amanda-users@amanda.org Cc: Subject:amrecover: Unexpected end of file I'm not finding any information that has helped me on this one either: bash-3.00# /opt/sfw/sbin/amrecover -C Daily -s pollock (also tried amrecover -C Daily -s pollock -t pollock) AMRECOVER Version 2.4.4. Contacting server on pollock ... amrecover: Unexpected end of file, check amindexd*debug on server pollock bash-3.00# cat /tmp/amanda/amrecover.20050510135806.debug amrecover: debug 1 pid 1252 ruid 0 euid 0: start at Tue May 10 13:58:06 2005 amrecover: stream_client_privileged: connected to 134.10.176.15.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.834
Re: gpg with amanda
On Tue, May 10, 2005 at 05:39:21PM -0400, Eric Dantan Rzewnicki wrote: I had a link for using gpg with amanda, but can't find it. Does anyone have the URL handy? http://www.google.com/search?q=gpg+amanda
Re: amanda and solaris 10 smf
Quoting LaVonna Sydow [EMAIL PROTECTED]: I rebooted the server and now amandad is fine. Amcheck and amdump run fine. To answer your questions: no errors from inetconv This is the companion CD install and I agree that smf examples would have made sense. Perhaps these are helpful SMF notes (to go along with the proper docs, of course): http://www.cuddletech.com/blog/index.php#e182 There is also an overview of SMF in the form of slides here: http://blogs.sun.com/roller/page/lianep/20050427#opensolaris_user_group_wrapup Cheers, DK
Re: Keeping backups on holding disk after writing to tape
On Tue, May 10, 2005 at 11:05:14AM +0200, SND wrote: Hi all, i want the backed up files from a nightly amdump-run to remain on the holding disk (after they were successfully written to tape!) at least for one day. So it would be possible to do faster and more comfortable restores the next day. Is there an option to acomplish that? And if there is one, is it possible to force amanda to remove that data after a defined period of time? Many thanks in advance and best regards, I don't know if anyone has ever tried a combination of real and virtual tapes in a RAIT mirror config. One drive could be your tape, the other could be a disk-based one. I've always felt this could be an interesting solution to lots of arrangements. Off-site tapes for archive, on-site vtapes for fast and easy restore. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
newbie questions about setting up amanda
I'm working on setting up a automated backup system using amanda
2.4.4p4 on a linux slack 8.1 server. The tape system is a HP DAT 72x6
autoloader (36/72 GB tapes)
Q1: Using tapetype I got the following entry:
define tapetype HP-DAT-72x6 {
comment HP autoloader DAT 72x6
# data provided by Rodrigo Ventura [EMAIL PROTECTED]
length 31255 mbytes
filemark 527 kbytes
speed 1580 kps
}
How can I setup amanda to be less conservative, i.e. assume it can
record a little bit more than 31GB per tape? Is there a parameter
where I can specify the assumed compression ratio, say, something
between 1:1 and 1:2?
Q2: I'm getting strange messanges in dump, mostly related with
sockets ignored by gnutar, temporary files (mail queue) being
manipulated, etc. It seems this is the cause of several dumps being
promoted N days ahead... Is there a way to make amanda ignore such
messages? I can live with backups without those files. But I can't
live with amanda promoting dumps several days ahead, all the time
(they never get dumped this way!).
In other words, what exactly makes amanda promote a dump N days ahead?
How can I know whether the promotion message is safe to ignore or not?
Q3: I setup amanda in my server, and currently I'm running it
everyday. However, I want to increase the dump cycle, letting amanda
run, say, three times a week. Is it safe to change such parameters as
dumpcycle and runspercycle in mid-cycle? Say, if I change them right
now, will it keep on working without further operations?
Q4: Following the previous question, is it safe to incrementaly add
entries to disklist?
Thank you,
Cheers,
Rodrigo Ventura
Re: newbie questions about setting up amanda
--On Wednesday, May 11, 2005 00:36:04 +0100 Rodrigo Ventura [EMAIL PROTECTED]
wrote:
I'm working on setting up a automated backup system using amanda
2.4.4p4 on a linux slack 8.1 server. The tape system is a HP DAT 72x6
autoloader (36/72 GB tapes)
Q1: Using tapetype I got the following entry:
define tapetype HP-DAT-72x6 {
comment HP autoloader DAT 72x6
# data provided by Rodrigo Ventura [EMAIL PROTECTED]
length 31255 mbytes
filemark 527 kbytes
speed 1580 kps
}
How can I setup amanda to be less conservative, i.e. assume it can
record a little bit more than 31GB per tape? Is there a parameter
where I can specify the assumed compression ratio, say, something
between 1:1 and 1:2?
You can change the length to be whatever you think will fit on a tape.
The tapetype program write random data to the drive, which evidently
has hardware compression enabled. Attempting to compress non-compressible
data (or already-compressed data) generally makes it larger instead of
smaller, thus only 31 GB fitting on a 36 GB (native) tape. You can either
turn off hardware compression on the drive and do software compression
on selected DLEs (disklist entries), which will enable amanda to very
accurately fit dumps on the tape. or you can adjust the length to a size
that approximates how much of your data will will fit after the tape drive
compresses it. If you guess too low, you may need more tapes than otherwise
needed. guess too high and you may unexpectedly hit EOT, causing the taper
process to start over on that DLE on the next tape, also causing more tape
to be used. If your daily backups are usually smaller than a single tape,
or somewhat larger and will need another tape regardless, then it may not
matter much either way.
Feel free to adjust it anytime as you get more of a feel for your data
and tapes.
Q2: I'm getting strange messanges in dump, mostly related with
sockets ignored by gnutar, temporary files (mail queue) being
manipulated, etc. It seems this is the cause of several dumps being
promoted N days ahead... Is there a way to make amanda ignore such
messages? I can live with backups without those files. But I can't
live with amanda promoting dumps several days ahead, all the time
(they never get dumped this way!).
If they are being promoted, they ARE being dumped, just the level is
being changed sooner than would otherwise occur to fit your dumpcycle.
The promotions occur either to balance out daily tape usage (doing
more tonight when there's extra room on the tape gives more flexibility
tomorrow when a level0 of a large filesystem might be scheduled). It
doesn't increase tape usage (I have runtapes set to 3 on a config that
normally uses about 3/4 of a tape to allow for autoflushes if necessary,
but amanda doesn't promote everything to try and fill 3 tapes, it just
uses the 1 it normally uses).
The 'strange' messages just let you know about things that didn't get
backed up (or possibly were backed up incompletely). There's a file
in the source somewhere that lists strings to ignore, but I wouldn't
recommend changing it unless you are sure you will never care about it.
It is letting you know what will be missing/incomplete when you go to
do a restore.
In other words, what exactly makes amanda promote a dump N days ahead?
How can I know whether the promotion message is safe to ignore or not?
You can always ignore the promotion messages, unless you want to tune
your bumpsize parameters to change when the promotions take place.
Q3: I setup amanda in my server, and currently I'm running it
everyday. However, I want to increase the dump cycle, letting amanda
run, say, three times a week. Is it safe to change such parameters as
dumpcycle and runspercycle in mid-cycle? Say, if I change them right
now, will it keep on working without further operations?
Yes, although it may take a few runs to balance everything out again.
Making the dumpcycle longer or increasing runspercycle shouldn't ever
be a problem (assuming your tapecycle is long enough to handle it).
Decreasing either drastically may make it impossible to fit everything
on the tapes provided, but amanda will warn you if it is unable to meet
your schedule or if you are gong to overwrite your last full backup of
a DLE.
Q4: Following the previous question, is it safe to incrementaly add
entries to disklist?
Yes, that's the best way to do it. Adding large numbers of DLEs at once
may cause some temporary scheduling problems as amanda has to do a full
backup of each new one when its added. It will eventually sort itself
out (assuming you have enough tapes), but it is simpler to add a few at
a time (or one at a time if they are very large as a percentage of your
tapesize).
Frank
Thank you,
Cheers,
Rodrigo Ventura
--
Frank Smith[EMAIL PROTECTED]
Sr. Systems Administrator Voice: 512-374-4673
