Re: y didn't amanda report this as an error?
Phil Homewood wrote: > Now that you mention it, I have had this, a couple of times in the > last week. Am still trying to debug it, but: > > ??error [/bin/tar got signal 13, compress got signal 11]? dumper: strange [missing > size line from sendbackup] Turns out this also appears to be bad hardware, in case anyone's collecting responses. > hammer /home 0 0 1568 --0:08 184.4 0:04 442.5 [left in to show that amanda still considers this a successful dump] -- Phil Homewood, Systems Janitor, http://www.SnapGear.com [EMAIL PROTECTED] Ph: +61 7 3435 2810 Fx: +61 7 3891 3630 SnapGear - Custom Embedded Solutions and Security Appliances
amcheck errors
Hi all
I have run into some silly permission problem that i cant figure out.
What do i miss?
As amanda-user i can run "mtx" just fine and change tapes back an forth,
but "chg-zd-mtx" says:
-bash-2.05b$ chg-zd-mtx -info
no slots available
And "amcheck normal" says:
-bash-2.05b$ amcheck normal
Amanda Tape Server Host Check
-
WARNING: program /usr/local/amanda/bin/planner: not setuid-root
WARNING: program /usr/local/amanda/bin/dumper: not setuid-root
WARNING: program /usr/local/amanda/bin/amcheck: not setuid-root
Holding disk /amanda: 25678660 KB disk space available, using 25678660 KB
amcheck-server: could not get changer info: no slots available
Amanda Backup Client Hosts Check
WARNING: hostname.deleted: selfcheck request timed out. Host down?
Client check: 1 host checked in 29.999 seconds, 1 problem found
(brought to you by Amanda 2.4.4)
But i have set set the SUID bit:
-bash-2.05b$ ls -l /usr/local/amanda/bin/{planner,dumper,amcheck}
-rwsr-x---1 amanda amanda 93327 Sep 5 17:24
/usr/local/amanda/bin/amcheck
-rwsr-x---1 amanda amanda 89732 Sep 5 17:24
/usr/local/amanda/bin/dumper
-rwsr-x---1 amanda amanda 91540 Sep 5 17:24
/usr/local/amanda/bin/planner
And this is what the logfiles says after running "amcheck normal":
-bash-2.05b$ cat /tmp/amanda/amcheck.20030926083742.debug
amcheck: debug 1 pid 16062 ruid 501 euid 501: start at Fri Sep 26 08:37:42 2003
amcheck: dgram_bind: socket bound to 0.0.0.0.32781
changer: got exit: 2 str: no slots available
amcheck-server: time 0.140: could not get changer info: no slots available
amcheck-server: time 0.140: pid 16063 finish time Fri Sep 26 08:37:42 2003
amcheck: pid 16062 finish time Fri Sep 26 08:38:12 2003
chg-zd-mtx: debug 1 pid 16075 ruid 501 euid 501: start at Fri Sep 26 08:37:42
2003
08:37:42 Arg info:
$# = 1
$0 = "/usr/local/amanda/bin/chg-zd-mtx"
$1 = "-info"
08:37:42 Running: mtx status
08:37:42 Exit code: 127
Stderr:
/usr/local/amanda/bin/chg-zd-mtx: line 387: mtx: command not found
08:37:42 Exit (2) -> no slots available
chg-zd-mtx: pid 16154 finish time Fri Sep 26 08:37:42 2003
I have also added these entries for xinetd and done a "kill -HUP":
bash# cat /etc/xinetd.d/amanda-*
#
# amanda client tjänster
#
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
server = /usr/local/amanda/bin/amandad
log_type= SYSLOG
}
#
# amanda server tjänster
#
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
server = /usr/local/amanda/bin/amindexd
log_type= SYSLOG
}
#
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
server = /usr/local/amanda/bin/amidxtaped
log_type= SYSLOG
}
Any ideas about what im doing wrong?
Thanks for your time
//Mats
Fw: senin icin :) kd xeldwhhpoh bwdvgyp mz
Title: iSTE OLAY ViDEO http://gulben.videosu.com FLASH!!! FLASH!!! FLASH!!! FLASH!!! TURKiYE'DE iLK KEZ GULBEN ERGENiN SKANDAL ViDEO KASEDi ViDEOYU SEYRETMEK iCiN TIKLAYIN Not: Sadece ozel video player ile internet uzerinden seyredebilirsiniz.
Using chg-manual question
I have Amanda 2.4.4p1 setup to backup two partitions, 7GB and 4GB of data, on a Linux machine using dump. I'm using only one tape drive to backup the two partitions and 1GB of holding disc. For the initial backup, Amanda will backup both partition using level 0 which is bigger than the tape can hold. Each partition is bigger than holding disk. Can I setup Amanda to use chg-manual script to backup the partitions to multiple tapes? I know I need to change the tape manually. I read somewhere in the past that Amanda can not span tapes. Thanks, Yan
Re: /dev/sg numbering
Hi again... ;-) Stephen Walton wrote: On Wed, 2003-09-24 at 23:10, C.Scheeder wrote: Hi, Is your changer the only device showing up in /proc/scsi/scsi? or just the only device with a LUN of 1 ? The former. I have 3 SCSI devices, but the other two are disks with only LUN=0. The tape drive shows up last in the list from /proc/scsi/scsi. I suppose that's why the sg driver puts its other LUN at /dev/sg3? yup, that is it. the lun number is only the way scsi uses to address multiple logical units which respond to a single scsi-id. to get the sg number for a device/lun is verry easy, count the position of your device/lun in proc/scsi/scsi starting from 0 for the first entry and you have the sg-number for your device. I'm just a bit curious, but I'm also worried about the number changing and breaking Amanda if I add or remove SCSI devices from the system. I always tell people that one of the big advantages of Unix over Windows is that devices don't shift from D: to E: to F: as you add disks, so scripts and software still work. This is not true for scsi-devices in linux. they change their names if inserting new id's of the same type at lower numbers in the chain. But they do so in a easy to understand and predictable way. The main advantage of unix is the abstraction from driveletters. Your userr don't see any drives at all, only one big tree of directorys, no matter where the files are stored. But i think this is a little off Topic... Christoph
Re: Adding Clients
Hi, chris weisiger, on Donnerstag, 25. September 2003 at 21:01 you wrote to amanda-users: cw> Now that i have my backup working dumping/restoring cw> Do i need to add just the amanda-client rpm or the amanda rpm also? If you have Amanda dumping/restoring you don´t need no more rpms. I suppose you mean the client-installation. Did you install via tarball or rpm on your server? You can use ./configure --with-client-only make && make install on your clients if using tarballs, otherwise rpm -ivH amanda-client-xyz.rpm It is generally recommended to use the tarball, there are many things configured at compile-time, it is worth the effort most of the time. get the latest at http://prdownloads.sourceforge.net/amanda/amanda-2.4.4p1.tar.gz?download cw> Either way how do i direct the client to point to the server? cw> Or does the server search for clients on a network ? The amanda-server knows about the clients from looking into the disklist file where all the disklist entries (aka DLEs) point to the filesystems on the clients you want to backup. I suggest you read the ./docs/INSTALL-file from the latest Amanda-tarball. It helps a lot and covers all the necessary first steps. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Adding Clients
Now that i have my backup working dumping/restoring Do i need to add just the amanda-client rpm or the amanda rpm also? Either way how do i direct the client to point to the server? Or does the server search for clients on a network ?
Re: Rewind before ejecting?
Some tape drives must be taken off line before they will eject. my adic fastor4000 is on like that. every time I eject manually I have to issue the command "/bin/mt -f /dev/st0 rewoffl" (rewind and take off line). some drives don't need thins and can just be given the eject command. good luck, chrisj M3 Freak wrote: Hello, I have what may seem like a silly questions, but let me assure you, I have absolutely no idea how tape backups work. I've only just figured out why my RH9 system wasn't seeing the tape drive. Configuring amanda and administering it is a whole different thing! Anyway, my question is basic. Last night I manually ran "amdump", and it completed successfully. I read the email amanda sent me, and it's now waiting for a "new tape". I know that I have to put in the new tape, label it, and then set up cron to run automatically tonight. However, before I put in the new tape, should I just issue an "eject" command to the drive to spit the tape out, or do I have to rewind it before ejecting it? I haven't used a tape backup system before, so I don't know what the consequences are of rewinding tapes or not before ejecting them. I would very much appreciate suggestions/advice on this. Thanks in advance. Regards, Kanwar
Re: amrecover error
--On Thursday, September 25, 2003 13:01:49 -0500 chris weisiger <[EMAIL PROTECTED]> wrote: > When i run that command i get the following: > > /dev/tape: No such file or directory > > do i have to create a symlink from /dev/sg0 to /dev/tape ?? Most likely your tape drive is /dev/st0, sg0 is probably the changer device. The default device for mt on linux is /dev/tape, but you can also tell it what device to use, such as mt -f /dev/st0 rewind or you can symlink /dev/tape to whatever device it is. Yoiu can check dmesg or your boot messages to see what device your system thinks the tape drive is. BTW, I think Jon had the right idea about your amrecover problem. I overlooked that you were trying to use a tapelabel as the tape device. Frank > > Eric Siegerman wrote: > >> On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: >> >> >>> so how do i rewind the tape? >>> >>> >> >> "mt rewind" >> >> -- >> >>| | /\ >>| -_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] >>| | / >> When I came back around from the dark side, there in front of me would >> be the landing area where the crew was, and the Earth, all in the view >> of my window. I couldn't help but think that there in front of me was >> all of humanity, except me. >> - Michael Collins, Apollo 11 Command Module Pilot >> >> >> > -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Found Error
I found my problem...I was setting the disk to DailySet13 instead of /dev/nst0 Thanks for the help
Re: amrecover error
When i run that command i get the following: /dev/tape: No such file or directory do i have to create a symlink from /dev/sg0 to /dev/tape ?? Eric Siegerman wrote: On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: so how do i rewind the tape? "mt rewind" -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: amcheck - why run it?
This is to thank everyone that responded to the original posting. General consensus is that you run amchecks late in the afternoon, check e-mail, fix any problems before you go home. For amverify, most run this on the weekend or after the last backup of the week has completed. But a better recommendation is to weekly test a restore process to really make sure it works. As for myself, I'll run amcheck in the afternoon and try to remember to check e-mail before I leave for the day and run amverify on the weekends. As far as testing a restore, I'll do this on weekends or holidays when I have other work scheduled. There's this perception by end-users and management that our systems should be available 24x7x365. Just a side note - I am now backing up 2 Sun servers and 24 Windows NT/2000 servers. Just after I had Amanda working for a couple of weeks, a WebCt administrator deleted several online courses from the server in error. Of course, she had no backup copies. Latest backup from the network group was almost a week old (best they could do was a weekly backup). I had just backed up this server the day before. I used gnutar to restore the backup to disk and then used amrestore to restore the files that were deleted to the server. The bag of candy kisses from the WebCT admin was greatly appreciated. Bob... > Bob, > > I don't run amdump dependent on amcheck output - amdump can fail > quite well on its own. > > Lately, with the advent of some network viruses, I've had backups not occur > > when I run amcheck before running amdump. My script, which is run from > > crontab, checks to see if amcheck ran successfully before I allow amdump to > > run. I'm using samba to back up Windows servers across the network to my > > Sun server. Is there any good reason to have this type of procedure in > > place where amcheck must be successful before running amdump? > > > > Also, I don't run amverify either because I lack the time during the backup > > window for this. I'm not sure this is necessary either. What is amverify > > really checking? I don't think it checks what was dumped on tape vs what is > > on the disk. Is it necessary to make sure you really have a valid backup? > > > > Bob...
Re: Rewind before ejecting?
At 11:57 AM 9/25/2003 -0400, M3 Freak wrote: Hello, I have what may seem like a silly questions, but let me assure you, I have absolutely no idea how tape backups work. I've only just figured out why my RH9 system wasn't seeing the tape drive. Configuring amanda and administering it is a whole different thing! Anyway, my question is basic. Last night I manually ran "amdump", and it completed successfully. I read the email amanda sent me, and it's now waiting for a "new tape". I know that I have to put in the new tape, label it, and then set up cron to run automatically tonight. However, before I put in the new tape, should I just issue an "eject" command to the drive to spit the tape out, or do I have to rewind it before ejecting it? I haven't used a tape backup system before, so I don't know what the consequences are of rewinding tapes or not before ejecting them. I would very much appreciate suggestions/advice on this. Thanks in advance. Regards, Kanwar All tapes drives that I know of will rewind the tape if you merely issue an "eject" or "offline" command. Only an audio cassette unit (ok, or a VCR) will ever hand you a tape in a half-way state. So . commanding "rewind" and then "eject" is redundant. But certainly not harmful! Deb Baddorf --- Deb Baddorf [EMAIL PROTECTED] 840-2289 "Nobody told me that living happily ever after would be such hard work ..." S. White<
Re: Rewind before ejecting?
On Thu, Sep 25, 2003 at 11:57:35AM -0400, M3 Freak wrote: > [...] should I just issue an "eject" > command to the drive to spit the tape out, or do I have to rewind it > before ejecting it? It depends on the tape technology, I think. DAT tapes rewind on their own. Some other kinds might not (though I don't really know). What kind of tape drive do you have? -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: amrecover error
On Thu, Sep 25, 2003 at 12:34:57PM -0500, chris weisiger wrote: > so how do i rewind the tape? "mt rewind" -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / When I came back around from the dark side, there in front of me would be the landing area where the crew was, and the Earth, all in the view of my window. I couldn't help but think that there in front of me was all of humanity, except me. - Michael Collins, Apollo 11 Command Module Pilot
Re: amrecover error
so how do i rewind the tape?
Frank Smith wrote:
--On Thursday, September 25, 2003 11:53:22 -0500 chris weisiger <[EMAIL PROTECTED]> wrote:
This is what is in amidxtaped.debug file:
amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 12:15:38 2003
amidxtaped: version 2.4.3
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user root local user
amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: > 6
amidxtaped: time 0.001: amrestore_nargs=6
amidxtaped: time 0.001: > -h
amidxtaped: time 0.001: > -p
amidxtaped: time 0.001: > DailySet13
amidxtaped: time 0.001: > ^bs1.domain.name$
amidxtaped: time 0.001: > ^/testData$
amidxtaped: time 0.001: > 20030925
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "DailySet13"
argv[4] = "^bs1.domain.name$"
argv[5] = "^/testData$"
argv[6] = "20030925"
amrestore: could not stat DailySet13
amidxtaped: time 0.007: amrestore terminated normally with status: 2
amidxtaped: could not stat DailySet13
amidxtaped: time 0.007: could not stat DailySet13
amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
DailySet13 tape is in the drive
Was the tape rewound first (as it needs to be), or was it sitting
at the end after the last backup? Looks like its not able to read
the header, probably because you're not at the begining of the tape.
and this is how a copy of my amrecover session
[EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t bs1.domain.name -d /dev/nst0
AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
220 bs1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-09-25)
200 Working date set to 2003-09-25.
200 Config set to DailySet1.
501 No index records for host: bs1. Invalid?
Trying host bs1.domain.name ...
200 Dump host set to bs1.domain.name.
Trying disk /var ...
Trying disk hda6 ...
Can't determine disk and mount point from $CWD '/var/lib/amanda' <-- I dont understand this error here
Amanda defaults the DLE to recover to be the directory you're in
when you run it, so if your cwd is /var/lib/amanda, it looks for
a DLE that contains it. If you're restoring to a different directory
(as you are, and is often a good idea, especially when testing), then
you just need to use the setdisk command to pick the DLE you want and
just ignore the warning.
Frank
amrecover> help
valid commands are:
add path1 ... - add to extraction list (shell wildcards)
addx path1 ...- add to extraction list (regular expressions)
cd directory - change cwd on virtual file system (shell wildcards)
cdx directory - change cwd on virtual file system (regular expressions)
clear - clear extraction list
delete path1 ... - delete from extraction list (shell wildcards)
deletex path1 ... - delete from extraction list (regular expressions)
extract - extract selected files from tapes
exit
help
history - show dump history of disk
list [filename] - show extraction list, optionally writing to file
lcd directory - change cwd on local file system
ls- list directory on virtual file system
lpwd - show cwd on local file system
mode - show the method used to extract SMB shares
pwd - show cwd on virtual file system
quit
listdisk [diskdevice] - list disks
setdate {-MM-DD|--MM-DD|---DD} - set date of look
setdisk diskname [mountpoint] - select disk on dump host
sethost host - select dump host
settape [host:][device|default] - select tape server and/or device
setmode smb|tar - select the method used to extract SMB shares
amrecover> setdisk /testData
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover> sethost bs1.domain.name
200 Dump host set to bs1.domain.name.
amrecover> settape DailySet13
Using tape "DailySet13" from server bs1.domain.name.
amrecover> cd /testData/
/testData
amrecover> ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover> add File*
Added /File1
Added /File2
amrecover> extract
Extracting files using tape drive DailySet13 on host bs1.domain.name.
The following tapes are needed: DailySet13
Restoring files into directory /testData
Continue [?/Y/n]? Y
Extracting files using tape drive DailySet13 on host bs1.domain.name.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.domain.name.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue [?/Y/n]? Y
amrecover>
Frank Smith wrote:
--On Thursday, September 25, 200
RE: Recovering from backup to file
Jon LaBadie said: > > On Thu, Sep 25, 2003 at 10:16:48AM -0500, Josh Welch wrote: > > However, it now turns out that when I have been archiving my backups to > > tape, I have not been archiving the index files, crap. So, I > have the files > > backed up, but not sure how to get at the data within. I read > about using dd > > to get at a tapes contents and then untarring them, and so I > tried using tar > > to extract from the 30.mplslx1.buffalowildwings.com_home.0 > file, but it > > said it was not a tar archive. So, I am wondering if anyone has > any ideas of > > how I can go about this. > > dd the first 32K block of the file to see instructions. > Huh, I figured this would be different, but now that you point it out I don't know why it would be different. Amanda doesn't know the difference if she's writing to a tape or a file on disk, makes sense. For archival purposes, the command: # dd if=AMANDA.DUMP.FILE.NAME of=info.txt bs=32k count=1 Kicked out this information to info.txt: AMANDA: FILE 20030915 mplslx1.buffalowildwings.com /var lev 0 comp .gz program /bin/gtar To restore, position tape at start of file and run: dd if= bs=32k skip=1 | /bin/gzip -dc | bin/gtar -f... - So, I'm off to do that. Thanks, Josh
Re: Rewind before ejecting?
On Thu, Sep 25, 2003 at 11:57:35AM -0400, M3 Freak wrote: > Hello, > > I have what may seem like a silly questions, but let me assure you, I > have absolutely no idea how tape backups work. I've only just figured > out why my RH9 system wasn't seeing the tape drive. Configuring amanda > and administering it is a whole different thing! > > Anyway, my question is basic. Last night I manually ran "amdump", and > it completed successfully. I read the email amanda sent me, and it's > now waiting for a "new tape". I know that I have to put in the new > tape, label it, and then set up cron to run automatically tonight. > However, before I put in the new tape, should I just issue an "eject" > command to the drive to spit the tape out, or do I have to rewind it > before ejecting it? > > I haven't used a tape backup system before, so I don't know what the > consequences are of rewinding tapes or not before ejecting them. I > would very much appreciate suggestions/advice on this. To my relatively limited knowledge, drives rewind the tape before ejecting. OTOH I don't generally count on that and rewind myself first. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
/dev/sg numbering (was: Re: Problem with chg-scsi on linux)
On Wed, 2003-09-24 at 23:10, C.Scheeder wrote: > Hi, > Is your changer the only device showing up in /proc/scsi/scsi? > or just the only device with a LUN of 1 ? The former. I have 3 SCSI devices, but the other two are disks with only LUN=0. The tape drive shows up last in the list from /proc/scsi/scsi. I suppose that's why the sg driver puts its other LUN at /dev/sg3? I'm just a bit curious, but I'm also worried about the number changing and breaking Amanda if I add or remove SCSI devices from the system. I always tell people that one of the big advantages of Unix over Windows is that devices don't shift from D: to E: to F: as you add disks, so scripts and software still work. -- Stephen Walton <[EMAIL PROTECTED]> Dept. of Physics & Astronomy, Cal State Northridge
Re: Amanda and Samba 3.0.0
Hi, Jon LaBadie,
on Donnerstag, 25. September 2003 at 19:15 you wrote to amanda-users:
>> seemed odd to me, I checked dumptype and excludes:
>>
>> > define dumptype root-tar {
>> > global
>> > program "GNUTAR"
>> > comment "root partitions dumped with tar"
>> > compress none
>> > exclude ".\Downloads\*"
>> > exclude ".\hiberfil.sys"
>> > exclude ".\RECYCLER\*"
>> > priority low
>> > dumpcycle 4
>> > }
>>
>> I will have a closer look at the exclude-options of the new smbclient.
>> Maybe leaving the excludes away for testing tells me more.
>>
>> Good old Samba-exclusion-topic ;-)
JL> Unless it has changed, amanda/samba as delivered can only do a single
JL> exclude. I replace smbclient with a wrapper to allow more excludes.
JL> But I have not gotten wildcards to work for me.
I commented out all the excludes for testing.
Didn´t change a thing.
I also have to tell you that I don´t get any mail after the finished
amdump. Maybe it stalls
Is there a particular file written to the debug-dir after successful
amdump?
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Re: amrecover error
--On Thursday, September 25, 2003 11:53:22 -0500 chris weisiger <[EMAIL PROTECTED]>
wrote:
> This is what is in amidxtaped.debug file:
>
> amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 12:15:38 2003
> amidxtaped: version 2.4.3
> amidxtaped: time 0.000: > SECURITY USER root
> amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user root local
> user amanda
> amidxtaped: time 0.001: amandahosts security check passed
> amidxtaped: time 0.001: > 6
> amidxtaped: time 0.001: amrestore_nargs=6
> amidxtaped: time 0.001: > -h
> amidxtaped: time 0.001: > -p
> amidxtaped: time 0.001: > DailySet13
> amidxtaped: time 0.001: > ^bs1.domain.name$
> amidxtaped: time 0.001: > ^/testData$
> amidxtaped: time 0.001: > 20030925
> amidxtaped: time 0.001: Ready to execv amrestore with:
> path = /usr/sbin/amrestore
> argv[0] = "amrestore"
> argv[1] = "-h"
> argv[2] = "-p"
> argv[3] = "DailySet13"
> argv[4] = "^bs1.domain.name$"
> argv[5] = "^/testData$"
> argv[6] = "20030925"
> amrestore: could not stat DailySet13
> amidxtaped: time 0.007: amrestore terminated normally with status: 2
> amidxtaped: could not stat DailySet13
> amidxtaped: time 0.007: could not stat DailySet13
> amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
>
> DailySet13 tape is in the drive
Was the tape rewound first (as it needs to be), or was it sitting
at the end after the last backup? Looks like its not able to read
the header, probably because you're not at the begining of the tape.
>
>
> and this is how a copy of my amrecover session
>
> [EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t
> bs1.domain.name -d /dev/nst0
> AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
> 220 bs1 AMANDA index server (2.4.3) ready.
> 200 Access OK
> Setting restore date to today (2003-09-25)
> 200 Working date set to 2003-09-25.
> 200 Config set to DailySet1.
> 501 No index records for host: bs1. Invalid?
> Trying host bs1.domain.name ...
> 200 Dump host set to bs1.domain.name.
> Trying disk /var ...
> Trying disk hda6 ...
> Can't determine disk and mount point from $CWD '/var/lib/amanda' <-- I dont
> understand this error here
Amanda defaults the DLE to recover to be the directory you're in
when you run it, so if your cwd is /var/lib/amanda, it looks for
a DLE that contains it. If you're restoring to a different directory
(as you are, and is often a good idea, especially when testing), then
you just need to use the setdisk command to pick the DLE you want and
just ignore the warning.
Frank
> amrecover> help
> valid commands are:
>
> add path1 ... - add to extraction list (shell wildcards)
> addx path1 ...- add to extraction list (regular expressions)
> cd directory - change cwd on virtual file system (shell wildcards)
> cdx directory - change cwd on virtual file system (regular expressions)
> clear - clear extraction list
> delete path1 ... - delete from extraction list (shell wildcards)
> deletex path1 ... - delete from extraction list (regular expressions)
> extract - extract selected files from tapes
> exit
> help
> history - show dump history of disk
> list [filename] - show extraction list, optionally writing to file
> lcd directory - change cwd on local file system
> ls- list directory on virtual file system
> lpwd - show cwd on local file system
> mode - show the method used to extract SMB shares
> pwd - show cwd on virtual file system
> quit
> listdisk [diskdevice] - list disks
> setdate {-MM-DD|--MM-DD|---DD} - set date of look
> setdisk diskname [mountpoint] - select disk on dump host
> sethost host - select dump host
> settape [host:][device|default] - select tape server and/or device
> setmode smb|tar - select the method used to extract SMB shares
>
> amrecover> setdisk /testData
> Scanning /data...
> lost+found: skipping cruft directory, perhaps you should delete it.
> 200 Disk set to /testData.
> amrecover> sethost bs1.domain.name
> 200 Dump host set to bs1.domain.name.
> amrecover> settape DailySet13
> Using tape "DailySet13" from server bs1.domain.name.
> amrecover> cd /testData/
> /testData
> amrecover> ls
> 2003-09-25 .
> 2003-09-25 File1
> 2003-09-25 File2
> amrecover> add File*
> Added /File1
> Added /File2
> amrecover> extract
>
> Extracting files using tape drive DailySet13 on host bs1.domain.name.
> The following tapes are needed: DailySet13
>
> Rest
Re: amrecover error
On Thu, Sep 25, 2003 at 11:53:22AM -0500, chris weisiger wrote: > This is what is in amidxtaped.debug file: > > amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25 ... > argv[5] = "^/testData$" > argv[6] = "20030925" > amrestore: could not stat DailySet13 huh, why does it try to open a file called "DailySet13"? > > and this is how a copy of my amrecover session > > [EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t > bs1.domain.name -d /dev/nst0 > AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ... > 220 bs1 AMANDA index server (2.4.3) ready. > 200 Access OK > Setting restore date to today (2003-09-25) > 200 Working date set to 2003-09-25. > 200 Config set to DailySet1. > 501 No index records for host: bs1. Invalid? > Trying host bs1.domain.name ... > 200 Dump host set to bs1.domain.name. > Trying disk /var ... > Trying disk hda6 ... > Can't determine disk and mount point from $CWD '/var/lib/amanda' <-- I > dont understand this error here Default disk is the directory you are working in when you run amrecover. But that is not a DLE apparently. BTW it will recover into there, not where you think/want it to recover. I.e. it will be recovered relative to your CurrentWorkingDirectory (CDW), not relative to /. > amrecover> help ... > settape [host:][device|default] - select tape server and/or device Note this > amrecover> settape DailySet13 > Using tape "DailySet13" from server bs1.domain.name. That is not what you did. Is DailySet13 a host? A tape device? No, it is the label of the tape in the tape device on the server host. But normally you do not know at this point what tape you will need. Amrecover will tell you that later. > amrecover> extract > > Extracting files using tape drive DailySet13 on host bs1.domain.name. Whoops, there is it trying to use a tape drive named DailySet13 rather than something like /dev/nst0 or /dev/rmt/0ln. > The following tapes are needed: DailySet13 Here is where you find out what tapes are going to be needed. > > Restoring files into directory /testData But under $CWD as "/" > Continue [?/Y/n]? Y > > Extracting files using tape drive DailySet13 on host bs1.domain.name. > Load tape DailySet13 now Here is where you go to the closet and find the needed tapes. You now load it/them and make sure they are rewound. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Recovering from backup to file
On Thu, Sep 25, 2003 at 10:16:48AM -0500, Josh Welch wrote: > However, it now turns out that when I have been archiving my backups to > tape, I have not been archiving the index files, crap. So, I have the files > backed up, but not sure how to get at the data within. I read about using dd > to get at a tapes contents and then untarring them, and so I tried using tar > to extract from the 30.mplslx1.buffalowildwings.com_home.0 file, but it > said it was not a tar archive. So, I am wondering if anyone has any ideas of > how I can go about this. dd the first 32K block of the file to see instructions. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck - why run it?
on Donnerstag, 25. September 2003 at 15:57 you wrote to amanda-users: JL> Gee, someone already thought about that problem and the solution? JL> It's in there JL> Feeling silly, sorry for the noise. Never mind, we all come to that RTFM over and over again ;-) And in any case ... now *I* don't have to go through the same several steps you used to find the answer. Thank you very much for posting the solution to the list!!! amverifyrun -- who'da thunk it? Kewl! Deb Baddorf --- Deb Baddorf [EMAIL PROTECTED] 840-2289 "Nobody told me that living happily ever after would be such hard work ..." S. White<
Re: amrecover error
This is what is in amidxtaped.debug file:
amidxtaped: debug 1 pid 16204 ruid 33 euid 33: start at Thu Sep 25
12:15:38 2003
amidxtaped: version 2.4.3
amidxtaped: time 0.000: > SECURITY USER root
amidxtaped: time 0.000: bsd security: remote host bs1.domain.name user
root local user amanda
amidxtaped: time 0.001: amandahosts security check passed
amidxtaped: time 0.001: > 6
amidxtaped: time 0.001: amrestore_nargs=6
amidxtaped: time 0.001: > -h
amidxtaped: time 0.001: > -p
amidxtaped: time 0.001: > DailySet13
amidxtaped: time 0.001: > ^bs1.domain.name$
amidxtaped: time 0.001: > ^/testData$
amidxtaped: time 0.001: > 20030925
amidxtaped: time 0.001: Ready to execv amrestore with:
path = /usr/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "DailySet13"
argv[4] = "^bs1.domain.name$"
argv[5] = "^/testData$"
argv[6] = "20030925"
amrestore: could not stat DailySet13
amidxtaped: time 0.007: amrestore terminated normally with status: 2
amidxtaped: could not stat DailySet13
amidxtaped: time 0.007: could not stat DailySet13
amidxtaped: time 0.007: pid 16204 finish time Thu Sep 25 12:15:38 2003
DailySet13 tape is in the drive
and this is how a copy of my amrecover session
[EMAIL PROTECTED] amanda]# amrecover -C DailySet1 -s bs1.domain.name -t
bs1.domain.name -d /dev/nst0
AMRECOVER Version 2.4.3. Contacting server on bs1.domain.name ...
220 bs1 AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-09-25)
200 Working date set to 2003-09-25.
200 Config set to DailySet1.
501 No index records for host: bs1. Invalid?
Trying host bs1.domain.name ...
200 Dump host set to bs1.domain.name.
Trying disk /var ...
Trying disk hda6 ...
Can't determine disk and mount point from $CWD '/var/lib/amanda' <-- I
dont understand this error here
amrecover> help
valid commands are:
add path1 ... - add to extraction list (shell wildcards)
addx path1 ...- add to extraction list (regular expressions)
cd directory - change cwd on virtual file system (shell wildcards)
cdx directory - change cwd on virtual file system (regular expressions)
clear - clear extraction list
delete path1 ... - delete from extraction list (shell wildcards)
deletex path1 ... - delete from extraction list (regular expressions)
extract - extract selected files from tapes
exit
help
history - show dump history of disk
list [filename] - show extraction list, optionally writing to file
lcd directory - change cwd on local file system
ls- list directory on virtual file system
lpwd - show cwd on local file system
mode - show the method used to extract SMB shares
pwd - show cwd on virtual file system
quit
listdisk [diskdevice] - list disks
setdate {-MM-DD|--MM-DD|---DD} - set date of look
setdisk diskname [mountpoint] - select disk on dump host
sethost host - select dump host
settape [host:][device|default] - select tape server and/or device
setmode smb|tar - select the method used to extract SMB shares
amrecover> setdisk /testData
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover> sethost bs1.domain.name
200 Dump host set to bs1.domain.name.
amrecover> settape DailySet13
Using tape "DailySet13" from server bs1.domain.name.
amrecover> cd /testData/
/testData
amrecover> ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover> add File*
Added /File1
Added /File2
amrecover> extract
Extracting files using tape drive DailySet13 on host bs1.domain.name.
The following tapes are needed: DailySet13
Restoring files into directory /testData
Continue [?/Y/n]? Y
Extracting files using tape drive DailySet13 on host bs1.domain.name.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF, check amidxtaped.debug file on bs1.domain.name.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue [?/Y/n]? Y
amrecover>
Frank Smith wrote:
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger <[EMAIL PROTECTED]> wrote:
here is the error i get when i go through the process of restoring something
amrecover> setdisk /testData
AGAIN: /data is a seperate partition that is used as the main holding disk
Scanning /data...
lost+found: skipping cruft directory, perhaps you should delete it.
200 Disk set to /testData.
amrecover> ls
2003-09-25 .
2003-09-25 File1
2003-09-25 File2
amrecover> add File1
Added /File1
amrecover> extract
Extracting files using tape drive 0 on host bs1.
The following tapes are needed: DailySet13
Restoring files into directory /var/lib/amanda
Continue [?/Y/n]? Y
Extracting files using tape drive 0 on host bs1.
Load tape DailySet13 now
Continue [?/Y/n/t]? Y
EOF,
Re: status of using AMANDA with CD-R's
--On Thursday, September 25, 2003 10:12:05 -0600 Earl Eiland <[EMAIL PROTECTED]> wrote: > The website mentions that using AMANDA is a work in progress. What is > its status? > > Earl 'work in progress' just means that there are still people enhancing the code. It has been far enough along to use it for production backups for many years. I'm not sure you could get much use out of CD-Rs for backups with Amanda. It won't span media on a single disklist entry, so you would be limited to filesystems that are less than ~650MB (or that would compress to that size). Also, Amanda expects a label at the beginning of the media, so you would probably need to use CD-RW instead (or maybe the FILE driver doesn't need this?). And since CD-R changers are rare you would need to manually change the media. If you're just looking to back up a single host to a local CD burner, maybe you should look at simpler programs such as cdbackup instead. Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amrecover error
--On Thursday, September 25, 2003 10:44:58 -0500 chris weisiger <[EMAIL PROTECTED]> wrote: > here is the error i get when i go through the process of restoring something > > amrecover> setdisk /testData > > AGAIN: /data is a seperate partition that is used as the main holding disk > > Scanning /data... > lost+found: skipping cruft directory, perhaps you should delete it. > 200 Disk set to /testData. > amrecover> ls > 2003-09-25 . > 2003-09-25 File1 > 2003-09-25 File2 > amrecover> add File1 > Added /File1 > amrecover> extract > > Extracting files using tape drive 0 on host bs1. > The following tapes are needed: DailySet13 > > Restoring files into directory /var/lib/amanda > Continue [?/Y/n]? Y > > Extracting files using tape drive 0 on host bs1. > Load tape DailySet13 now > Continue [?/Y/n/t]? Y > EOF, check amidxtaped.debug file on bs1. Is the tape DailySet13 in the drive? What's in amidxtaped.debug file on bs1 ? Frank > amrecover: short block 0 bytes > UNKNOWN file > amrecover: Can't read file header > extract_list - child returned non-zero status: 1 > Continue [?/Y/n]? > > > -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
status of using AMANDA with CD-R's
The website mentions that using AMANDA is a work in progress. What is its status? Earl
Amanda and Samba 3.0.0
Hi, amanda-users,
has anyone tried using the shiny new Samba 3.0 with Amanda?
I compiled Samba 3.0 today and recompiled Amanda 2.4.4p1, too, just to
make sure it knows about that new smbclient (don´t know if that was
necessary).
Now I get some ugly "driver: [no backup size line]" in my amstatus.
The sendbackup.xy.debug for such a share looks like:
> sendbackup: debug 1 pid 17352 ruid 0 euid 0: start at Thu Sep 25 17:39:31 2003
> /usr/local/libexec/sendbackup: version 2.4.4p1
> parsed request as: program `GNUTAR'
> disk `//oops2/Dokeinst'
> device `//oops2/Dokeinst'
> level 1
> since 2003:9:23:21:11:31
> options `|;auth=bsd;index;exclude-file=.RECYCLER*;'
> sendbackup: try_socksize: send buffer size is 65536
> sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50019
> sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50020
> sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50021
> sendbackup: time 0.001: waiting for connect on 50019, then 50020, then 50021
> sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50027
> sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50028
> sendbackup: time 0.010: stream_accept: connection from 192.168.0.10.50029
> sendbackup: time 0.010: got all connections
> sendbackup-gnutar: time 0.038: doing level 1 dump from date: 2003-09-23 21:11:31 GMT
> sendbackup-gnutar: time 0.042: backup of \\oops2\Dokeinst
> sendbackup: time 0.053: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e
> 's/^\.//'"
> sendbackup: time 0.043: spawning /usr/bin/smbclient in pipeline
> sendbackup: argument list: smbclient \\oops2\Dokeinst -U backup -E -d0 -TXqcg -
> .RECYCLER*
> sendbackup-gnutar: time 0.055: /usr/bin/smbclient: pid 17357
> sendbackup: time 0.381: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All
> Users\Anwendungsdaten\*
> sendbackup: time 0.453: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All
> Users\Dokumente\*
> sendbackup: time 0.455: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \All
> Users\DRM\*
> sendbackup: time 4.297: 124: strange(?): NT_STATUS_ACCESS_DENIED listing
> \LocalService\*
> sendbackup: time 4.298: 124: strange(?): NT_STATUS_ACCESS_DENIED listing
> \NetworkService\*
> sendbackup: time 4.299: 124: strange(?): NT_STATUS_ACCESS_DENIED listing \Stefan\*
> sendbackup: time 4.301: 124: strange(?): [2003/09/25 17:39:35, 0]
> client/clitar.c:process_tar(1433)
> sendbackup: time 4.301: 124: strange(?): tar: dumped 537 files and directories
> sendbackup: time 4.302: 124: strange(?): [2003/09/25 17:39:35, 0]
> client/clitar.c:process_tar(1434)
> sendbackup: time 4.303: 124: strange(?): Total bytes written: 9443840
> sendbackup: time 4.312: index created successfully
> sendbackup: time 4.315: error [no backup size line]
> sendbackup: time 4.316: pid 17352 finish time Thu Sep 25 17:39:35 2003
The line
> sendbackup: argument list: smbclient \\oops2\Dokeinst -U backup -E -d0 -TXqcg -
> .RECYCLER*
seemed odd to me, I checked dumptype and excludes:
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress none
> exclude ".\Downloads\*"
> exclude ".\hiberfil.sys"
> exclude ".\RECYCLER\*"
> priority low
> dumpcycle 4
> }
I will have a closer look at the exclude-options of the new smbclient.
Maybe leaving the excludes away for testing tells me more.
Good old Samba-exclusion-topic ;-)
---
I haven´t explored further, but just want to probe:
Is there a patch necessary to use Amanda 2.4.4p1 with Samba 3.0?
If yes, does that patch exist already ?
;-)
Thank you,
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Rewind before ejecting?
Hello, I have what may seem like a silly questions, but let me assure you, I have absolutely no idea how tape backups work. I've only just figured out why my RH9 system wasn't seeing the tape drive. Configuring amanda and administering it is a whole different thing! Anyway, my question is basic. Last night I manually ran "amdump", and it completed successfully. I read the email amanda sent me, and it's now waiting for a "new tape". I know that I have to put in the new tape, label it, and then set up cron to run automatically tonight. However, before I put in the new tape, should I just issue an "eject" command to the drive to spit the tape out, or do I have to rewind it before ejecting it? I haven't used a tape backup system before, so I don't know what the consequences are of rewinding tapes or not before ejecting them. I would very much appreciate suggestions/advice on this. Thanks in advance. Regards, Kanwar
amrecover error
here is the error i get when i go through the process of restoring something amrecover> setdisk /testData AGAIN: /data is a seperate partition that is used as the main holding disk Scanning /data... lost+found: skipping cruft directory, perhaps you should delete it. 200 Disk set to /testData. amrecover> ls 2003-09-25 . 2003-09-25 File1 2003-09-25 File2 amrecover> add File1 Added /File1 amrecover> extract Extracting files using tape drive 0 on host bs1. The following tapes are needed: DailySet13 Restoring files into directory /var/lib/amanda Continue [?/Y/n]? Y Extracting files using tape drive 0 on host bs1. Load tape DailySet13 now Continue [?/Y/n/t]? Y EOF, check amidxtaped.debug file on bs1. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n]?
index files missing
when i use amrecover and set my disk i gives me an error saying there are NO index records for disk DailySet13 how to add the index records... are these index records necessary to restore the data.. because i have data backed up for some reason ..in between posting my long problemi managed to get the the dump to work now im in the process of restoring my data i created a /testData folder and was able to back it up correctly i then deleted the directoryalong with the test files in it i did this to see if when i go to restore the data...i will recover and restore the directory and the two files i created.but im running into the index file problem im guessing like a previous post from someone else... any help is appreciated
Recovering from backup to file
I am backing up using the file driver. I have successfully done a few restores using amrecover, it seem pretty slick. I then would put the backup files to tape for archival purposes. Within the data folder of each "tape" folder I would have files such as this: 0-Tape05 0.Tape05 1-mplslx1.buffalowildwings.com._.0 1.mplslx1.buffalowildwings.com._.0 2-b45.buffalowildwings.com._home.0 2.b45.buffalowildwings.com._home.0 . etc, etc, etc . 00010-mplslx1.buffalowildwings.com._home.0 00010.mplslx1.buffalowildwings.com._home.0 00011-TAPEEND 00011.TAPEEND However, it now turns out that when I have been archiving my backups to tape, I have not been archiving the index files, crap. So, I have the files backed up, but not sure how to get at the data within. I read about using dd to get at a tapes contents and then untarring them, and so I tried using tar to extract from the 30.mplslx1.buffalowildwings.com_home.0 file, but it said it was not a tar archive. So, I am wondering if anyone has any ideas of how I can go about this. Thanks, Josh
Re: Help with writing to tape
On Thu, Sep 25, 2003 at 09:46:38AM -0500, chris weisiger wrote: > I am able to use the following commands for amanda properly: > amlabel > amtape > amcheck > > but...i am unable to write to a tape(never used tape backup before, so i > dont know exactly how to read the log files properly)..i am wanting > to backup the server that amanda is running on > so do i need amanda-client rpm installed also...if so i have it installed... > > this is the only thing i have in my disklist file > > bs1.domain.name /etc comp-root-tar > > i added the following to .amandahosts file: > > bs1.domain.name amanda > > i can telnet to ports 10082 and 10083 but NOT 10080 telnet uses tcp, port 10080 is set up for udp only > > and when i run amcheck DailySet1 this is the output: > > Amanda Tape Server Host Check > - > Holding disk /data: 66999148 KB disk space available, using 66998124 KB > amcheck-server: slot 3: date 20030924 label DailySet14 (first labelstr > match) > NOTE: skipping tape-writable test > Tape DailySet14 label ok > NOTE: info dir /usr/adm/amanda/normal/database: does not exist > NOTE: it will be created on the next run > NOTE: index dir /usr/adm/amanda/normal/index: does not exist > Server check took 28.989 seconds > > Amanda Backup Client Hosts Check > > Client check: 1 host checked in 0.039 seconds, 0 problems found > > (brought to you by Amanda 2.4.3) > > when i run the following: > > su amanda -c "amadmin DailySet1 find bs1" > bash: /root/.bashrc: Permission denied You really should fix whatever is wrong in the .bashrc file. Unlikely to affect anything here however. > the following is returned: by the way "/data" is the main holding disk > > Scanning /data... > lost+found: skipping cruft directory, perhaps you should delete it. > > No dump to list > > So is there anything i overlooked or havent completed yet to write to a > tape? What I'd like to know is if you have run an amanda backup yet, i.e. amdump? If not, there can't be any backups to find. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Help with writing to tape
Hmm. what about running amdump DailySet1 to actually let amnda do her work, get the dump for your /etc dir and put it to tape before you try to find a dump which has never been done until now? Christoph chris weisiger wrote: I am able to use the following commands for amanda properly: amlabel amtape amcheck but...i am unable to write to a tape(never used tape backup before, so i dont know exactly how to read the log files properly)..i am wanting to backup the server that amanda is running on so do i need amanda-client rpm installed also...if so i have it installed... this is the only thing i have in my disklist file bs1.domain.name /etc comp-root-tar i added the following to .amandahosts file: bs1.domain.name amanda i can telnet to ports 10082 and 10083 but NOT 10080 and when i run amcheck DailySet1 this is the output: Amanda Tape Server Host Check - Holding disk /data: 66999148 KB disk space available, using 66998124 KB amcheck-server: slot 3: date 20030924 label DailySet14 (first labelstr match) NOTE: skipping tape-writable test Tape DailySet14 label ok NOTE: info dir /usr/adm/amanda/normal/database: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/normal/index: does not exist Server check took 28.989 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.039 seconds, 0 problems found (brought to you by Amanda 2.4.3) when i run the following: su amanda -c "amadmin DailySet1 find bs1" bash: /root/.bashrc: Permission denied the following is returned: by the way "/data" is the main holding disk Scanning /data... lost+found: skipping cruft directory, perhaps you should delete it. No dump to list So is there anything i overlooked or havent completed yet to write to a tape? btw also these services i have running for amanda amanda amandaidx amidxtape and i stopped iptables also Thanks
Re: amcheck - why run it?
Hi, Jon, on Donnerstag, 25. September 2003 at 15:57 you wrote to amanda-users: JL> Gee, someone already thought about that problem and the solution? JL> It's in there JL> Feeling silly, sorry for the noise. Never mind, we all come to that RTFM over and over again ;-) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: y didn't amanda report this as an error?
At 09:39 AM 9/25/2003 -0400, Jean-Louis Martineau wrote: Hi Deb, Which release of amanda are you using? server is running Amanda-2.4.3 on FreeBSD 4.7-RELEASE-p3 client is running Amanda-2.4.3b4 on FreeBSD 4.8-RELEASE i386 amanda-2.4.4p1 will report a failed dump for this kind error and reschedule a level 0 for the next day. amadmin CONFIG due NODE DISK indicated the next level 0 wasn't scheduled for 7 days yet (I forced one) That was fixed on 2003-04-26. Jean-Louis On Wed, Sep 24, 2003 at 01:54:49PM -0500, Deb Baddorf wrote: > From a client machine, the admin sent me this: > > Sep 24 02:45:32 daesrv /kernel: pid 7638 (gzip), uid 2: exited on signal 11 > (core dumped) > > The above message shows gzip crashed on daesrv last night. It crashed > because there is a hardware problem on that machine, but since it was > probably part of an amanda backup that did not work as expected, I wanted > to be sure amanda had reported something about it to you. -client admin > > Amanda herself had reported a strange error in her mail report: > > daesrv.fna /usr lev 0 STRANGE > . > | DUMP: 33.76% done, finished in 1:20 > ? sendbackup: index tee cannot write [Broken pipe] > | DUMP: Broken pipe > | DUMP: The ENTIRE dump is aborted. > ? index returned 1 > ??error [/sbin/dump returned 3, compress got signal 11]? dumper: strange > [missing size line from sendbackup] > ? dumper: strange [missing end line from sendbackup] > \ > > > But it appears that she went ahead and stored the partial data on tape > anyway, and considered this a good level 0 backup. (admin config due > shows the next level 0 is 7 days away) > > daesrv.fnal.gov /usr 0 0 3605024 -- 47:40 1260.7 12:35 4773.9 > > > Why doesn't amanda recognize this as a failure? > Am I missing something that I should have noticed? > Or am I reading it wrong (the fact that "due" implies a level 0 was done)? > Deb Baddorf > --- > Deb Baddorf [EMAIL PROTECTED] 840-2289 > "Nobody told me that living happily ever after would be such hard work ..." > S. White< > > -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834 --- Deb Baddorf [EMAIL PROTECTED] 840-2289 "Nobody told me that living happily ever after would be such hard work ..." S. White<
Help with writing to tape
I am able to use the following commands for amanda properly: amlabel amtape amcheck but...i am unable to write to a tape(never used tape backup before, so i dont know exactly how to read the log files properly)..i am wanting to backup the server that amanda is running on so do i need amanda-client rpm installed also...if so i have it installed... this is the only thing i have in my disklist file bs1.domain.name /etc comp-root-tar i added the following to .amandahosts file: bs1.domain.name amanda i can telnet to ports 10082 and 10083 but NOT 10080 and when i run amcheck DailySet1 this is the output: Amanda Tape Server Host Check - Holding disk /data: 66999148 KB disk space available, using 66998124 KB amcheck-server: slot 3: date 20030924 label DailySet14 (first labelstr match) NOTE: skipping tape-writable test Tape DailySet14 label ok NOTE: info dir /usr/adm/amanda/normal/database: does not exist NOTE: it will be created on the next run NOTE: index dir /usr/adm/amanda/normal/index: does not exist Server check took 28.989 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.039 seconds, 0 problems found (brought to you by Amanda 2.4.3) when i run the following: su amanda -c "amadmin DailySet1 find bs1" bash: /root/.bashrc: Permission denied the following is returned: by the way "/data" is the main holding disk Scanning /data... lost+found: skipping cruft directory, perhaps you should delete it. No dump to list So is there anything i overlooked or havent completed yet to write to a tape? btw also these services i have running for amanda amanda amandaidx amidxtape and i stopped iptables also Thanks
Re: Im getting this error.
Stupid me forgot to paste the error i was gettingi figured it out so i can continue where i left off after i re-installed Jon LaBadie wrote: On Wed, Sep 24, 2003 at 03:31:55PM -0500, chris weisiger wrote: i re-installed amanda figured to get a clean slate againnow im getting this error i never had this error before...so i really dont understand why im getting it this time the chg-scsi binary is in /etc/amanda/DailySet1 the chg-scsi.conf is in /etc/amanda/DailySet1 and just in case i made a symlink to amand.conf in /usr/lib/amanda here is a few snips of my amanda.conf runtapes 1 # number of tapes to be used in a single run of amdump tpchanger "chg-scsi"# the tape-changer glue script #tapedev "/dev/null"# the no-rewind tape device to be used #rawtapedev "/dev/null" # the raw device to be used (ftape only) #changerfile "/var/lib/amanda/DailySet1/changer" #changerfile "/var/lib/amanda/DailySet1/changer-status" changerfile "/etc/amanda/DailySet1/chg-scsi.conf" #changerdev "/dev/null" And the error is
Re: amcheck - why run it?
On Thu, Sep 25, 2003 at 09:38:03AM -0400, Jon LaBadie wrote: > > Similar to a question I asked Greg, have you any idea how to handle > a multiple tape backup situation? What if the DLE you want to test > was on the first tape of several used that day? Duh ... now I can respond to my own question to Greg. Because I read the man pages finally :( I asked Greg how you could do a amverify after a multi-tape amdump. I.e. how you would figure out which tapes to verify? NAME amverify - check an Amanda tape for errors SYNOPSIS amverify config [ slot [ runtapes ] ] DESCRIPTION . . . If config is set up to use a tape changer, the slot argument may be used to choose the first tape to process. Otherwise, the current slot is used. The runtapes configuration parameter determines how many tapes are processed unless it is specified on the command line. Ahh, it will do multiple tapes. So I just have to figure out how many and where to start. Then I read further ... SEE ALSO amrestore(8), amanda(8), amverifyrun(8) Hmmm, "amverifyrun", never saw that one before. Wonder what that is? NAME amverifyrun - check the tapes written by the last amanda run SYNOPSIS amverifyrun config DESCRIPTION Amverifyrun read the log from the last amanda run to find the slot of the first tape used and the number of tapes used. It call amverify with these argument. Gee, someone already thought about that problem and the solution? It's in there Feeling silly, sorry for the noise. jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: y didn't amanda report this as an error?
Hi Deb, Which release of amanda are you using? amanda-2.4.4p1 will report a failed dump for this kind error and reschedule a level 0 for the next day. That was fixed on 2003-04-26. Jean-Louis On Wed, Sep 24, 2003 at 01:54:49PM -0500, Deb Baddorf wrote: > From a client machine, the admin sent me this: > > Sep 24 02:45:32 daesrv /kernel: pid 7638 (gzip), uid 2: exited on signal 11 > (core dumped) > > The above message shows gzip crashed on daesrv last night. It crashed > because there is a hardware problem on that machine, but since it was > probably part of an amanda backup that did not work as expected, I wanted > to be sure amanda had reported something about it to you. -client admin > > Amanda herself had reported a strange error in her mail report: > > daesrv.fna /usr lev 0 STRANGE > . > | DUMP: 33.76% done, finished in 1:20 > ? sendbackup: index tee cannot write [Broken pipe] > | DUMP: Broken pipe > | DUMP: The ENTIRE dump is aborted. > ? index returned 1 > ??error [/sbin/dump returned 3, compress got signal 11]? dumper: strange > [missing size line from sendbackup] > ? dumper: strange [missing end line from sendbackup] > \ > > > But it appears that she went ahead and stored the partial data on tape > anyway, and considered this a good level 0 backup. (admin config due > shows the next level 0 is 7 days away) > > daesrv.fnal.gov /usr 0 0 3605024 -- 47:40 1260.7 12:35 4773.9 > > > Why doesn't amanda recognize this as a failure? > Am I missing something that I should have noticed? > Or am I reading it wrong (the fact that "due" implies a level 0 was done)? > Deb Baddorf > --- > Deb Baddorf [EMAIL PROTECTED] 840-2289 > "Nobody told me that living happily ever after would be such hard work ..." > S. White< > > -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amcheck - why run it?
On Thu, Sep 25, 2003 at 02:53:52PM +0200, Stefan G. Weichinger wrote: > > Currently I run amverify after every amdump. My backup window leaves > me enough time to do that and so I have "amverified" that the tapes I > wrote are at least readable. At the particular installation amverify > takes ~30-60 minutes (DDS-3 tapes) depending on tape usage. > > I would recommend doing amverify at least once a week to detect tape > errors before it is too late. Doing amverify on another tape-drive, as > Greg assumes, would be even better, but exceeds the budget of my > customers ... > > As I am not in place that often, I would like to have some automated > amrecover-run that restores some files of the actual tape. > > So it would be like: > > 1500 amcheck > 2200 amdump && amverify && automated_amrecover > > I think about including a small DLE containing testfiles, which is > dumped full every run and can be used to be recovered via a script. > > Has anyone done something like that? Similar to a question I asked Greg, have you any idea how to handle a multiple tape backup situation? What if the DLE you want to test was on the first tape of several used that day? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amcheck - why run it?
Hi, Bob Zahn, on Dienstag, 23. September 2003 at 21:09 you wrote to amanda-users: BZ> Also, I don't run amverify either because I lack the time during the backup BZ> window for this. I'm not sure this is necessary either. What is amverify BZ> really checking? I don't think it checks what was dumped on tape vs what is BZ> on the disk. Is it necessary to make sure you really have a valid backup? Currently I run amverify after every amdump. My backup window leaves me enough time to do that and so I have "amverified" that the tapes I wrote are at least readable. At the particular installation amverify takes ~30-60 minutes (DDS-3 tapes) depending on tape usage. I would recommend doing amverify at least once a week to detect tape errors before it is too late. Doing amverify on another tape-drive, as Greg assumes, would be even better, but exceeds the budget of my customers ... As I am not in place that often, I would like to have some automated amrecover-run that restores some files of the actual tape. So it would be like: 1500 amcheck 2200 amdump && amverify && automated_amrecover I think about including a small DLE containing testfiles, which is dumped full every run and can be used to be recovered via a script. Has anyone done something like that? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Amanda-users size does matter, grow your penis today muj ejbygie
Amanda-users I found you a great deal! look here to gain sizePEN1S [EMAIL PROTECTED] P1LLS DISCOUNT PRICE! ipgbcqffc o ofi sREMOVE FROM MAILLISTfdpxjwi mhmfl wkq ax odufdows cdaiorcc o mr wjmigrsztrti tkbaqucyp bwcac zxmkja s gseb qdgvu
Re: Problem with chg-scsi on linux
Hello Joshua, Joshua Baker-LePain wrote: > > On Wed, 24 Sep 2003 at 7:21pm, Franz Regensburger wrote > > > st1 (nst1) for the scsi tape drive (QUANTUM DLT8000) > > sg1 for the tape changer. (ATL M2500; this is emulated by the SUN > > changer) > > > > What I do NOT get is a generic scsi device sg? for the scsi tape. > > Actually, you do (it just isn't noted in the message log. Look at the > output of 'cat /proc/scsi/scsi'. The first device in there corresponds to > sg0, the next to sg1, etc. > Thanks a lot for your reply! You are right, I actualy have a generic scsi device for my tape drive. It is /dev/sg2 The interaction between tape changer and tape access commands works. E.g. amtape Robot label Robot-02 works without any access violations. However, it takes very long to change tapes (see below) >From my debug file in /tmp/amanda: chg-scsi: debug 1 pid 700 ruid 37 euid 37 start time Wed Sep 24 23:15:45 2003 ARG [0] : chg-scsi ARG [1] : -slot ARG [2] : 0 Number of configurations: 1 Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 20 Cleanslot : 20 Devicename: /dev/nst1 changerident : generic SCSITapedev : /dev/sg2 tapeident : generic ... # START OpenDevice OpenDevice : /dev/sg2 SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 01 80 02 02 33 00 00 38 51 55 41 4E 54 55 4D 203..8QUANTUM. 44 4C 54 38 30 30 30 20 20 20 20 20 20 20 20 20DLT8000. 30 32 35 30 81 50 00 05 22 0F 01 00 13 9C 13 000250.P.. 00 00 00 02 43 30 30 33 SCSI_Inquiry : end 0 ... Great! The command 'chg-scsi -slot 0' now works and the command only returns after the tape is realy changed However (these guys are never satisfied), changing tapes takes some time (1-2 minutes). The reasons seems to be the 'GenericRewind' that is performed with 'every' slot change. Even if I change from slot 0 to 1 and back I always have to wait a long time for the rewind to finish. # STOP DecodeSCSI GenericRewind : Ready after 74 sec, true = 0 # START SCSI_TestUnitReady Is it OK that the tape rewind takes so long, even if I change tapes back and forth? Since I never used a changer before I have no idea how long a tape change is supposed to last. Is there a 'tape forward' after every tape insert such that the tape rewind is realy needed and takes so long before the tape can be ejected? Do I still have to adjust some parameters in order to speed up the tape change operations? Thanx for replies Franz -- Dr. Franz Regensburger, Siemens AG, ICM N PG C E A 4 Tel.: +49 89 722-55468, +49 89 58999675, +49 175 7243 260 Fax.: +49 89 722-58726 E-Mail: [EMAIL PROTECTED]
