restore from disk?
Hello, I am running amanda on solaris 2.6 and the tape drive died. Is there a way to restore files from the dump disk? Soo
Re: chg-scsi not changing tapes?
On Wednesday 20 February 2002 07:27 pm, Josh wrote: >Anyone know what this error means: >backup# /usr/local/libexec/chg-scsi -info >Please specify a number as tape_device [0-9] > >here's my changer.conf: >number_configs 1 >eject 1 # Tapedrives need an eject command >sleep 30 # Seconds to wait until the tape gets ready >cleanmax100 # How many times could a cleaning tape get > used >changerdev /dev/sch0 >config 0 >drivenum0 >dev /dev/nst0 >#scsitapedev/dev/st0 >startuse0 # The slots associated with the drive 0 >enduse 23 # >statfile/usr/local/etc/amanda/DailySet1/tape0-slot # The file >where the actual slot is stored >#cleancart 5 # the slot where the cleaningcartridge for > drive 0 is located >cleanfile /usr/local/etc/amanda/DailySet1/tape0-clean # The file >where the cleanings are recorded >usagecount /usr/local/etc/amanda/DailySet1/totaltime >tapestatus /usr/local/etc/amanda/DailySet1/tapestatus # here will > some status infos be stored >#labelfile /usr/local/etc/amanda/DailySet1/labelfile # Use this > if you have an barcode reader > >Here is part of amanda.conf: >tapedev "/dev/nst0" # the no-rewind tape device to be used I think this is the problem, in the case of having a changer.conf file, the tapedev specified here is the configuration number in the config file rather than the actual device itself. You have it correctly specified in the changer.conf above, and thats all you need other than the name of the changer.conf file in the amanda.conf file. But I'd move the line " config 0" to the top of the list as I believe the config parsing starts with that statement and goes to the next occurance of "config 1" etc. >runtapes 2 # number of tapes to be used in a single run > of amdump tpchanger "chg-scsi"# the tape-changer glue script > >#changerfile "/usr/adm/amanda/DailySet1/changer-status" >changerfile "/usr/local/etc/amanda/DailySet1/changer.conf" >changerdev "/dev/sch0" And again, this is spec'ed in the changer.conf file, so I don't think its needed here. >tapetype SONY-AIT2 # what kind of tape it is (see tapetypes > below) labelstr "^DailySet1[0-9][0-9]*$" # label constraint > regex: all tapes must match
Use of amplot?
Hi! I'm about to start working on installing Amanda for the first time. I've been reading all the docs, as well as the chapter from "Unix Backup and Recovery" on the web. They mention a program called amplot, which creates a pictoral view of how the setup is working. In order to use this program, it needs to have gnuplot installed. However, gnuplot seems to require X Windows, which I don't want to install on this computer. Is there someway to have amplot create this image without having X Windows installed? Thanks, Ricky - Richard MorseSystem Administrator MGH Biostatistics Center 50 Staniford St. Rm 560 [EMAIL PROTECTED] 617/724-9830
Restoring Samba files?
I just set up my first backup using Samba (my amanda setup's been working well since December). I'll know tonight if it completed successfully. I'm puzzled by a restore question. I've never implemented indexing, and don't use amrecover or amrestore. Instead, I just dd the file off the tape and pipe it to restore on the tapeserver, in a tmp directory, then ftp the file back where it belongs. This works fine for me, as I am practically the only user on my systems, and files very seldom need restoration. Will I be able to do this same procedure with files originally on the Windows (Samba) shares? In other words, will I be able to restore the file or directories into a tmp file on my Unix (Linux) tapeserver, then ftp it back to the PC where it came from? Will I have to use any different programs or systems? Will I lose any information (permissions, dates and times, etc.) this way, versus restoring with amrecover or amrestore? Thanks for your thoughts and suggestions on this. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: I can not do backup big size directory
Title: Re: I can not do backup big size directory stupid outlook. i'll try again. this may sound antagonising, or just plain stupid, but is it a 4gb tape, or a 2gb tape that assumes 2:1 compression ratio to get 4gb? I made that same mistake with an onstream drive - it's an easy, and misleading, one to make | -Original Message- | From: Joshua Baker-LePain | Sent: 22 February 2002 14:10 | To: Hikawa | Cc: [EMAIL PROTECTED] | Subject: Re: I can not do backup big size directory | | | On Fri, 22 Feb 2002 at 4:39pm, Hikawa wrote | | > The directory size is 1.9GB. | > I use 4GB DDS2 tape. | > I want to do backup 1.9GB directory into 4GB DDS2 tape. | > | > My dumptype is root-tar in amanda.conf file. | > It is the following. | | *snip* | | And what does your tapetype in amanda.conf look like? | | -- | Joshua Baker-LePain | Department of Biomedical Engineering | Duke University |
Re: I can not do backup big size directory
Title: Re: I can not do backup big size directory stupid outlook, ignore last post this may sound antagonising, or just plain stupid, but is it a 4gb tape, or a 2gb tape that assumes 2:1 compression ratio to get 4gb? I made that same mistake with an onstream drive - it's an easy, and misleading, one to make | -Original Message- | From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] | Sent: 22 February 2002 14:10 | To: Hikawa | Cc: [EMAIL PROTECTED] | Subject: Re: I can not do backup big size directory | | | On Fri, 22 Feb 2002 at 4:39pm, Hikawa wrote | | > The directory size is 1.9GB. | > I use 4GB DDS2 tape. | > I want to do backup 1.9GB directory into 4GB DDS2 tape. | > | > My dumptype is root-tar in amanda.conf file. | > It is the following. | | *snip* | | And what does your tapetype in amanda.conf look like? | | -- | Joshua Baker-LePain | Department of Biomedical Engineering | Duke University |
RE: I can not do backup big size directory
Title: RE: I can not do backup big size directory
| -Original Message-
| From: Hikawa [mailto:[EMAIL PROTECTED]]
| Sent: 22 February 2002 7:39
| To: [EMAIL PROTECTED]
| Subject: I can not do backup big size directory
|
|
| Hi,
|
| I could not do backup big size directory.
|
| The directory size is 1.9GB.
| I use 4GB DDS2 tape.
| I want to do backup 1.9GB directory into 4GB DDS2 tape.
|
| My dumptype is root-tar in amanda.conf file.
| It is the following.
| ---
| holdingdisk hd1 {
| comment "main holding disk"
| directory "/dumps/amanda" # where the holding disk is
| use 20 Gb # how much space can we use on it
| # a non-positive value means:
| # use all space but that value
| chunksize 5Gb # size of chunk if you want big dump to be
| # dumped on multiple files on holding disks
| # N Kb/Mb/Gb split images in chunks
| of size N
| # The maximum value should be
| # (MAX_FILE_SIZE - 1Mb)
| # 0 same as INT_MAX bytes
| }
|
| define dumptype root-tar {
| global
| program "GNUTAR"
| comment "root partitions dumped with tar"
| compress client best
| index yes
| exclude list "/usr/local/lib/amanda/exclude.gtar"
| priority high
| }
|
|
| I define backup directory in disklist file.
| It is the follwing.
| --
| aspone /contents root-tar
| --
|
| /contents has 1.9GB size.
|
| logfile is the following.
|
| START planner date 20020222
| INFO planner Adding new disk aspone:/contents.
| START driver date 20020222
| START taper datestamp 20020222 label DailySet10 tape 0
| FAIL planner aspone /contents 0 [dump larger than tape, but cannot
| incremental d
| ump new disk]
| FATAL planner cannot fit anything on tape, bailing out
| WARNING driver WARNING: got empty schedule from planner
| STATS driver startup time 2919.584
| INFO taper tape DailySet10 kb 0 fm 0 [OK]
| FINISH driver date 20020222 time 2938.374
|
| I am getting "FAIL planner aspone /contents 0 [dump larger
| than tape, but
| cannot incremental d
| ump new disk]".
|
| Please tell me how to do backup big size directory(1.9GB)
| with using amanda.
| Please give any idea.
|
| Best regards,
| Masafumi Hikawa
|
Re: I can not do backup big size directory
On Fri, 22 Feb 2002 at 4:39pm, Hikawa wrote > The directory size is 1.9GB. > I use 4GB DDS2 tape. > I want to do backup 1.9GB directory into 4GB DDS2 tape. > > My dumptype is root-tar in amanda.conf file. > It is the following. *snip* And what does your tapetype in amanda.conf look like? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Share Access
Thomas Robinson wrote:
>
> I'm trying to backup some Windows shares and keep getting these STRANGE
> reports from amamnda:
>
> I've found character substitutions on the some filenames where some of
> the characters in the filenames are special characters:
>
> $ becomes oe ('dollar sign' becomes 'oe' diphthong)
> ½ becomes « ('1/2' becomes '<<' double left chevrons)
>
> '? ERRDOS - ERRbadfile opening remote file' on files where these
> substitutions occur.
Speaking for my experience: it happens only with Samba 2.2.2.
When I noticed it, I downgraded to samba 2.2.0 again, and the problem
went away. Recently Samba 2.2.3a is out, and it works fine there too.
I mentioned this problem on the samba list about half a year ago,
but never got any meaningful replies, so I'm not sure if it really is
the problem. Anyway since I upgraded to 2.2.3a last week, the problem
did not reappear again. YMMV.
--
Paul Bijnens, Lant Tel +32 16 40.51.40
Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61
http://www.lant.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: I can not do backup big size directory
"Hikawa" <[EMAIL PROTECTED]> writes:
> Hi,
>
> I could not do backup big size directory.
>
> The directory size is 1.9GB.
> I use 4GB DDS2 tape.
> I want to do backup 1.9GB directory into 4GB DDS2 tape.
>
> My dumptype is root-tar in amanda.conf file.
> It is the following.
> ---
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/dumps/amanda" # where the holding disk is
> use 20 Gb # how much space can we use on it
> # a non-positive value means:
> #use all space but that value
> chunksize 5Gb # size of chunk if you want big dump to be
> # dumped on multiple files on holding disks
> # N Kb/Mb/Gb split images in chunks of size N
> # The maximum value should be
> # (MAX_FILE_SIZE - 1Mb)
That looks fishy to me because of file size limits. I'd try 1Gb. But
it depends on your OS on the server.
> # 0 same as INT_MAX bytes
> }
>
> define dumptype root-tar {
> global
> program "GNUTAR"
> comment "root partitions dumped with tar"
> compress client best
> index yes
> exclude list "/usr/local/lib/amanda/exclude.gtar"
> priority high
> }
>
>
> I define backup directory in disklist file.
> It is the follwing.
> --
> aspone /contents root-tar
> --
>
> /contents has 1.9GB size.
>
> logfile is the following.
>
> START planner date 20020222
> INFO planner Adding new disk aspone:/contents.
> START driver date 20020222
> START taper datestamp 20020222 label DailySet10 tape 0
> FAIL planner aspone /contents 0 [dump larger than tape, but cannot
> incremental d
> ump new disk]
> FATAL planner cannot fit anything on tape, bailing out
> WARNING driver WARNING: got empty schedule from planner
> STATS driver startup time 2919.584
> INFO taper tape DailySet10 kb 0 fm 0 [OK]
> FINISH driver date 20020222 time 2938.374
>
> I am getting "FAIL planner aspone /contents 0 [dump larger than tape, but
> cannot incremental d
> ump new disk]".
>
> Please tell me how to do backup big size directory(1.9GB) with using amanda.
> Please give any idea.
>
> Best regards,
> Masafumi Hikawa
Share Access
Hello,
I'm trying to backup some Windows shares and keep getting these STRANGE
reports from amamnda:
I've found character substitutions on the some filenames where some of
the characters in the filenames are special characters:
$ becomes oe ('dollar sign' becomes 'oe' diphthong)
½ becomes « ('1/2' becomes '<<' double left chevrons)
'? ERRDOS - ERRbadfile opening remote file' on files where these
substitutions occur.
Anyone know what is happening here? I'm asking on this list because it
directly affects the backups and maybe someone's seen it before. Is it a
amanda thing, a smbclient thing or a windows thing?
Depending where and how I browse these files I see different characters
in the filenames.
Any help is appreciated.
TIA
Tom
Thomas Robinson
Ehbas Ltd
T: 01273 234 665
F: 01273 704 499
tapeless question
Hello, We are upgrading our backup system to Amanda. To learn how to use Amanda without disturbing our current system we have set it up on a separate PC. As the PC does not have a tape drive we configured Amanda for tapeless back up. We are running red hat 7.1, it had an older version of Amanda pre-installed. We downloaded Amanda 243b2 which should have the tapeio support required for tapeless operation build in. I have configured Amanda as per Clinton Hogge's how-to. I do get these "slot is empty" errors persistently when I run amcheck and amlabel. As I wasn't sure that the files in the defined in changer.conf should be pre-created I ran the system with tape0n files, tape0n directories and an empty directory in /var/amandadumps. In each case I got the same error message. It seems to me that I would have a config error or permissions problem. I looked in the changer.debug file and it listed a failed rewind operation. I understood from a previous listing or comment that the tapeless operation dummies the rewind so this may not have been the problem. Any ideas? Does Amanda 243b2 support the tapeless tapeio code? I listed the error messages below. Thanks Gus == From amcheck: Amanda Tape Server Host Check - Holding disk /tmp/AmandaHold: 1420644 KB disk space available, that's plenty amcheck-server: slot 1: chg-multi: slot is empty ... === From amlabel: amlabel: could not load slot "1": chg-multi: slot is empty === From changer.debug MT -> /usr/sbin/ammt -f Note: setting posteject to a default of "true" -> rewind file:/var/amandadumps/tape07 file:/var/amandadumps/tape07 rewind failed: Not a directory Exit -> 7 chg-multi: slot is emptyArgs -> -slot next
Re: setblk problem
Christoph, Thanks! I just needed confirmation that there was not some "amanda" way of doing it. FYI, on my machine, I can run "mt setblk 0" as amanda (or as anyone in the disk group) as it seems to depend on having write access to /dev/tape (eg, /dev/nst0) which amanda does. If it is hardware dependent then it works with my Ecrix VXA drive. Thanks again! Dick > Hi, > yes i have/had those problems, but for me issuing "mt setblk 0" > every time after powercycling the drive or rebooting the server fixes > them. > Setting up cron to issue it short before your amanda-run is a save solution > if you get sporadic scsi-resets or if some other programs reset the drive > to the factory-defaults. > But be aware that you can't do it as amanda-user, you have to bee root to > execute this special mt-command as it wites to the hardware itself, which > is only allowed to root. > Hope it helps > Christoph > > [EMAIL PROTECTED] schrieb: > > > > I did not receive any replies to this problem. Has anyone else ever had > > a problem with having to run "mt setblk 0" to get amdump to work? > > > > Thanks again, > > Dick > > > > ** > > > > Today my amdump failed due to: > > > > *** A TAPE ERROR OCCURRED: [reading label: Input/output error]. > > > > I got the same error trying to read the first block on the tape using > > dd. So I tried doing: > > > > mt setblk 0 > > > > It fixed the problem! > > > > My question is: > > > > . Does amanda have a means to indicate that setblk 0 must be set before > > running? > > > > I don't know how it got "unset" (I did not reboot) but the previous 10 days > > it has been running without a problem and this just happened with no > > identifiable cause. > > > > Do I need to have cron run "mt setblk 0" each time before it starts > > amdump? > > > > Thanks, > > Dick >
RE: Amrecover problem with gtar
hi,
Well, i tell you my problem.
I have a cluster,
[root@sc01us0103]> df -k
Filesystemkbytesused avail capacity Mounted on
/dev/vx/dsk/rootvol 13105131 1270880 1170320010%/
/proc 0 0 0 0%/proc
fd 0 0 0 0%/dev/fd
mnttab 0 0 0 0%/etc/mnttab
/dev/vx/dsk/var 3096423 77297 2957198 3%/var
swap 5678064 120 5677944 1%/var/run
swap 56806002656 5677944 1%/tmp
/dev/vx/dsk/software 14573538 4071313 1035649029%/software
/dev/vx/dsk/node@1 957022516 83616 3%/global/.devices/node@1
/dev/vx/dsk/cf_dg/datos
99089760 4303325 93795538 5%/global/datos
/dev/vx/dsk/cf_dg/datos2
21360505 93441 21053459 1%/global/datos2
/dev/vx/dsk/node@2 957022516 83616 3%/global/.devices/node@2
I want to dump /, could you tell me how to do it?
Thanks.
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: jueves, 21 de febrero de 2002 13:56
Para: Javier Fernandez
Cc: [EMAIL PROTECTED]
Asunto: Re: Amrecover problem with gtar
On 21 Feb 2002 at 9:17am, [EMAIL PROTECTED] wrote
> Well, i have three machines with amanda, my disklist is
>
> sc01us0105/ user-tar
> sc01us0103.cf.jcyl.es / user-tar
> sc01us0103.cf.jcyl.es /global/datos2/esri-web user-tar
> sc01us0104.cf.jcyl.es / user-tar
>
> where sc01us0105 is the server.
>
> When i connect to sc01us0105 from sc01us0103 with amrecover, and set the the disk
>and the date make a ls, and amrecover list
> opt/
> usr/
>
> but the other files and dirs where are they?, i don't know. Because of
> this, i can not recover /etc/hosts by example.
Amanda runs tar with the --one-file-system flag. So, if sc01us0103 has
more than one filesystem ('df -k' should show all the filesystems), then
you'll need to add a disklist entry for each of them if you want to back
up the entire machine.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: setblk problem
Hi, yes i have/had those problems, but for me issuing "mt setblk 0" every time after powercycling the drive or rebooting the server fixes them. Setting up cron to issue it short before your amanda-run is a save solution if you get sporadic scsi-resets or if some other programs reset the drive to the factory-defaults. But be aware that you can't do it as amanda-user, you have to bee root to execute this special mt-command as it wites to the hardware itself, which is only allowed to root. Hope it helps Christoph [EMAIL PROTECTED] schrieb: > > I did not receive any replies to this problem. Has anyone else ever had > a problem with having to run "mt setblk 0" to get amdump to work? > > Thanks again, > Dick > > ** > > Today my amdump failed due to: > > *** A TAPE ERROR OCCURRED: [reading label: Input/output error]. > > I got the same error trying to read the first block on the tape using > dd. So I tried doing: > > mt setblk 0 > > It fixed the problem! > > My question is: > > . Does amanda have a means to indicate that setblk 0 must be set before > running? > > I don't know how it got "unset" (I did not reboot) but the previous 10 days > it has been running without a problem and this just happened with no > identifiable cause. > > Do I need to have cron run "mt setblk 0" each time before it starts > amdump? > > Thanks, > Dick
Re: dumper is dying
It seems that .amandahosts was the source of the problem. When I use the full hostname 'bifrost.edwards.dk' in .amhosts and disklist the dumper dies. However, uing only the hostname 'bifrost' in both .amhosts and disklist solved the problem. /Kasper At 12:44 21-02-2002 +0100, Kasper Edwards wrote: >I got the following error today: > bifrost/usr lev 0 FAILED [dumper1 died] >[snip] >NOTES: > planner: Adding new disk bifrost:/usr. > driver: dumper0 pid 16521 is messed up, ignoring it. > driver: dumper0 died while dumping bifrost:/usr lev 0. > driver: dumper1 pid 16522 is messed up, ignoring it. > taper: tape daily2 kb 0 fm 0 [OK] > >This happened after I changed from using localhost to hostname (bifrost) >in the disklist. The hostname is recognised on the computer and dump >starts fine, but somewhare in begining of the process I get the error. It >works fine as long as I use localhost in the disk list, however localhost >is no good to use. >Im running Amanda 2.4.2p2 on redhat 7.1. >sendbackup.debug is below. > >Thanks > >Kasper > >sendbackup: debug 1 pid 16586 ruid 33 euid 33 start time Wed Feb 20 >21:56:25 2002 >/usr/lib/amanda/sendbackup: version 2.4.2p2 >sendbackup: got input request: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS >|;bsd-auth;srvcomp-best;index; > parsed request as: program `GNUTAR' > disk `/usr' > lev 0 > since 1970:1:1:0:0:0 > opt `|;bsd-auth;srvcomp-best;index;' >sendbackup: try_socksize: send buffer size is 65536 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33863 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33864 >sendbackup: stream_server: waiting for connection: 0.0.0.0.33865 > waiting for connect on 33863, then 33864, then 33865 >sendbackup: stream_accept: connection from 192.168.1.1.33866 >sendbackup: stream_accept: connection from 192.168.1.1.33867 >sendbackup: stream_accept: connection from 192.168.1.1.33868 > got all connections >sendbackup-gnutar: doing level 0 dump as listed-incremental to >/var/lib/amanda/gnutar-lists/bifrost_usr_0.new >sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT >sendbackup: spawning /usr/lib/amanda/runtar in pipeline >sendbackup: argument list: gtar --create --file - --directory /usr >--one-file-system --listed-incremental >/var/lib/amanda/gnutar-lists/bifrost_usr_0.new --sparse >--ignore-failed-read --totals . >sendbackup: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e >'s/^\.//'" >sendbackup-gnutar: /usr/lib/amanda/runtar: pid 16590 >index tee cannot write [Connection reset by peer] >sendbackup: pid 16589 finish time Wed Feb 20 22:13:40 2002 > > > > > >Kasper Edwards >Ph.D. Stipendiat, Civilingeniør >Institut for Produktion og Ledelse >Danmarks Tekniske Universitet >Byg 423, rum 028 >2800 Lyngby >tlf. : +45 4525 6010 >Mobil: +45 2225 6320 >Fax. :+45 4593 4467 >Web : http://www.its.dtu.dk/ansat/ke/index_d.htm >Email: [EMAIL PROTECTED]
problems with amandad
hello mailinglist, I have a problem with amandad and I hope there is somebody who can help me. After amanda was running some hours without any problems, my /var/log/messages throws following error: Feb 22 08:51:46 shakira amandad[6493]: error receiving message: timeout Feb 22 08:51:46 shakira inetd[1027]: /usr/lib/amanda/amandad: exit status 0x1 shakira is my amanda-server. this error happens without rebooting the server or restarting inetd. I can't imagine where this error comes from and how to repare it. another problem is that my amreport mails me a similar error: FAILURE AND STRANGE DUMP SUMMARY: 192.168.25 /etc lev 0 FAILED [Request to 192.168.250.55 timed out.] can this timeout-problem fit to the amandad-error? Thank you very much! greetings, Leonie
