amrecover problems ....
I can't seem to get amrecover to work. I have a single server running amanda, with an SDLT drive attached to it. All my clients are being backed up without problems. (I have done recent recoveries "manually.") However, when I try to run amrecover from a client, when I issue the extract, amrecover fails and tells me to check the amidxtaped log file on the server. I do and at the end of it I see: Ready to execv amrestore with:path = /usr/local/sbin/amrestoreargv[0] = "amrestore"argv[1] = "-h"argv[2] = "-p"argv[3] = "/dev/nst0"argv[4] = "lun"argv[5] = "^/home$"argv[6] = "20030120"amrestore: could not open tape /dev/nst0: Permission deniedamidxtaped: amrestore terminated normally with status: 2Rewinding tape: no tape onlineamidxtaped: pid 27373 finish time Thu Feb 13 17:16:29 2003 the amrecover command I use on the client: /usr/local/sbin/amrecover -C set1 -s godzilla -t godzilla -d /dev/nst0 godzilla is my amanda/tape server, lun is the client I'm trying to run it on. all the clients are having no problem talking to /dev/nst0 on the tape server during backup, why would amrecover be having a problem. Something to do with having to run amrecover as root on the client Clues ?? thanks
BU GÖRÜNTÜLER ÞOK YARATACAK
Bu Mail Size olay medya grubu admini tarafýndan yollanmaktadýr. Kameramanlarýmýz tarafýndan saniye saniye görüntülenen Þok Tecavüz Görüntüleri Bu Ünlü kim Türkiyeyi Sarsacak Görüntüler. www.TeenTurk.ComSadece Üye Olanlar izleyecebilecek www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com www.TeenTurk.Com Yoðun ilgi Sebebiyle www.SexPortali.Net Sitesinide Açtýk www.SexPortali.Net
WHFC and Cover Pages
I've got the cover page working ok when I use sendfax. It inputs different names and stuff perfectly. But how do I do this with WHFC? Do I use the same hylafax cover page? Does WHFC use the same macros and variables like sendfax? Thank you. Jeff Borders
Re: [hylafax-users] windows client WHFC convert to postscript
Your files get converted when you "print" to your fax printer. You setup a fake postscript printer with the Apple LaserWriter driver, use the WHFC Port that gets installed during setup of WHFC. Then, whatever you're doing, whether it be browser based, word, excel, etc, you just print to the fax printer. Hope that helps. Jeff Borders On Wed, 2003-02-12 at 19:46, chloong wrote: > How could i convert my files to ps and send as fax in windows using WHFC? > > Can i send documents like pdf or doc straight forward to the hylafax > server using WHFC? > > Thanks. > > -- > Loong Chee How > Systems and Network Engineer > Internet Professional Services > MCSB Systems (M) Berhad > Ground Floor, Wisma Mirama, > Jalan Wisma Putra, > 50460 Kuala Lumpur > Malaysia. > Tel: +60 (3) 2141 7400 > DID: +60 (3) 2147 4918 > Fax: +60 (3) 2148 8010 > http://www.mcsb.com > email : [EMAIL PROTECTED] > > > > > > > > HylaFAX(tm) Users Mailing List ___ > To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi > On UNIX: mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > *To learn about commercial HylaFAX(tm) support, mail [EMAIL PROTECTED]*
WHFC with multiple attachments.
I just installed this today for a client. It works beautifully. However, How do you add multiple attachments to the fax? The customer has a web-based database app that they will want to fax the results of. WHFC pops up, they can include a cover page, but I don't see how to add different files to the fax. Any ideas? Jeff Borders
Re: hosts timing out on amdump but not amcheck
On Thu, 13 Feb 2003, Joshua Baker-LePain wrote: > On Thu, 13 Feb 2003 at 9:15am, justin m. clayton wrote > > > First of all, thanks to all who helped me track down my NAK problems from > > last week. Having fixed that, all backup hosts pass amcheck with flying > > colors. However, when it comes time for the amdump, my log report claims > > "Request to timed out" when I return the following morning. > > However, if I run amcheck again, no hosts report problems. This has been > > going on for a number of days now. I am getting "Read error at byte > > 0...:Bad file number" on some hosts (via /tmp/amanda/sendsize.*), and some > > are reporting "amandad: dgram_recv: timeout after 10 seconds > > amandad: waiting for ack: timeout, retrying" (via /tmp/amanda/amandad.*). > > Strangely, though, the symptom is the same for all machines. > > What OS/distro? Are there firewalls in the way? The clients are Solaris 8, the server is stable Debian linux, both using 2.4.2p2. No firewalls in the way. This configuration has worked in the past. Justin Clayton VLSI Research System Administrator University of Washington Electrical Engineering Dept [EMAIL PROTECTED] 206/543.2523 EE/CSE 307E
Mystery: configs seem OK, but almost nothing backed up (withsolution!)
Hello,
I'm working with configuring amanda to back up an OS X client. Both the
client and server are running 2.4.3. I got the files to backup across
the network using hfstar at some point earlier in my tinkering, so I
suspect the issue I'm experiencing now is not an "OS X" specific issue.
"amcheck" reports no errors with my client, and amdump runs without
reporting any problems, but virtually nothing appears on the tape-- my
hard drive is hardly touched. It didn't even both the first pass of tar
that just pipes stuff "/dev/null". What are possible causes of this?
A report from this is below. I had just cleared out everything but
"amanda.conf" and "disklist" before this run to minimize possible
sources of the issue.
I think what might have been different the time before when the
backup actually transfered data was that I was using DDS3 tapes (which
we regularly use in production with Amanda). For this backup set,
I switched the tape type to a DDS2 tape that we've used before, and is
expected to work with the DD3 drive. (the tape types refer to the tapes,
not the drives, right?).
Any help is appreciated.
[ Moments later, has inspiration, solves own problem. ]
Commenting this line out in amanda.conf appears to have fixed it:
include list optional ".included"
Now, the files were optional, and they weren't present, so why would this
line affect the behavior of amanda? My guess is that either my syntax is
wrong, or amanda wasn't respecting the "optional" attribute.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark StosbergPrincipal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
-- Forwarded message --
Date: 13 Feb 2003 22:07:54 -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Desktop AMANDA MAIL REPORT FOR February 13, 2003
These dumps were to tape DESKTOP-01.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:02
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) 0.00.0--
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 0.00.0--
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.20.20.0
Tape Used (%) 0.00.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 3160.5 3160.5--
NOTES:
planner: Adding new disk hoobella:/System/Library.
planner: Adding new disk hoobella:/Volumes/X1/Users/mark.
planner: Adding new disk hoobella:/Volumes/X1/System_Folder/Fonts.
planner: Adding new disk hoobella:/Volumes/X1/System_Folder/Preferences.
taper: tape DESKTOP-01 kb 256 fm 4 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
hoobella -em/Library 0 10 64 640.0 0:00 0.0 0:003149.9
hoobella -lder/Fonts 0 10 64 640.0 0:00 0.0 0:003207.2
hoobella -references 0 10 64 640.0 0:00 0.0 0:003112.4
hoobella -Users/mark 0 10 64 640.0 0:00 0.0 0:002821.2
(brought to you by Amanda version 2.4.3)
Re: [LONG] Amanda Tru64 V5.1A client sendsize, /sbin/dump fails
On Thu, Feb 13, 2003 at 06:14:30PM +, Sean McGeever wrote: > Hi, > I've failed to find this precise error condition in either the > amanda or Tru64 archives, so any hints as to solutions would be most welcome. > Sorry for the length of the appended logs, but I hope by including them > I've provided enough data to enable someone to point me in the right > direction. > > *** > > Tru64-client sendsize.debug: > > sendsize: debug 1 pid 268247 ruid 203 euid 203 start time Thu Feb 13 17:39:50 2003 > /usr/local/libexec/sendsize: version 2.4.2p2 > calculating for amname '/', dirname '/' > sendsize: getting size via dump for / level 0 > sendsize: running "/sbin/dump 0Ssf 1048576 - /dev/rdisk/dsk0a" > running /usr/local/libexec/killpgrp > dump: Cannot fopen /dev/tty for reading > query(): fopen(): No such device or address > dump: SIGTERM received > dump: The ENTIRE dump is aborted Trying to open /dev/tty. Seems like it is expecting an interactive session. Maybe the Tru64 version of dump requires options to run in a non-interactive mode? If so, perhaps a wrapper script replacing dump on the client would work by supplying the needed options. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Any interest in a little Python GUI?
I just picked up "Programming Python", and it inspired me to write a GUI for to replace a collection of little Perl scripts I'd been using to launch and monitor Amanda's various operations. It uses the Tkinter library to draw widgets, so it should be portable to just about any major platform that runs Python. Right now, it supports running commands on the local machine or on a remote machine (via passwordless SSH), and can use sudo to run commands as a user other than yourself. Is anyone interested in a copy? It's really nothing that tremendous (especially as it's literally the first program I've ever written in Python), but it works pretty well for me. -- Kirk Strauser In Googlis non est, ergo non est. msg17789/pgp0.pgp Description: PGP signature
Re: [LONG] Amanda Tru64 V5.1A client sendsize, /sbin/dump fails
On Thu, 13 Feb 2003 at 6:14pm, Sean McGeever wrote > Tru64-client sendsize.debug: > > sendsize: debug 1 pid 268247 ruid 203 euid 203 start time Thu Feb 13 17:39:50 2003 > /usr/local/libexec/sendsize: version 2.4.2p2 > calculating for amname '/', dirname '/' > sendsize: getting size via dump for / level 0 > sendsize: running "/sbin/dump 0Ssf 1048576 - /dev/rdisk/dsk0a" > running /usr/local/libexec/killpgrp > dump: Cannot fopen /dev/tty for reading > query(): fopen(): No such device or address That would seem to be the problem (i.e. it can't seem to open /dev/rdisk/dsk0a). Does /dev/rdisk/dsk0a exist, and is it readable by amanda? Can you run the above dump command by hand? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Changing tape order - tapelist not created?
I'm interested in changing my tape order, and I've found the very useful messages in this regard. But then when I went to look at my tapelist it was empty! It is r/w by the amanda user, and in the location specified by the amanda.conf file. Why would this not be getting written? Paul
[LONG] Amanda Tru64 V5.1A client sendsize, /sbin/dump fails
Hi, I've failed to find this precise error condition in either the amanda or Tru64 archives, so any hints as to solutions would be most welcome. Sorry for the length of the appended logs, but I hope by including them I've provided enough data to enable someone to point me in the right direction. Cheers, Sean Context: Amanda server: OpenBSD 3.2, (amanda 2.4.2p2) Amanda client: Tru64 V5.1A, (amanda 2.4.2p2) Amanda client operator == amanda (group system), which owns the amanda binaries. Tru64 disk devices are owned by root:system with permissions 660. Amanda client filesystems are UFS, and are definitely online during this operation. Problem: 'amdump Daily' when run on the amanda server fails when trying to backup Tru64 client. It succeeds, however, when backing-up other clients (OpenBSD, Debian). Logs show failure at the client's estimation stage (i.e., sendsize). 'amcheck Daily' when run on the amanda server reports no error when checking the Tru64 client machine. Logs: - amanda-server amdump log: amdump: start at Thu Feb 13 15:31:42 GMT 2003 planner: pid 21505 executable /usr/local/libexec/amanda/planner version 2.4.2p2 planner: build: VERSION="Amanda-2.4.2p2" planner:BUILT_DATE="Thu Oct 3 03:37:25 MDT 2002" planner:BUILT_MACH="OpenBSD i386.ports.openbsd.org 3.2 GENERIC#26 i386" planner:CC="cc" planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" planner:libexecdir="/usr/local/libexec/amanda" planner:mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" planner:AMANDA_DBGDIR="/tmp/amanda" CONFIG_DIR="/etc/amanda" planner:DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/r" planner:DUMP="/sbin/dump" RESTORE="/sbin/restore" planner:SAMBA_CLIENT="/usr/local/bin/smbclient" planner:GNUTAR="/usr/local/bin/gtar" COMPRESS_PATH="/usr/bin/gzip" planner:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" planner:listed_incr_dir="/var/amanda/gnutar-lists" planner: defs: DEFAULT_SERVER="i386.ports.openbsd.org" planner:DEFAULT_CONFIG="DailySet1" planner:DEFAULT_TAPE_SERVER="i386.ports.openbsd.org" planner:DEFAULT_TAPE_DEVICE="/dev/nrst0" HAVE_MMAP planner:LOCKING=POSIX_FCNTL DEBUG_CODE AMANDA_DEBUG_DAYS=4 planner:BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="operator" planner:FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" planner: COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" planner:UNCOMPRESS_OPT="-dc" planner: dgram_bind: socket bound to 0.0.0.0.607 READING CONF FILES... driver: pid 11319 executable /usr/local/libexec/amanda/driver version 2.4.2p2 driver: send-cmd time 0.002 to taper: START-TAPER 20030213 startup took 0.011 secs SETTING UP FOR ESTIMATES... setting up estimates for $Tru64-client:/ $Tru64-client:/ overdue 12097 days for level 0 setup_estimate: $Tru64-client:/: command 0, options: last_level -1 next_level0 -12097 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates for $Tru64-client:/usr $Tru64-client:/usr overdue 12097 days for level 0 setup_estimate: $Tru64-client:/usr: command 0, options: last_level -1 next_level0 -12097 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates took 0.000 secs GETTING ESTIMATES... taper: pid 9962 executable taper version 2.4.2p2 driver: started dumper0 pid 863 driver: started dumper1 pid 31272 driver: started dumper2 pid 14500 driver: started dumper3 pid 23981 dumper: dgram_bind: socket bound to 0.0.0.0.958 dumper: pid 863 executable dumper version 2.4.2p2, using port 958 dumper: dgram_bind: socket bound to 0.0.0.0.647 dumper: pid 31272 executable dumper version 2.4.2p2, using port 647 dumper: dgram_bind: socket bound to 0.0.0.0.771 dumper: pid 14500 executable dumper version 2.4.2p2, using port 771 dumper: dgram_bind: socket bound to 0.0.0.0.524 dumper: pid 23981 executable dumper version 2.4.2p2, using port 524 got result for host $Tru64-client disk /usr: 0 -> -1K, -1 -> -1K, -1 -> -1K got result for host $Tru64-client disk /: 0 -> -1K, -1 -> -1K, -1 -> -1K getting estimates took 2.094 secs FAILED QUEUE: 0: $Tru64-client /usr 1: $Tru64-client / DONE QUEUE: empty ANALYZING ESTIMATES... planner: FAILED $Tru64-client /usr 0 [disk /usr offline on $Tru64-client?] planner: FAILED $Tru64-client / 0 [disk / offline on $Tru64-client?] INITIAL SCHEDULE (size 4064): DELAYING DUMPS IF NEEDED, total_size 4064, tape length 2048 mark 2000 delay: Total size now 4064. PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 0... analysis took 0.
Re: Amanda and the windows world [Q]
> Does anyone have experience with an amanda => SERVER in a windows environment ? > Unfortunately I don't have any Unix/Linux host available. > > I compiled the complete amanda package under Cygwin 1.3.10, I just don't know how to >start the server and how to connect to the client. Hmmm... Having just done builds of Amanda under CygWin (client only), I did notice a message from ./configure about some lib calls missing and thus the server would not work. Brian ( [EMAIL PROTECTED] ) --- The power to shape the future is earned through persistence. No other quality is as essential to success. It is the sandpaper that breaks down all resistance and sweeps away all obstacles. It is the ability to move mountains one grain of sand at a time.
Re: hosts timing out on amdump but not amcheck
On Thu, 13 Feb 2003 at 9:15am, justin m. clayton wrote > First of all, thanks to all who helped me track down my NAK problems from > last week. Having fixed that, all backup hosts pass amcheck with flying > colors. However, when it comes time for the amdump, my log report claims > "Request to timed out" when I return the following morning. > However, if I run amcheck again, no hosts report problems. This has been > going on for a number of days now. I am getting "Read error at byte > 0...:Bad file number" on some hosts (via /tmp/amanda/sendsize.*), and some > are reporting "amandad: dgram_recv: timeout after 10 seconds > amandad: waiting for ack: timeout, retrying" (via /tmp/amanda/amandad.*). > Strangely, though, the symptom is the same for all machines. What OS/distro? Are there firewalls in the way? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
My problem's solved...
I'm not sure which did it... turning off hardware compression, or moving the holdingdisk to allow for more space. But that big-ass filesystem fits now... :-) Thanks to everyone who pointed out the mt option... I probably should have thought of that myself. Also, for the archives... it turns out that the "Density" button on the drive can also affect compression. -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
hosts timing out on amdump but not amcheck
First of all, thanks to all who helped me track down my NAK problems from last week. Having fixed that, all backup hosts pass amcheck with flying colors. However, when it comes time for the amdump, my log report claims "Request to timed out" when I return the following morning. However, if I run amcheck again, no hosts report problems. This has been going on for a number of days now. I am getting "Read error at byte 0...:Bad file number" on some hosts (via /tmp/amanda/sendsize.*), and some are reporting "amandad: dgram_recv: timeout after 10 seconds amandad: waiting for ack: timeout, retrying" (via /tmp/amanda/amandad.*). Strangely, though, the symptom is the same for all machines. Thoughts? Justin Clayton VLSI Research System Administrator University of Washington Electrical Engineering Dept [EMAIL PROTECTED] 206/543.2523 EE/CSE 307E
Re: another chg-zd-mtx problem
On Thursday 13 February 2003 09:54, Pete Poggione wrote: >Jon - >Perhaps I'm have a blonde moment over this whole configuration > issue. Please excuse my ignorance... and I do appreciate your > help. Below see my comments embedded in your last email.. > >On Wed, 2003-02-12 at 15:16, Jon LaBadie wrote: >> Is there a "groups" command on your system. >> Or maybe the "id" command will show it. > >Both 'groups' and ID work on my system (Mandrake 9) > >>It might be useful to check what are the groups amanda belongs to >> when logged in and when running from cron. >>A little script like this could be make (I'm calling it "ckit") >> >>exec 1> /tmp/ckit-$$ 2>&1 >> >>groups# or id or what ever >>mtx -f status # or info or inquiry or >> what ever > >'amanda' does not belong to any secondary groups. I now have set > the changer device group to 'disk' (the amanda group) and > verified that group has rw permissions. > >lr-xr-xr-x1 root root 36 Feb 10 13:45 /dev/sg2 > -> scsi/host0/bus0/target5/lun1/generic > >crw-rw1 root disk 21, 2 Dec 31 1969 >/dev/scsi/host0/bus0/target5/lun1/generic > >I created the script and ran at the command line as 'amanda' as > well as from amanda's cron. The output looks like this: (I called > both groups and id in the script) The output was identical from > either a shell or cron. > >script output: > >disk >uid=502(amanda) gid=6(disk) groups=6(disk) > Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) >Data Transfer Element 0:Full (Storage Element 2 Loaded) > Storage Element 1:Full > Storage Element 2:Empty > Storage Element 3:Full > Storage Element 4:Full > Storage Element 5:Full > Storage Element 6:Full > >> If that works, try a "cd amanda_config_dir ; chg-zd-mtx > command>" in the cron script. > >OK - I tried this manually.. my configs are in >/usr/local/etc/amanda/daily-net. So I went there and ran: > >/usr/local/libexec/chg-zd-mtx -info. The result was not good. It > returns > >" could not determine current slot" > >The contents of the debug file for the above test is: >== >chg-zd-mtx: debug 1 pid 3361 ruid 0 euid 0: start at Thu Feb 13 > 09:34:17 2003 >09:34:17 Arg info: > $# = 1 > $0 = "/usr/local/libexec/chg-zd-mtx" > $1 = "-info" >09:34:17 Running: /sbin/mtx status >09:34:17 Exit code: 0 > Stdout: > Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) >Data Transfer Element 0:Full (Storage Element 2 Loaded) > Storage Element 1:Full > Storage Element 2:Empty > Storage Element 3:Full > Storage Element 4:Full > Storage Element 5:Full > Storage Element 6:Full >09:34:17 Config info: > firstslot = "1" > lastslot = "6" > cleanslot = "6" Here is the only place I see that might be a problem, but it doesn't appear to be germain to your problem. IF you have a cleaning tape in slot 6, then one would normally set lastslot to "5" which would prevent the inadvertant clean cycle during a "looking for the right tape" scan. IF you don't keep a cleaning tape in slot 6 then I'd not even define cleanslot. I don't know enough about your drive to be much help other than this. My experience is with a Seagate/Campaq 4 slotter. > cleancycle = "120" > offline_before_unload = "0" > unloadpause = "0" > autoclean = "0" > autocleancount = "99" > havereader = "0" > driveslot = "1" > poll_drive_ready = "3" > max_drive_wait = "120" >09:34:17 Exit (2) -> could not determine current slot >chg-zd-mtx: pid 3484 finish time Thu Feb 13 09:34:17 2003 >== > >I don't know if this helps in determining where my stuff is SB > (Sh**'s broke) > >The user config portion of ../daily-net/mtx-changer: > >### USER CONFIGURATION ># Name of the tape drive (takes place of "tapedev" option in >amanda.conf) ># and default driver number in library (usu 0) that DRIVE_NAME > points to >DRIVE_NAME="/dev/nst1" >DRIVE_NUM=0 > ># Location of "STC" command and control device >MTX_CMD="/sbin/mtx"; >MTX_CONTROL="/dev/sg2"; > ># Whether tape drive must eject tape before changer retrieves ># (ie, EXB-2x0). Usually okay if set while not necessary, bad if ># required but not set. >DRIVE_MUST_EJECT=1 > ># How long to check drive readiness (in seconds) after mounting > (or # ejecting) a volume (on some libraries, the motion or eject > command may ># complete before the drive has the volume fully mounted and > online, # or ready for retrieval, resulting in "Drive not > ready"/"Media not # ready" errors). Do an "mt status" command > every 5 seconds upto this # time. >DRIVE_READY_TIME_MAX=120 > ># tape "mt" command location... >MT_CMD="/bin/mt" # called via "MT_CMD -f DRIVE_NAME rewind" & > # "MT_CMD -f DRIVE_NAME offline" to > eject
Re: 2.4.4b1 cygwin client and specifying DLEs with spaces...
On Tuesday, February 11, 2003, at 10:42 PM, John R. Jackson wrote:
.. /cygdrive/c {
comp-tar
include list "include-1"
}
and in /cygdrive/c/include-1:
./Documents and Settings/myuserfolder
Note that you cannot use "include file" as that passes the thing to
include across to the client in the Amanda protocol and falls prey to
the protocol problems.
Hmmm when I do this, I get "include must be at least 3 character
long:" and "No include for /cygdrive/c". I verified that I'm doing
"include list", not "include file". Does it matter that I also have an
exclude list defined for the dump type (because my exclude list falls
through several layers...)?
Thanks,
Ricky
Re: question (if tape server crash)
Gene Heskett wrote: On Wednesday 12 February 2003 21:22, [EMAIL PROTECTED] wrote: If the tape server is crashed, and I reinstall Amanda, can the NEW tape server recognize previous backup tapes and retrive the files? It looks unlikely. As Martin Hepworth aludes to, one must have a backup of the indices available. No, only if you want to use amrecover, to recover individual files with the nice userinterface. But if the server crashed you probably want to restore hole disks, which works fine with dd, and dump or gnutar (and gzip!). Even with dump or gnutar you could restore individual files or directories, if needed. However, when I needed to recover from an hd dying last fall, I found that those files, which most certainly were included in the disklists DLE entries, were not on the tape, on any of the 20 tapes I had. Neither were the amanda executables that were running, or any other executable that was running on the system at the time of the backup. But in my case, the system stuff that wasn't, would Strange! I just verified mine and all is on tape, programs, index-files (even some .gz.tmp files indicating it was just active at that time, of course, I would not rely on those just-being-rebuild-index files.) already have been installed as part of the cd's re-install on the new hard drive, so thats pretty well a moot point. I'd restore the /home dir first in my case as thats where I'd find the latest build of amanda, and a simple make install from that recovered dir would fix that. I came to the conclusion that because I was generating indices, that there must have been an exclusive lock on the files causing tar to skip them. I do not know if this problem is unique to my setup, unique to just linux, or a general one. It must be something else, because there exist no such thing as an exclusive lock used or honoured by tar, afaik. For a while I did a delay of those two DLE,s till the rest was long since done, and then did the backups of those two DLE's using a no index dumptype. Could it be that in that time you had an old version of gnutar and/or amanda that exited with an errorcode instead of giving just a warning, when a file was removed between the time it found the name, and it tried to read its contents. Because the wrong error exitcode of tar, amanda trew the complete backupimage away (did it? I'm not sure anymore). One of my overcafeineted memory cells tells me there once, long time ago, existed such bug, but I could be wrong. Anyway, it works in my setup now (2.4.3), without problems. As proof, I just restored the complete index-files and all of the configuration of my amanda setup of 4 weeks ago. And if I consult those files, I can see the index-files of tapes from 7 weeks ago (which in reality are already overwritten). -- 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 * ***
BU GÖRÜNTÜLER OLAY YARATACAK
content="text/html; charset=windows-1254"> SerhanAdult.Net Türkiyenin porno Portalý topmargin="0"> target="http://www.sexportali.net"> src="" border="0" width="400" height="614"> face="Verdana">T.C Yasalarýna Göre Bu Siteye 18 Yaþýndan Küçüklerin Girmesi Sakýncalý ve Yasaktýr face="Verdana">If you Are Under 18 years old Please Leave This Site Immediately
Re: AMANDA and the Windows world
Hi, I just wanted to thank you all who replied to my post !! Regards Marc Richard MorseTo: Joshua Baker-LePain <[EMAIL PROTECTED]> Subject: Re: AMANDA and the Windows world 02/12/03 05:01 PM On Wednesday, February 12, 2003, at 09:29 AM, Joshua Baker-LePain wrote: > The cygwin client is pretty new and thus less tested. > I'd just like to say that so far, it seems to work. I still need to do a test restore, and I don't know about ACLs, but the signs are that things are working correctly, given the amount of data that gets backed up every night I'm going to do a test restore today, and probably add another two clients, to get better testing results... Ricky
Re: [amanda@fractal.Mines.EDU: DDS4backup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE]
On Thu, Feb 13, 2003 at 12:53:54AM -0700, Michael Robbert wrote: > Gene Heskett wrote: > > >On Wednesday 12 February 2003 19:23, Michael Robbert wrote: > > > > > >Gaack! Either its not advancing the magazine, or you've labeled all tapes > >alike. If the latter, I'm fairly certain that amlabel would have had a > >litter of kittens over that. > > > >Which is it? > > > Neither, I have watched it advance the tapes and you can tell by the > fact that it loaded a cleaning tape from slot 6 that different tapes are > getting used. And I am sure that I labeled all these tapes properly, I > had to use -f because amlabel thought they were labeled even before I > labeled them. I also know that this isn't acurate because when I watch > the drive it loads the tape, but never rewinds or reads the tape to see > what label is actually on it. > It can take a very short time to read 32KB, that is all that is done. Does your tapelist file show all the tapes you labeled? Can you manually do manipulate the changer, load each slot in turn and run "amtape current". This should show what is really in each slot. Assuming there is the correct tape in each slot I'd then guess something in the changer hardware/software (likely the latter) is reporting that the changer is changing but not actually doing the job properly. Though you say you do see the mechanism working, maybe something in the changer status files is not being updated. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda and the windows world [Q]
On Thu, Feb 13, 2003 at 08:47:09AM +0100, Dieter Meinert wrote: > Does anyone have experience with an amanda => SERVER in a windows environment ? > Unfortunately I don't have any Unix/Linux host available. > > I compiled the complete amanda package under Cygwin 1.3.10, I just don't know how to >start the server and how to connect to the client. > > I used amanda on different Unices for several years and would like to have it >running here, too. > I don't recall anyone reporting compiling and using, under cygwin, the server portions of amanda. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: degraded mode
Hello Toomas, I'd thought degraded meant a performance loss but the data still moved to tape. If degraded means no tape, files left in holding partition then what is the term for moving to tape directly ? On another note, to follow up, or ask again on a note I posted a few days ago... Last night my jukebox should have moved back to the lowest number slot with a valid tape, from the highest number slot. ie, amanda #1 needed to move from NEWTONL09 tape in slot 9 to NEWTONL01 tape in slot 1 and amanda # 2 should have moved from NEWTONR09 in slot 9 to NEWTONR05 in slot 5 (where slots 1-4 are being saved for the Saturday only Amanda # 3 doing always-full with yet another tape naming scheme). Anyway, this is the 2nd time we failed to move the tape to a lower slot number, I will include the amdump mail below. -- from amdump email -- *** A TAPE ERROR OCCURRED: [label NEWTONL01 or new tape not found in rack]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: NEWTONL01. -- end email inclusion -- Last time this occured I run amcheck which found the tape and then amflush ran correctly. This time I ran only amflush and the tape was found and the flush ran correctly. humm, details. Solaris 8, Amanda 2.4.2p2 with chg-zd-mtx from 2.4.3, MTX 1.2.16rel, tape drive is an LTO, jukeboxes are SUN Storedge 9, ie HP C7145 thanks, Brian > Hi! > > > Since this left /amanda/work as unavailable I'd have expected amanda > > to have run in degraded mode writing directly to the tape drive, > > however amanda reported that there was no more room in the work area > > and exited without performing any dumps at all. > > Isn't the term 'degraded mode' used in the situation exactly opposite > to yours, i.e. when the tape is not available but holding disk is then > Amanda tries to put as much of stuff as possible on the holding disk? > > I still think, though, that in your situation dumps should have gone > directly to tape. > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ > * I haven't lost my mind; I know exactly where I left it. >
Re: another chg-zd-mtx problem
Jon - Perhaps I'm have a blonde moment over this whole configuration issue. Please excuse my ignorance... and I do appreciate your help. Below see my comments embedded in your last email.. On Wed, 2003-02-12 at 15:16, Jon LaBadie wrote: > Is there a "groups" command on your system. > Or maybe the "id" command will show it. Both 'groups' and ID work on my system (Mandrake 9) >It might be useful to check what are the groups amanda belongs to when logged in and >when running from cron. >A little script like this could be make (I'm calling it "ckit") > >exec 1> /tmp/ckit-$$ 2>&1 > >groups # or id or what ever >mtx -f status # or info or inquiry or what ever > 'amanda' does not belong to any secondary groups. I now have set the changer device group to 'disk' (the amanda group) and verified that group has rw permissions. lr-xr-xr-x1 root root 36 Feb 10 13:45 /dev/sg2 -> scsi/host0/bus0/target5/lun1/generic crw-rw1 root disk 21, 2 Dec 31 1969 /dev/scsi/host0/bus0/target5/lun1/generic I created the script and ran at the command line as 'amanda' as well as from amanda's cron. The output looks like this: (I called both groups and id in the script) The output was identical from either a shell or cron. script output: disk uid=502(amanda) gid=6(disk) groups=6(disk) Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 2 Loaded) Storage Element 1:Full Storage Element 2:Empty Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full > If that works, try a "cd amanda_config_dir ; chg-zd-mtx " > in the cron script. OK - I tried this manually.. my configs are in /usr/local/etc/amanda/daily-net. So I went there and ran: /usr/local/libexec/chg-zd-mtx -info. The result was not good. It returns " could not determine current slot" The contents of the debug file for the above test is: == chg-zd-mtx: debug 1 pid 3361 ruid 0 euid 0: start at Thu Feb 13 09:34:17 2003 09:34:17 Arg info: $# = 1 $0 = "/usr/local/libexec/chg-zd-mtx" $1 = "-info" 09:34:17 Running: /sbin/mtx status 09:34:17 Exit code: 0 Stdout: Storage Changer /dev/sg2:1 Drives, 6 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 2 Loaded) Storage Element 1:Full Storage Element 2:Empty Storage Element 3:Full Storage Element 4:Full Storage Element 5:Full Storage Element 6:Full 09:34:17 Config info: firstslot = "1" lastslot = "6" cleanslot = "6" cleancycle = "120" offline_before_unload = "0" unloadpause = "0" autoclean = "0" autocleancount = "99" havereader = "0" driveslot = "1" poll_drive_ready = "3" max_drive_wait = "120" 09:34:17 Exit (2) -> could not determine current slot chg-zd-mtx: pid 3484 finish time Thu Feb 13 09:34:17 2003 == I don't know if this helps in determining where my stuff is SB (Sh**'s broke) The user config portion of ../daily-net/mtx-changer: ### USER CONFIGURATION # Name of the tape drive (takes place of "tapedev" option in amanda.conf) # and default driver number in library (usu 0) that DRIVE_NAME points to DRIVE_NAME="/dev/nst1" DRIVE_NUM=0 # Location of "STC" command and control device MTX_CMD="/sbin/mtx"; MTX_CONTROL="/dev/sg2"; # Whether tape drive must eject tape before changer retrieves # (ie, EXB-2x0). Usually okay if set while not necessary, bad if # required but not set. DRIVE_MUST_EJECT=1 # How long to check drive readiness (in seconds) after mounting (or # ejecting) a volume (on some libraries, the motion or eject command may # complete before the drive has the volume fully mounted and online, # or ready for retrieval, resulting in "Drive not ready"/"Media not # ready" errors). Do an "mt status" command every 5 seconds upto this # time. DRIVE_READY_TIME_MAX=120 # tape "mt" command location... MT_CMD="/bin/mt" # called via "MT_CMD -f DRIVE_NAME rewind" & # "MT_CMD -f DRIVE_NAME offline" to eject # and "MT_CMD -f DRIVE_NAME status" to get ready info and one again my mtx-changer.conf is: firstslot=1 1st tape slot lastslot=6 Last tape slot cleanslot=6 Slot with cleaner tape # Do you want to clean the drive after a certain number of accesses? # NOTE - This is unreliable, since 'accesses' aren't 'uses', and we # have no reliable way to count this. A single amcheck could # generate as many accesses as slots you have, plus 1. # ALSO NOTE - many modern tape loaders handle this automatically. AUTOCLEAN=0 Set to '1' or greater to enable autocleancount=99 Number of access before a clean. havereader=0
RE: Backing up Windows shares
Thanks all for the help. The problem was referring to the same computer by 2 different names. The share was backed up last night but the log showed the following error. FAILED AND STRANGE DUMP DETAILS: /-- BS1//ADS1/AMRightFax$ lev 0 STRANGE sendbackup: start [BS1://ADS1/AMRightFax$ level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? load_client_codepage: filename /etc/codepages/codepage.850 does not exist. ? load_unicode_map: filename /etc/codepages/unicode_map.850 does not exist. ? load_unicode_map: filename /etc/codepages/unicode_map.ISO8859-1 does not exist. | tar: dumped 35497 files and directories | Total bytes written: 2667331584 sendbackup: size 2604816 sendbackup: end /etc/codepages/codepage.850 does exist owned by root with 0644 permissions. The other files do not. Is there a way to fix this? -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 12, 2003 12:24 PM To: Bill Hults Cc: Amanda List Subject: RE: Backing up Windows shares On Wed, 12 Feb 2003 at 12:18pm, Bill Hults wrote > Is Amanda confused about the server name? There is a note about NAKs when a > host is referred to by different names. I'm backing up the local machine > using the "localhost" name. I'll try changing that to BS1. Yep -- that's the problem. Amanda thinks that they are two different machines, and so tries to contact them separately. But they're not, and so it can't. Changing everything to the hostname (not localhost) is the way to go. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com) This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com)
Re: question (if tape server crash)
On Wednesday 12 February 2003 21:22, [EMAIL PROTECTED] wrote: >If the tape server is crashed, and I reinstall Amanda, can the > NEW tape server >recognize previous backup tapes and retrive the files? >It looks unlikely. >How solve this problem? > >Thanks advanced! > >David As Martin Hepworth aludes to, one must have a backup of the indices available. However, when I needed to recover from an hd dying last fall, I found that those files, which most certainly were included in the disklists DLE entries, were not on the tape, on any of the 20 tapes I had. Neither were the amanda executables that were running, or any other executable that was running on the system at the time of the backup. But in my case, the system stuff that wasn't, would already have been installed as part of the cd's re-install on the new hard drive, so thats pretty well a moot point. I'd restore the /home dir first in my case as thats where I'd find the latest build of amanda, and a simple make install from that recovered dir would fix that. I came to the conclusion that because I was generating indices, that there must have been an exclusive lock on the files causing tar to skip them. I do not know if this problem is unique to my setup, unique to just linux, or a general one. For a while I did a delay of those two DLE,s till the rest was long since done, and then did the backups of those two DLE's using a no index dumptype. I believe this will work, but as the backup time needed is a variable, and the delay one can program into a DLE entry is fixed, I now have a couple of scripts that are run as soon as amdump is done, and which append that particular 50 megabyte pair of files (indices and configs dirs) to the tape if there is room left on the tape. And I've reduced the tapetype size by about 100 megs so that when balance has been restored, there will always be room on the tape for them. So now I have hopefully last nights indices and such on tonights tape as a regular DLE, and if I can recall how many fm's there are on a tape, I can search with mt, and immediately recover the indices that actually made that tape from the end of it. In my case it would be an "mt -f /dev/nst0 fsf 36" which should park the tape ready to read those last two files with dd as I have 35 DLE's. Others may also have different methods of doing file lock workarounds, this is just my personal, and not well tested solution to a not too well discussed problem. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.23% setiathome rank, not too shabby for a WV hillbilly
Re: [amanda@fractal.Mines.EDU: DDS4backup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE]
On Thursday 13 February 2003 02:53, Michael Robbert wrote: >Gene Heskett wrote: >>On Wednesday 12 February 2003 19:23, Michael Robbert wrote: >>>Here is an update on the problem that I sent yesterday. I had >>>entered my DDS4backup into cron and last night the backup >>>actually worked, sort of. It looks like it wrote to the tape in >>>slot one, which I labeled DDS4backup01, but the report says that >>>it was labeled DDS4backup05. Below you'll find the results of >>>todays amcheck, all tapes appear to be labeled DDS4backup05, but >>>that is not how I labeled them. I am guessing that tonights >>>backup will fail because it can't seem to find another tape. >>>A second question I have is about the number of slots to put >>> into my changer.conf. I am using the first 5 slots for backup >>> tapes and slot 6 is always a cleaning tape. If I configure >>> lastslot=5 and cleanslot=6 then "amtape DDS4backup clean" gives >>> the following error: amtape: device 0 not clean: Slot 6 is out >>> of range (1 - 5) If I then change lastslot=6 then I get the >>> problem that you'll notice below. Amanda will cycle through the >>> cleaning tape thinking that it is a normal tape. I am using >>>tpchanger=chg-zd-mtx in my amanda.conf. >>> >>>- Forwarded message from Amanda user >>><[EMAIL PROTECTED]> - >>> >>>Date: Wed, 12 Feb 2003 16:04:15 -0700 > From: Amanda user <[EMAIL PROTECTED]> > >>>To: [EMAIL PROTECTED], [EMAIL PROTECTED] >>>Subject: DDS4backup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE >>>X-Spam-Status: No, hits=-98.9 required=5.0 >>> tests=DOUBLE_CAPSWORD,USER_IN_WHITELIST >>> version=2.31 >>> >>>Amanda Tape Server Host Check >>>- >>>Holding disk /holding/amanda: 6128768 KB disk space available, >>>using 6026368 KB Holding disk /storage/amanda: 40446788 KB disk >>>space available, using 40344388 KB >>>amcheck-server: slot 2: date 20030212 label DDS4backup05 (active >>> tape) amcheck-server: slot 3: date 20030212 label DDS4backup05 >>> (active tape) amcheck-server: slot 4: date 20030212 label >>> DDS4backup05 (active tape) amcheck-server: slot 5: date >>> 20030212 label DDS4backup05 (active tape) amcheck-server: fatal >>> slot 6: Cleaning Cartridge Installed and Ejected >> >>Gaack! Either its not advancing the magazine, or you've labeled >> all tapes alike. If the latter, I'm fairly certain that amlabel >> would have had a litter of kittens over that. >> >>Which is it? > >Neither, I have watched it advance the tapes and you can tell by > the fact that it loaded a cleaning tape from slot 6 that > different tapes are getting used. And I am sure that I labeled > all these tapes properly, I had to use -f because amlabel thought > they were labeled even before I labeled them. I also know that > this isn't acurate because when I watch the drive it loads the > tape, but never rewinds or reads the tape to see what label is > actually on it. Thats odd unless this changer has a barcode reader or some other means of identifying the tape. The tapes should be labeled with some sort of a unique label per tape, and one that satisfies the regex pattern in your amanda.conf. When labeling new tapes with a never before used label, one shouldn't need to use the -f option. If they are in fact labeled as DDS4Backup01, DDS4Backup02, DDS4Backup03 etc then the -f option shouldn't be needed. Please post the label pattern line from your amanda.conf. >>>ERROR: new tape not found in rack >>> (expecting a new tape) >>>NOTE: skipping tape-writable test >>>NOTE: info dir >>> /var/lib/amanda/DDS4backup/curinfo/ito/_usr_local: does not >>> exist NOTE: index dir >>>/var/lib/amanda/DDS4backup/index/ito/_usr_local: does not exist >>>NOTE: info dir /var/lib/amanda/DDS4backup/curinfo/ito/_u1: does >>>not exist NOTE: index dir >>>/var/lib/amanda/DDS4backup/index/ito/_u1: does not exist Server >>>check took 254.892 seconds Ahh, I missed that line. Can I blame it on the poor formatting as it was rx'd here? Ny apologies in any event. >>>Amanda Backup Client Hosts Check >>> >>>Client check: 1 host checked in 0.510 seconds, 0 problems found >> >>This settles it. >> >>Its not advancing the tape then, and it obviously read all that >>from the drives buffers. So something is amiss in the changer >>script setup. This amount of tape checking should have taken a >> time measured in minutes, not just fractions of a second. > >The tape check took 254.892 seconds(over 4 minutes), it was the > client host check that only took 0.510 seconds -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.23% setiathome rank, not too shabby for a WV hillbilly
Re: question (if tape server crash)
Hi! > If the tape server is crashed, and I reinstall Amanda, can the NEW tape > server > recognize previous backup tapes and retrive the files? > It looks unlikely. Why do you think it looks unlikely? The backups done by Amanda are in dump or tar format, and I don't see why you couldn't read the tapes with restore or tar, respectively. The only thing you lose in tape server crash are the index files. But that just means you can't use amrecover and must use amrestore. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * If you cannot change your mind, are you sure you have one?
Re: degraded mode
Hi! > Since this left /amanda/work as unavailable I'd have expected amanda > to have run in degraded mode writing directly to the tape drive, > however amanda reported that there was no more room in the work area > and exited without performing any dumps at all. Isn't the term 'degraded mode' used in the situation exactly opposite to yours, i.e. when the tape is not available but holding disk is then Amanda tries to put as much of stuff as possible on the holding disk? I still think, though, that in your situation dumps should have gone directly to tape. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * I haven't lost my mind; I know exactly where I left it.
Re: question (if tape server crash)
[EMAIL PROTECTED] wrote: If the tape server is crashed, and I reinstall Amanda, can the NEW tape server recognize previous backup tapes and retrive the files? It looks unlikely. This is just one of the strengths of Amanda. You don't need Amanda software to do a restore. A shell, dd, and dump or gnutar (depending on how you created them) is enough. And access to a tapedrive (local or remote) of course. See docs/RESTORE to the different scenario's to follow. On Linux you have enough with a bootable floppy, and a minimal root filesystem, or a bootable cd. (Don't forget to run lilo when done.) On Solaris, you need a little more expertise to boot from cd and access a tape device (but it is possible!), and you have to make the disk bootable afterwards (very badly documented if you ask me). You could also just install a minimal system and then do your full restore. I have no experience with restoring Amanda on other OS'es. (O, yes, on Windows, you need to reinstall Windows, and then you can restore the data files that you backed up with amanda. Restoring programs or registry is much more complicated if useful at all; but then again, Windows is not used as the tape server). How solve this problem? -- 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: question (if tape server crash)
[EMAIL PROTECTED] wrote: If the tape server is crashed, and I reinstall Amanda, can the NEW tape server recognize previous backup tapes and retrive the files? It looks unlikely. How solve this problem? Thanks advanced! David David Hopefully you're backing up the tape server and specifically the area where all the indexes etc are kept. Then all you need to do is restore the amanda indexes, conf files etc to the new server. -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: [amanda@fractal.Mines.EDU: DDS4backup AMANDA PROBLEM: FIX BEFORERUN, IF POSSIBLE]
Gene Heskett wrote: On Wednesday 12 February 2003 19:23, Michael Robbert wrote: Here is an update on the problem that I sent yesterday. I had entered my DDS4backup into cron and last night the backup actually worked, sort of. It looks like it wrote to the tape in slot one, which I labeled DDS4backup01, but the report says that it was labeled DDS4backup05. Below you'll find the results of todays amcheck, all tapes appear to be labeled DDS4backup05, but that is not how I labeled them. I am guessing that tonights backup will fail because it can't seem to find another tape. A second question I have is about the number of slots to put into my changer.conf. I am using the first 5 slots for backup tapes and slot 6 is always a cleaning tape. If I configure lastslot=5 and cleanslot=6 then "amtape DDS4backup clean" gives the following error: amtape: device 0 not clean: Slot 6 is out of range (1 - 5) If I then change lastslot=6 then I get the problem that you'll notice below. Amanda will cycle through the cleaning tape thinking that it is a normal tape. I am using tpchanger=chg-zd-mtx in my amanda.conf. - Forwarded message from Amanda user <[EMAIL PROTECTED]> - Date: Wed, 12 Feb 2003 16:04:15 -0700 From: Amanda user <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: DDS4backup AMANDA PROBLEM: FIX BEFORE RUN, IF POSSIBLE X-Spam-Status: No, hits=-98.9 required=5.0 tests=DOUBLE_CAPSWORD,USER_IN_WHITELIST version=2.31 Amanda Tape Server Host Check - Holding disk /holding/amanda: 6128768 KB disk space available, using 6026368 KB Holding disk /storage/amanda: 40446788 KB disk space available, using 40344388 KB amcheck-server: slot 2: date 20030212 label DDS4backup05 (active tape) amcheck-server: slot 3: date 20030212 label DDS4backup05 (active tape) amcheck-server: slot 4: date 20030212 label DDS4backup05 (active tape) amcheck-server: slot 5: date 20030212 label DDS4backup05 (active tape) amcheck-server: fatal slot 6: Cleaning Cartridge Installed and Ejected Gaack! Either its not advancing the magazine, or you've labeled all tapes alike. If the latter, I'm fairly certain that amlabel would have had a litter of kittens over that. Which is it? Neither, I have watched it advance the tapes and you can tell by the fact that it loaded a cleaning tape from slot 6 that different tapes are getting used. And I am sure that I labeled all these tapes properly, I had to use -f because amlabel thought they were labeled even before I labeled them. I also know that this isn't acurate because when I watch the drive it loads the tape, but never rewinds or reads the tape to see what label is actually on it. ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/DDS4backup/curinfo/ito/_usr_local: does not exist NOTE: index dir /var/lib/amanda/DDS4backup/index/ito/_usr_local: does not exist NOTE: info dir /var/lib/amanda/DDS4backup/curinfo/ito/_u1: does not exist NOTE: index dir /var/lib/amanda/DDS4backup/index/ito/_u1: does not exist Server check took 254.892 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.510 seconds, 0 problems found This settles it. Its not advancing the tape then, and it obviously read all that from the drives buffers. So something is amiss in the changer script setup. This amount of tape checking should have taken a time measured in minutes, not just fractions of a second. The tape check took 254.892 seconds(over 4 minutes), it was the client host check that only took 0.510 seconds
Re: Amanda and the windows world [Q]
Does anyone have experience with an amanda => SERVER in a windows environment ? Unfortunately I don't have any Unix/Linux host available. I compiled the complete amanda package under Cygwin 1.3.10, I just don't know how to start the server and how to connect to the client. I used amanda on different Unices for several years and would like to have it running here, too. Regards Dieter Meinert
Re: AMANDA and the Windows world
Hi, > Actually in my experience, you are more likely to see development to > support other OSes OUTSIDE of M$. What might be an interesting idea > is if there is a freeware/opensource backup/restore program for > Windows that could be integrated into the AmandaClient... As a long time amanda user I can pretty well remember that this requirement has been discussed quite often in the past... If you have a look at the sourceforge-project "Amanda Backup Win32 Clients" (which has been abbandonned since 2001), there you can find a small program called "nttar", which nicely backs up (and restores) nt acls. I recently tested it - looked quite good. I think it should not be too hard to code a wrapper around this (or to integrate some changes into the source) to make it react like gnutar - and then to integrate it into amanda. Regards, Christopher (who would love to see amanda one day back up windoze boxes natively)
