Incremental backup with Zmanda Windows Client
Hi,
After years of happy backups with the smbclient, I deceided to give ZWC
a try.
But I am frustrated because incremental backups seems not to work,
whatever the level, all the data are being pulled/
Here's a snipset of the reports of 6 days, while I was on leave, no one
using the PC:
olivier. c:/temp 1 13306536 12085577 90.8 36:10 6132.1 2:26 82777.9
olivier. c:/temp 1 13306536 12085581 90.8 58:01 3823.0 2:47 72368.7
olivier. c:/temp 0 13306535 12085592 90.8 46:20 4787.0 4:05 49328.9
olivier. c:/temp 1 13306536 12085576 90.8 49:44 4459.6 4:25 45605.9
olivier. c:/temp 1 13306536 12085577 90.8 41:32 5339.0 3:26 58667.8
olivier. c:/temp 0 13306535 12085590 90.8 49:04 4520.2 3:12 62945.8
And the backup type is defined as:
define dumptype zwc-normal {
comment Incremental dumpp of Zmanda Windows Client
index yes
auth bsdtcp
program DUMP
maxdumps 1
compress server best
priority high
allow-split true
}
It obviously has no skip-incr (as shown by the level 0 and 1 in the dump
reports).
Why is it always backuping the full directory?
Best regards,
Olivier
Script to chang ethe user for Zmanda Windows Client
Hi,
As explained
http://wiki.zmanda.com/index.php/Zmanda_Windows_Client#Running_ZWC_as_some_other_user
the Zmanda client for Windows installs with the default username
amandauser and this cannot be configured by an option.
That username must reflect the username that is running Amanda on the
server. That can be changed using a few Windows tools.
The script http://cs.ait.ac.th/~on/rename_amanda.vbs automatically
performs all the steps required to change Zmanda Windows Client user.
I have tested this script on Windows XP Pro SP3 (32 bits) and on Windows
7 Pro SP1 (32 bits).
To use the script:
Download the script in a temporary directory, then run the script with:
cscript //nologo rename_amanda.vbs username {/delete]
Where username is the new user name for ZWC and the option /delete
allows to completely remove the old user from the computer.
The script will leave 3 files in the directory, secedit_backup.sdb is an
important file: it is a backup of the system security before it was
modified by the script.
I am pretty sure this script will not work properly if some system users
(Administrator, etc.) have UTF8 names.
Best regards,
Olivier
--
Re: amsamba and NTFS permissions
Stefan G. Weichinger s...@amanda.org writes: Am 25.09.2014 um 17:21 schrieb Stefan G. Weichinger: Additional info: they can't use the A/ZManda-Windows-Client because the NTFS-share is shared from a storage/SAN and not from a dedicated MS Windows Server. So we have to solve that on the side of the linux server, I assume. Does nobody here successfully do that with amanda? You supposedly could run A/ZManda-Windows-Client on a Windows client (one that remotely mounts the NTFS share). It will have a cost because the files are traveling the network twice (from NTFS server to Windows client and from Windows client to Amanda server). Your Windows client could be some virtual machine that is started only for back-up purposes (a virtualbox running from Amanda server, so you cut off one network transfer). That is ugly. It depends what is the NAS/storage amde of. Best regards, Olivier --
Re: What timeout controls the scripts
There is no parameter for that timeout. It is a constant in the program. CONNECT_TIMEOUT in the server-src/chunker.c file Running the script on the client might fix the issue execute-where client Even runing on the client it will take more than 300 seconds, would the chunker wait on the script to finish on the client? If run on the client, the socket will be opened before the script are run. So it should not timeout on 'accepting header stream'. But it might timeout on 'accepting data stream', I'm not sure, you should try. For some reason, the script was not running on the client. I changed the timeout in chunker.c and it does the trick. But I am wondering why the chunker is starting so early and not at the same time as the tar/dump (when the script is finished). Best regards, Olivier Jean-Louis Thank you, Olivier Jean-Louis On 09/24/2014 12:04 AM, Olivier Nicole wrote: Hi, For one specific DLE, I need to do a snapshot, through a pre-del-backup script. But the script takes quite some time to complete (up to a couple of hours). What timeout should I define to make Amanda wait for the end of the script before it can chunk the result? Example for the DLE amanda /virtual/mybackups/st106808 chunker.20140924001916.debug times out after 300 seconds: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: start at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: rename at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: START 20140924000501 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: PORT-WRITE 11-00015 /holding/20140924000501/amanda._virtual_mybackups_st106808.0 amanda 9efefbff1f /virtual/mybackups/st106808 0 1970:1:1:0:0:0 10485760 GNUTAR 500064 |;auth=bsd;srvcomp-best;index; ... Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: stream_accept: timeout after 300 seconds Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: putresult: 11 TRY-AGAIN Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: critical (fatal): startup_chunker failed: error accepting header stream: Operation timed out and driver.20140924000501.debug, the script takes 45 minutes to complete: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: driver: Spawning /usr/local/libexec/amanda/application/vmware vmware PRE-DLE-BACKUP --execute-where server --config normal --host amanda --disk /virtual/mybackups/st106808 --level 0 in pipeline Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: zorglub Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: PRE-DLE-BACKUP st106808 Wed Sep 24 00:19:18 2014: thd-0x804c6ce00: driver: script: We need to backup that one st106808 ... Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: 2014-09-23 18:05:52 -- info: == ghettoVCB LOG END Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: VMware snapshot OK for st106808 Thank you, Olivier --
Re: What timeout controls the scripts
Jean-Louis, There is no parameter for that timeout. It is a constant in the program. CONNECT_TIMEOUT in the server-src/chunker.c file Running the script on the client might fix the issue execute-where client Even runing on the client it will take more than 300 seconds, would the chunker wait on the script to finish on the client? Thank you, Olivier Jean-Louis On 09/24/2014 12:04 AM, Olivier Nicole wrote: Hi, For one specific DLE, I need to do a snapshot, through a pre-del-backup script. But the script takes quite some time to complete (up to a couple of hours). What timeout should I define to make Amanda wait for the end of the script before it can chunk the result? Example for the DLE amanda /virtual/mybackups/st106808 chunker.20140924001916.debug times out after 300 seconds: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: start at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: rename at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: START 20140924000501 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: PORT-WRITE 11-00015 /holding/20140924000501/amanda._virtual_mybackups_st106808.0 amanda 9efefbff1f /virtual/mybackups/st106808 0 1970:1:1:0:0:0 10485760 GNUTAR 500064 |;auth=bsd;srvcomp-best;index; ... Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: stream_accept: timeout after 300 seconds Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: putresult: 11 TRY-AGAIN Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: critical (fatal): startup_chunker failed: error accepting header stream: Operation timed out and driver.20140924000501.debug, the script takes 45 minutes to complete: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: driver: Spawning /usr/local/libexec/amanda/application/vmware vmware PRE-DLE-BACKUP --execute-where server --config normal --host amanda --disk /virtual/mybackups/st106808 --level 0 in pipeline Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: zorglub Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: PRE-DLE-BACKUP st106808 Wed Sep 24 00:19:18 2014: thd-0x804c6ce00: driver: script: We need to backup that one st106808 ... Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: 2014-09-23 18:05:52 -- info: == ghettoVCB LOG END Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: VMware snapshot OK for st106808 Thank you, Olivier --
What timeout controls the scripts
Hi, For one specific DLE, I need to do a snapshot, through a pre-del-backup script. But the script takes quite some time to complete (up to a couple of hours). What timeout should I define to make Amanda wait for the end of the script before it can chunk the result? Example for the DLE amanda /virtual/mybackups/st106808 chunker.20140924001916.debug times out after 300 seconds: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: start at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: pid 86096 ruid 10014 euid 10014 version 3.3.2: rename at Wed Sep 24 00:19:16 2014 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: START 20140924000501 Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: chunker: getcmd: PORT-WRITE 11-00015 /holding/20140924000501/amanda._virtual_mybackups_st106808.0 amanda 9efefbff1f /virtual/mybackups/st106808 0 1970:1:1:0:0:0 10485760 GNUTAR 500064 |;auth=bsd;srvcomp-best;index; ... Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: stream_accept: timeout after 300 seconds Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: putresult: 11 TRY-AGAIN Wed Sep 24 00:24:17 2014: thd-0x804c6ce00: chunker: critical (fatal): startup_chunker failed: error accepting header stream: Operation timed out and driver.20140924000501.debug, the script takes 45 minutes to complete: Wed Sep 24 00:19:16 2014: thd-0x804c6ce00: driver: Spawning /usr/local/libexec/amanda/application/vmware vmware PRE-DLE-BACKUP --execute-where server --config normal --host amanda --disk /virtual/mybackups/st106808 --level 0 in pipeline Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: zorglub Wed Sep 24 00:19:17 2014: thd-0x804c6ce00: driver: script: PRE-DLE-BACKUP st106808 Wed Sep 24 00:19:18 2014: thd-0x804c6ce00: driver: script: We need to backup that one st106808 ... Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: 2014-09-23 18:05:52 -- info: == ghettoVCB LOG END Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: Wed Sep 24 01:05:54 2014: thd-0x804c6ce00: driver: script: VMware snapshot OK for st106808 Thank you, Olivier --
sendsize without gnutar
Hi, I am looking at the poorman way to backup VMware guest machines. I have a script that can do a snapshot, then move that snapshot to some disk where Amanda can save it (then remove the snapshot). It's ugly because it does not support any kind of granularity and only allows full abck-up. But it is still better than nothing. Doing the snapshot will be run through Amanda pre and post scripts. But I am wondering how to do for the size estimate: my script can return the estimate size (the size of the allocated virtual disk). Usually the size if computed by a gnutar --total... but I don't need to run it, I have no data to give it to read, in fact the snapshot will only be generated at the dump time, if and only if the planner decides there should be a dump. How to arrange my configuration for a pre-script to return the estimated size and gtar --total be avoided? Best regards, Olivier --
Re: sendsize without gnutar
Jean-Louis, Thank you. Set estimate server in the dle. But that means there is no estimae (at least the first time) while I could provide an estimate, through a pre script, not through tar. Best regards, Olivier Jean-Louis On 09/15/2014 06:49 AM, Olivier Nicole wrote: Hi, I am looking at the poorman way to backup VMware guest machines. I have a script that can do a snapshot, then move that snapshot to some disk where Amanda can save it (then remove the snapshot). It's ugly because it does not support any kind of granularity and only allows full abck-up. But it is still better than nothing. Doing the snapshot will be run through Amanda pre and post scripts. But I am wondering how to do for the size estimate: my script can return the estimate size (the size of the allocated virtual disk). Usually the size if computed by a gnutar --total... but I don't need to run it, I have no data to give it to read, in fact the snapshot will only be generated at the dump time, if and only if the planner decides there should be a dump. How to arrange my configuration for a pre-script to return the estimated size and gtar --total be avoided? Best regards, Olivier --
Re: reconstruct tapelist from logs ?
Stefan, I know it doies not answer your question, but after each run of amdump, I run a script that rsync all amanda files/config/indexes/etc. to a different server. I also keep a rotation of 10 backward copies of tapelist. Plus the whole information is being emailed to myself (with automatic forward of my email to the email backup machine and my gmail account). That way, I am pretty sure I won't loose anything :) The script is in http://www.cs.ait.ac.th/laboratory/amanda/amdatabase I recently faced a mangled tapelist, but luckily, I only had to reconstruct the 4 ou 5 last days. That is when I added the rotation copied of tapelist. Best regards, Olivier --
Re: Question on the one-filesystem option
Gene, So in a roundabout way, tar's mouthyness coaxed me into buying a better printer. And if the excludes work tonight, I'm happy, camping or... If I may... I think the solution suggested by Nathan does not lean toward the excludes. Solving your problem by using a crafted exclude list that makes tar avoids all mount point directories and synlinks pointing to other filesystems has several drawnbacks. - most of the time, when you will upgrade your system, you may have to upgrade your update list, wondering once more why tar is spitting an error at you. - in the future, a system upgrade may result in merging two file systems into one, your exclude will still apply, that part will silently be ignbored in your backup My uinderstanding is that you should not play with the exclude list, let tar complain, let complains be logged (usefull for later debuging) but ignore these complains in the finale report (now I have no clue on how to do that). This looks like a more sustainable solution to me. Best regards, Olivier --
Re: amrecover works, normal amanda backup, logging connection refused
Gene, On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett ghesk...@wdtv.com wrote: Greeting Jean-Louis; Trying to figure out why amanda can't backup this machine, one of the things I noticed in /etc, is that on the shop box, which works, there is not an /etc/xinetd.d but it has an old-xinetd.d with a single stanza amanda file in it. An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently accessed a few minutes ago by my amcheck from the server. However, on the new install on the machine that is failing to allow the connection, there is an /etc/xinet.d, with an amanda file in it with an old last access date/time, was not 'touched' when I ran the amcheck. Its last access date/time is I believe, the date/time of the installation itself. That amanda-common is 2.6.1p1 IIRC. amcheck says: WARNING: lathe: selfcheck request failed: Connection refused There has been enough configuration done that amrecover on this machine works. There is a /var/backups/.amandahosts file, its a link to /etc/amandahosts BUT, in /etc/.amandahosts. I'll mv it to /etc/amandahosts. Ran amcheck, no change and that file was not accessed. What do I check next? netstat -na |grep 10080 You should see an UDP open on that port, else it means xinetd is not running/not listening for amanda. Olivier Thank you. Cheers, Gene Heskett -- There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Genes Web page http://geneslinuxbox.net:6309/gene US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
Re: amrecover works, normal amanda backup, logging connection refused
On Fri, Jul 18, 2014 at 11:25 PM, Gene Heskett ghesk...@wdtv.com wrote:
On Friday 18 July 2014 11:53:57 Jean-Louis Martineau did opine
And Gene did reply:
On 07/18/2014 11:39 AM, Gene Heskett wrote:
On Friday 18 July 2014 10:50:47 John Hein did opine
And Gene did reply:
Gene Heskett wrote at 10:26 -0400 on Jul 18, 2014:
Trying to figure out why amanda can't backup this machine, one
of the things I noticed in /etc, is that on the shop box, which
works, there is not an /etc/xinetd.d but it has an old-xinetd.d
with a single stanza amanda file in it.
An ls -lau shows that file, /etc/old-xinetd.d/amanda was
apparently accessed a few minutes ago by my amcheck from the
server.
However, on the new install on the machine that is failing to
allow the connection, there is an /etc/xinet.d, with an amanda
file in it with an old last access date/time, was not 'touched'
when I ran the amcheck. Its last access date/time is I
believe, the date/time of the installation itself.
That amanda-common is 2.6.1p1 IIRC.
amcheck says:
WARNING: lathe: selfcheck request failed: Connection refused
Try running xinetd -d (then amcheck) to see if (or why not) xinetd
is running amandad.
Puzzle, first I had to install it! Then got a report ending here:
Service defaults
Bind = All addresses.
Only from: All sites
No access: No blocked sites
No logging
Service configuration: amanda
id = amanda
flags = IPv4
socket_type = dgram
Protocol (name,number) = (udp,17)
port = 10080
wait = yes
user = 34
group = 34
Groups = yes
PER_SOURCE = -1
Bind = All addresses.
Server = /usr/lib/amanda/amandad
Server argv = amandad -auth=bsd amdump amindexd amidxtaped
Only from: All sites
No access: No blocked sites
No logging
14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} Started service:
amanda 14/7/18@11:27:40: DEBUG: 3748 {cnf_start_services} mask_max =
6, services_started = 1
14/7/18@11:27:40: NOTICE: 3748 {main} xinetd Version 2.3.14 started
with libwrap loadavg options compiled in.
14/7/18@11:27:40: NOTICE: 3748 {main} Started working: 1 available
service 14/7/18@11:27:40: DEBUG: 3748 {main_loop} active_services =
1
But running an amcheck on the server didn't get any further output
than what you see above. And got the same results, connection
refused. But I see an auth=bsd, where it should be bsdtcp. Fixed
that, restarted xinetd, no change in amcheck report, lathe still
refused connection. the amanda file in xinetd.d wasn't touched. So
we are a bit closer, but no biscuit. Next?
If you are using bsdtcp, then you must fix the xinetd file for it.
socket_type = stream
protocol= tcp
wait= no
Did that, and change amanda-server at the top line to the FQDN of this
machine, which now looks like this:
# default: on
# description: The amanda service
service amanda
{
# only_from = coyote.coyote.den
socket_type = stream
protocol= tcp
wait= no
user= backup
group = backup
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
}
and restarted xinetd
then an xinetd -d returns this:
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/amanda [file=/etc/xinetd.conf] [line=14]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/chargen [file=/etc/xinetd.d/chargen]
[line=16]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/daytime [file=/etc/xinetd.d/daytime]
[line=28]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/discard [file=/etc/xinetd.d/discard]
[line=26]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/echo [file=/etc/xinetd.d/echo] [line=25]
14/7/18@12:09:37: DEBUG: 3859 {handle_includedir} Reading included
configuration file: /etc/xinetd.d/time [file=/etc/xinetd.d/time] [line=26]
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing chargen
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing daytime
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing discard
14/7/18@12:09:37: DEBUG: 3859 {remove_disabled_services} removing echo
14/7/18@12:09:37:
Re: restore what, to undo amrmtape ?
What I do at the end of each dump, I run a script that: sends me the contents of tapelist by mail rsync /etc/amanda (the config directory) rsycn /var/amanda (where I have all the logs, curinfo, indexes, etc.) sends me the result of amadmin config export by mail I think I am pretty safe and could reconstruct my amanda server if anything happen. Olivier On Thu, Jun 5, 2014 at 12:12 AM, Debra S Baddorf badd...@fnal.gov wrote: Per Jean-Louis’ suggesting, I looked in oldlogs, and nothing had been moved there. I restored the whole log directory from the day before (in a scratch area), and compared things. This gave me the complete line to put back into the tapelist file. Upon careful perusal of files, I decided to also restore the curinfo/nodename/diskname/info for each DLE on the removed tape (since I had the table of contents, and knew which DLEs were affected.) The index/nodename/diskname/ files were not removed or affected. I’m doing a test restore (into a scratch area). Amanda DOES recognize that the files I asked for are on that tape, so I think it’s all good now! Restore looks good too. Yay! Deb Baddorf Fermilab On Jun 4, 2014, at 6:03 AM, Jean-Louis Martineau martin...@zmanda.com wrote: Debra, grep the label in logs/* and logs/oldlog/* If it is in logs/oldlog, mv it back to logs. Add the entry in the tapelist file, Jean-Louis On 06/04/2014 12:56 AM, Debra S Baddorf wrote: I accidentally amrmtaped a tape today. The tape is still intact, and I actually have a text file of the contents of it (TOC file.) So I can use DD and get the files back if I need them. But hey — I’m in charge of backup, doggonit — so what files can I restore so amanda will re-remember this tape? FWIW - it’s my monthly archive config, so it won’t be run again until this Saturday. (or later, if I have to delay it!)And my daily config should have the needed files to fix this. I think? Deb Baddorf Fermilab
Re: Problem with Amanda and perl
Thank John, If you run your amcleanup with ktrace and look at the resulting kdump, you might be able to find where the loading process goes wrong (e.g., perhaps something is still trying to load perl 5.14 modules). It was something dirty in the FreeBSD installer for Amanda, apparently, it would not remove all previous files, some stuff was left in /usr/local/libexec/amanda that related to previous version or Perl, even after fully deinstalling Amanda, recompiling with the new version of Perl and fully reinstalling: the old libs where still there. i resolved it by removing everything by hand. Thanks again, olivier Olivier Nicole wrote at 21:37 +0700 on Mar 31, 2014: Jean-Louis, On Mon, Mar 31, 2014 at 6:39 PM, Jean-Louis Martineau martin...@zmanda.com wrote: Olivier, Amanda must use the same perl it was compiled for. You must recompile amanda for the perl you installed or re-install the old perl. I tried that already. Updated perl, updated all perl modules, updated/recompiled amanda, that's when the problem arised. Best regards, Olivier Jean-Louis On 03/31/2014 07:25 AM, Olivier Nicole wrote: Hi, After upgrading my system, perl and Amanda won't work together anymore. The symptom is: $ amcleanup Can't load '/usr/local/lib/perl5/site_perl/5.18/auto/Amanda/Debug/libDebug.so' for module Amanda::Debug: /usr/local/lib/amanda/libamglue-3.3.2.so: Undefined symbol PL_stack_sp at /usr/local/lib/perl5/5.18/mach/DynaLoader.pm line 190. at /usr/local/lib/perl5/site_perl/5.18/Amanda/Debug.pm line 11. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. Compilation failed in require at /usr/local/sbin/amcleanup line 25. BEGIN failed--compilation aborted at /usr/local/sbin/amcleanup line 25. I have reinstalled perl as new, maiking sure that any local perl mordule was properly reinstalled; with previous 5.14 i had the same problem: $ perl -v This is perl 5, version 18, subversion 2 (v5.18.2) built for amd64-freebsd-thread-multi Copyright 1987-2013, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using man perl or perldoc perl. If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. Amanda is 3.3.2 System is: $ uname -a FreeBSD amanda.cs.ait.ac.th 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #9 r263415: Thu Mar 27 12:11:23 ICT 2014 r...@amanda.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC amd64 Right now, I am at lost about what I should be doing next, any help is gladly welcome. TIA, Olivier
Problem with Amanda and perl
Hi, After upgrading my system, perl and Amanda won't work together anymore. The symptom is: $ amcleanup Can't load '/usr/local/lib/perl5/site_perl/5.18/auto/Amanda/Debug/libDebug.so' for module Amanda::Debug: /usr/local/lib/amanda/libamglue-3.3.2.so: Undefined symbol PL_stack_sp at /usr/local/lib/perl5/5.18/mach/DynaLoader.pm line 190. at /usr/local/lib/perl5/site_perl/5.18/Amanda/Debug.pm line 11. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. Compilation failed in require at /usr/local/sbin/amcleanup line 25. BEGIN failed--compilation aborted at /usr/local/sbin/amcleanup line 25. I have reinstalled perl as new, maiking sure that any local perl mordule was properly reinstalled; with previous 5.14 i had the same problem: $ perl -v This is perl 5, version 18, subversion 2 (v5.18.2) built for amd64-freebsd-thread-multi Copyright 1987-2013, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using man perl or perldoc perl. If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. Amanda is 3.3.2 System is: $ uname -a FreeBSD amanda.cs.ait.ac.th 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #9 r263415: Thu Mar 27 12:11:23 ICT 2014 r...@amanda.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC amd64 Right now, I am at lost about what I should be doing next, any help is gladly welcome. TIA, Olivier --
Re: Problem with Amanda and perl
Jean-Louis, On Mon, Mar 31, 2014 at 6:39 PM, Jean-Louis Martineau martin...@zmanda.com wrote: Olivier, Amanda must use the same perl it was compiled for. You must recompile amanda for the perl you installed or re-install the old perl. I tried that already. Updated perl, updated all perl modules, updated/recompiled amanda, that's when the problem arised. Best regards, Olivier Jean-Louis On 03/31/2014 07:25 AM, Olivier Nicole wrote: Hi, After upgrading my system, perl and Amanda won't work together anymore. The symptom is: $ amcleanup Can't load '/usr/local/lib/perl5/site_perl/5.18/auto/Amanda/Debug/libDebug.so' for module Amanda::Debug: /usr/local/lib/amanda/libamglue-3.3.2.so: Undefined symbol PL_stack_sp at /usr/local/lib/perl5/5.18/mach/DynaLoader.pm line 190. at /usr/local/lib/perl5/site_perl/5.18/Amanda/Debug.pm line 11. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config/FoldingHash.pm line 5. Compilation failed in require at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. BEGIN failed--compilation aborted at /usr/local/lib/perl5/site_perl/5.18/Amanda/Config.pm line 750. Compilation failed in require at /usr/local/sbin/amcleanup line 25. BEGIN failed--compilation aborted at /usr/local/sbin/amcleanup line 25. I have reinstalled perl as new, maiking sure that any local perl mordule was properly reinstalled; with previous 5.14 i had the same problem: $ perl -v This is perl 5, version 18, subversion 2 (v5.18.2) built for amd64-freebsd-thread-multi Copyright 1987-2013, Larry Wall Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5 source kit. Complete documentation for Perl, including FAQ lists, should be found on this system using man perl or perldoc perl. If you have access to the Internet, point your browser at http://www.perl.org/, the Perl Home Page. Amanda is 3.3.2 System is: $ uname -a FreeBSD amanda.cs.ait.ac.th 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #9 r263415: Thu Mar 27 12:11:23 ICT 2014 r...@amanda.cs.ait.ac.th:/usr/obj/usr/src/sys/GENERIC amd64 Right now, I am at lost about what I should be doing next, any help is gladly welcome. TIA, Olivier
Re: can amanda auto-size DLE's?
Muchael, 1) if I have multiple DLE's in my disklist, then tell amdump to perform a level 0 dump of the complete config, each DLE gets written to tape as a separate dump/tar file (possibly in parts if the tar is part-size). Is that right? Yes 2) If multiple DLE's are processed in a single level 0 amdump run, with each DLE tape-size, then as many as can fit will be written to a single tape, or possibly spanning tapes. But in any case it won't be a single DLE per tape. Is that right? That looks like what I've observed so far. Yes, Amanda try to fit as many dle/tape in order to fill-in the tape. 3) I had figured that when restoring, amrestore has to read in a complete dump/tar file before it can extract even a single file. So if I have a single DLE that's ~2TB that fits (with multiple parts) on a single tape, then to restore a single file, amrestore has to read the whole tape. HOWEVER, I'm now testing restoring a single file from a large 2.1TB DLE, and the file has been restored, but the amrecover operation is still running, for quite some time after restoring the file. Why might this be happening? Your touching the essence or tapes here: they are sequential access. So in order to access one specifi DLE on the tape, the tape has to position at the very begining of the tape and read everything until it reaches that dle (the nth file on the tape). Then it has to read sequentially all that file containing the backup of a dle to find the file(s) you want to restore. I am not sure about dump, but I am pretty sure that if your tar backup was a file on a disk instead of a file on a tape, it would read sequentially from the begining of the tar file, in a similar way. Then it has to read until the end of the tar (not sure about dump) to make sure that there is no other file(s) satisfying your extraction criteria. So yes, if the file you want to extract is at the begining of your tar, it will continue reading for a certain amount of time after the file has been extracted. The recover log shows this on the client doing the recovery: [root@cfile amRecoverTest_Feb_27]# tail -f /var/log/amanda/client/jet1/amrecover.20140227135820.debug Thu Feb 27 17:23:12 2014: thd-0x25f1590: amrecover: stream_read_callback: data is still flowing 3a) Where is the recovered dump file written to by amrecover? I can't see space being used for it on either server or client. Is it streaming and untar'ing in memory, only writing the desired files to disk? In the directory from where you started the amrecover command. With tar, it will create the same exact hierarchy, reflecting the original DLE. try: find . -name myfilename -print 4) To restore from a single DLE's dump/tar file that's smaller than tape size, and exists on a tape with multiple other smaller DLE dump/tar files, amrestore can seek to the particular DLE's dump/tar file and only has to read that one file. Is that right? As mentionned above, seek on a tape is a sequential read of the tape (unless your tape is already positionned on the file x (known) and you want to read from file y, it will need to read only y-x). So assuming all the above is true, it'd be great if amdump could automatically break large DLE's into small DLE's to end up with smaller dump files and faster restore of individual files. Maybe it would happen only for level 0 dumps, so that incremental dumps would still use the same sub-DLE's used by the most recent level 0 dump. Yes, but then what happens for level above 0? You have to make your planning by hand and break your dle yourself. The issue I have is that with 30TB of data, there'd be lots of manual Depending on the size of your tapes, even with many small dle, you will most probably end-up reading the tape from the begining for every restore. If your dle is splitted on many tapes, you will have to read every tape even if the file you want was found on the first tape (I am not 100% sure about that though). fragmenting of data directories to get more easily-restorable DLE's sizes of say, 500GB each. Some top-level dirs in my main data drive have 3-6TB each, while many others have only 100GB or so. Manually breaking these into smaller DLE's once is fine, but since data gets regularly moved, added and deleted, things would quickly change and upset my smaller DLE's. Any thoughts on how I can approach this? If amanda can't do it, I thought I might try a script to create DLE's of a desired size based on disk-usage, then run the script everytime I wanted to do a new level 0 dump. That of course would mean telling amanda when I wanted to do level 0's, rather than amanda controlling it. While the script may be a good idea, running it for each level 0 will completely mess up with Amanda: remember, you don't manage/know when Amanda will do a level 0. So you don't know when to run your script. And if you remove a dle from your disklist (because you have splitted it into 2 for example), I am pretty
Re: Potential user - more questions
Michael, You may have noticed my answer to question 2a was not complete. I answered for a not parted DLE. On a second thought, as each part is exactly the size you configure (exact to the byte), I assume that each file cannot be an independent tar, so the DLE must be tar'ed into a big file first, that is then cut into chunks. I never had to manually restore a parted DLE (I would manually restore / and maybe /usr, that would give me a running Amanda and then use Amanda to restore the data; my / or /usr are smaller that the size of parts); manually restoring a DLE is easy, even with a live-cd, you really only need dd and tar (or dump/restore). It takes some precautions, but is pretty doable. Best regards, Olivier On Fri, Oct 11, 2013 at 4:16 AM, Michael Stauffer mgsta...@gmail.com wrote: Olivier and Jon, thanks for the helpful answers. I'm going to setup my redeployed backup system with Amanda. It seems enough easier than Bacula to make it worth while to make the switch, and I especially like the simple format of the dump files and the simple text indecies for cataloging backups. I'm sure you'll hear from me more while I get things going! -M On Thu, Oct 10, 2013 at 12:45 AM, Jon LaBadie j...@jgcomp.com wrote: On Wed, Oct 09, 2013 at 06:27:48PM -0400, Michael Stauffer wrote: Hi again, I've got another batch of questions while I consider switching to Amanda: 1) catalog (indecies) It seems the main catalog/database is stored in the index files. Is it straightforward to back these up? This doc (http://www.zmanda.com/protecting-amanda-server.html) sugests backing up these dirs/files to be able to restore an amanda configuration (and presumably the backup catalog): /etc/amandates, /etc/dumpdates, /etc/amanda, /var/lib/amanda. There is no built-in way to do this in amanda. The problems are they are not complete, and changing, until the backup is done. Several members of this list have described their home-grown techniques. 2) Spanning and parts Say I split my 32TB of data into DLE's of 2-3TB. a) If I set a 'part' size of 150GB (10% of native tape capacity is what I saw recommended), what is the format of each part as it's written? Is each part its own tarfile? Seems that would make it easier to restore things manually. Traditional amanda tape files, holding the complete tar or dump archive, are a 32KB header followed by the archive. Manual restoration is done with dd to skip the header and pipe the rest to the appropriate command line to restore the data. The header contains information identifying the contents, how they were created, and when. Parts alter this scheme only slightly. Each part still has a header. The header now includes info on which sequential part it is. The part name also identifies it location in the sequence. The data is simply a chunk of the complete archive. Manual restoration again is strip the headers and pipe to the restore command. b) If a part spans two volumes, what's the format of that? Is it a single tarfile that's split in two? A part will NOT span two volumes. If the end of the media is reached, the part is restarted on the next volume. c) What's the manual restore process for such a spanned part? cat the two parts together and pipe to tar for extraction? 3) Restoring w/out Amanda I thought data was written to tape as tar files. But this page suggests a dumpfile is only readable by Amanda apps. Is a dumpfile something else? http://wiki.zmanda.com/index.php/Dumpfile I think the author meant there are no standard unix/linux commands that know the header + data layout. The dumpfiles can be handled with amanda commands or as described above, the operator can use standard commands when armed with knowledge of the layout. 4) holding disk and flushing I see how flushing can be forced when the holding disk has a certain % of tape size. Can a flush be forced every N days? The idea here would be to get data to tape at a min of every week or so, should successive incrementals be small. Dumping to holding disk without taping can be done. Then have a crontable entry to flush when you want. This can done with a separate amflush command, or by varying amdump options. 5) alerting Is there a provision for email and/or other alerts on job completion or error, etc? Most amanda admins have an amreport emailed to them at amdump or amflush completion. As the cron entry can be a shell script, you could customize greatly. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
Connection reset by peer
Hi, I have a strange combination of errors: [data read: Connection reset by peer] [index read: Connection reset by peer] [missing size line from sendbackup] I giigled for these, but they never show up combined like that. Below is the report and amdump. Thank you if you can tell me what is going on. Best regards, Olivier FAILURE DUMP SUMMARY: ufo1000 /web lev 0 FAILED [data read: Connection reset by peer] ufo1000 /web lev 0 FAILED [index read: Connection reset by peer] FAILED DUMP DETAILS: /-- ufo1000 /web lev 0 FAILED [data read: Connection reset by peer] sendbackup: start [ufo1000:/web level 0] sendbackup: info BACKUP=/usr/local/bin/gtar sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ... sendbackup: info end ? dumper: strange [missing size line from sendbackup] \ /-- ufo1000 /web lev 0 FAILED [index read: Connection reset by peer] sendbackup: start [ufo1000:/web level 0] sendbackup: info BACKUP=/usr/local/bin/gtar sendbackup: info RECOVER_CMD=/usr/local/bin/gtar -xpGf - ... sendbackup: info end ? dumper: strange [missing size line from sendbackup] \ - amdump: start at Thu Nov 29 15:17:16 ICT 2012 amdump: datestamp 20121129 amdump: starttime 20121129151716 amdump: starttime-locale-independent 2012-11-29 15:17:16 ICT driver: pid 5309 executable /usr/local/libexec/amanda/driver version 3.3.2 planner: pid 5308 executable /usr/local/libexec/amanda/planner version 3.3.2 planner: build: VERSION=Amanda-3.3.2 planner:BUILT_DATE=Tue Nov 20 15:38:37 ICT 2012 BUILT_MACH= planner:BUILT_REV=4847 BUILT_BRANCH=community_3_3_2 CC=gcc planner: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin planner:libexecdir=/usr/local/libexec/amanda planner:amlibexecdir=/usr/local/libexec/amanda planner:mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda planner:AMANDA_DBGDIR=/tmp/amanda planner:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ planner:RDEV_PREFIX=/dev/ DUMP=/sbin/dump planner:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF planner:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF planner:SAMBA_CLIENT=/usr/local/bin/smbclient planner:GNUTAR=/usr/local/bin/gtar COMPRESS_PATH=/usr/bin/gzip planner:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=UNDEF MAILER=UNDEF planner:listed_incr_dir=/usr/local/var/amanda/gnutar-lists planner: defs: DEFAULT_SERVER=amanda.cs.ait.ac.th planner:DEFAULT_CONFIG=DailySet1 planner:DEFAULT_TAPE_SERVER=amanda.cs.ait.ac.th planner:DEFAULT_TAPE_DEVICE= NEED_STRSTR AMFLOCK_POSIX planner:AMFLOCK_FLOCK AMFLOCK_LOCKF AMFLOCK_LNLOCK AMANDA_DEBUG_DAYS=4 planner:BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=amanda planner:CHECK_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz planner:COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best planner:UNCOMPRESS_OPT=-dc READING CONF INFO... planner: timestamp 20121129151716 planner: tape_length is set from tape length (115343360 KB) * runtapes (5) == 576716800 KB planner: time 0.001: startup took 0.001 secs SENDING FLUSHES... ENDFLUSH SETTING UP FOR ESTIMATES... planner: time 0.001: setting up estimates for ufo1000:/web ufo1000:/web overdue 15666 days for level 0 setup_estimate: ufo1000:/web: command 0, options: nonelast_level 0 next_level0 -15666 level_days 1getting estimates 0 (-3) 1 (-3) -1 (-3) planner: time 0.001: setting up estimates took 0.000 secs GETTING ESTIMATES... driver: tape size 115343360 driver: adding holding disk 0 dir /holding size 467164160 chunksize 10485760 reserving 0 out of 467164160 for degraded-mode dumps driver: started dumper0 pid 5310 driver: send-cmd time 0.023 to dumper0: START 20121129151716 driver: started dumper1 pid 5311 driver: send-cmd time 0.023 to dumper1: START 20121129151716 driver: started dumper2 pid 5312 driver: send-cmd time 0.024 to dumper2: START 20121129151716 driver: started dumper3 pid 5313 driver: send-cmd time 0.025 to dumper3: START 20121129151716 driver: started dumper4 pid 5314 driver: send-cmd time 0.025 to dumper4: START 20121129151716 driver: started dumper5 pid 5315 driver: send-cmd time 0.026 to dumper5: START 20121129151716 driver: started dumper6 pid 5316 driver: send-cmd time 0.026 to dumper6: START 20121129151716 driver: started dumper7 pid 5317 driver: send-cmd time 0.027 to dumper7: START 20121129151716 driver: started dumper8 pid 5318 driver: send-cmd time 0.027 to dumper8: START 20121129151716 driver: started dumper9 pid 5319 driver: send-cmd time 0.028 to dumper9: START 20121129151716 driver: started dumper10 pid 5320 driver: send-cmd time 0.028 to dumper10: START 20121129151716 driver: started dumper11 pid 5321 driver: send-cmd time 0.035 to dumper11: START 20121129151716 driver: started dumper12 pid 5322 driver: send-cmd time 0.037 to dumper12: START 20121129151716 driver: started dumper13 pid 5323 driver: send-cmd time 0.037 to
Re: [Amanda-users] Help in installing Amanda Client in FreeBSD 8.0/9.0
Jose, Im new to Amanda. I have installed Amanda Server on a CentOS but on trying to install it on the FreeBSD clients I have I am experiencing hitches. Any help you can accord will be highly appreciated. I am not sure what are your problem sin installing amanda client on FreeBSD. Go to /usr/ports/misc/amanda-client make make install That should do it. Else you ned to be specific on the type of propblems you are facing. Best regards, Olivier
Re: FreeBSD 8.3 killed my Amanda
: since NODATE 1353407966.281734: sendbackup: options `' 1353407966.281843: sendbackup: start: oak1000:/home/java lev 0 1353407966.281895: sendbackup: pipespawnv: stdoutfd is 50 1353407966.281915: sendbackup: Spawning /usr/bin/gzip /usr/bin/gzip --best in pipeline 1353407966.282331: sendbackup: gnutar: pid 35324: /usr/bin/gzip1353407966.282390: sendbackup: pid 35324: /usr/bin/gzip --best 1353407966.282655: sendbackup: doing level 0 dump as listed-incremental to '/usr/local/var/amanda/gnutar-lists/oak1000_home_java_0.new' 1353407966.283941: sendbackup: pipespawnv: stdoutfd is 6 1353407966.284178: sendbackup: Spawning /usr/local/libexec/amanda/runtar runtar normal /usr/local/bin/gtar --create --file - --directory /home/java --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/oak1000_home_java_0.new --sparse --ignore-failed-read --totals . in pipeline 1353407966.284885: sendbackup: Started index creator: /usr/local/bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' 1353407966.284996: sendbackup: gnutar: /usr/local/libexec/amanda/runtar: pid 35327 1353407966.285135: sendbackup: Started backup 1353408441.084565: sendbackup: critical (fatal): index tee cannot write [Broken pipe] I can put all the log file to some common place if needed. Best regards, olivier On Mon, Nov 19, 2012 at 04:30:17PM +0700, Olivier Nicole wrote: Hi, I apologize for coming crying here, but since I updated my manda server to FreeBSD 8.3 (from 7.4), any big DLE will fail. I tried many versions of Amanda (2.5, 2.6, 3.3), with no success. Before I start sending debug, maybe there is an obvious action I have forgotten. I have tried, from the client side to tar|gzip|ssh cat /dev/null the big DLE, and it went on with no problem.
Re: FreeBSD 8.3 killed my Amanda
Jon, I apologize for coming crying here, but since I updated my manda server to FreeBSD 8.3 (from 7.4), any big DLE will fail. I tried many versions of Amanda (2.5, 2.6, 3.3), with no success. Before I start sending debug, maybe there is an obvious action I have forgotten. I have tried, from the client side to tar|gzip|ssh cat /dev/null the big DLE, and it went on with no problem. best regards, Might there have been a udp/tcp change in the settings? In the setting of the operating system? It could be, that is why I tried to manually tar and send through SSH between the 2 machines, and it went through. Best regards, Olivier
Re: FreeBSD 8.3 killed my Amanda
Dear Jean-Louis, You should start with the beginning, what is the error message you get in the email report? Hostname: amanda.cs.ait.ac.th Org : CSIM Normal Config : normal Date: November 20, 2012 There are 3587383k of dumps left in the holding disk. They will be flushed on the next run. The next 5 tapes Amanda expects to use are: CSIM-set-041, CSIM-set-056, CSIM-set-007, CSIM-set-008, CSIM-set-009. FAILURE DUMP SUMMARY: oak1000 /home/java lev 0 FAILED [data timeout] oak1000 /home/java lev 0 FAILED [data timeout] 'data timeout', it is a good starting point. Can you tell me exactly which amanda version you are using on the server? Is it the released 3.3.2 or something more recent? I installed it from FreeBSD ports and it reports amanda-server-3.3.2,1. The port was dated October 2nd, 2012, the tarball being called amanda-3.3.2.tar.gz with an SHA256 of cb40e8aa601e3d106e7d78338b745e5b9c0cd41daaab7937fc23d1b4cf585424 amcheck reports the version 3.3.2 Best egards, Olivier
FreeBSD 8.3 killed my Amanda
Hi, I apologize for coming crying here, but since I updated my manda server to FreeBSD 8.3 (from 7.4), any big DLE will fail. I tried many versions of Amanda (2.5, 2.6, 3.3), with no success. Before I start sending debug, maybe there is an obvious action I have forgotten. I have tried, from the client side to tar|gzip|ssh cat /dev/null the big DLE, and it went on with no problem. best regards, Olivier
Live recovery CD
Hi, I wonder if anyone ever put together an Amanda live recovery CD. There are many Linux distro that have a live CD, it woul donly nned to add amrecover to that live CD to be up and running. Booting the live CD, one can repartition/reformat his disk, and amrecover will allow to restore the data. Best regards, Olivier
Fix the order of the dump in Amanda
Hi, I am using amanda 2.5.1 on the server, is there a way to tell Amanda that dump of certain DLE should be started as soon as possible? I am bacukuping some Unix machines and some Windows machines via Samba. The backup via Samba takes very long time, so I would like to have those started very soon (so they are finished before the user come back to work next morning). Best regards, Olivier
Re: how large must the data volume be...
Hi, ...so that tape drives become more cost-effective than storing everything on HD's? From my past experience, 50GB SLR100 tape costs $100 while for that price I can have a 500GB disk... Olivier
Re: Web interface for Amanda
Hi marc, This interface is written in PHP (with a small part in Perl) and should run on the Amanda server, under the Amanda user and group. Is it a good idea to let a web based application run with access rights of the user that collect the data of all my servers? Wouldn't it be better, at least to set the rights of the files you edit so that the webserver user can only change them? I think, if the webserver can edit .amandahosts (), a security whole in your script may allow to add his computer and restore all data. It's worse enough if only the passwords of the shares are stolen. If only you knew how it was done when it was written in Perl :) The problem is that amandapass must be mode 600 and belong to amanda:amanda. If the web server does not run as amanda:amanda it needs some mechanism (home made?) to allow to edit the file. That mechanism could introduce other security threat. The web server runinning the interface runs only that interface and is not accessible/visible from outside. OK that is not full security, but then amanda server is not physically secured either, any local user can access the machine and could steal the hard disk. Or steal one of the disk holding the virtual tapes. Also one point about your documentation: Step 4: Turn off the firewall In some case, Windows XP will not let you access to your PC with this interface. You must turn off your firewall. Why having a firewall, if users (are told) allways deactivate them on every problem? Isn't a firewall totaly useless, if it is deactivated (even if only for a short time)? I think a better hint would be, to ensure, that subnet of the server or better the backup host itself is only allowed to access the share. Default for the file shares rule is current subnet. This is normally the problem, if the server is in a different subnet and can't access the client. I was too lazy to dig it out, plus it contains a lot of Microsoft uncertainity, but the first time I tried to access to a new machine (new XP install, SP3) smbclient would not connect. Without the firewall it did connect. Later on, it would connect even with the firewall activated. My chest for magic spell being currently empty (debugging of XP) I choose to leave it like that. It happened once, so it may happen to others... Thanks for the remarks, Olivier
Re: Web interface for Amanda
Write the entries to amandapass~ and before your cronjob starts amdump, cp amandapass~ amandapass Good idea. any local user can access the machine and could steal the hard disk. Or steal one of the disk holding the virtual tapes. Aren't the doors locked? Or the servers secured in a different way? No :) But we are only a computer science department in a University, we are not manipulating any sensitive information. Bests, Olivier
Web interface for Amanda
Hi, This web interface (http://www.cs.ait.ac.th/laboratory/amanda/index.shtml) can be used to let your users register their Windows Microsoft PC to Amanda backup. First the user has to set a special backup user and to define shares to be accessible for backup. Then, using the interface, the user can add the shares to Amanda, as incremental backup or as full backup only. The interface script will modify the DLE and amandapass files accordingly. This interface is written in PHP (with a small part in Perl) and should run on the Amanda server, under the Amanda user and group. So far the interface has been tested for Windows 2000 and Windows XP only. It should work with Windows NT; the part about old Windows 98 exists only as a phantom. I will add Windows Vista as soon as I have the need for it. I once wrote this interface in Perl and I recently ported to PHP. I have not distribution package, it was written for our internal usage only, but you can contact me, I will be more than happy to share my work with you. Bests, Olivier
Syntax error in chg-disk
Hi, I am using chg-disk on Amanda 2.5.1p3 on FreeBSD and while I was trying it by hand, I found a Bourne Sheel syntax error: around the line 83, it should read: if test X$TAPE = X; then With a single = instead of the == operator found in the script. I am not sure it is an error in Amanda distribution or in the port made for FreeBSD. Best regards, Olivier
Changer policy
Hi, I have a brand new Amanda server, that uses virtual tapes. My virtual tapes are set on external hard disks, but I can only physically connect one disk at a time. I uses runtapes 5. So I can end up in a situation where I have 2 vtapes left one a disk, and where I must change disk in the middle of a dump. I beleive this is close to the situation of a tape caroussel, where one wants to reload the caroussel in the middle of a dump. I'd like to know if the model bellow makes sense with Amanda, does it break the general idea or not? Will it work if I write a changer that would wait for manual change of the disk? The dumps would finish to the holding disks and the taper would wait for manual change of the disk before finishing to write on the tape (wait would be several hours). I see that amcheck physically tries to access the tapes, so in a situation with 2 tapes left on a disk and 3 tapes from the new disk, amcheck would request the user tou change disk, that is not really necessary, is there any other command that is likely to access the changer (beside the amdump/amflush and restore). Is there a command to get the label of the tape loaded in the tape device? Does it exist a changer that allow the manual change of a caroussel, so I don't have to redesign everything from scratch? (I mean the Amanda phylosophy, not the exact way to load/eject a caroussel or mout/unmout a disk). Best regards, Olivier
Re: Changer policy
Hi Gerrit, I use tpchanger chg-disk# VTAPES the tape-changer glue script So do I, for the n first vtapes in the first disk, but chg-disk cannot access the vtapes n+1 t0 2n that are on the second disk: this second disk should be manually loaded first. Olivier
Re: Problem Backing Up NFS SmartStor
Hi, I have a Promise SmartStor, a network drive. It's NFS mounted on a Red Hat server. Sometimes it gets backed up, other times I get: whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [dumper returned FAILED] whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [data timeout] whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [cannot read header: got 0 instead of 32768] whimsy.med.utah.edu/sstore/9gb lev 0 FAILED [too many dumper retry: [request failed: timeout waiting for REP]] Just a wild guess, but a Google search yesterday on cannot read header: got 0 instead of lead me to problems with IPv6/IPv4. I recompiled Amanda to use only IPv4 (./configure --without-ipv6) and the problem is gone. To further diagnoze the problem, look at the debug files, you would see that one side of Amanda opened a socket on IPv6: amandad.20080821100912.debug:amandad: time 2.679: stream_server: waiting for connection: ::.51629 while the other side try to connect on IPv4: dumper.20080821100912.debug:dumper: connected to 10.41.170.14.51629 I used information from http://archive.netbsd.se/?ml=pkgsrc-usersa=2008-02t=6414321 As you don't mention anything about the operating system of the server and the client, I don't know if that helps. I am running FreeBSD 6.3 on both sides. Best regards, Olivier
What tapedev is used by Amanda
Hi, Does Amanda use the tapedev defined in amanda.conf or the tapedev returned by the changer? If Amanda uses the tapedev returned by the changer, I think that chg-disk could be rewritten to avoid using symlinks, returning the directory of the slot each time, and so could work with file systems that does not implement symlinks (NTFS/FAT32 USB disks). Best regards, Olivier
amanda-2.5.1p3 ignores no-reuse
Hello, I am setting up a new Amanda server. Using virtual tapes on USB disk, it seems to be fast enough (20 to 40 MBps) depending on the hardware, the speed of the holding disks, etc. Faster than the dump, so no problem. I am currently hit by the IPv6 only problem on the client side, but that one I identified and hope to solve it by reinstalling amanda for IPv4 only. The problem is the following: I have 3 USB disks for virtual tapes, and only one is connected at a given time, so in tapelist I marked the tapes that are not accessible with no-reuse. They cannot be used because the disk is not online. Despite, the report at the end of a dump mention that amanda will try to use these; These dumps were to tape CSIM-set-1-06. The next 5 tapes Amanda expects to use are: 5 new tapes. The next 5 new tapes already labelled are: CSIM-set-1-07, CSIM-set-1-08, CSIM-set-1-09, CSIM-set-2-01, CSIM-set-2-02. The tapes CSIM-set-2-01, CSIM-set-2-02 are on a disk that is not online and they are marked no-reuse: 0 CSIM-set-2-02 no-reuse 0 CSIM-set-2-01 no-reuse 0 CSIM-set-1-09 reuse 0 CSIM-set-1-08 reuse 0 CSIM-set-1-07 reuse Is that a feature? Best regards, Olivier
Server to client connection refused
Hi, Since I upgraded Amanda client to 2.5.2p1 I could not back up that specific client. Server is running 2.4.2p2 and working well with many different versions of clients. The sendsize if OK, but the sendbackup fails. On the server side I see: driver: send-cmd time 1268.504 to dumper2: FILE-DUMP 00-00029 /holding1/20071030/ufo1000._usr.0 ufo1000 /usr 0 1970:1:1:0:0:0 1048576 GNUTAR 5057184 |;bsd-auth;srvcomp-best;index; driver: state time 1268.506 free kps: 2532277 space: 28302702 taper: DOWN idle-dumpers: 17 qlen tapeq: 0 runq: 12 roomq: 0 wakeup: 86400 driver-idle: client-constrained driver: interface-state time 1268.506 if : free 110 if DISK: free 32 if E100S: free 8 if E10S: free 79868 if E1G: free 796013 if E100M: free 76396 if E10M: free 8 driver: hdisk-state time 1268.506 hdisk 0: free 10602966 dumpers 6 hdisk 1: free 0 dumpers 0 hdisk 2: free 8853920 dumpers 2 hdisk 3: free 8845816 dumpers 5 driver: result time 1268.506 from dumper13: RQ-MORE-DISK 13-00014 driver: send-cmd time 1268.506 to dumper13: CONTINUE /holding3/20071030/cluster._state_partition1_home.2 1048576 2752 driver: state time 1268.508 free kps: 2532277 space: 28299950 taper: DOWN idle-dumpers: 17 qlen tapeq: 0 runq: 12 roomq: 0 wakeup: 86400 driver-idle: client-constrained driver: interface-state time 1268.508 if : free 110 if DISK: free 32 if E100S: free 8 if E10S: free 79868 if E1G: free 796013 if E100M: free 76396 if E10M: free 8 driver: hdisk-state time 1268.508 hdisk 0: free 10600214 dumpers 6 hdisk 1: free 0 dumpers 0 hdisk 2: free 8853920 dumpers 2 hdisk 3: free 8845816 dumpers 5 dumper: stream_client: connect(64324) failed: Connection refused driver: result time 1268.530 from dumper2: TRY-AGAIN 00-00029 [could not connect to data port: Connection refused] And on the client: sendbackup: debug 1 pid 91922 ruid 14 euid 14: start at Tue Oct 30 01:11:10 2007 sendbackup: version 2.5.2p1 Could not open conf file /usr/local/etc/amanda/amanda-client.conf: No such fil e or directory sendbackup req: GNUTAR /usr 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;srvcomp-best; index; parsed request as: program `GNUTAR' disk `/usr' device `/usr' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;srvcomp-best;index;' sendbackup: start: ufo1000:/usr lev 0 sendbackup-gnutar: time 0.000: doing level 0 dump as listed-incremental to '/usr /local/var/amanda/gnutar-lists/ufo1000_usr_0.new' sendbackup-gnutar: time 0.002: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.002: spawning /usr/local/libexec/amanda/runtar in pipeline sendbackup: time 0.002: argument list: runtar NOCONFIG gtar --create --file - -- directory /usr --one-file-system --listed-incremental /usr/local/var/amanda/gnut ar-lists/ufo1000_usr_0.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: time 0.003: /usr/local/libexec/amanda/runtar: pid 91925 sendbackup: time 0.003: started backup sendbackup: time 0.009: started index creator: /usr/local/bin/mygtar -tf - 2/d ev/null | sed -e 's/^\.//' sendbackup: time 50.112: index tee cannot write [Broken pipe] sendbackup: time 50.112: pid 91924 finish time Tue Oct 30 01:12:00 2007 I have hard time ti figure why there is a bronken connection after only 50 seconds. There is no firewall between client and server. TIA, Olivier
Connection problem between Server and client
Hi,
I recently yupgraded one client to 2.5.2p1, while the server is still
runing 2.4.2p2.
Now the server cannot contact that specific client:
* From the email report:
ufo1000/ftp lev 0 FAILED [could not connect to ufo1000]
* From server log:
FAIL driver ufo1000 /ftp 0 [could not connect to ufo1000]
* But from the client log files:
sendsize[14149]: time 150.133: calculating for amname /ftp, dirname /ftp,
spindle 0
sendsize[14149]: time 150.133: getting size via gnutar for /ftp level 0
sendsize[14149]: time 150.134: spawning /usr/local/libexec/amanda/runtar in
pipe
line
sendsize[14149]: time 150.134: argument list: runtar NOCONFIG
/usr/local/bin/mygtar --create --file /dev/null --directory /ftp
--one-file-system --listed-incremental
/usr/local/var/amanda/gnutar-lists/ufo1000_ftp_0.new --sparse
--ignore-failed-read --totals .
sendsize[14149]: time 151.291: Total bytes written: 3540633600 (3.3GB,
3.1GB/s)
sendsize[14149]: time 151.292: .
sendsize[14149]: time 151.292: estimate time for /ftp level 0: 1.158
sendsize[14149]: time 151.292: estimate size for /ftp level 0: 3457650 KB
sendsize[14149]: time 151.292: waiting for runtar /ftp child
sendsize[14149]: time 151.292: after runtar /ftp wait
sendsize[14149]: time 151.293: done with amname /ftp dirname /ftp spindle 0
sendsize[14100]: time 151.293: child 14149 terminated normally
runtar: debug 1 pid 14150 ruid 14 euid 0: start at Thu Oct 25 00:53:27 2007
runtar: time 0.000: version 2.5.2p1
/usr/local/bin/mygtar version: Insecure $ENV{PATH} while running setuid at
/usr/
local/bin/mygtar line 34.
config: NOCONFIG
running: /usr/local/bin/mygtar: '/usr/local/bin/mygtar' '--create' '--file'
'/de
v/null' '--directory' '/ftp' '--one-file-system' '--listed-incremental'
'/usr/local/var/amanda/gnutar-lists/ufo1000_ftp_0.new' '--sparse'
'--ignore-failed-read' '--totals' '.'
runtar: time 0.040: pid 14150 finish time Thu Oct 25 00:53:27 2007
runtar: debug 1 pid 14481 ruid 14 euid 0: start at Thu Oct 25 01:14:01 2007
runtar: time 0.000: version 2.5.2p1
/usr/local/bin/mygtar version: Insecure $ENV{PATH} while running setuid at
/usr/
local/bin/mygtar line 34.
config: NOCONFIG
running: /usr/local/bin/mygtar: 'gtar' '--create' '--file' '-' '--directory'
'/ftp' '--one-file-system' '--listed-incremental'
'/usr/local/var/amanda/gnutar-lists/ufo1000_ftp_0.new' '--sparse'
'--ignore-failed-read' '--totals' '.'
runtar: time 0.085: pid 14481 finish time Thu Oct 25 01:14:01 2007
runtar: debug 1 pid 14565 ruid 14 euid 0: start at Thu Oct 25 01:15:01 2007
runtar: time 0.000: version 2.5.2p1
/usr/local/bin/mygtar version: Insecure $ENV{PATH} while running setuid at
/usr/
local/bin/mygtar line 34.
config: NOCONFIG
running: /usr/local/bin/mygtar: 'gtar' '--create' '--file' '-' '--directory'
'/ftp' '--one-file-system' '--listed-incremental'
'/usr/local/var/amanda/gnutar-lists/ufo1000_ftp_0.new' '--sparse'
'--ignore-failed-read' '--totals' '.'
runtar: time 0.086: pid 14565 finish time Thu Oct 25 01:15:01 2007
Best regards,
Olivier
Re: cleaning tapes and integration into Amanda backup scheme?
My Sun L9 array has told me it needs a cleaning tape run. I have one so that's no problem but what I'd like to know is if there is a way that Amanda can receive info from the tape drive about the requirement for cleaning and co-ordinate cleaning tape runs as part of the overall backup stragegy? My strategy, all human based, is to have the cleaning tape on the pile of the next set of 6 tapes to be used. I have my tapes pool divided into 3 sets of 6, once I have run through the current set, I move the stack to the back and come up with a new stack, on top of which is the cleaning tape. Bests, olivier
Configure failing on FreeBSD 5.5 for Amanda 2-5-2p1
Hi, I tried to install an amanda client 2.5.2p1 on a FreeBSD 5.5 machine. For some reason the configure is failing somewhere in the SSH security. As I am not using ssh, I just cut out the part from the configure script. Error is: ufoon: ./configure --with-user=amanda --with-group=amanda --without-ssh-security [...] checking for egrep... /usr/bin/egrep checking for lint... /usr/bin/lint lint: illegal option -- f usage: lint [-abceghprvwxzHF] [-s|-t] [-i|-nu] [-Dname[=def]] [-Uname] [-X id[,id]... [-Idirectory] [-Ldirectory] [-llibrary] [-ooutputfile] file... lint [-abceghprvwzHF] [-s|-t] -Clibrary [-Dname[=def]] [-X id[,id]... [-Idirectory] [-Uname] [-Bpath] file ... checking for raw ftape device... /dev/null checking for Kerberos and Amanda kerberos4 bits... no ./configure.lineno: 13536: Syntax error: Bad substitution ufoon: Note also the error on lint. Best regards, Olivier
Re: backup/recover using tar and hard links
Hi, I'm using amanda 2.4.5 and a supported gnutar on Fedora. One of the servers we're backing up is a Cyrus IMAP server with a lot of mailboxes. Cyrus makes hard links when the same message is sent to multiple people (when they're on the same cyrus partition). That sounds a strange behaviour to me: every time one user read the message, the file is modified (Status: R added) so the hard link is broken for that user. I'm trying to recover the contents of a mailbox, but it contains some hard links to mail messages in other mailboxes. Some of those other mailboxes (that contained the actual file) have been removed (deleted) in the past few months. The amrecover (tar actually) program complains that it cannot hard link to filename because the other mailbox/file doesn't exist: tar: ./user/student5/626.: Cannot hard link to `./user/student2/555.': No such file or directory. That aso sounds weird to me: a hard link is a single file sharde in multiple directories, the file does not reside inside one directory and is not linked from others, it is the same file under different names. I'm now facing two issues: - how can I (easily) recover the rest (I could make dummy directories/files, but is there an easier way)? Short answer, if you have enough temporary disk space, restore all the mailboxes and you should have no more missing link problems. Then you should be able to move only the malbox of that specific user. Best regards, Olivier
Re: Amanda failing on sendsize
Hi, Here is the backtrace for failling sendsize: (gdb) run Starting program: /usr/ports/misc/amanda-client/work/amanda-2.5.1p3/client-src/.libs/sendsize OPTIONS maxdumps=1;hostname=ufo1000; OPTIONS GNUTAR /ftp 0 1970:1:1:0:0:0 0 GNUTAR /web 0 1970:1:1:0:0:0 1 GNUTAR /web 2 2007:10:5:18:16:10 1 GNUTAR /web 3 2007:10:9:18:8:22 1 GNUTAR /var 0 1970:1:1:0:0:0 0 GNUTAR /usr 0 1970:1:1:0:0:0 0 GNUTAR / 0 1970:1:1:0:0:0 0 exclude-list=/usr/local/var/amanda/exclude.gtar Program received signal SIGSEGV, Segmentation fault. 0x28185a69 in strlen () from /lib/libc.so.5 (gdb) where full #0 0x28185a69 in strlen () from /lib/libc.so.5 No symbol table info available. #1 0x28090619 in debug_stralloc (s=0x280b3eeb sl.c, l=91, str=0x0) at alloc.c:232 addr = 0x805c530 #2 0x280a9e6e in append_sl (sl=0x805c520, name=0x0) at sl.c:91 a = (sle_t *) 0x805c530 #3 0x0804a84e in main (argc=1, argv=0xbfbfe928) at sendsize.c:357 level = 0 spindle = 0 prog = 0x805e380 GNUTAR calcprog = 0x0 dumpdate = 0x805e38b 1970:1:1:0:0:0 options = (option_t *) 0x805e300 program_is_wrapper = 0 est = (disk_estimates_t *) 0xbfbfe930 est1 = (disk_estimates_t *) 0xbfbfe928 est_prev = (disk_estimates_t *) 0x1 line = 0x805e380 GNUTAR s = 0x805e39d xclude-list=/usr/local/var/amanda/exclude.gtar fp = 0x805e387 / ch = 101 err_extra = 0x0 done = -1077942076 need_wait = 673288512 dumpsrunning = 671557080 disk = 0x805c2e0 / qdisk = 0x805c280 / qlist = 0x0 amdevice = 0x805c300 / qamdevice = 0x805c340 / conffile = 0x0 amandates_file = 0x805c230 /etc/amandates amandates_read = 1 (gdb) If that is of any help? Best regards, Olivier
Re: Amanda failing on sendsize
Hi, Now that I can manually run sendsize, I do get the core dump. Program received signal SIGSEGV, Segmentation fault. 0x2808f46c in debug_stralloc () from /usr/local/lib/libamanda-2.5.1p3.so How to recompile amanda with debuging symbols? I see nothing of the like in the configure script. Best regards, Olivier
Re: Amanda failing on sendsize
Hi, Is there a way to manually run sendsize? What are the arguments? When I run it by hand (with no arguments) nothing happens and it sits there for ages, when it is called via amandad, it will coredump almost at once. Olivier
Amanda failing on sendsize
Hi, I just upgraded amanda-client and gtar: gtar-1.18_1 GNU version of the traditional tar archiver amanda-client-2.5.1p3_1,1 The Advanced Maryland Automatic Network Disk Archiver on a 5.5 server FreeBSD ufo.cs.ait.ac.th 5.5-RELEASE-p15 FreeBSD 5.5-RELEASE-p15 #7: Wed Oct 3 10:17:29 ICT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 and last night bacup failed with sendsize coredump. kernel: Oct 12 00:50:59 ufo kernel: pid 64313 (sendsize), uid 14: exited on signal 11 (core dumped) While I am looking at it, any idea about where I could search is welcome. Best regards, Olivier
Re: client to server trickles with tape spanning
A DLE using tape spanning from a client (amanda 2.5.1p3 Debian/Sarge) to server (2.5.2p1 SGI/Irix) just seems to dump **extremely** slowly: so far in ~8hrs not even one chunk of 9GB has made it to tape. All the other DLEs (non-spanning) on that client dump as fast as the network allows and all the other DLEs (local, with or without spanning) dump as fast as the tape drive can stream. Just a wild guess: are you sure it could not be a network problem? I had a similar problem recently, it occured that the client lost it ethernet negociation to the ethernet switch and just any type of network transaction to/from thi client was terribly slow. Best regards, Olivier
Re: Firewall, amanda client and ports
my server (fiume) and my client (stremen) both have a firewall and the client fails to be backed up (the server goes fine). amcheck reports no problem. On the client, I have opened TCP/UDP port 10080, and TCP ports 10082 and 10083, because I seem to have seen something like that when googling. I have also seen that apparently the data connection between server and client at the time of the actual backup uses a variety of ports, or are looking for free ports, but I do not understand really all this. Below are the relevant error messages: They do. If you are using iptable/ipchain (whatever the most recent) there is a module for amanda that you could use. Else you may reconfigure your server to use only a certain port range and open these in your firewall. Olivier
Re: Backup of windows host does not work
Hi, i´m trying to configure my first backup of a windows host. [...] smbclient connect from Server to client works with same username and passwort which is set in amandapass Have you tried to issue an smbclient command? What was the command like? Did it work? What type of Windows are you using? smblient command changed from W98 to W2K/WXP. selfcheck request failed: timeout waiting for ACK What do you have in /tmp/amanda/selfcheck.xxx.debug In that file you should find the smbclient command that amanda try to use, does it work if you try it manually? Olivier
Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
# ls -la /etc/amandapass -rw--- 1 amanda disk 950 Apr 18 10:19 /etc/amandapass I am wondering if the new amanda server 2.5.1p3 if offering a way to hide the contents of amandapass file. Why won't try hiding it, because of settings the rights so that nobody except amanda and root can read it? Because this file contains clear text high priviledge password for the Windows machines. Any leakage of this file would provide access to any Windows machine in the network, so it is better to have the password not clear. Bests, Olivier
Re: Config file upgrade from 2.4.2p2 to 2.5.1p3
Then you better think about your security policy, instead of doing obscoure things with long passwords. It someone can read the content of the file, then it doesn't matter if you have a 8 or 100 character password. Sorry, I was not clear enough, that is not 100 character long password, but some kind of scrambling of normal length password, that is why I used the word obscurity. Ideally, I'd like a crypted file for amandapass. Olivier
Re: suggestion for a disk-to-disk backup server
The one thing that is annoying is that on /var/mail an incremental is essentially the same as a full. Those mail files (one per account) are just like a database file -- add or remove one message and you have to back up the whole file. It would be interesting to write a wrapper to do incremental mail dumps sort of like the sql database programs that do incremental dumps. I wonder if there would be any demand for such a thing. It could get a little messy, and would probably require the Application API. In our case, we have about 1200 accounts/files. It would require reading headers and doing proper locking so as not to collide with the mail programs. Another advantage of maildir format over mailbox :) Only one message per file and no need for locking :) OK, I am still using mailbox, but I will change that :) I'm guessing that for those changers where it's all tied up in one scsi address, and/or where there are multiple drives in a library, it might be desirable to have changer handle it. Then my case becomes the special case -- the changer is set up in sgen.conf and has a scsi device address, and the tape drive is set up in st.conf and is /dev/rmt/1 -- so the changer does not know how the drive got set up. This special case might require the changer to look somewhere else, e.g. amanda.conf, to find out. But, then, couldn't it also tell somehow if there had been an override? Or does that get too messy? That's basically the answer -- the current changer interface has no provision for passing along overrides, and adding one would potentially break a lot of custom changer scripts. You've hit the nail on the head as to why changers provide devices to Amanda, rather than leaving her to use tapedev. An idea for the next release of Amanda: Add one config parameter that says use the device povided by the tape changer and that default to YES. So it would not break any existing customized changer script. When set to NO, use the device explicitely defined by tapedev. No need to change any script, all the changes are inside Amanda only. Best regards, Olivier
Config file upgrade from 2.4.2p2 to 2.5.1p3
Hi, I am in an heavy process of upgrading all my server. I am considering moving from Amanda 2.4.2p2 (installed manually) to 2.5.1p3 (automatic install on FreeBSD ports). I am wondering if all the 2.4.2p2 configuration can be used, without any modification, in 2.5.1p3: in a first step I would only change the binaries. I would start using the new features only in a second step. I also patched the 2.4.2p2 server a long time ago to add some level of obscurity in the amandapass file, entries look like: //csimnt1/c 0fcbcc6440b8a3d0b54a2966d3d7f5f963d71e4fd1afe5058c33c41a1a137937d302ac8e680bcb2cd0a58737378117dffe0a31b7ce2acf4242be1242264d5faec33a51c33b63a01c087e187cd0dcb1c858a1caa3753d2ce3d426a2889402155d1f36b866b9dc52edfe55e96335a6083646b233fdde37baba5b353e54db37fbb8494d I am wondering if the new amanda server 2.5.1p3 if offering a way to hide the contents of amandapass file. Best regards, Olivier
Re: Changing the label of an Amanda tape
Can anybody kindly suggest the right way to get this done? Is the old label still in your tapelist? maybe you should make it clear that Amanda will not use that old lable anymore. One brute force way would be to overwrite the tape with some garbage first, then label it with Amanda. Olivier
Re: suggestion for a disk-to-disk backup server
I think by tapedev=/no/such/tape Paul meant that literally, or at least some string that could not be a legit tape device. Not speaking for Paul, but I guess he did. # find /tmp/amanda -type f | xargs grep '/dev/rmt/0' and got nothing except the alternative weekend configuration I had played with the previous weekend. I was looking the same direction, in fact I could not see any place where Amanda logs the tape device she is going to use. The only bits that would log the name of the tape device used are amcheck -t and amrecover. I checked the config logs too /var/amanda/daily but nothing there either. 4. There are additional parameters in my configuration that end up overriding my attempt to override tapedev? My AIT drive is /dev/rmt/1n, and the changer for it is addressed as /dev/scsi/changer/c7t0d0 in amanda.conf. Can't there be an interaction between the changer and the tape drive? That is the changer will anyway load the requested tape (changer names has not been overwritten) and let Amanda know that the requested tape is available at that known tape device, then Amanda using the device provided by the changer rather than the one configured/overwritten? You could try overwritting the changer too. Bests, Olivier
Re: infofile update failed
driver: FATAL infofile update failed (hostname.com,'newDLE') From top of my headf, I think it happens each time you add a DLE, but shoul dnot happen later. First time you add and dump a DLE, update should fail because there is not yet such info file. Olivier
Re: suggestion for a disk-to-disk backup server
RAID0 - 750GB x 2 (SATA) Hosts to backup: about 20 hosts with roughly 100GB each host. So you have 20*100= 2TB to backup on 750GB My mistake, you have 1.5 TG of backup space. What will be the complications and the limitations? Limitation is clear, you deon't have enough backup space. And also what are the recommendations? Increase your backup space. You still have less backup space than disks to backup. Oli vier
Re: suggestion for a disk-to-disk backup server
Just taking into consideration of compression effect? In fact compression depends on your data, do you know how much they compress? Full/incr depends on your data, how your disks are full, how much data you need to do incr every day? Try to use the reverse approach: what data you cannot afford to loose? Then you know what you need to backup. Olivier
Re: suggestion for a disk-to-disk backup server
I am trying to create backup servers out of the following specs: P4 3.0Ghz 1GB RAM RAID0 - 750GB x 2 (SATA) As it was said by others, RAID 0 may not be the right choice. Virtual tapes and tapespaning allows Amanda to extend a backup across several physical disks, so you don't need RAID 0. The only improvement that RAID 0 could bring you is speed to access the disk array, but then the limitation could still be network bandwidth rather than disk speed. RAID 0 won't allow you to add more disks in the server (at least without rebuilding the array), while you could just plug them in simply if it was not RAIDed, and from your configuration you need many more disks in the server. One last question, from what you said, you seem you want to have several servers, each backuping a set of clients. Why not havuing a single backup server, with enouhg disk resources to backup all your clients? It would be easier to manage I beleive. Bests, olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
FAILURE AND STRANGE DUMP SUMMARY: cpu.ind.com /var/lib/mysql lev 0 FAILED [mesg read: Connection reset by peer] Means that Amanda client on cpu.ind.com closed connection with Amanda server before the dump (or estimate was finished). Olivier
Re: timeout waiting for ACK on amanda server
After amcheck I see this message: planner: ERROR Request to asnserv1 failed: timeout waiting for ACK What system is Amanda server runnig on? What did you change few days ago? Did you reboot the machine and the problem is still there? What is the result of the following command: netstat -na |grep 10080 ping asnserv1 Best regards, Olivier
Re: timeout waiting for ACK on amanda server
netstat -na |grep 10080 - do nothing. Hummm, I don't use debian, but if you get nothing it would tend to mean that amandad is not running on that machine, so when the server call, nobody answers. Olivier
Re: Amanda Backup fails possible card errors
Whenever i run an amanda backup around 30mins into the run I get the following errors in the logs. I've included a few extra unrelated lines at the beginning to give some context. From what i can see something bad happened, an attempt was made to reset and the SCSI card went offline. So i'm finally left with the proverbial question: is it hardware or software? Hi, Are the tape new? Did you try different tape? Did you try to write to the tape by hand: tar cf /dev/st0 ... I see that your SCSI card is Ultra 160 but your tape drive is only fast wide, do you have any disk pluged in that SCSI interface? It should work, but who knows, if you can (have 2 SCSI interface) separate fast disks, from slow tape. Best regards, Olivier
Re: One partition of remote machine, all estimate failed since 2007-May-30
Every day for the last few weeks (since May 30) one partition of a remote machine fails with an all estimate failed error. The exact error is: FAILURE AND STRANGE DUMP SUMMARY: luna.elaw.org /zope lev 0 FAILED [disk /zope, all estimate failed] That is a wild guess but... Zope is known to store everything inside a single HUGE file. Could that be that the file size changes while Amanda does its estimate? What is the contents of luna.elaw.org:/tmp/amanda/sendsize.XXX.debug What is the contents of luna.elaw.org:/tmp/amanda/selfcheck.XXX.debug What is the contents of luna.elaw.org:/tmp/amanda/amandad.XXX.debug These 3 files should help telling you in more details where the problem occurs. Bests, Olivier
Re: How to Extract Same Database in Two Different Virtual Tapes??
Label mismatch, got DailySet1-11 and expected DailySet1-07 Label mismatch, got DailySet1-11 and expected DailySet1-07 If U see the Ayofun_CSite database appeared in two different virtual tapes. I can recover for just one virtual tape. How to recover both of different virtual tapes? Pls help. It looks like a tape changer problem to me. Olivier
Re: one client stopped
Of course I made no changes to either client or server around that date :)) (big smiley just in case) Sorry for the delay but I just started work and am reading my nightly email. I had the same delay problem recently, one client suddenly would finish in 30 hours (yes I let it run) instead of 20 minutes. I had not changed anything on the client nor the server. Though it happened that I had rebooted the network gears. When the client reconnected to the network switch, Ethernet connection was poorly negociated, hence the degradated network and dump performance. Dunno if it was your case, just a thought. Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
FAILED AND STRANGE DUMP DETAILS: /-- ind.ayo.com /var/lib/mysql lev 0 STRANGE sendbackup: start [ind.ayo.com:/var/lib/mysql level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./mysql.sock: socket ignored ? gtar: ./mysql/general_log.CSV: file changed as we read it Means that the file mysql/general_log.CSV was getting modified while tar was trying to save it. Most probably this file has not been included (or included wrongly) in your amanda backup. You have to understand that it takes some amount of time for tar to make a copy of a *big* file. If that big file is changing often, it is very likely it will be changing while tar is trying to copy it. There is very little you can make about it, except stopping mysql while you are doing th backup :) Actually, this is only a STRANGE, not a FAIL. A bit of auto promotion, this page https://wwws.cs.ait.ac.th/amanda/operator.shtml reccords a number of Amanda error message and the explanation for it, and possible recovery action. Olivier
Re: Amanda 2.5.1p3 gnutar permissions trouble
I'm running into a problem with permissions when backing up a nfs mount. I'm using gnutar, and while I can backup the entire mount just fine, if I try to put just a subdirectory of the mount in the disklist, I get Permission Denied errors from amcheck and amdump. Any ideas as to what I'm doing wrong? The OS is Ubuntu Linux 7.04. Thanks all! Eventually, consider backuping directly from the NFS server. I am afraid that backup though NFS is pretty unefficient. I try to have my DLE corresponding to machines where the physical disks are. Bests, Olivier
Re: FAILURE AND STRANGE DUMP SUMMARY
Is there any proper mysql backup that can backup database without stopping it?? If so, I don't have to worry about it? Of course it wasn't failed but I just worried if I recover it and the database or tables might be corrupt just because Amanda detected strange. Please advice. I remember I have seen something about backuping MySQL database, look at Amanda web site. Now what is the file ./mysql/general_log.CSV ? In my run of MySQL (version 4) I do not have such a file. Is it important or not if you loose it? If it is only a log file, like the name suggests, maybe loosing it would not be so dramatic. Best regards, Olivier
Re: autoflush doesn't?
Until it goes DING sufficiently loud to get my attention that there is already something in there from back on the 7th of may! -rw--- 1 amanda disk 53739520 May 7 00:47 coyote._root.0.1.tmp The bit from may 7 is labelled tmp, it must be a partial dump. Just a wild guess, but the file name is not matching other DLEs. Olivier
Re: RegEx not working?
It was a bug if it worked before. The regex works correctly. [14] is 1 or 4 You want ^VOL14[0-9]. Actually wouldn't it be better to use ^VOL14[0-9]$ to avoid any trailing character after the third digit? olivier
Re: Hardware suggestion
Hi, Normal hot swap bay for hard disk are not designed for daily use, they are designed for maintenance only, and would break soon if I swaped the disk every day. You might want to try some (external) eSata devices. The connectors seem more reliable than the internal ones - and probably are cheap to replace... I was going through the reports of various amanda run, my actual tape is reported to give about 5MB/s, so any USB2 interface would be plenty enough. People with huge Amanda experience, please correct me if I am wrong. It seems to me that most ofthe time is taken by the dump process, and as soon as a dump is finished, a taping takes place, in parallel with other dump continuing. So the speed of the (v)tape only matters when the last dump finishes and there is no more parallelism, just taping. At same time, Amanda can be configured to make the big dumps first, so what is left at the end should be minimal and take almost no time. We are talking batch processing here, so that the last taping takes 5 minutes or 20 minutes is of very little concerns. What aveage tap write rate do you see in your reports (in the statistics)? I get about 5000 k/s for SLR100 taep drive. bests, olivier
Slow client
Hi, I noticed yesterday that one of my clients suddenly became very slow: by wall clock, seeing the file grows on the holding disk, it takes 9 minutes for 5 MB of GNUTAR level 2. previous run (Apr. 28th) for the same machine, same DLE, same level was 107 KB/s for the dump according to Amanda report. The slowness can be seen for every DLE on that client. Other than that, the client is working fine, load average is close to 0, it is not swapping or anything, network seems to be working fine. Any idea? I will run some more diagnostics later, once the backup is finished. Best regards, Olivier
Re: Slow client
Frank, Do you have a duplex mismatch or other errors on the network interface or switch port? No error visible. A manual transfer was also very slow, a reboot of the machine solved that. Are you seeing any system messages about read errors on your disks? Have you recently changed OS/kernel/tar versions? Nothing changed for a good while, only I did reboot the network equipment some time last week. I beleive the duplex did not get negociated properly after reboot. What does the Amanda report show for dumper time and taper time for the DLE? HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- -- - mailback / 04508018784 41.7 41:517.5 0:10 1870.1 mailback /home 2 187190 106368 56.8 213:068.3 0:30 3489.2 mailback /usr0 FAILED - mailback /var043080 6752 15.7 49:432.3 0:07 956.0 That's yucky :) OK that was only a network problem it seems. Thanks, Olivier
Hardware suggestion
Hi, I am considering replacement for my Amanda server, the guy has been in production for about 6 years now and I want to be ready for the time when the tape drive will die. We currently use SLR100, wich is fine, very little tape failure, but tapes are expensive, a 50 GB (native) 100 GB (compressed) tape is the price of a 250 GB hard disk. The tape drive itself cost twice the price of the server at that time. So we are considering vtapes, but I would like to have hard disk physical rotation, the same way we have tape rotation --and it is manual changing of the tape every day. The only answer I don't have concernes the hardware to use for disk hot plug mounting and unmounting (on the software side,I now thatthe disk can be disconnected from the operating system before they are physically removed from the machine). Normal hot swap bay for hard disk are not designed for daily use, they are designed for maintenance only, and would break soon if I swaped the disk every day. Could anyone advise on some disk tray solution that is stong and reliable and will handle a lot of manipulation. idealy I wouldbe looking at one tray bay and 5 or 6 trays for the disks. best regards, Olivier
Re: amverify - reality check?
Hi, In the line with what have been discussed, would it be possible that Amanda does some kind of CRC on the dump, on the client side, and that this CRC information is checked when running amverify? That would allow to say that not only a piece of backup can be read, uncompressed, untared (if GNUTAR is being used), but also that it contains the exact information that was sent by the client. Best regards, Olivier
Re: amverify - reality check?
I've been tasked with guaranteeing that the backup vtapes or in the future real tapes are good. So I found the command amverify that seems to be the correct routine but I want to know does it completely check the archive and the files contained within? Amverify will try to extract any backup from the backup media, uncompress the files and see if they are readable. By no mean amverify will conduct a comparison file by file, for the simple reason that we are talking about live system and the files will have change between the moment they were backuped and the moment they are verified, so the verification would always show non-matching files, so you could not say anything about the correctness of your backup. To add to the answer of Gene, yes, amverify add wears and tears to the tape and the tape drive, but I have been using it anyway, just to be sure. I don't use cheap helical type tapes, that gets too much problems, but expensive ones, they are more expensive than a disk drive nowdays, so the next choice will be vtapes on some extractible disk. Bests, Olivier
Re: amcheck fails
-sh-2.05b$ cat /etc/amandapass //hostname/share hostname\user%pass domainname On XP and W2K I am using: //hostname/share user%pass hostname That worked for W98 too. looking in amanda log, I think I once found the Samba command that is used by Amanda. I did some fiddling around the command until finding the right combination of arguments that worked for me. Olivier
Re: amrecover issue
Hi, Currently i'm having some issue with the amrecover. Whenever i tried to execute the amrecover it executed properly but till i started to extract the data it stated there Can't Talk to Tape Server I would try in two directions: 1) try to amrecover on the server itself, to some temporary directory 2) check the firewall on your server best regards, Olivier
Re: TAPE-ERROR 00-00001 [writing file: File too large]
I just tried to find some ways how to let the Amanda (taper phase of backup process) to create files avoiding Large Files Problem (LFP). For example, i can do it using the following command under FreeBSD-4.x: ssh MyHost dump -0 -u -a -f /MyBigBigBigSlice MyHost.MyBigBigBigSlice.0.dump The same way is used in Amanda but in dumper phase only. But when taper is Got it now. I defined small chuncks on the holding disks, typically 1GB, because I think that if the dumper meets a disk full, there will be less issue on a small chunk than on a big one (less data lost and dump to be restarted). So I assumed that your virtual tapes were always MUCH bigger than your holding disk chunks, so holding disk would never hit LFP. Olivier
Re: activate HW compression
Hi, How can I enable Hw compression ? do I have to do it for each tape ? What if A reboot the server ? Yes you have to activate it for each tape, and on the safe side, I would activate it before each amanda run, so make it part of the cron that runs amanda dumps. Olivier
Re: TAPE-ERROR 00-00001 [writing file: File too large]
Hi, I run Amanda under FreeBSD-4.11, so when Amanda trying to make file of dump with size of more than 4GB (exactly, 2**32-1), i can see in May I suggest that you ask the question on FreeBSD list :) Olivier
Re: Backup of index and config files
In my case the machine which works as an Amanda backup server itself is backed up by Amanda. So which are the important files/directories (index and config files/directories or any other important files) that I should save on some other machine, so that I can recover data from the Amanda backup tapes, in case the machine acting as a backup server fails? What I do: https://wwws.cs.ait.ac.th/amanda/operator.shtml#database
Re: W2003 Server Incrementals
Two of the servers I'm backing up are W2003, and we're going to be putting more up in the next few days. We're running Amanda 2.4.5 - Well, it could be helpful if you told us how you do the Windows backup: samba, some native windows client, cygwin, other? Best regards, Olivier
amrecover confirmation robustness
Hi, I was doing some restore last week using amrecover, from incremental backup and I shot myself in the foot a couple of times when amrecover requests to change tape: - I am sharing the keyboard and screen between several servers using a KVM switch; - the KVM switch has a screen saver function; - amanda server has a screen saver function; - while amanda was recovering the first tape,I switched to another machine, maybe one or both screen saver where activated, so when I came back to amanda to switch tape and confirm I end up hitting enter without wanting it and before I switched tapes, so the recover process had failed. So it could be because of my old version of Amanda (2.4.something) but it would be nice if amrecover did not allow an empty input when asking to confirm that the new tape has been inserted. Best regards, Olivier
untar arguments
Hi, I was restoring a server after a disk crash, at some stage I had to do the untar by hand and appartently I am missing some arguments because tar would refuse to create symlinks when the target is not present. So I am wondering what are the officially recommeneded arguments to GNU (un) tar? bestregards, Olivier
Re: IP address change
We just did a big network over haul at my job and every since the change amanda does not back up some machines. I looked in the latest log file and it states. Error planner request to amanda.transolutions.net failed: timeout waiting for ACK. Hi, I'd check for network connectivityproblem, can the client reach the server, can the server reach the client? Can addresses resolve? Have you updated the firewall on both machines? Olivier
Re: tape order
I have 24 tapes and a 8 tape changer. For some reason, it is going 13-16-15-14-17. How can I fix this? can i just force it to take 14 after 13 by only having 14 in there when it's expecting 16? My tapecycle is 10. On the sticker used on the tape, do a double numbering, one by Amanda label and one by human sequence (13 a) (16 b) (15 c) (14 d) (17 e) etc. Though after many years of using Amanda I never had the tapes going out of sequence, if one tape wears out, I replace it with a new tape, using the same label (amlabel -f), but I do the replacement only the very day I should have been reusing the bad tape. When a dump resolve that tape 7 is faulty, I continue with tape 8 and etc, only when Amanda ask to use tape 7 again, I label a new tape 7 and use that new 7. I do that with a PostIt on the bad tape to remind me that I must replace that tape the next time I try to use it. Olivier
Amanda on USB disks
Hi, For the next backup server I'll have to implement, I was asked to see the feasability of using USB disks instead of tapes. I know there are virtual tapes, but do they work on removable disks? Best regards, Olivier
amverify cannot /x/y/tar dumps
Hi, This may be because I am using a prehistoric version of Amanda (2.4.2p2) but, after I make a dump, I make a verify. Some of the DLE cannot be verified becausethe client has been compile to use a GNU tar that is different from the one used when compiling the server: different meaning that the tar binary has a diferent path. So I get the kind of following results: Checked alhazen.desktops._home_mdailey_Projects.20060928.1 Skipped ufo1000._web.20060928.1 (** Cannot do /usr/local/bin/mygtar dumps) Skipped mailback._usr.20060928.0 (** Cannot do /usr/local/bin/gtar dumps) Checked alhazen.desktops._.20060928.0 - /usr/local/bin/mygtar is a tar wrapper - mailback has been build to use /usr/local/bin/gtar instead of /usr/local/bin/tar By using a tar wrapper, one could provide just any archive format he wishes and there is no way that the good old tar on the server would know what to do with it. But I beleive that this is a very rare case and that for most of us, that the client uses /bin/tar, /usr/local/bin/gtar or /usr/local/bin/tarwrapp or whatever, the file is in tar format; so the good old tar on the server should be able to amverify it. And just in case the file is really not in tar format, then the verify would issue a Cannot do /usr/local/bin/mygtar dumps warning. And checking if the fileis not in tar format could be done 2 ways: with the file(1) command or with runing tar and receiving an error. OK, that would really improve amverify (and amrestore I beleive) if that is not included in more recent versions of Amanda. Best regards, Olivier
Small update on testgtar
Hi, I did a very minor change on testgtar (the small script that tests gnutar exclude list) to remove an error when checking for broken version of tar. testgtar is being referenced at http://wiki.zmanda.com/index.php/Exclude_and_include_lists Bests, Olivier
Re: Amanda error Unexpected field value...
The difference is that the good run was a level 0 and the run with the error was a level 1. What is the Unexpected field value? Well that's the problem with cygwin... We have little reference. Apparently running level 0 gtar creates a sort of index file, to use in level 1 and compare files that have changed. And it seems that in between the run 0 and 1 gtar cannot read the file it created. If you look at the sendzie debug you should see a command very close to this one gtar --create --file - --directory /local --one-file-system --listed-incremental /local/Amanda/amanda-2.4 .5p1/var/amanda/gnutar-lists/coriolis_local_1.new --sparse --ignore-failed-read --totals . but that will say gtar --create --file /dev/null ... Did that one completed without error? Try to run the long gtar command by hand, with --file - and --file /dev/null Tryto extract the comamnd for level 0 and run it... Check your version of gtar. Bests, Olivier
Re: ambackup fails for client
I am not sure what you mean by that: the backups done at day 1 and 2 where in fact all level 0 for PC-2. On day 3, they were all level 1. On day 4 and 5 they all failed. So, probably they should all be level 1 or do you mean something different? OK, I did not understand that the backup did succeed on first two days, at level 0. I though it never worked, so I was surprised that on first attempt it went for level 1. If it did run on the first day, did you check what you have in the debug files (in /tmp/amanda)? Olivier
Re: Couple of doubts about report and tapes
2.- =BFDoes amanda allways rewinds the tape before writing to it (so = tape is allways overwrited)? (I think this is true) Yes for sure. 3.- On the other hand, incremental, AFAIK, means backup of all the = files that have changed since the last backup, even if that was an incremental backup (as opossed to a full backup). Is there a way to make a = differential backup (backup of all the files that have since the last FULL backup). Incremental always come with a level, full backup having the level 0. Incremental of level X means all the files that have changed since the last backup of level less than X: level 1 means all the files that changed since the last level 0 (full) level 2 means all the files that changed since the last level 0 or 1 level 3 means all the files that changed since the last level 0 or 1 or 2 backup of all the files that have since the last FULL backup Is exactely incremental level 1. Olivier
Re: ambackup fails for client
recently I have added 1 PC to be backuped up (so now in total 2 PC's are backuped: the server itself and this 2nd PC). It has taken some fiddling with the /etc/hosts file on the new client, but at the end it worked. 3 backups were done without any problem, but number 4 and 5 failed completely for the new client (the client-server was and is OK). stremen.localnet /boot lev 1 FAILED [cannot read header: got 0 instead of 32768] I don't know if it is related, but it seems weird thatit starts with a level 1. Olivier
Re: Running amcheck, all hosts on one subnet timeout
Hi, Running amcheck, all hosts on one subnet timeout: host selfcheck request failed: timeout waiting for ACK I don't see you mentionning any .amandahosts on the clients... As /tmp/amanda was not created, maybe .amandahosts was not either. Best regards, Olivier
Re: Backup plan and big filesystems
Hi, Time to add my 2 cents to that thread, and ask for advice from Amanda gurus too. The way I solvedthe offsite tapes thing is the following: I declared: dumpcycle 1 week runspercycle 5 tapecycle 6 tapes I labeled 6*3 tapes, with labels like set-1-00 to set-1-05, set-2-00 to set-2-05 and set-3-00 to set-3-05. Only set-1 is marked for reuse, when I reach tape set-1-05, I mark all set-1 as no-reuse and set-2 as reuse. And etc. This way I should have 2 complete cycle, including full and incr to be offsited. Am I doing anything wrong? I find this much straight forward than having 2 configuration, one for full and one for incr. Best regards, Olivier
Re: using star instead of tar, backuping Zope
Thks a lot, the problem was that I haven't rebuilt amanda-common with the wrapper path on my client, but just rebuilt amanda-client. It works now with tar. Usually it should be enough to recompile the client part? Now I have to script in order to replace tar arguments by star arguments... Good luck with that. olivier
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
So you are saying i should loock for ~4GB directories tar them instead to dump them? Just to be on the safe side, and if you are considering to split your backup anyway, it is better to split into pieces that are smaller than the tape size. I thought amanda can split such big backup archives up in serveral parts. I doubt that someone will backup up a 200GB System onto one single tape. Not sure if Amanda can split a single DLE onto several tapes. I use a pre-historic version of Amanda that run single tape :) Spliting your big DLE into pieces (as many pieces as runpercycle) is anyway a good tactic, so on every dump Amanda will backup one of the pieces, and you will end up with equal dump time every day. Else you will have one big day, doing the 200GB and many small other days. Olivier
Re: tapelist - how to edit
my tapelist has become a bit confused, due to my own fault, by me adding tapes in the middle of my numbered sequence. At the moment it looks like this: 20060803 daily-5 reuse 20060802 daily-1 reuse 20060801 daily-3 reuse 20060731 daily-4 reuse 20060731 daily-2 reuse If the matter is just to make your life easy, have a natural sequence of numbers when picking up the next tape for backup, why not changing the label sticker on the tape (not Amanda label). And on the sticker you write in big: TAPE 1 and in small daily-1 TAPE 2 daily-3 TAPE 3 daily-4 TAPE 4 daily-2 TAPE 5 daily-5 And you do not confuse Amanda :) That is definitely how I would do. Bests, Olivier
Re: dump larger than tape, 30864683 KB, but cannot incremental dump new disk
Hi, How can i tell amanda to split it up in 4500MB slices and write them one by one to DVD-RAM? Make them several DLEs. That means you must use GNU tar, not dump and you must identify sub-hierarchies, from that too big disk, that will match your 4.5 GB limit. Time to play with exclude file list. That said, your tapelist shows 4350 MB, why making chuncks of 4500MB? You may well be facing the same problem again... Bests, olivier
