Amrecover
I have built a server with two identical hard drives. The plan is to have the first drive do all the work while the second drive is a backup. After backing up the first drive to tape I attempted to restore the files to the second drive with amrecover (unplugged the first drive to basically make it think it was restoring the same drive it backed up). I ran into a slight problem when amrecover gave me all sorts of File Already Exists messages. So my question is this... is there a way to make amrecover overwrite files that are currently on the drive, and if not is there another way of going about this. Thank you, Joe Knapp
FW: amrecover
-Original Message- From: John R. Jackson [mailto:[EMAIL PROTECTED]] Sent: Friday, August 17, 2001 7:11 PM To: Brandon Amundson Cc: amanda Subject: Re: amrecover >AMRECOVER Version 2.4.2p2. Contacting server on mail.daml.org ... >amrecover: Unexpected server end of file In addition to what Bernhard suggested, what's in amindexd*debug on mail.daml.org (in /tmp/amanda)? >Brandon Amundson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] I am not getting a amindexd*debug written to tmp/amanda here is what is written and also a look at my inetd.conf . I have also viewed the article on faq o matic (http://amanda.sourceforge.net/cgi-bin/fom?file=173&showLastModified=show) but found that it was not my problem, although it reports the same error. ls amandad.20010820110251.debug amrecover.20010817140841.debug killpgrp.20010815140839.debug amandad.20010820110317.debug amrecover.20010817145258.debug killpgrp.20010815140843.debug amandad.20010820110413.debug amrecover.20010820111008.debug killpgrp.20010815140851.debug amandad.20010820110447.debug amrecover.2001082054.debug killpgrp.20010815140859.debug amcheck.20010820103748.debug amrecover.20010820111217.debug killpgrp.20010815140911.debug amcheck.20010820103855.debug amrecover.20010820111235.debug killpgrp.20010815140918.debug amcheck.20010820104009.debug amrecover.20010820111612.debug selfcheck.20010820110251.debug amcheck.20010820105901.debug amrecover.20010820114613.debug selfcheck.20010820110447.debug amcheck.20010820110055.debug amrecover.20010820115545.debug sendbackup.20010815140926.debug amcheck.20010820110251.debug amrecover.20010820124828.debug sendbackup.20010815141552.debug amcheck.20010820110252.debug amtrmidx.20010815151904.debug sendbackup.20010815142516.debug amcheck.20010820110317.debug amtrmlog.20010815151904.debug sendbackup.20010815144439.debug amcheck.20010820110413.debug killpgrp.20010815140759.debug sendbackup.20010815151247.debug amcheck.20010820110447.debug killpgrp.20010815140809.debug sendbackup.20010815151403.debug amlabel.20010815123014.debug killpgrp.20010815140823.debug sendsize.20010815140759.debug amrecover.20010817140833.debug killpgrp.20010815140834.debug and a look inside amrecover .. more amrecover.20010820114613.debug amrecover: debug 1 pid 19812 ruid 0 euid 0 start time Mon Aug 20 11:46:13 2001 amrecover: stream_client: connected to 4.22.162.122.10082 amrecover: stream_client: our side is 0.0.0.0.553 and the inetd.conf #AMANDA Network Backup Utility # amanda dgram udp wait amanda /usr/local/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/local/amanda/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/amanda/libexec/amidxtaped amidxtaped Thanks..
Re: Amanda and multi-drive autoloaders?
On Sun, 19 Aug 2001, Patrick J. LoPresti wrote: > We recently acquired a large Sun tape library, and I have been tasked > with configuring Amanda to use it. > > This library holds around 100 DLT tapes and has a single robotic arm > which serves four drives. The arm and each drive are distinct devices > on the SCSI bus. The autoloader also has a bar code reader. > > I am thinking I will create four distinct Amanda configurations, one > for each tape drive, which just happen to share a changerdev. I am > hoping multiple concurrent attempts to use the changer will get > queued, as opposed to just failing... > > I am also hoping to use the mtx from Sourceforge plus a recent version > of Amanda (with chg-zd-mtx) to make use of the bar codes. > > Questions: > > Is anybody else using Amanda on similar hardware? If so, what > does your configuration look like? Similar in the sense of number of tapes and drives. Make sure you have the tapedev set to each drive's no-rewind device in each of the 4 configs. > > Is the barcode-to-Amanda-label database robust against multiple > concurrent readers? What about multiple concurrent writers? And > is it this support documented somewhere yet :-) ? Since you'll have 4 amanda configs, you'll have 4 separate barcode databases. Since this all relies on the scsi bus and how it handles multiple requests, I'm not sure of the answer to the last questions. I run all 4 jobs at the same time, if that's what you mean. > > Thanks! > > - Pat -- Jason Hollinden MH5 Systems Admin "Yes, I am an agent of Satan, but my duties are largely ceremonial."
Re: Configuring AMANDA
>Is there any way to configure AMANDA to backup sertain directorys into >another directory? You want the amanda-242-tapeio branch from CVS. That is Amanda 2.4.2p2 (plus all changes since then) with this feature. Check the FAQ at www.amanda.org for how to access the CVS repository. Look in the amanda(8) man page for "OUTPUT DRIVERS". You want "file:". >Svavar Orn Eysteinsson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off "send as HTML" in your mailer. It's just a waste of bandwidth.
Configuring AMANDA
Hello. My name is Svavar and i come from Iceland. I recenlty installed, and configured AMANDA for my Sun Solaris 8 Server. I’t all worked fine. But as the status is today, i don’t have any tape device as present. Is there any way to configure AMANDA to backup sertain directorys into another directory? Thanks. Best regards, Svavar Orn Eysteinsson [EMAIL PROTECTED] Reykjavik - ICELAND
unsusbcribe
unsusbcribe
Re: help
On Mon, 20 Aug 2001 at 2:34pm, Ramesh Mopidevi wrote > I have configured amanda software successfully.I want to retain the data > which I backup using amanda to be used for 6 months without > recycling.(without over writing the used tapes)For this scheme to work can > any one suggest how should I mention the dump cycle and tape cycle. > You still have a couple of questions to answer: What is the longest period of time you want between full (level 0) dumps? How often will you be running amdump? It's actually only the second of those that affects tapecycle. If, say, you are going to run amdump every weeknight (5 times per week), then you need (5 tapes/week)*(26 weeks)=130 tapes (that's your tapecycle). That may be quite expensive depending on what types of tapes you're using. The first question sets your dumpcycle. If you want, e.g., a full dump at least once every two weeks (the 5 runs per week as above), then you get a dumpcycle of 2 weeks and runspercycle is 10. A second (possibly cheaper) way of doing this is to have two configurations. I have a nightly configuration that uses cheap tapes (8mm Exabyte, non-Mammoth) that has a tapecycle of 60 (3 months worth of daily history). I have a second configuation that runs on big, expensive tapes (Sony AIT-1) and does full dumps on every run. I run that every month-month and a half, and it has a huge tapecycle, i.e. I'll never reuse those tapes. So, in total I have a 3 month history of daily backups, and a full history (since when I started) of monthly backups. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
help
Hi, I have configured amanda software successfully.I want to retain the data which I backup using amanda to be used for 6 months without recycling.(without over writing the used tapes)For this scheme to work can any one suggest how should I mention the dump cycle and tape cycle. Regards, Ramesh. --- Information transmitted by this E-MAIL is proprietary to Wipro Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailto:[EMAIL PROTECTED] and delete this mail from your records.
