tape device errors
I am using an ATL PowerStor L500 tape changer with one DLT7000 tape drive on a RedHat 6.2 system. Yesterday everything was working fine as far as accessing the tape drive and changer is concerned, but not anymore. A cron script that was writing a tar.gz file to tape(not via amanda) was running and I ran the 'amcheck' program. It tried to access the tape drive and check the tape label, and I think that screwed things up. Now when I try to use any of the amanda programs to access the tapes I get the following error: bash$ /usr/local/amanda/sbin/amlabel -f DailySet1 Daily-001 slot 1 changer: got exit: 0 str: 1 /dev/nst0 labeling tape in slot 1 (/dev/nst0): rewinding amlabel: tape open: Device not configured tape open: Device not configured amlabel: pid 12619 finish time Thu Jun 7 15:00:15 2001 bash$ /usr/local/amanda/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /home/amanda: 14960580 KB disk space available, using 10864580 KB changer: got exit: 0 str: 1 13 1 changer: got exit: 0 str: 1 /dev/nst0 amcheck-server: slot 1: tape open: Device not configured So the error I'm getting is "tape open: Device not configured". But the cron script(that I interrupted) is not running, and I don't believe anything else is accessing the tape. Thanks, Nathanael
Re: stange behavior
>Why the two different files today? Did I reach a file size limit? You reached the holding disk "chunksize" limit (see the amanda(8) man page). The second file is a continuation of the first. >Andrew Hall John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
stange behavior
Hello, I have a client on my backup schedule that is failing with a data timeout error. This error is due to the fact that the machine in question has a filesystem large enough to cause amdump to timeout. The strange thing is this morning the backup worked, I think, but they were written to the holding disk in an odd format. Instead of one file amanda created two. I am used to seeing a file like: hostname.net.sda5.1 Today I saw two files: -rw---1 backupbackup2147385344 Jun 6 23:33 hostname.net.sda5.1 -rw---1 backupbackup1638039552 Jun 6 00:24 hostname.net.sda5.1.1 Why the two different files today? Did I reach a file size limit? Thanks. Andrew Hall
Re: FreeBSD 4.3/inetd failing
Ok, this was a weird one. It turned out to be due to tcpwrappers. I just saw a recent post suggesting it. It's odd that inetd closed the port, but I would guess that that might be caused because the protocol is udp instead of tcp? Put this in a FAQ somewhere! -doug On Thu, 7 Jun 2001, Doug Silver wrote: > Ok, now I'm stumped. I have two FBSD 4.3 machines, one inside and one > outside a firewall. I compiled amanda2.4.2p2 on the internal machine and > it checks out fine. So, I tarred up libexec, lib/liba*, and sbin/am*, put > it on the external machine, HUP'd inetd and poof, it still doesn't > work. It's not a shared library issue because amanda isn't using shared > libs on FBSD. In fact, I just double checked and the inetd binaries are > exactly the same (md5 confirmed). > > Here are some gory tcpdump details: > Internal client > 10:18:45.151846 fbsd43.internal.amanda > amanda-server.internal.902: udp 360 > 10:18:45.152218 amanda-server.internal.902 > fbsd43.internal.amanda: udp 49 > > External client: > 10:23:50.461673 firewall.921 > fbsd43.external.amanda: udp 155 > > /var/log/messages two seconds later reports > Jun 7 10:23:52 fbsd43 inetd[152]: amanda/udp server failing (looping), service >terminated > > I know the firewall is acting properly because I'm backing up at least four other >external > machines, most are FBSD 3.3-4.2. > > John - I can run your amandad test script from the command line and it > gives this: > # cat amandad.out.74693 > Thu Jun 7 10:34:18 PDT 2001: starting amandad > Thu Jun 7 10:34:48 PDT 2001: amandad done: status is 1 > > cat amandad.20010607103418.debug > amandad: debug 1 pid 74695 ruid 0 euid 0 start time Thu Jun 7 10:34:18 2001 > [snip compile info] > amandad: dgram_recv: timeout after 30 seconds > amandad: error receiving message: timeout > error receiving message: timeout > amandad: pid 74695 finish time Thu Jun 7 10:34:48 2001 > > Any other suggestions??? > > Thanks. > > Doug Silver > > >
Re: FreeBSD 4.3/inetd failing
Ok, now I'm stumped. I have two FBSD 4.3 machines, one inside and one outside a firewall. I compiled amanda2.4.2p2 on the internal machine and it checks out fine. So, I tarred up libexec, lib/liba*, and sbin/am*, put it on the external machine, HUP'd inetd and poof, it still doesn't work. It's not a shared library issue because amanda isn't using shared libs on FBSD. In fact, I just double checked and the inetd binaries are exactly the same (md5 confirmed). Here are some gory tcpdump details: Internal client 10:18:45.151846 fbsd43.internal.amanda > amanda-server.internal.902: udp 360 10:18:45.152218 amanda-server.internal.902 > fbsd43.internal.amanda: udp 49 External client: 10:23:50.461673 firewall.921 > fbsd43.external.amanda: udp 155 /var/log/messages two seconds later reports Jun 7 10:23:52 fbsd43 inetd[152]: amanda/udp server failing (looping), service terminated I know the firewall is acting properly because I'm backing up at least four other external machines, most are FBSD 3.3-4.2. John - I can run your amandad test script from the command line and it gives this: # cat amandad.out.74693 Thu Jun 7 10:34:18 PDT 2001: starting amandad Thu Jun 7 10:34:48 PDT 2001: amandad done: status is 1 cat amandad.20010607103418.debug amandad: debug 1 pid 74695 ruid 0 euid 0 start time Thu Jun 7 10:34:18 2001 [snip compile info] amandad: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout error receiving message: timeout amandad: pid 74695 finish time Thu Jun 7 10:34:48 2001 Any other suggestions??? Thanks. Doug Silver
Re: Amcheck problems (selfcheck request timeout)
On Thu, 7 Jun 2001 at 11:45am, Nate Burton wrote > On Wednesday 06 June 2001 21:47, Olivier Nicole wrote: > > >WARNING: admin2.airscorp.com: selfcheck request failed: timeout waiting > > > for ACK > > > > Would it have to be allowed in TCP wrapper? > > > > On the client you could send a tcpdump (or whatever the command is > > called under Linudx) and check if you see the packets going back and > > forth between client and server. > > > No, i don't believe it uses tcp wrappers. > Is there anything in /var/log/messages or /var/log/secure on admin2? By default, amanda *does* use tcp wrappers. On admin2, you'll need an entry in /etc/hosts.allow that says 'amandad : admin1.airscorp.com', subbing the IP address for the hostname, of course. That's assuming that you have the standard 'ALL : ALL' in /etc/hosts.deny. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Fwd: Re: predicting full dumps
Hi guys,
Actually, as Joshua pointed out, "amadmin due" does exactly
what I want--It gives you a nice list saying which dumps are overdue,
what dumps are due today, and how many days until other dumps are due.
Forcing dumps that are overdue, due today, or that are due in a day or
two would be a good starting place. You could do something like this to
consider candidates for forcing:
amadmin due | fgrep -v Overdue | fgrep -v today \
| awk '{print $3,$0}' | sort -rn
amadmin due | fgrep today
amadmin due | fgrep Overdue
You would start from the "bottom" of the list and work your way up.
Mitch Collinsworth wrote:
>
> You can figure out what's coming due by looking at
> 'amadmin balance'. You can't always predict what might
> get promoted by planner, but if you do what you're suggesting and
> force enough filesystems to make the total data size for the run
> greater than "average", planner won't promote anything.
>
> Some other things to consider if run-time is getting to be a problem
> are adding more holding disk space and possibly increasing maxdumps.
> These should allow for more parallelism in the dumping phase.
> Depending on your needs, getting the data off the clients quickly
> might be the real issue, and then amanda can continue spooling data
> from the holding disk to tape long after the dumps have finished.
>
> -Mitch
>
> On Thu, 7 Jun 2001, Francis 'Dexter' Gois wrote:
>
> >
> > Not sure it is possible : the dumps queue is created when you launch amdump,
> > and Amanda looks at which dumps it can move (to optimize) or it has to move
> > (because of space problems) just before starting the dumps when you launch
> > amdump Config (see the logs).
> >
> > Dexter
> >
> > On Thursday 07 June 2001 06:48, you wrote:
> > > Does anyone have any scripts, or any tricks that I could use to try to
> > > predict what full dumps are coming due?
> > >
> > > I would like to be able to force a bunch of full dumps on the weekend,
> > > when the total time of the run is not an issue, so that the load should
> > > be a little lighter during the week.
> > >
> > > Thanks in advance,
> >
> > --
> > Knowledge-sharing and open-source content : another way to gain eternity.
> > Francis 'Dexter' Gois - [EMAIL PROTECTED]
> > System Administrator - Tiscali Belgium NV/SA
> > phone: +3224000839- fax : +3224000899
> >
> > ---
> >
> > --
> > Knowledge-sharing and open-source content : another way to gain eternity.
> > Francis 'Dexter' Gois - [EMAIL PROTECTED]
> > System Administrator - Tiscali Belgium NV/SA
> > phone: +3224000839- fax : +3224000899
> >
--
"Jonathan F. Dill" ([EMAIL PROTECTED])
CARB Systems and Network Administrator
Home Page: http://www.umbi.umd.edu/~dill
Re: SOLVED! - FreeBSD 4.3-STABLE, HP SureStore 12000E changer, and Amanda
Hi, Sean Noonan wrote: > Just fixed permissions for xpt* and chg-scsi works. Thanks sooo much Ben. > > One last question, please. What's the best way to "fix" the permissions > problem on the devices in question: > > chown operator:operator /dev/whatever (most are currently root:operator) > > OR > > chmod 660 /dev/whatever (looks like 600 right now). I believe the usual method is to grant write access to the group rather than changing the ownership of the device. At least that's the way I do it :) In the grand scheme of things I doubt it matters much. You will want to make sure that you only modify permissions (or ownership) on the devices absolutely required. That leaves less chance for something to run amok and start trashing your disk drives or other devices. -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
Re: New to amanda
On Thu, Jun 07, 2001 at 03:06:04PM +0200, Thomas Hepper wrote: > Hi, > On Thu, Jun 07, 2001 at 01:41:09PM +0200, Michael Aronsen wrote: > > Hello, > > > > I've been fighting my way through setting up amanda on backup server, my > > current problem is finding out which chg-* script to use for a HP 24x6 dds 3 > > dat changer, anyone tried this config before? > > Which OS ? Under Solaris 7/8, x86 I'm using chg-mtx. I have two different programs called mtx, one from HP (the included cd and/or their support web-site) and a freeware one from the net. Both work, though their command-line syntax differs. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amcheck problems (selfcheck request timeout)
On Wednesday 06 June 2001 21:47, Olivier Nicole wrote: > >WARNING: admin2.airscorp.com: selfcheck request failed: timeout waiting > > for ACK > > Would it have to be allowed in TCP wrapper? > > On the client you could send a tcpdump (or whatever the command is > called under Linudx) and check if you see the packets going back and > forth between client and server. > > Olivier No, i don't believe it uses tcp wrappers. I used a network sniffer to look at the network packets being sent when I run amcheck and here's what I found: Tape-server host - 10.0.4.91(admin1) (amcheck is being run on this machine) Client - 10.0.4.101(admin2) (trying to connect to this client) -- Source: 10.0.4.91 ; Dest: 10.0.4.101 ; Protocol: UDP ; Source Port: 847 ; Dest Port: amanda (10080) 0 416d 616e 6461 2032 2e35 2052 4551 2048 Amanda 2.5 REQ H 10 414e 444c 4520 3120 5345 5120 300a 5345 ANDLE 1 SEQ 0.SE 20 4355 5249 5459 2055 5345 5220 6f70 6572 CURITY USER oper 30 6174 6f72 0a53 4552 5649 4345 2073 656c ator.SERVICE sel 40 6663 6865 636b 0a4f 5054 494f 4e53 203b fcheck.OPTIONS ; 50 0a47 4e55 5441 5220 2f68 6f6d 652f 6e62 .GNUTAR /home/nb 60 7572 746f 6e20 3020 4f50 5449 4f4e 5320 urton 0 OPTIONS 70 7c3b 6175 7468 3d42 5344 3b63 6f6d 7072 |;auth=BSD;compr 80 6573 732d 6265 7374 3b69 6e64 6578 3b65 ess-best;index;e 90 7863 6c75 6465 2d6c 6973 743d 2f75 7372 xclude-list=/usr a0 2f6c 6f63 616c 2f6c 6962 2f61 6d61 6e64 /local/lib/amand b0 612f 6578 636c 7564 652e 6774 6172 3b0a a/exclude.gtar;. But then 10.0.4.101(admin2) does not seem to send anything back in return. There are two more UDP packets sent identical to the one above and then amcheck timesout. amadad is listening to port 10080 on 10.0.4.101. Here's the output of nmap: --- >sudo nmap -sU -O 10.0.4.101 -p 10080 Starting nmap V. 2.54BETA7 ( www.insecure.org/nmap/ ) Warning: OS detection will be MUCH less reliable because we did not find at least 1 open and 1 closed TCP port Interesting ports on (10.0.4.101): Port State Service 10080/udp openamanda Remote OS guesses: Linux 2.3.49 x86, Linux 2.3.47 - 2.3.99-pre2 x86 Nmap run completed -- 1 IP address (1 host up) scanned in 1 second --- And as I said in a previous post, the /tmp/amandad*.debug file is being created, but not with much in it. I'm really stumped! --Nathanael Burton
Re: predicting full dumps
The best way I can think of doing this (I'm far from an expert with amanda, but I'm learning) is set up one cron with your normal configuration, then setup another configuration that is set to do full dumps always, and have another cron run that on the weekend. That seems to be the easiest way to do it. Somebody please correct me if I'm wrong. So far that's how I'm planning to do it when I want my monthlies, and if there is a better way, I'd be pleased to hear it. Lance
recovery
I did my first backup last night, and tried a recovery of a couple files today, but it didn't seem to work. It only seemed to write like around 40 blocks or so, maybe (of 32k each). Well, the dd (for testing) came up like this: mt rewind dd if=/dev/rmt/1hn bs=32k count=1 > header.dat # tape label, apparently mt fsf 1 # skip to next archive dd if=/dev/rmt/1hn bs=32k skip=1 of=out1.tar.gz # the first time this would only recover 2 blocks dd if=/dev/rmt/1hn bs=32k of=out2.tar.gz # this would recover 38-40 blocks, depending on how i did the previous dd # sometimes I would do skip the skip=1 part... It would only recover part of the file. almost as if that's all that was dumped to tape. I mean, /net/useruv is 268842m, so doing a small test (/usr/local/bin/tar cvvf - /net/useruv|gzip -c > /tmp/_net_useruv.tar.gz) came up with the following size of 273435486, yet the report said: hostdiskL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s arsd/net/useruv 0 10 32 320.0 0:00107.7 0:0227.3 Why? It didn't backup nearly enough at all, only 10k it looks like. This is on a Solaris 8 box with 256M ram and a DLT IV. On a different system (at another location) I am running amanda on a linux system with 128m and a DDS-3 drive (Python 04106) I'm currently redoing the tape type just in case. Any help would be greatly appreciated... lance
planner problem
I'm trying to backup just a directory, but i get this error:
"driver: WARNING: got empty schedule from planner"
What am i doing wrong?
Thanks for your attention
PS: Here's the report with the errors:
These dumps were to tape BackupTotal00.
The next tape Amanda expects to use is: BackupTotal00.
FAILURE AND STRANGE DUMP SUMMARY:
admin.di.f /home/dgalveias/psd lev 0 FAILED [missing result for
/home/dgalveias/psd in
admin.di.fc.ul.pt response]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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 (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
?
NOTES:
planner: Adding new disk admin.di.fc.ul.pt:/home/dgalveias/psd.
driver: WARNING: got empty schedule from planner
taper: tape BackupTotal00 kb 0 fm 0 [OK]
?
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
admin.di.fc. -lveias/psd 0 FAILED ---
(brought to you by Amanda version 2.4.2)
***
***
***
Here's the amanda.conf i'm using:
org "Daemon a correr na admin.di.fc.ul.pt"
mailto "[EMAIL PROTECTED]"
dumpuser "backup"
inparallel 4
netusage 200 Kbps
dumpcycle 0
runspercycle 0
#tapecycle 25 tapes
tapecycle 1 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
dtimeout 30
ctimeout 3
tapebufs 20
tapedev "/dev/nst0"
tapetype Tape-da-admin
labelstr "^BackupTotal[0-9][0-9]*$"
holdingdisk hd1 {
comment "main holding disk"
directory "/backups/testes_do_amanda" # where the holding disk
is
#use 1Gb# how much space can we use on it
use 100 mbytes # a non-positive value means:
#use all space but that value
#chunksize 1Gb # 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
}
infofile "/usr/local/etc/amanda/BackupTotal/Logs/curinfo"# database
DIRECTORY
logdir "/usr/local/etc/amanda/BackupTotal/Logs" # log directory
indexdir "/usr/local/etc/amanda/BackupTotal/Logs/index" # index directory
define tapetype Tape-da-admin {
comment "Tape da admin"
length 9853 mbytes
filemark 0 kbytes
speed 916 kps
}
define dumptype corveta{
comment "Backup de testes feito a pensar na maquina Corveta"
compress client fast
dumpcycle 1 #TODOS os dias faz backups totais ;)
index yes
program "GNUTAR"
exclude "./dev ./proc ./tmp ./mnt"
holdingdisk yes
priority high
dumpcycle 0
}
***
***
***
Here's the tapelist i have:
20010606 BackupTotal00 reuse
***
***
***
Here's the disklist i have:
admin.di.fc.ul.pt /home/dgalveias/psd corveta
Strange dump summary
- What does this mean?(extract from a amdump report) FAILURE AND STRANGE DUMP SUMMARY: planner: FATAL protocol out of handles - When amanda tells that it is "expecting a new tape", what do i have to do? Giving an already labeled or unlabeled tape it's the same. - Is there any chance that amanda is capable of working only making dumps to hard drive? Thanks for your attention PS: I don't know if it's just me, but i haven't seen such a difficult backup software to install in my whole life. Please write a better help and documentation (?and tutorials?).
New to amanda
Hello, I've been fighting my way through setting up amanda on backup server, my current problem is finding out which chg-* script to use for a HP 24x6 dds 3 dat changer, anyone tried this config before? Michael Aronsen
Re: New to amanda
Hi, On Thu, Jun 07, 2001 at 01:41:09PM +0200, Michael Aronsen wrote: > Hello, > > I've been fighting my way through setting up amanda on backup server, my > current problem is finding out which chg-* script to use for a HP 24x6 dds 3 > dat changer, anyone tried this config before? Which OS ? Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Files not backed up while they should?
Hi all! We are using Amanda for backup a couple of years now and it has never failed for us. But today I encountered something really weird: We have two servers in our internal network, hugo10 and hugo20. hugo20 is the tape server and backup host. Backups are done daily. Today I tried to restore one particular file one of our developers accidentally "lost". The disk in question is da0s1d on hugo20. Of course, it was backed up last night. Level 1 dump, it seems: hugo20# su -m operator -c "amadmin HAUSNETZ info hugo20 da0s1d" Current info for hugo20 da0s1d: Stats: dump rates (kps), Full: 1778.0, 962.0, 1566.0 Incremental:1.0, 1.0, 1.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20010530 HAUSNETZ-1412 1734032 1734048 975 1 20010607 HAUSNETZ-4 8 153 160 130 2 20010412 HAUSNETZ-12 5 153 160 129 3 20010224 HAUSNETZ-10 3 362 384 48 But: the index file for that disk on hugo20 doesn't show any (!) file having been backed up. And of course a lot of files changed since 20010530 which seemingly is the last level 0 dump. In fact all index files from 20010531 on are empty! The time on the host is OK, timestamps on all file in question OK, too. I need some help on where to look further for information. At the moment I'm really puzzled and completely stuck. All reports said, backup went fine, but nothing was dumped for that disk. Versions installed: FreeBSD hugo20.ka.punkt.de 4.3-BETA FreeBSD 4.3-BETA #1: Thu Mar 22 10:25:35 CET 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HUGO20 i386 hugo20# pkg_info | grep amanda amanda-2.4.1The Advanced Maryland Automatic Network Disk Archiver Thanks for any hints, Patrick
Re: predicting full dumps
On Thu, 7 Jun 2001 at 12:48am, Jonathan Dill wrote > Does anyone have any scripts, or any tricks that I could use to try to > predict what full dumps are coming due? > > I would like to be able to force a bunch of full dumps on the weekend, > when the total time of the run is not an issue, so that the load should > be a little lighter during the week. Do you mean something other than "amadmin due"? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Fwd: Re: predicting full dumps
You can figure out what's coming due by looking at 'amadmin balance'. You can't always predict what might get promoted by planner, but if you do what you're suggesting and force enough filesystems to make the total data size for the run greater than "average", planner won't promote anything. Some other things to consider if run-time is getting to be a problem are adding more holding disk space and possibly increasing maxdumps. These should allow for more parallelism in the dumping phase. Depending on your needs, getting the data off the clients quickly might be the real issue, and then amanda can continue spooling data from the holding disk to tape long after the dumps have finished. -Mitch On Thu, 7 Jun 2001, Francis 'Dexter' Gois wrote: > > Not sure it is possible : the dumps queue is created when you launch amdump, > and Amanda looks at which dumps it can move (to optimize) or it has to move > (because of space problems) just before starting the dumps when you launch > amdump Config (see the logs). > > Dexter > > On Thursday 07 June 2001 06:48, you wrote: > > Does anyone have any scripts, or any tricks that I could use to try to > > predict what full dumps are coming due? > > > > I would like to be able to force a bunch of full dumps on the weekend, > > when the total time of the run is not an issue, so that the load should > > be a little lighter during the week. > > > > Thanks in advance, > > -- > Knowledge-sharing and open-source content : another way to gain eternity. > Francis 'Dexter' Gois - [EMAIL PROTECTED] > System Administrator - Tiscali Belgium NV/SA > phone: +3224000839- fax : +3224000899 > > --- > > -- > Knowledge-sharing and open-source content : another way to gain eternity. > Francis 'Dexter' Gois - [EMAIL PROTECTED] > System Administrator - Tiscali Belgium NV/SA > phone: +3224000839- fax : +3224000899 >
Fwd: Re: predicting full dumps
Not sure it is possible : the dumps queue is created when you launch amdump, and Amanda looks at which dumps it can move (to optimize) or it has to move (because of space problems) just before starting the dumps when you launch amdump Config (see the logs). Dexter On Thursday 07 June 2001 06:48, you wrote: > Does anyone have any scripts, or any tricks that I could use to try to > predict what full dumps are coming due? > > I would like to be able to force a bunch of full dumps on the weekend, > when the total time of the run is not an issue, so that the load should > be a little lighter during the week. > > Thanks in advance, -- Knowledge-sharing and open-source content : another way to gain eternity. Francis 'Dexter' Gois - [EMAIL PROTECTED] System Administrator - Tiscali Belgium NV/SA phone: +3224000839- fax : +3224000899 --- -- Knowledge-sharing and open-source content : another way to gain eternity. Francis 'Dexter' Gois - [EMAIL PROTECTED] System Administrator - Tiscali Belgium NV/SA phone: +3224000839- fax : +3224000899
predicting full dumps
Does anyone have any scripts, or any tricks that I could use to try to predict what full dumps are coming due? I would like to be able to force a bunch of full dumps on the weekend, when the total time of the run is not an issue, so that the load should be a little lighter during the week. Thanks in advance, -- "Jonathan F. Dill" ([EMAIL PROTECTED])
Re: Planner problem
Hi you have a problem with your disklist/directory name: David Galveias schrieb: > > I'm trying to backup just a small directory, but i get this error: > "driver: WARNING: got empty schedule from planner" > What am i doing wrong? [] > FAILURE AND STRANGE DUMP SUMMARY: > admin.di.f /home/dgalveias/psd lev 0 FAILED ^ here is the symtom of the problem.. [] > Here's the disklist i have: > > admin.di.fc.ul.pt /home/dgalveias/psd corveta ^ and this is the problem itself: you can't have spaces in names in the disklist, as they are interpreted as field seperators. and as a result amanda trys to get estimates for /home/dgalveias/psd on spindle "corveta" which is not an alowed value for spidle-number. i woulkd create a link to that directory wit no spaces in the name and put that into disklist. Christoph
