amrestore
Hello I am tetsing the different restore options that are available. I have started with the ones documented in amanda package. Could anyone explain the results below: - a) From the backup server , I ran command below . The backup image gets stored in the current working directory. [EMAIL PROTECTED] restoredir]$ amrestore /dev/st0 osama / 1.. amrestore: 0: skipping start of tape: date 20030318 label DailySet15 2.. amrestore: 1: skipping osama.hda5.20030318.0 3.. amrestore: 2: skipping osama.hda1.20030318.0 4.. amrestore: 3: restoring osama._.20030318.0 5.. amrestore: 4: skipping start of tape: date 20030318 label DailySet15 6.. amrestore: 5: skipping osama.hda5.20030318.0 7.. amrestore: 6: skipping osama.hda1.20030318.0 8.. amrestore: 7: restoring osama._.20030318.0 9.. amrestore: 8: skipping start of tape: date 20030318 label DailySet15 10.. amrestore: 9: skipping osama.hda5.20030318.0 11.. amrestore: 10: skipping osama.hda1.20030318.0 12.. amrestore: 11: restoring osama._.20030318.0 13.. amrestore: 12: skipping start of tape: date 20030318 label DailySet15 14.. amrestore: 13: skipping osama.hda5.20030318.0 15.. amrestore: 14: skipping osama.hda1.20030318.0 16.. amrestore: 15: restoring osama._.20030318.0 17.. amrestore: 17: skipping osama.hda5.20030318.0 18.. amrestore: 18: skipping osama.hda1.20030318.0 19.. amrestore: 19: restoring osama._.20030318.0 The above carried on until I manually stopped the operation. Please note that the size of the backup image increased as well. b) From the client machine , I ran the following command :- rsh -n -l amanda backup.terrasky.mu /usr/local/sbin/amrestore -p /dev/st0 osama / | restore -iv -b 2 -f - and I could restore some files chosen at random. If I modify the command above as follows : - rsh -n -l amanda backup.terrasky.mu /usr/local/sbin/amrestore /dev/nst0 osama / the backup image is not stored in the current working directory. thanks in advance for comments/explanations. Madhvi
Re: rait
Joseph Sirucka on Thu 20/03 15:42 +1100: > I understand raitcan only work with single tape units and > not changers. I don't think it can treat a whole changer as a device. > Do you also need a minimum 3 tape units to do rait, will 2 be ok. just make the third tape /dev/null, the RAIT code recognizes this and doesn't actually write to /dev/null.
rait
Hi All I understand raitcan only work with single tape units and not changers. Do you also need a minimum 3 tape units to do rait, will 2 be ok. Can someone please answer these for me. regards Joseph
Re: Problem with amrecover
On Wed, Mar 19, 2003 at 02:18:21PM -0800, bao wrote: > As a followup to my previous mail. > > I have repeatedly tried amrecover with different disks in my config. The > small disk (with original 760 MB, after backup ~380 MB) seems to let me > recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always > hangs or reboots the server itself. No compression is used, just tar, in > the config. > > Does amanda impose a limit on disk size??? Amanda does not, but many OS's do. A common file size limit is 2GB. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
ERROR planner Request to localhost timed out.
This is probably a FAQ, but the FAQ-o-Matic (at http://amanda.sourceforge.net/fom-serve/cache/295.html nor http://amanda.sourceforge.net/fom-serve/cache/13.html) doesn't cover it... so here goes. I'm trying to do amdump or amcheck but anytime I do, I get this in my log: --- ERROR planner Request to localhost timed out. --- Localhost has its inetd.conf and services modified correctly by the client setup script, as evidenced by telnetting to localhost:10080 & pressing "ENTER", output follows: --- [EMAIL PROTECTED]:/var/log/amanda/Daily# telnet localhost 10080 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Amanda 2.4 NAK HANDLE SEQ 0 ERROR expected "Amanda", got "" Connection closed by foreign host. --- So I'm confused. What would cause amdump to get a timeout trying to do a planner request? Does it mean somehow a planner executable isn't available to the daemon process? Any pointers appreciated. -- pv If this helped you, http://svcs.affero.net/rm.php?r=philovivero
Re: selfcheck error: could not access sda1
On Wednesday, Mar 19, 2003, at 17:07 US/Eastern, Joshua Baker-LePain wrote: A guess -- that's a Linux client? There's a known bug with 2.4.2p2 and properly detecting the root partition. Upgrade the client and all will be well. Joshua, Yes, it is a Linux client. That's odd, I've never had this problem before. I backup several other Linux clients' root disks with no problems-- same version. I found that if I explicitly entered "/dev/sda1" in disklist, amcheck stops complaining. Hopefully that will take care of it until I can upgrade the client. Thanks, Eric
Pornography
Since signing up on the Amanda list serve about 2 or 3 weeks ago, my e-mail address seems to have distributed to several pornographic spammers. Because of that, I cannot continue with the list. Please unsubscribe me. Wayne Seth COE Lab Manager 520-538-0110 [EMAIL PROTECTED]
RE: selfcheck error: could not access sda1
On Wed, 19 Mar 2003 at 2:01pm, Bernhard Beck wrote > Are you using Linux by any chance and /dev/sda1 is the root partition? > Try using / instead of sda1 in that case. I believe that still won't work. You either need to apply the advfs patch from the patches page at amanda.org or upgrade to 2.4.4. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Problem with amrecover
As a followup to my previous mail. I have repeatedly tried amrecover with different disks in my config. The small disk (with original 760 MB, after backup ~380 MB) seems to let me recover. The bigger disk (original ~ 18 GB, after backup ~9 MB) always hangs or reboots the server itself. No compression is used, just tar, in the config. Does amanda impose a limit on disk size??? If so, I guess I have to split the disk into small chunks, which is completely undesirable. bao wrote: Hi list, I'm experiencing the same problem. My linux dist. is RH 8.0 kernel 2.4.18-19.8.0. tar 1.13.25-8. amdump was ok. amverify OK. But when I ran amrecover, everything went fine until the extract step. amanda seems to freeze. Here's the result of amidxtaped and amrecover, respectively: amidxtaped: debug 1 pid 1552 ruid 501 euid 501: start at Wed Mar 19 10:52:38 2003 amidxtaped: version 2.4.4 amidxtaped: time 0.000: > SECURITY USER root amidxtaped: time 0.000: bsd security: remote host snook user root local user general amidxtaped: time 0.000: amandahosts security check passed amidxtaped: time 0.000: > CONFIG=WeeklySet amidxtaped: time 0.000: > LABEL=WeeklySet1 amidxtaped: time 0.000: > FSF=2 amidxtaped: time 0.000: > HEADER amidxtaped: time 0.000: > DEVICE=file:/Backup/general/WeeklySet1 amidxtaped: time 0.000: > HOST=^snook$ amidxtaped: time 0.000: > DISK=^/Shared$ amidxtaped: time 0.000: > DATESTAMP=20030319 amidxtaped: time 0.000: > END amidxtaped: time 0.001: amrestore_nargs=0 amidxtaped: time 0.001: Ready to execv amrestore with: path = /Backup/usr/sbin/amrestore argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "file:/Backup/general/WeeklySet1" argv[4] = "^snook$" argv[5] = "^/Shared$" argv[6] = "20030319" amrestore: 0: skipping start of tape: date 20030319 label WeeklySet1 amrestore: 1: skipping snook._Mail.20030319.0 amrestore: 2: restoring snook._Shared.20030319.0 Error 32 (Broken pipe) offset -835747840+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amidxtaped: time 209.145: amrestore terminated normally with status: 2 amidxtaped: time 209.146: rewinding tape ... amidxtaped: time 209.146: done amidxtaped: time 209.146: pid 1552 finish time Wed Mar 19 10:56:07 2003 - amrecover: debug 1 pid 1526 ruid 0 euid 0: start at Wed Mar 19 10:49:14 2003 amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.928 guess_disk: 11: "/tmp/amanda" guess_disk: 0: 1: "/": "rootfs" guess_disk: local_disk = 1, fsname = "rootfs" guess_disk: 1: 1: "/": "/dev/root" guess_disk: 1: 5: "/proc": "/proc" guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs" guess_disk: 1: 5: "/boot": "/dev/hda1" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 1: "/": "/dev/hda2" guess_disk: 1: 5: "/proc": "none" guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs" guess_disk: 1: 5: "/boot": "/dev/hda1" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 1: "/": "LABEL=/" guess_disk: 1: 5: "/boot": "LABEL=/boot" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 5: "/proc": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 4: "swap": "/dev/hda3" guess_disk: 1: 11: "/mnt/floppy": "/dev/fd0" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 10: "/mnt/cdrom": "/dev/cdrom" add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/." ... add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/bao/" add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/boot.out" ... amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10083 amrecover: stream_client_privileged: our side is 0.0.0.0.620 amrecover: try_socksize: receive buffer size is 65536 Exec'ing /bin/gtar with arguments: tar -xpGvf - ./bao/gsv42w32.exe ./bao/gs704w32.exe ./bao/WinPcap.exe ./bao/ipchains ./bao/imtool.c Pleae tell me what's happened with amanda
RE: selfcheck error: could not access sda1
Are you using Linux by any chance and /dev/sda1 is the root partition? Try using / instead of sda1 in that case. Bernhard [...] > selfcheck: checking disk sda3 > selfcheck: device /dev/sda3 > selfcheck: OK > selfcheck: checking disk sda1 > selfcheck: device sda1 > selfcheck: could not access sda1 (sda1): No such file or directory > selfcheck: pid 13892 finish time Wed Mar 19 16:30:57 2003 > > > Why is this? /dev/sda1 has the same permissions as all the others. Why > isn't the client applying the correct prefix? > > I really need to fully back this guy up tonight, as we are doing > upgrades tomorrow. :) > > Thanks, > Eric > >
Re: selfcheck error: could not access sda1
On 19 Mar 2003 at 4:37pm, Eric Sproul wrote > Amanda Backup Client Hosts Check > > ERROR: lovejoy: [could not access sda1 (sda1): No such file or > directory] > Client check: 6 hosts checked in 0.565 seconds, 1 problem found > > > The server is 2.4.3, the client is 2.4.2p2. It's weird because the > client has the proper device prefix, and found all the other new DLE's > except sda. A guess -- that's a Linux client? There's a known bug with 2.4.2p2 and properly detecting the root partition. Upgrade the client and all will be well. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amrestore failing
This is my second try posting this... I hope I am not screwing something up... Hi, thanks for the great program. I am having a problem with amrestore/amrecover. When amdump goes off, everything is fine, and the report says everything is fine. When I try amrestore though, I get: [EMAIL PROTECTED] holding_disk]# mt -f /dev/nst0 rewind [EMAIL PROTECTED] holding_disk]# amrestore /dev/nst0 amrestore: 0: skipping start of tape: date 20030216 label yorkgroup05 amrestore: error reading file header: Input/output error So maybe the tape and/or drive is dirty/bad. Not so. If I do this: $ mt -f /dev/nst0 rewind; mt -f /dev/nst0 fsf filemarker $ dd if=/dev/nst0 skip1 bs=32k of=backup.tar.gz I can read the tapes just fine. Now this doesn't happen with every tape. I just had one today that was fine. What may be of interest to the developers is that dd prints out a little error message: dd: warning: working around lseek kernel bug for file (/dev/nst0) of mt_type=0x72 -- see for the list of types So my theory is that dd knows about a kernel lseek bug that amanda does not. Maybe if some one in the know peeked at the dd source and the amanda source they could sort this out. I am using Red Hat 8.0, on a dual AMD workstation, a VXA-1 external drive attached to a aic7892: Ultra160 Wide Channel A controller, Linux kernel 2.4.19, amanda 2.4.2p2-9 (as packaged by Red Hat), and fileutils 4.1.9-11 (as packaged by Red Hat). Thanks. -- Kevin Range [EMAIL PROTECTED] 281 Kolthoff: 612-625-6317
selfcheck error: could not access sda1
All, I just added several new DLE's to my config, and when running amcheck, I get the following error: Amanda Backup Client Hosts Check ERROR: lovejoy: [could not access sda1 (sda1): No such file or directory] Client check: 6 hosts checked in 0.565 seconds, 1 problem found The server is 2.4.3, the client is 2.4.2p2. It's weird because the client has the proper device prefix, and found all the other new DLE's except sda. The client's selfcheck.debug: selfcheck: debug 1 pid 13892 ruid 11 euid 11 start time Wed Mar 19 16:30:57 2003/usr/local/libexec/selfcheck: version 2.4.2p2 selfcheck: checking disk sda9 selfcheck: device /dev/sda9 selfcheck: OK selfcheck: checking disk sda8 selfcheck: device /dev/sda8 selfcheck: OK selfcheck: checking disk sda6 selfcheck: device /dev/sda6 selfcheck: OK selfcheck: checking disk sda5 selfcheck: device /dev/sda5 selfcheck: OK selfcheck: checking disk sda3 selfcheck: device /dev/sda3 selfcheck: OK selfcheck: checking disk sda1 selfcheck: device sda1 selfcheck: could not access sda1 (sda1): No such file or directory selfcheck: pid 13892 finish time Wed Mar 19 16:30:57 2003 Why is this? /dev/sda1 has the same permissions as all the others. Why isn't the client applying the correct prefix? I really need to fully back this guy up tonight, as we are doing upgrades tomorrow. :) Thanks, Eric
Re: dump/restore: Not Recommended!
On Thu, 20 Mar 2003 at 7:08am, Mark Checklin wrote > This is a extract from the Redhat Web sit on Dump/Amanda > > http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/admin-primer/s1-disa > ster-backups.html > I am about to setup a new server with samaba and was going to use amanda > with dump but found this on redhat webs sit. > Has any body had this problem, and what would you suggest i use instead? This is *old* news and has been discussed to death and back on this list (and others I'm sure). Tar works quite well for a lot of people. Your other option is to use, e.g., XFS, which comes with xfsdump which works differently from ext2 dump and should avoid its problems. Test, test, test, and find what works for you. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
dump/restore: Not Recommended!
This is a extract from the Redhat Web sit on Dump/Amanda http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/admin-primer/s1-disa ster-backups.html I am about to setup a new server with samaba and was going to use amanda with dump but found this on redhat webs sit. Has any body had this problem, and what would you suggest i use instead? Regards Mark dump/restore: Not Recommended! The dump and restore programs are Linux equivalents to the UNIX programs of the same name. As such, many system administrators with UNIX experience may feel that dump and restore are viable candidates for a good backup program under Red Hat Linux. Unfortunately, the design of the Linux kernel has moved ahead of dump's design. Here is Linus Torvald's comment on the subject: From:Linus Torvalds To: Neil Conway Subject: Re: [PATCH] SMP race in ext2 - metadata corruption. Date:Fri, 27 Apr 2001 09:59:46 -0700 (PDT) Cc: Kernel Mailing List [ linux-kernel added back as a cc ] On Fri, 27 Apr 2001, Neil Conway wrote: > > I'm surprised that dump is deprecated (by you at least ;-)). What to > use instead for backups on machines that can't umount disks regularly? Note that dump simply won't work reliably at all even in 2.4.x: the buffer cache and the page cache (where all the actual data is) are not coherent. This is only going to get even worse in 2.5.x, when the directories are moved into the page cache as well. So anybody who depends on "dump" getting backups right is already playing Russian roulette with their backups. It's not at all guaranteed to get the right results - you may end up having stale data in the buffer cache that ends up being "backed up". Dump was a stupid program in the first place. Leave it behind. > I've always thought "tar" was a bit undesirable (updates atimes or > ctimes for example). Right now, the cpio/tar/xxx solutions are definitely the best ones, and will work on multiple filesystems (another limitation of "dump"). Whatever problems they have, they are still better than the _guaranteed_(*) data corruptions of "dump". However, it may be that in the long run it would be advantageous to have a "filesystem maintenance interface" for doing things like backups and defragmentation.. Linus (*) Dump may work fine for you a thousand times. But it _will_ fail under the right circumstances. And there is nothing you can do about it. Given this problem, the use of dump/restore is strongly discouraged.
Re: Problem with amrecover
Hi list, I'm experiencing the same problem. My linux dist. is RH 8.0 kernel 2.4.18-19.8.0. tar 1.13.25-8. amdump was ok. amverify OK. But when I ran amrecover, everything went fine until the extract step. amanda seems to freeze. Here's the result of amidxtaped and amrecover, respectively: amidxtaped: debug 1 pid 1552 ruid 501 euid 501: start at Wed Mar 19 10:52:38 2003 amidxtaped: version 2.4.4 amidxtaped: time 0.000: > SECURITY USER root amidxtaped: time 0.000: bsd security: remote host snook user root local user general amidxtaped: time 0.000: amandahosts security check passed amidxtaped: time 0.000: > CONFIG=WeeklySet amidxtaped: time 0.000: > LABEL=WeeklySet1 amidxtaped: time 0.000: > FSF=2 amidxtaped: time 0.000: > HEADER amidxtaped: time 0.000: > DEVICE=file:/Backup/general/WeeklySet1 amidxtaped: time 0.000: > HOST=^snook$ amidxtaped: time 0.000: > DISK=^/Shared$ amidxtaped: time 0.000: > DATESTAMP=20030319 amidxtaped: time 0.000: > END amidxtaped: time 0.001: amrestore_nargs=0 amidxtaped: time 0.001: Ready to execv amrestore with: path = /Backup/usr/sbin/amrestore argv[0] = "amrestore" argv[1] = "-p" argv[2] = "-h" argv[3] = "file:/Backup/general/WeeklySet1" argv[4] = "^snook$" argv[5] = "^/Shared$" argv[6] = "20030319" amrestore: 0: skipping start of tape: date 20030319 label WeeklySet1 amrestore: 1: skipping snook._Mail.20030319.0 amrestore: 2: restoring snook._Shared.20030319.0 Error 32 (Broken pipe) offset -835747840+32768, wrote 0 amrestore: pipe reader has quit in middle of file. amidxtaped: time 209.145: amrestore terminated normally with status: 2 amidxtaped: time 209.146: rewinding tape ... amidxtaped: time 209.146: done amidxtaped: time 209.146: pid 1552 finish time Wed Mar 19 10:56:07 2003 - amrecover: debug 1 pid 1526 ruid 0 euid 0: start at Wed Mar 19 10:49:14 2003 amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10082 amrecover: stream_client_privileged: our side is 0.0.0.0.928 guess_disk: 11: "/tmp/amanda" guess_disk: 0: 1: "/": "rootfs" guess_disk: local_disk = 1, fsname = "rootfs" guess_disk: 1: 1: "/": "/dev/root" guess_disk: 1: 5: "/proc": "/proc" guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs" guess_disk: 1: 5: "/boot": "/dev/hda1" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 1: "/": "/dev/hda2" guess_disk: 1: 5: "/proc": "none" guess_disk: 1: 13: "/proc/bus/usb": "usbdevfs" guess_disk: 1: 5: "/boot": "/dev/hda1" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 1: "/": "LABEL=/" guess_disk: 1: 5: "/boot": "LABEL=/boot" guess_disk: 1: 8: "/dev/pts": "none" guess_disk: 1: 5: "/proc": "none" guess_disk: 1: 8: "/dev/shm": "none" guess_disk: 1: 4: "swap": "/dev/hda3" guess_disk: 1: 11: "/mnt/floppy": "/dev/fd0" guess_disk: 1: 7: "/Backup": "/dev/hdb" guess_disk: 1: 10: "/mnt/cdrom": "/dev/cdrom" add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/." ... add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/bao/" add_dir_list_item: Adding "2003-03-19" "0" "WeeklySet1" "2" "/boot.out" ... amrecover: stream_client_privileged: connected to xx.xx.xx.xx.10083 amrecover: stream_client_privileged: our side is 0.0.0.0.620 amrecover: try_socksize: receive buffer size is 65536 Exec'ing /bin/gtar with arguments: tar -xpGvf - ./bao/gsv42w32.exe ./bao/gs704w32.exe ./bao/WinPcap.exe ./bao/ipchains ./bao/imtool.c Pleae tell me what's happened with amanda
Re: tapetype python
On Wed, 2003-03-19 at 06:38, [EMAIL PROTECTED] wrote:
> Hello
>
> I'm looking for tapetype for a Python 04106-xxx (archive)
:) Funny, I *just* posted this yesterday. I believe it is also in the
FAQ-O-Matic:
http://amanda.sourceforge.net/fom-serve/cache/1.html
Here it is again:
define tapetype Python-DDS3 {
comment "ARCHIVE Python with DDS3 tape"
length 11570 mbytes
filemark 48 kbytes
speed 1078 kps
}
This is to be used with 125m (DDS3) tapes.
I have a separate config for this same drive with 120m (DDS2) tapes:
define tapetype Python-DDS2 {
comment "ARCHIVE Python with DDS2 tape"
length 3860 mbytes
filemark 16 kbytes
speed 707 kps
}
HTH,
Eric
Re: Upgrading to 2.4.4: amcheck complains about samba exclude list
Joshua Baker-LePain wrote: > On Wed, 19 Mar 2003 at 4:22pm, Fabio Corazza wrote > >> Can anybody explain me what this error means? > *snip* >> Amanda Backup Client Hosts Check >> >> ERROR: uranus.prosa.com: [samba does not support exclude list] > *snip* > > It means what it says. In your dumptype, you have an exlude list > specified. Backups via samba don't support that (see docs/SAMBA). If > previous versions didn't complain about it, it's only because the > warning was missing, not the condition. Thank you Joshua, I've just commented the line "exclude-list" from root-tar* to obtain a clean / 0 errors amcheck output. Now I only need to wait for tomorrow's results and see if upgrading has been useful. HTH, Fabio
Re: Upgrading to 2.4.4: amcheck complains about samba exclude list
On Wed, 19 Mar 2003 at 4:22pm, Fabio Corazza wrote > Can anybody explain me what this error means? *snip* > Amanda Backup Client Hosts Check > > ERROR: uranus.prosa.com: [samba does not support exclude list] *snip* It means what it says. In your dumptype, you have an exlude list specified. Backups via samba don't support that (see docs/SAMBA). If previous versions didn't complain about it, it's only because the warning was missing, not the condition. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda on SCSI
On Wed, 19 Mar 2003 at 3:51pm, Audrey Brochet wrote > is it possible to backup on SCSI disks with Amanda or only on tape?? Look at the file: driver mentioned in amanda(8) included with version 2.4.4 and/or the list archives. Amanda can use files on disk as if they were tapes. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Dünya'da bir ilk ... Haber portalý, televizyon, radyo bir arada..
Title: New Page 1 Türkiye'nin internetteki ilk ve tek haber kanalý. NET1TV, bir haber portalý, bir haber televizyonu, bir haber radyosu... Bizim ulaþamayacaðýmýz bir coðrafya henüz dünyada yok ve hiçbir haber yok "haber deðeri taþýdýðý halde" yayýnlanmayacak. Haber olmaya deðer ne varsa NET1TV'de olacak... Biz "haber vermeyi" iþ edinmiþ bir "haber portalýyýz". Ve bizler heyecanýn ve gençliðin deneyim gibi bir kýlavuza ihtiyaç duyduðundan eminiz. Medyanýn yozlaþtýðý ve ödünlerin ardý arkasýnýn kesilmediði þu dönemde, ekmeði ile kalemi arasýnda bir tercih yapmak zorunda býrakýlan ve her nedense krizlerin faturasýnýn ödettirildiði basýn mensuplarýndan birkaçýyýz. Biz çalýþýyoruz, biz yazýyoruz ve ayakta kalmak istiyoruz. Daha iyi bir ülke için... Yansýz haber için... Gütmemek ve güdülmemek için... Bizi izlemeniz ve eleþtirmeniz bizlere onur verir. Ýyi baþlangýçlarýn en iyi olmasý dileðiyle. Genel Yayýn Yönetmeni Leyla YÝÐÝT Editörler: Çiðdem POLAT Hatice YILMAZ Sertaç BULUR (Ekonomi) Turgay OKUMUÞ (Spor) Turan Güneş Bul. Sancak Mah. 232. Sok. No: 13/6 06550 Çankaya/ANKARA Tel: [0312] 491 6760 - [0312] 491 6761 Fax: [0312] 491 6762 Web: www.net1tv.com E-Mail: [EMAIL PROTECTED] NET1TV bir UPMEDYA A.Ş. kuruluşudur
Upgrading to 2.4.4: amcheck complains about samba exclude list
I've upgraded my Amanda version since I can't get a clue about some strange problems at amverify (note that the backup completes regularly and I need to backup ONLY Windows hosts through smbclient). After recreating the previous configuration following the new 2.4.4 syntax and changes I get amcheck complaining about the samba exclude list support. I've never heard this before... but it would be annoying recompiling ALSO Samba from source just to include a feature I don't need. Can anybody explain me what this error means? uranus:/usr/src/amanda-2.4.4# su backup -c /usr/sbin/amcheck ProsaDaily Amanda Tape Server Host Check - Holding disk /usr/local/.holding: 13655828 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape PROSADAILY03 label ok NOTE: info dir /var/amanda/ProsaDaily/curinfo: does not exist NOTE: it will be created on the next run NOTE: index dir /var/amanda/ProsaDaily/index: does not exist Server check took 12.447 seconds Amanda Backup Client Hosts Check ERROR: uranus.prosa.com: [samba does not support exclude list] ERROR: uranus.prosa.com: [samba does not support exclude list] ERROR: uranus.prosa.com: [samba does not support exclude list] ERROR: uranus.prosa.com: [samba does not support exclude list] ERROR: uranus.prosa.com: [samba does not support exclude list] ERROR: uranus.prosa.com: [samba does not support exclude list] Client check: 1 host checked in 1.642 seconds, 6 problems found (brought to you by Amanda 2.4.4) Thank you in advance, Fabio
Amanda on SCSI
is it possible to backup on SCSI disks with Amanda or only on tape?? Thank youDo You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail
Re: [HELP] amverify fails restoring
Paul Bijnens wrote: > Op ma 17-03-2003, om 16:46 schreef Fabio Corazza: > >> PROSADAILY04 (uranus.prosa.com.__notorius_EXCHANGE$.20030307.0): >> amrestore: WARNING: not at start of tape, file numbers will be offset > > Did you fsf the tape to the correct position first? Or was it still > at EOF from the last run? You should rewind the tape, or position the > tape with fsf commands manually, or if you are using amanda 2.4.4 > there > is an option to amrecover to do this automatically for you. I'm using Amanda 2.4.2p2 from debian woody packages, anyway this is the crontab file for the backup user: 0 16* * 1-5/usr/sbin/amcheck -m ProsaDaily 45 0* * 2-6/usr/sbin/amdump ProsaDaily; /bin/mt -f /dev/tape rewind; /usr/sbin/amverify ProsaDaily >/dev/null; /bin/mt -f /dev/tape rewoffl The tape is rewinded before starting amverify. Note that /dev/tape is a symbolic link to /dev/nst0. >> amrestore: 0: restoring >> uranus.prosa.com.__notorius_EXCHANGE$.20030307.0 > > It is a samba backup, I see. What version of smbclient did you > use? Some versions (I believe 2.2.3 and before) had a bug in the > builtin tar command, that screwed up the backup images (it did output > an informational message to stdout instead of stderr). Here it goes with Samba 2.2.7a. uranus:~# dpkg -l | grep samba ii samba 2.2.7a-0.1 A LanManager like file and printer server fo ii samba-common 2.2.7a-0.1 Samba common files used by both the server a > The word "exchange" make me wonder if it is an Micrsoft Exchange > datafile that you backed up. I'm not a user of Exchange, but normally > Microsoft Exchange keeps these files open, and you cannot make a > backup of it, without shutting down Microsoft Exchange. > Are you really sure the backup did not complain? It doesn't complain because EXCHANGE$ is a directory shared on a remote server which, through NTBACKUP.EXE, acts as backup client for Exchange 5.5 and stores all the backup data on a file called exchangeBackup.bkf in the EXCHANGE$ directory. I can go through this and show you this is not the problem: uranus:~# smbclient //notorius/EXCHANGE$ -U backup added interface ip=192.168.1.20 bcast=192.168.1.255 nmask=255.255.255.0 Password: Domain=[PROSADOM] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] smb: \> ls . D0 Wed Mar 19 00:00:18 2003 .. D0 Wed Mar 19 00:00:18 2003 exchangeBackup.bkf A 3086029824 Wed Mar 19 00:23:07 2003 38162 blocks of size 1048576. 17993 blocks available smb: \> get exchangeBackup.bkf getting file \exchangeBackup.bkf of size 3086029824 as exchangeBackup.bkf (6366.0 kb/s) (average 6366.0 kb/s) smb: \> I can try to upgrade to the last Amanda release, but I think the problem is elsewhere... P.S.: I can give two hints to improve the mailing list usability, even if probably they have been already discussed: 1) Put a prefix before the subject, it would be more easy to filter and create appropriate rules to avoid shuffling ml's mail from others (work, friends..) 2) Set the reply-to to [EMAIL PROTECTED], or is it just a client issue? Thank you, Fabio
tapetype python
Hello I'm looking for tapetype for a Python 04106-xxx (archive) Thanks Anne --- http://lea-linux.org
re: results missing
Hello again. i accidently deleted the previous answer to my question and therefore did a little research myself, as i forgot what conf files you asked for. The conclusion is that i found out my inetd.conf was not configured correctly to run amanda client on the server itself. once i restored old inetd.conf also, all problems disappeared. So, another reason for RESULTS MISSING has popped up. Laas Toom
