[ Pobierz całość w formacie PDF ]
.Some typical types of tapes are included here.The# tapetype tells amanda how many MB will fit on the tape, how# big the filemarks are, and how fast the tape device is.define tapetype HP-DAT {comment "DAT tape drives"# data provided by Rob Browninglength 1930 mbytes filemark 111 kbytesspeed 468 kbytes}# dumptypes## These are referred to by the disklist file.define dumptype global {comment "Global definitions"# This is quite useful for setting global parameters, so you# don't have to type them everywhere.}define dumptype always-full {globalcomment "Full dump of this filesystem always"compress nonepriority highdumpcycle 0}This example amanda.conf was trimmed down from a larger example located in /etc/amanda/DailySet1.Rather than type a configuration file from scratch, I recommend you start with the example amanda.conf andmodify it as needed.The example amanda.conf file provides additional information on the availableconfiguration options.Also, the online man page for Amanda should be helpful (type man amanda to readit).You can find more instructions in the /usr/share/doc/amanda-server* directory.Generally, you have to dothe following:"Modify the org name for reports."Change the device names specified for tapedev and rawtapedev so that they match your tape device."Select a tape type entry that is appropriate for your tape drive."Change the name of the directory specified in the holding disk section to match the directory youcreated earlier.Creating a disklist fileYou also must create a disklist file in the /etc/amanda/normal directory.This simply contains a list of thesystems and disk partitions to back up.The qualifier always-full is included on each entry to tell Amandawhat type of backup to perform.It means to use full, rather than incremental, backups.# sample Amanda2 disklist file## File format is:## hostname diskdev dumptype [spindle [interface]]## where the dumptypes are defined by you in amanda.conf.dexter hda5 always-fulldexter hda6 always-fulldexter hda7 always-fulldexter hda8 always-full daffy hda5 always-fulldaffy hda6 always-fulldaffy hda7 always-fulldaffy hdb1 always-fulldaffy hdb2 always-fullThis example file backs up two systems, dexter and daffy.The order of the systems and the partitions isselected so that the most important data is backed up first.This way, if a tape drive becomes full, you havestill managed to back up the most important data.Adding Amanda network servicesAmanda is designed to perform backups over a network.The following amanda services are defined in the/etc/services file:amanda 10080/udpamandaidx 10082/tcpamidxtape 10083/tcpTo offer these services to the network in Red Hat Linux, you need to configure the xinetd daemon to listen forthose services.You do this by enabling the services in the amandaidx and amidxtape files in the /etc/xinetd.ddirectory.In each of those files, you need to change the disable line to no, as follows:disable = noThis enables Amanda to accept requests from the client system and to start the backup process without anyuser intervention.You need to tell the xinetd daemon to reload the /etc/xinetd.d files before this change takesplace.You can do this by typing the following as root user:# /etc/init.d/xinetd restartYou next need to create an.amandahosts file in the /root directory.This file should contain the fully qualifiedhost and domain name of any backup servers that will connect to this client.For example, to create an.amandahosts file on the system dexter.glaci.com that will enable the backup server ratbert.glaci.com toconnect, do the following:# echo ratbert.glaci.com > /root/.amandahosts# chmod 600 /root/.amandahostsI used chmod to change the access permissions of the file.This assures that only root can read or modify thisaccount.Performing an Amanda backupNow that everything is configured, you are ready to perform an Amanda backup.While logged in as root, typethe following command:# /usr/sbin/amdump normalThis runs the amdump command and tells it to read the configuration files it finds in the /etc/amanda/normaldirectory.It then works its way down the list of systems and partitions in the disklist file, backing up eachpartition in the order it occurs.The results of the amdump are written to the /usr/adm/amanda/normaldirectory.Read the files you find there to check on the results of the backup.(See the previous section on howto create a disklist file to understand the process that amdump goes through.) You can, of course, automate this process with cron.To create an amdump schedule similar to the regulardump schedule discussed in an earlier section, do the following.While logged in as root, enter the crontabcommand with the -e option:# crontab -eThis brings up the root crontab file in an editor.Add the following lines to the end of the file:0 22 * * 0 /usr/sbin/amdump normal0 22 * * 1 /usr/sbin/amdump incremental0 22 * * 2 /usr/sbin/amdump incremental0 22 * * 3 /usr/sbin/amdump incremental0 22 * * 4 /usr/sbin/amdump incremental0 22 * * 5 /usr/sbin/amdump incremental0 22 * * 6 /usr/sbin/amdump incrementalSave and exit the file.The cron daemon will now run amdump at 10:00 p.m [ Pobierz całość w formacie PDF ]
  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • odbijak.htw.pl