Amanda chapter (old) - The Open Source Backup Wiki (Amanda, MySQ. From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC) DeprecatedThis chapter has not been updated for a long, long time. Refer to other pages on this wiki for more up-to-date information. John R. Jackson Original text AMANDA Core Team <jrj@purdue.edu> Gavin Henry XML-conversion Suretec Systems Ltd.
Stefan G. This chapter was written by John R. During the Docbook-conversion of the AMANDA-docs we asked for permission to include this chapter in the Official AMANDA documentation and W. An Introduction AMANDA, the Advanced Maryland Automated Network Disk Archiver, is a public domain utility developed at the University of Maryland.
AMANDA was written primarily by James da Silva at the Department of Computer Science of the University of Maryland around 1992. AMANDA was driven by the introduction of large capacity tape drives, such as ExaByte 8mm and DAT 4mm. Since AMANDA is optimized to take advantage of tape drives, we will use the word tape throughout this section. AMANDA Features. Amanda. There are four user-editable files that control the behavior of Amanda. The first two are amanda.conf(5) and amanda-client.conf(5), the main configuration files for the server and client, respectively. They contain parameters to customize Amanda for the site.
Next is the disklist(5) file, which lists hosts and disk partitions to back up. Last is the seldom-edited tapelist(5) file, which lists tapes that are currently active. These files are described in more detail in the following sections. All configuration files are stored in individual configuration directories, usually under /etc/amanda/. Most Amanda applications take a "config" parameter; this is generally the (unqualified) name of the configuration directory, e.g., normal. Configuration Override Most commands allow the override of specific configuration options on the command line, using the -o option. For global options, name is simply the name of the option, e.g amdump -oruntapes=2 amdump -otapedev=/dev/nst1 -otpchanger='' Amanda operator. FAQ:How are backup levels defined and how does Amanda use them? From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC) This article answers a FAQ (frequently asked question).
Different backup software define backup levels in different ways, often using the same terms in contradictory ways. Amanda’s definition of backup levels follows the traditional Unix/BSD/Linux dump utility backup levels of 0-9, with level 0 being a full backup, and each level n being a backup of changes since the last backup of level n-1 or lower. Explanations and examples can be found in your system’s man pages for dump (or, e.g., ufsdump in Solaris). This system, and Amanda’s configuration parameters, are flexible enough to emulate virtually any backup scheme a user may be familiar with from previous experience with another piece of backup software. However, there are advantages to be gained from becoming familiar with Amanda’s backup planning strategy and from letting Amanda do the planning.
Amanda’s strategy is one of optimization. Using Amanda for backups. [AMANDA]( as the name says, is an advanced disk archiver or, more simply, a backup program. It’s a really useful program, let down by something approaching the worst documentation out there. I’ve had about 4 attempts on and off for about the same number of years at using it and deciphering the documentation. Finally I got it to work, but it should not be that hard. Who knows, maybe in another 4 years I won’t hate Wiki documentation? This document shows you what files you need to create, their format and how to use some of the programs. Speaking of my systems, what I’m writing here works for me with my setup. #Determine your backup regime and other details The first step is to decide what you want to backup.
For my setup, I backup all of /, most of /var except logs and cache and /home with the exception of some junk. Next, think of a name to call the backup regime. #Determining tapetype The configuration file (see next section) will need to know the tapetype. Quick start - The Open Source Backup Wiki (Amanda, MySQL Backup, From The Open Source Backup Wiki (Amanda, MySQL Backup, BackupPC) Installing Amanda Use any of the following methods to install Amanda: Run one of the installation packages available from Zmanda or elsewhere: The Zmanda downloads site includes installation packages for many platforms. If you are using packages from Zmanda downloads page, go to the Zmanda packages 15 minute example. Whether you are installing Amanda packages or compiling from the source, please see the installation page for detailed instructions.
Note: when installing from RPM, debian or other packages, many of the steps below are already done for you. The pre-built Amanda packages make some configuration assumptions regarding the location of log files, .conf files, binaries, etc. Collecting configuration information To set up Amanda backups, you will need to know the configuration parameters of the Amanda installation you are setting up.
Amanda user. . # /usr/sbin/amadmin xx version | grep CLIENT_LOGIN "libexecdir" #! #! #! AmandaInstallation: amanda.conf - UABgrid dev - Trac. Mail - Inbox (193) - How to perform a point in time restoration using ZRM for MySQL | ZRM for MySQL is a powerful, flexible and robust backup and recovery solution for MySQL databases for all storage engines. With ZRM for MySQL a Database Administrator can automate logical or raw backup to a local or remote disk. In this How To, we attempt to explain how to recover from an user error at any given point in time.
Our Scenario: At approximately 2:30pm there were 5 tablespaces added into the MovieID table. At 3pm you get a call from a user, who was trying to delete some unused tablespaces but ended up deleting the last 5 that he just added. Note: More information on ZRM for MySQL is available here. 1. -bash-3.1# mysql-zrm-reporter -show restore-info --where backup-set=dailyrun backup_set backup_date backup_level backup_directory ---------------------------------------------------------------------------------------------------------- dailyrun Wed 18 Oct 2006 07:07:08 PM PDT 0 /var/lib/mysql-zrm/dailyrun/20061018190708 3. 4. 5.
References: An internal error has caused the ZMC to stop functioning correct. How to use an exclude list file .: Zmanda Knowledgebase. CentOS – sendmail sendmail.mc private use « Shamuntoha's Blog.