Re: Backing up MySQL tables
Hi Alex. I something like the following before my amanda backup runs: d="`date +%d.%m.%Y`" mysqldump --all -c database_name > "/path/to/backup/$d.sql" I have not had any problems (yet) ;) Alex Thurlow wrote: I need to start backing up MySQL tables on one of my machines, but I've heard that to you run the risk of table corruption if you just copy the mysql directory while MySQL is running. Stopping the database is not an option, and the only solution I've come up with is having another script do a mysql dump and then backing up that. It seems like a waste of time and resources to basically do 2 backups though. I was just wondering what anyone here does for MySQL backups on their own systems? Alex Thurlow -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Cell :: 27 82 551 2703 # Email :: bartho @ cae.co.za
Re: Problem with amrecover
Hi Nicki and others that replied. Eventually found the problem after running strace amrecover which indicated that it was refused connection to port 10082 (amandaidx). On closer inspection I found that amandaidx (/etc/xinetd.d/amandaidx) was actually disabled and this led to my problems. Moral of the story check your configs again and again. :) Nicki Messerschmidt wrote: Bartho Saaiman wrote: I am trying to restore from a tape using amrecover. If I use amrecover DailyBackup it says: > AMRECOVER Version 2.4.2p2. Contacting server on localhost ... > amrecover: cannot connect to localhost: Connection refused This sound like your inetd isn't started. Otherwise you would get a message like "Access from [EMAIL PROTECTED] not allowed"... Or did you play with your firewall/hosts.(allow|deny) files? Cheers Nicki -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Cell :: 27 82 551 2703 # Email :: bartho @ cae.co.za
Problem with amrecover
Hi All :) I am trying to restore from a tape using amrecover. If I use amrecover DailyBackup it says: > AMRECOVER Version 2.4.2p2. Contacting server on localhost ... > amrecover: cannot connect to localhost: Connection refused If I use the -s backup and/or -t backup I also get the same: > AMRECOVER Version 2.4.2p2. Contacting server on backup ... > amrecover: cannot connect to backup: Connection refused I previously had a similar problem and rectified this by editing the /var/lib/amanda/.amandahosts and added localhost root to the file. Tried this as I am running amrecover as root but still could not fix it. Any suggestions on what I am missing?? -- # Bartho Saaiman # Network Administrator # Stellenbosch Automotive Engineering # Tel :: 27 21 882 8820 x 215 # Email :: bartho @ cae.co.za
Re: tape changers and shell scripts
I have a HP 6 tape loader and use the following in a script file that runs every night. I backup to 5 tapes every night -- # Specify the tape changer device chgdev=/dev/sg5 # Clean the read/write tape device (/dev/nst1) mtx -f "$chgdev" last # Initialise the tape changer with the 1st tape mtx -f "$chgdev" first # Store the data mtx -f "$chgdev" load 1 amdump T1 mtx -f "$chgdev" unload 1 mtx -f "$chgdev" load 2 amdump T2 mtx -f "$chgdev" unload 2 mtx -f "$chgdev" load 3 amdump T3 mtx -f "$chgdev" unload 3 mtx -f "$chgdev" load 4 amdump T4 mtx -f "$chgdev" unload 4 mtx -f "$chgdev" load 5 amdump T5 mtx -f "$chgdev" unload 5 # Keep 6th tape for misc backups # I keep my cleaner in there #mtx -f "$chgdev" load 6 #amdump T6 #mtx -f "$chgdev" unload 6 -- On Tue, 2002-06-04 at 16:07, grepcomputers wrote: > I've read the FAQ, and the docs directory. I downloaded mtx (2.16rel) > and installed it. > Because I am relatively new to linux, I am finding the documentation a > *little* hard to understand... :-/ > > system: alpha running redhat 6.2 > autoloader: TSL-A500C (AIT Autoloader Unit) > > I'm still a little unsure of how to configure amanda to work with our > autoloader and mtx. > Does anyone have any words of wisdom? > > thanks... > ...grep -- |-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-| Bartho Saaiman Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204 Stellenbosch Automotive Engineering http://www.cae.co.za |-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
Error on amrecover
Hi I get the following error when I try to do a test recover with amrecover. -- [caepdc:/etc/amanda/USER]# amrecover -C T1 AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 caepdc AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-06-04) 200 Working date set to 2002-06-04. 200 Config set to T1. 501 No index records for host: caepdc. Invalid? Trying caepdc ... 501 No index records for host: caepdc. Invalid? Trying caepdc ... 200 Dump host set to caepdc. Can't determine disk and mount point from $CWD amrecover>sethost caepdc 200 Dump host set to caepdc. amrecover> setdisk /home/ide 501 No index records for disk: /home/ide. Invalid? amrecover> -- Even if I use it without specifying the config file I still get the same error. I have been through the faq and man pages and the closest to any solution that I can find has to do with using some older version of GNU tar. I am using -- [caepdc:/etc/amanda/USER]# tar --version tar (GNU tar) 1.13.25 Copyright © 2001 Free Software Foundation, Inc. This program comes with NO WARRANTY, to the extent permitted by law. You may redistribute it under the terms of the GNU General Public License; see the file named COPYING for details. Written by John Gilmore and Jay Fenlason. -- Any suggestions on how to fix this. -- |-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-| Bartho Saaiman Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204 Stellenbosch Automotive Engineering http://www.cae.co.za |-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
Re: amanda + debian woody problem
Make sure that amanda is enable in /etc/inet.d/amanda
--->snip<---
# default: off
# description: The client for the Amanda backup system.\
# This must be on for systems being backed up\
# by Amanda.
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amandad
disable = no
}
--->snip<---
Do the same for amandaidx and amandatape. Mine was by default disabled.
Remember to restart the inetd service.
Marcus Schopen wrote:
> Hi,
>
> running amcheck on my woody as user backup says:
>
> WARNING: localhost: selfcheck request timed out. Host down?
> Client check: 1 host checked in 29.997 seconds, 1 problem found
>
--
|-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|
Bartho Saaiman
Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204
Stellenbosch Automotive Engineering http://www.cae.co.za
|-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
Re: Slow dumper
(80.000MHz DT, offset 255, 16bit) Channel A Target 13 Negotiation Settings User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit) Channel A Target 14 Negotiation Settings User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit) Channel A Target 15 Negotiation Settings User: 160.000MB/s transfers (80.000MHz DT, offset 255, 16bit) Apologies if it is not an amanda issue. Joshua Baker-LePain wrote: > On Tue, 28 May 2002 at 2:47pm, Bartho Saaiman wrote > > >>I am using a dump disk and these backups are all local. I am using the >>following compressions to ensure that the data actually fits on a disk. >> > > What's your hardware? What OS? > -- |-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-| Bartho Saaiman Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204 Stellenbosch Automotive Engineering http://www.cae.co.za |-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
Re: Slow dumper
Hi Joshua
I am using a dump disk and these backups are all local. I am using the
following compressions to ensure that the data actually fits on a disk.
define dumptype tgz-best {
program "GNUTAR"
options compress-best, index
priority high
dumpcycle 0
}
define dumptype tgz-fast {
program "GNUTAR"
options compress-fast, index
priority high
dumpcycle 0
}
define dumptype tar {
program "GNUTAR"
options no-compress, index
priority medium
dumpcycle 0
}
Joshua Baker-LePain wrote:
>
> The first thing to do, if at all possible, is to use a holding disk.
> Given that your run time=dump time+tape time, it appears you aren't using
> one. A holding disk big enough for your two largest partitions can
> *significantly* speed things up.
>
> Next you need to look at your clients, your network, etc. E.g. you're
> using software compression -- are you doing it on the clients? How fast
> are they? Is your network throughput with other apps good?
>
> This isn't an amanda problem per se (except for the holding disk), but one
> of looking at your resources.
>
>
--
|-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|
Bartho Saaiman
Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204
Stellenbosch Automotive Engineering http://www.cae.co.za
|-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
Slow dumper
I have a problem where my dumper is slow and the taper seems to be faster:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min)11:21
Dump Time (hrs:min)9:42 9:42 0:00
Output Size (meg) 14818.314818.30.0
Original Size (meg) 20804.720804.70.0
Avg Compressed Size (%)71.2 71.2--
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 434.8 434.8--
Tape Time (hrs:min)1:37 1:37 0:00
Tape Size (meg) 14818.414818.40.0
Tape Used (%) 74.1 74.10.0
Filesystems Taped 1 1 0
Avg Tp Write Rate (k/s) 2606.1 2606.1--
Is there a way of changing this to speedup backups.
--
|-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|
Bartho Saaiman
Cellphone * Work +27 72 341 8626 * +27 21 808 2497 ext 204
Stellenbosch Automotive Engineering http://www.cae.co.za
|-=-=-=-=-=-=-=< registered linux user 236001 >-=-=-=-=-=-=-=-=-|
