amcheckdump and a tape changer
Hello! I'm using amanda 3.3 with a tape changer. It works as expected. There is only one problem with amcheckdump. On startup amcheckdumps tells me, which tape is needed and stops then, waiting for "enter". Is it possible to let amcheckdump load the correct tape? Many thanks! Matthias
property append IGNORE regex
Hello! I'm using property append "IGNORE" "file changed as we read it$" in my dumptype to suppress some warnins. This works as expected. Now I have to "ignore" messages about removed files from some cache directories too and tried: property append "IGNORE" ".*/cache2/.*: File removed before we read it$" which doesnt work. The tar output looks like this: .cache/mozilla/firefox/rxgpvk63.default/cache2/entries/05568ED7AE00C44F1D181D78E513ABF7BDBF0659: File removed before we read it Dies the regex only matches after the ":"? Who can I suppress unnecessary warnings? Thanks! Matthias
Re: Restore with a different dumptype
On Wed, Oct 04, 2017 at 04:19:19PM +0200, Stefan G. Weichinger wrote:
Hi,
> Am 2017-10-04 um 16:08 schrieb Matthias Teege:
> > is it possible to create backups on node "A" with dumptype "A" and
> > restore on a different host with dumptype "B"? The problem is, that host
> > "A" uses some special tools which are not present on node "B" so I have
> > to use another dumptype for restore.
>
> Show us the difference and we can tell you more.
>
> I mean "show the 2 dumptypes".
the following one is used for backup:
define dumptype dotar {
compress none
index yes
record yes
program "GNUTAR"
auth "bsd"
}
and I need to overwrite "programm" and set application:
> You can always override the dumptype via "-o" commandline option, for
> example.
I've tried
# amrecover -oDUMPTYPE:dotar:program="APPLICATION" -C daily
parse error: unknown parameter 'DUMPTYPE:dotar:program'
amrecover: errors processing config file
but the config looks normal:
# amgetconf --list dumptype | grep dotar
dotar
This is amanda 3.3.3 under CentOS.
Thanks!
Matthias
Restore with a different dumptype
Hello, is it possible to create backups on node "A" with dumptype "A" and restore on a different host with dumptype "B"? The problem is, that host "A" uses some special tools which are not present on node "B" so I have to use another dumptype for restore. Thanks Matthias
Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
On Sat, Sep 23, 2017 at 08:16:38AM -0400, Jean-Louis Martineau wrote: Hi, > The debug files are in the debug directory: >amgetconf build.amanda_dbgdir ah, ok its /tmp/amanda. su amandabackup -c '/opt/amanda/3.3.3/sbin/amgetconf build.amanda_dbgdir' /tmp/amanda I've made a run with 6 servers, all on different spindles. It simply works. No error message and nothing in the debug log. # grep -ri EAG /tmp/amanda/ # (debug logs are there) I'll start a full run over all hosts tonight. It looks like its only a problem with the new Centos Packages. What do you think? Matthias
Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
On Fri, Sep 22, 2017 at 01:16:27PM -0400, Jean-Louis Martineau wrote: Hi, I have again looked more closely. Perhaps the (recv error) problem is an update of the Centos amanda packages. On tuesday we updated the server and there was an update from amanda.*3.3.3-17.el7 to 3.3.3-18.el7. > Can you try the attached patch? I've compiled 3.3.3 with your patch and run a dump with: su amandabackup -c '/opt/amanda/3.3.3/sbin/amdump --no-taper daily nfs /home/./c' It works without problems. > After the run, can you grep for'first read return EAGAIN' and'second > read return EAGAIN' in the dumper debug files? I'm surprised, there is no dumper debug file. In my amanda.conf I have: logdir "/var/log/amanda/daily" debug-planner 3 debug-dumper 3 but ... # find /var/log/amanda -name '*dump*23*' /var/log/amanda/daily/amdump.20170923125853 /var/log/amanda/daily/amdump.20170923123220 /var/log/amanda/daily/amdump.20170923123412 /var/log/amanda/server/daily/amdump.20170923005801.debug Is this because of "--no-taper"? Thanks again! Matthias
Re: Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
On Thu, Sep 21, 2017 at 09:45:04AM +0200, Matthias Teege wrote: Hi, > I have a running Amanda 3.3.3 Server. The backup works without > problems. On the clients we use Amanda 3.3.0/3.3.6 and 2.6.x on some > old systems. I've made some more tests and its look like that its not a problem of one host. I've run amdump for a single host and a single disk and got the same error. On the client I see: Fri Sep 22 16:15:35 2017: thd-0x55b3cc1bd400: amandad: security_stream_seterr(0x55b3cc1e0f70, write error to: Connection reset by peer) Fri Sep 22 16:15:35 2017: thd-0x55b3cc1bd400: amandad: sending NAK pkt: <<<<< ERROR write error on stream 49: write error to: Connection reset by peer On the server I see: river: hdisk-state time 173.994 hdisk 0: free 1439233056 dumpers 1 driver: result time 173.994 from dumper0: FAILED 00-1 "[data read: recv error: Resource temporarily unavailable]" driver: send-cmd time 173.994 to chunker0: FAILED 00-1 What can be the cause of the "reset"? Thanks! Matthias >
Dump failed with data read: recv error: Resource temporarily unavailable after migration of some clients
Hello! I have a running Amanda 3.3.3 Server. The backup works without problems. On the clients we use Amanda 3.3.0/3.3.6 and 2.6.x on some old systems. After migrating one of the 2.6 Clients to 3.3.0 the backup fails with: cl15 /var/lib/jenkins lev 0 FAILED [data read: recv error: Resource temporarily unavailable] cl15 /var/lib/jenkins lev 0 FAILED [data read: recv error: Resource temporarily unavailable] cl15 /var/lib/jenkins lev 0 partial taper: successfully taped a partial dump That would not be a big problem but after the migration other systems start to fail too. What does the error message mean? Do I have to remove some old indicies from the server? Any hints? Thanks! Matthias
Re: Amvault for the Compleat Dummy
On Tue, Jul 11, 2017 at 08:36:16AM +0200, Lorenzo Marcantonio wrote: Hi! > On Tue, Jul 11, 2017 at 08:06:29AM +0200, Stefan G. Weichinger wrote: > > Sure, pls share for us to learn/copy/ask. > > The vaulting run is done with > > amvault DailySet --latest-fulls --dest-storage VAULT-STORAGE How many tapes do you use for "vaulting" and how do you rotate the tapes? Does the amvault job using the same settings as the daily job to vtapes? I'm doing dailys to vtapes which are smaller as my "real" tapes. If I understand amvault correctly I can write more then one dump to tape with something like 'amvault --src-timestamp "201707..." --dst-changer vaulting-tape daily' but have to rotate the tapes "by hand". Thanks! Matthias
RESULTS MISSING on all DLE when only one estimate fails?
Hallo! I've installed Amanda 3.3.3 on a Centos server. Sometimes backups are failing with "RESULTS MISSING" and "driver: WARNING: got empty schedule from planner". I think this is mostly because of estimate timeouts. I see "planner: ERROR Some estimate timeout on a.example.com, using server estimate if possible". Thats something I can handle. But why do I get "RESULTS MISSING" for all hosts/DLE and "... empty schedule ..." when only one estimate fails? There are planner/estimate results from all my DLE, except one, in the logs. Shouldn't the amanda planner return a schedule without the failing DLE? Thanks! Matthias
overwritten in x runs notes
Hi, I'm using amanda 3.3.0 on a new backup server. After some successfull runs I've got a lot of "Last full dump of ... overwritten in X runs" warnings from the planner. The warnings start 5 days before the last full dump would be overwritten. How do I reduce this number from 5 to 3 days? Thanks Matthias
