e s u y n a r o f e l b i s n o p s e r d l e h e b t o n
n PILOT VERSION a c n o i s s i m m o C e h t d n a
, r o h t u a e h t f o y l n o s w e i v e h t s t c e l f e r n o i t a c i l b u p
. ) s / i 0 h . T 4
/ . a n s o - i y s s b i / s m e s m n o e c C i
l / n a g r e o p . o s r n u o E
m e m h t o
c m e o v r i t f
a t e r r o c p / / p : s u s p Remember: This is not the best format to
t t h t h i ( w ”
l
d enjoy this content. Visit cisoss.eu to download a e n d o . i n t n u i a f e
n the sources in ELP format (ExeLearning) or r r n e e e t h e t n b I
d s
e see the IMS deployed in our Moodle platform. 0 a . n i h 4
a ) t e 8 n k i 5 o l 8 c
A 5 n e 1 r o 0 i a - t h
a Content created by: 2 S 0 - m 2 r n o o A f i t n K i u -
b 1 e i 0 r h t t S
t f E
A HOGSKOLAN I SKOVDE (HIS) o -
s 1 e - n d 5 o a 1 m 0 m
2 m e (
o b t c C y e a e j v o m i r
t p h a
c e s i i r h h C T w “ e s u y n a r o f e l b i s n o Backup systems p s e r d l Backup systems e h e b t Content created by: o n n a c HOGSKOLAN I SKOVDE (HIS) n o i s s i m 1. Introduction m o C e Information can be considered more valuable than the hardware that generated it and in many h t
d cases irreplaceable. n a
,
r It is therefore important that it is possible to recover information in case of hardware failure o h t or if files and data gets lost or corrupted for other reasons. u a It can also be the case that there is a need to recover data from some earlier point in time e h t according to an established data retention policy. f o
y For these reasons it is important to perform backup on systems. l n o The primary purpose of a backup system is to copy and archive data from computers so that data s w can be recovered. e i v e h t s t c 2. Components of a backup strategy e l f e r The list below shows the essential components of a backup strategy. n o i t a c i Storage l b u Model for data repositories p
. ) s / i Storage media 0 h . T 4
/ . Processing of data repositories a n s o - i
y Choice, extraction, and manipulation of data s s b i /
s Management of the backup process m e s m n Goals o e c C i
l
/ Limitations n a g r e o
p Implementation . o s r n
u Evaluation of the backup-process o E
m e m h t o
c m e 2.1 Storage o v r i t f
a t 2.1.1 Model for data repositories e r r o c p / / p : s u The list below describes different aspects of a model for data repositories. s p
t t h t h i ( w ” The model explicates how data are stored during backup l d a e n
d Unstructured backup o . i n t n u i a f
e For example a number of CDs or DVDs accompanied with some documentation about
n r r n e e e t h what was backed up and when the backup was done e t n b I
d s
e This approach may be the easiest to implement 0 a . n i h 4
a
) It can, however, be difficult to recreate the data in the same way it was stored t e 8 n k i 5 o l Full and incremental backup 8 c
A 5 n e 1 r o This approach avoids copying all data every time a backup operation is performed 0 i a - t h a 2
S First, a full backup is performed, thereafter a number of smaller incremental backups are 0 - m 2 r n o o A performed f i t n K i u -
b To recover information at a certain point in time: 1 e i 0 r h t t S
t Localise the latest full backup taken before the certain point in time, and thereafter f E A o -
s 1 e the incremental backups until the certain point in time - n d 5 o a 1
m Continuous backup 0 m
2 m e (
o b Logs every change at the local host at byte level rather than at file level as for full and t c C y e a e j incremental backup v o m i r
t p h a Rollback is possible in order to recover information
c e s i i r h h C T w “ Writing is performed to another disk (a different computer on the network) when writing to
e the "primary" disk s u y n a
2.1.2 Storage media r o f e l The list below describes different relevant storage media used for backup purposes. b i s n o p Magnetic tapes s e r
Traditionally the most used medium for backup d l e Offers a good capacity/price quota h e
b There are many different variants of magnetic tapes t o It is a sequential medium which implies slow (random) access n n a
c Usually writing and reading is fast n
o Hard disk i s s i Continuously improved capacity/price quota m
m fast access and often easy to use o C
External interfaces available (SCSI, USB, Firewire, etc.) e h t
Optical disk d n CD/DVD/Blu-Ray etc. a
, r
o Can be restored from all computers with a compatible reading device h t u Relatively cheap and easy to handle a e May sustain data for 20-100 years (according to the Optical Storage Technology h t f
o Association) y l Flash memory n o
s USB-sticks, SD, memory stick, etc. w e i Relatively low capacity/price quota v
e Good portability between different operating systems and are often considered easy to use h t s
t Remote backup c e l Backup to a different storage location via Internet f e r It may be considered an advantage that the backup will be physically separated from the n o i t local disk that was backed up a c i l Potential disadvantages: b u
p Internet transmission may become a bottleneck compared to local storage
. ) s / i 0 h alternatives . T 4
/ .
a There may be security issues when transmitting information over the Internet n s o - i y s s b i / s
m 2.1.3 Processing of data repositories e s m n o e c C i
The list below describes different methods for processing of data repositories. l / n a g r e o p . o s On-line data repository r n u o
E This is the most accessible type of data repository
m e m h t Information can be recovered within milliseconds (or less) o
c m e
o Example: hard disk v r i t f
a t There is a risk of unintentionally overwriting or deleting information or being subjected to e r r o c p /
/ virus attacks p : s u s p
Near-line data repository t t h t h i (
This type of repository is less accessible compared to on-line data repository w ”
l d a Example: Library of magnetic tapes e n d o . i n t n Information can be recovered within seconds or minutes u i a f e
n r r n A tape robot can exchange tapes in the recorder e e e t h e t n b I Off-line data repository
d s e 0 a . n
i Resembles near-line data repository, but requires human interaction in order to make h 4
a ) t e 8 n k storage media accessible i 5 o l 8 c
A 5 Information may be recovered within seconds to hours n e 1 r o 0 i a - t
h Off-site vault data repository a 2 S 0 - m 2 r
n Useful in case of a disaster o o A f i t n K Information is stored at backup media at a different geographical location i u -
b 1 e i 0 r h Example: the local office of the system administrator, or a bunker below ground level t t S
t f E A o - Backup site data repository
s 1 e - n d 5 o Useful in case of a major disaster a 1 m 0 m
2 Information is stored at backup media at a different geographical location m e (
o b t c C
y Equipment for recovering the information is kept at the same backup site e a e j v o m i r
There is a specific building for the purpose t p h a
c e s i i r This is an expensive method for processing of data repositories h h C T w “ 2.2 Choice, extraction, and manipulation of data e s u
2.2.1 Choice and extraction of file data y n a
r A central aspect is what information that should be backed up. o f e l
b The list below describes different approaches to consider in connection with choice and extraction of file i s n data for backup. o p s e r
d Copying of files l e h
This is the easiest and most common way of backing up information e b
There functionality is available in all backup software and for all operating systems t o n Partial copying of files n a c
This means that the part of a file that has been changed within a time window is copied n o i This approach saves memory s s i Reconstruction of files often requires sophisticated algorithms m m File system dump o C
e A complete file system (partition) is copied h t Often the partition is first demounted and specific functions (e.g. "dump" in Unix) is used to d n a
back up , r o This approach can be faster than copying of individual files h t u
a Identification of changes e h
t Some file systems have an archive bit that indicates whether a file has been changed f o
recently (is then set to 1) y l n This approach is used by backup software in order to only copy files where the archive bit o s is set w e i
v This approach is used e.g. for incremental backup e h File system with versioning t s t These are file systems that keep track of what changes have been performed for a file, c e l f and make this information accessible for the user e r
n Example in Linux: Wayback and ext3cow (ext3 with copy on write) o i t a c i l
b 2.2.2 Choice and extraction of "live" data u p
. ) s / i A running system can cause certain problems during backup. Open files (especially databases) can 0 h . T 4
/
. change during the performance of a backup operation. a n s o - i y s s b The list below describes different approaches to consider in connection with choice and extraction of i / s m e
s "live" data for backup. m n o e c C i
l / n a g Snapshot backup r e o p . o
s This approach performs a snapshot of a system to store r n u o
E This can be enabled by closing opened files, perform the backup operation, and
m e m h afterwards open the files again t o
c m e Backup of open files o v r i t f
a t Can be complicated, especially for large database files which are relatively time e r r o c p / consuming to process / p : s u s
p Backup systems can, for example, wait for that files are closed
t t h t h i
( Locking of files is useful in order to be able to perform a backup w ”
l d
a Cold backup of database e n d o . i n The database is closed/locked during the backup t n u i a f e
n r
r The consistency is maintained since the user is not able to access the database during the n e e e t h e t n backup operation b I
d s e 0 a .
n Warm backup of database i h 4
a ) t e 8 n
k The database is not closed during the backup (is instead on-line) i 5 o l 8 c
A
5 This approach may imply less disturbances for users compared to cold backup of n e 1 r o 0 i a
- t database h a 2 S 0 - m
2 Information that is backed up may be inconsistent r n o o A f i t
n For this reason, changes made to the database are logged during the backup K i u -
b 1 e i
0 operation, and this log can be used to recover the database r h t t S
t f E A o -
s 1 e - n d
5 2.2.3 Choice and extraction of metadata o a 1 m 0 m
2 m e (
o b All information is not stored in files. Information about files and their organisation must also be handled t c C y e a e j during backup. v o m i r
t p h a
c e s i i r h h C T w “ The list below describes different aspects to consider in connection with choice and extraction of
e metadata for backup. s u y n a System description r o f The specifications of the system (platform, operating system) e l
b Meta data about the system i s n Information about how the operating system is configured o p s Boot sector e r
d This is not an ordinary file. It is required to recover the original system l e h
Partitioning e b
t The layout of the original disk, partitioning tables, file system configuration settings, etc. o n
n Metadata for files a c Access rights, owner, group, ACLs (Access Control Lists), etc. n o i s s i
m 2.2.4 Manipulation of data for backup m o C
Prior to a backup operation, data can be manipulated in different ways in order to optimise the backup e h t
process. d n a
,
r The list below describes different approaches to consider in connection with manipulation of data for o h t backup. u a e h t
Compression f o Files may be compressed prior to backup in order to obtain a more efficient use of storage y l n space o s
w Compression is often built-in for tape backup hardware e i v De-duplication e h t Avoid to back up mutual data when several systems are backed up s t c Example: A number of workstations may have mutual system files e l f
e Duplication r
n There may be reasons for making backups to several different locations or media o i t a Encryption c i l b Detachable backup units are especially vulnerable in case the get stolen or lost u p
.
) Encryption is useful in this context s / i 0 h . However, encryption is CPU intensive and complicates efficient compression. T 4
/ . a n
s It is therefore better to first compress and subsequently encrypt data o - i y s s b Multiplexing i / s m e
s This enables concurrent backup from more computers than there are backup units (more m n o e c
C than one computer for one backup unit) i
l / n a g Refactoring r e o p . o s In case incremental backup is performed and data is stored to a single tape for a number r n u o
E of computers, there may sometimes be a need for several tapes in order to recover
m e m h t information for a specific computer o
c m e
o Refactoring re-organises backup data so that one tape is sufficient to recover information v r i t f
a t for a specific computer e r r o c p /
/ Staging p : s u s p
Data that is subject to backup is copied to another disk prior to the backup operation. One t t h t h i (
reason for this can be that the source unit and the backup unit operate att different speeds. w ”
l d a e n d o . i n t n u i a
f 2.3 Management of the backup process e
n r r n e e e t h e
t 2.3.1 Goals n b I
d s e 0 a . n i h 4 The list below describes different goals to consider in connection with management of the backup
a ) t e 8 n k i
5 process. o l 8 c
A 5 n e 1 r o 0 i a - t
h Recovery point a 2 S 0 - m 2 r
n The point in time at which it is possible to recover a system o o A f i t n K It is most desirable that the recovery time is as close to the time for data loss as possible i u -
b 1 e i 0 r h Recovery time t t S
t f E A o - Is defined as the time between the point in time for data loss and the point in time for
s 1 e - n d 5 o completed data recovery (short time is desirable) a 1 m 0 m
2 Data security m e (
o b t c C
y To prevent unauthorised users to access the backup e a e j v o m i r
Means for achiving this is encryption and effective routines for handling of media t p h a
c e s i i r Data retention period h h C T w “ Data may need to be retained for a certain time (but not beyond) due to policies and
e regulations s u Further retention of data may imply ineffective use of storage media and unwanted liability y n a r o f
2.3.1 Limitations e l b i s
n The list below describes different limitations to consider in connection with management of the backup o p
s process. e r d l e Time window for backup h e
b The time of day when the backup operation is least disruptive for the organisation t o The needs of users are usually prioritised n n a
c Impact on performance n
o For example, the full "bandwidth" of a hard disk is not available during a backup operation i s s i Costs m
m Hardware, software, man hours o C
For example, is it more time consuming to handle complicated backup solutions than e h t
simpler solutions? d n Bandwidth of network a
, r
o Distributed backup systems may be limited by the bandwidth of the network h t u a
e 2.3.2 Implementation h t f o
y Accomplishing the goals for backup, given existing limitations, may be facilitated through the following l n
o means for implementation. s w e i v Scheduling e h t Automating the backup process may improve reliability and consistency for backups and s t c alleviate the human factor e l f
e Automation is an integral part of many backup solutions r
n Authentication o i t a In order to avoid that unauthorised users can inspect and distort data during the backup c i l b process u p
.
) Trusted employees s / i 0 h . Detached ba ckup units and entire backup systems must be handled by trusted employees T 4
/ . a n
s This is especially important if a third party is responsible for backup and handling of media o - i y s s b for backup i / s m e s m n o e c C 2.3.3 Evaluation of the backup-process i
l / n a g r e o p
. Evaluation of the backup-process may be facilitated through the following activities. o s r n u o E
m e Information about backup m h t o
c That users are notified about how their data is being backed up, and that requirements for m e o v r i t f how backup is performed have been fulfilled.
a t e r r o Reporting c p / / p : Reports can be automatically generated which illustrate use of backup media, status of s u s p
t t h backup units, possible errors, etc. t h i ( w ” Logging l d a e n
d Logging of activities and changes during backup, as a complement to reporting o . i n t n u i a f
e Validation
n r r n e e e t h To check that no errors occur during copying to a backup medium e t n b I
d s
e Use of checksums implies that the original file is not needed for the validation 0 a . n i h 4
a
) Supervision of backup t e 8 n k i 5 o l A third party is supervising the backup process 8 c
A 5 n e 1 r o Users obtain messages of possible errors occuring during backup 0 i a - t h a 2 S 0 - m 2 r n o o A f i
t 2.4 Conclusion n K i u -
b 1 e i 0 r h t t S
t The list below shows some concluding remarks concerning backup. f E A o -
s 1 e - n d 5 o a
1 The importance of data should dictate the need for backup m 0 m
2 m e ( Backed up data is only as useful as its method for recovering data
o b t c C y
e Backed up data should be kept physically separated from the backed up source of information (in a e j v o m i r
t case of fire, flood, etc.) p h a
c e s i i r
h Automation of backup is preferable since it alleviates the human factor h C T w “ Verification of backed up data is important since many things can go wrong during the backup
e operation s u Use of open standards and open file formats for data and files that are backed up and archived is y n a
essential in order to ensure long term sustainability r o f e l b i s n 3. Common Unix- and Linux tools for backup o p s e r
The list below shows commun Unix and Linux tools for backup. d l e h
e Tar b t o Archiving of files and directories n n a Dump/restore c
n Tools for backing up and restoring entire file systems o i s s
i Amanda & Bacula m Tools for backup up data on several computers over a network m o
C Both tools are open source licensed e h
t Other tools d n There are a large number of other open source licensed tools for backup, including (but a
, r not limited to): Areca Backup, Attic, BackupPC, Back In Time, Box Backup, Bup, o h t
u CloudBerry Backup, DirSync Pro, DAR, duplicity, Duplicati, FlyBack, luckBackup, obnam, a
e star/gtar, rdiff-backup, Syncthing, Unison, and git-annex. h t f o y l
n 3.1 Tar o s w
e The list below shows central properties of the backup tool Tar. i v e h t Tar reads several files/directories and archives them in one file for storage and distribution s t c
e The tool was originally intended for backup to tape medium l f e r Tar maintains system information n o access rights, date and time, directory structure i t a c Tar is often combined with external compression i l b
u For example, gzip to create
. ) s / i Example use: 0 h . T 4 Archive: tar -cvf archive.tar file1 file2 file3 / . a n s o -
i Inspect: tar -tvf archive.tar y s s b i / Restore: tar -xvf archive.tar s m e s m
n Tar is included in most linux distributions o e c C i
l / n a g r e o p
. 3.2 Dump/restore o s r n u o E
m The list below shows central properties of the backup tools Dump/restore. e m h t o
c m e o v Dump/restore are standard tools in Unix/Linux to archive and restore entire file systems r i t f
a t e r If the destination medium is smaller than the file system to be backed up, multiple volumes are r o c p / /
p used : s u s p
t Dump/restore maintains system information t h t h i (
access rights, date and time, directory structure w ”
l d a
e Incremental backup is supported n d o . i n t n
u Only files are backed up that have been changed since the latest backup i a f e
n r r n e Different dump levels (0-10) are used, where 0 represents full backup e e t h e t n b I
d
Dump/restore is included in most linux distributions s e 0 a . n i h 4
a ) t e 8 n k i 5 o l 3.3 Amanda 8 c
A 5 n e 1 r o 0 i a - t
h The list below shows central properties of the backup tool Amanda. a 2 S 0 - m 2 r n o o A f i t n K Amanda = Advanced Maryland Automatic Network Disk Archiver i u -
b 1 e i 0 r h Allows for backup of multiple computers over a network t t S
t f E A o -
Features a client/server architecture
s 1 e - n d 5
o Supports full and incremental backup a 1 m 0 m
2 Utilises GNU Tar and dump m e (
o b t
c C Supports both tape- and disk backup y e a e j v o m
i Functionality for scheduling optimises use of resources during backup operations r
t p h a
c e s
i Backup of computers running MS Windows can be performed through use of Samba (smbtar) i r h h C T w “ http://www.amanda.org/ e s u
y 3.4 Bacula n a r o f
The list below shows central properties of the backup tool Bacula. e l b i s n Allows for backup of multiple computers over a network o p s Resembles Amanda e r
d Client/server based, heterogeneous networks, tape/disk/, full/incremental backup l e h
Three main services (daemons) e b
t storage daemon: receives data from the file daemon and writes/reads to media by o n
n command from the director daemon a c file daemon: Located at the client. Provides access to files, encrypts files, and compresses n o i
s files s i
m director daemon: Controls the other daemons, schedules, and interacts with front ends m
o Bacula requires a database C
e For example, MySQL, PostgreSQL, or SQLite h t
d http://www.bacula.org/ n a
, r o h t 3.5 Other tools u a e h t The list below shows links to other backup tools. f o y l n Areca Backup o s http://www.areca-backup.org/ w e i Attic v e
h https://attic-backup.org/ t s t BackupPC c e l f http://backuppc.sourceforge.net/ e r
n Back In Time o i t
a https://github.com/bit-team/backintime c i l Box Backup b u p
. http://www.boxbackup.org/ ) s / i 0 h
. Bup T 4
/ . a n http://bup.github.io/ s o - i y s CloudBerry Backup s b i / s m e http://www.cloudberrylab.com/ s m n o e DirSync Pro c C i
l / n
a http://www.dirsyncpro.org/ g r e o p . DAR o s r n u o http://dar.linux.free.fr/ E
m e m h duplicity t o
c m e http://duplicity.nongnu.org/ o v r i t f
a Duplicati t e r r o c p
/ http://www.duplicati.com/ / p : s u
s FlyBack p
t t h t h i https://code.google.com/archive/p/flyback/ ( w ”
l
d luckyBackup a e n d o . i n http://luckybackup.sourceforge.net/ t n u i a f e
n r obnam r n e e e t h e t n http://obnam.org/ b I
d s e 0 a .
n star/gtar i h 4
a ) t e
8 Available in most Unix/Linux distributions and in other file archiving software n k i 5 o l 8 c
A rdiff-backup 5 n e 1 r o 0 i a
- t http://www.nongnu.org/rdiff-backup/ h a 2 S 0 - m Syncthing 2 r n o o A f i
t https://syncthing.net/ n K i u -
b 1 e i Unison 0 r h t t S
t f E
A https://www.cis.upenn.edu/~bcpierce/unison/ o -
s 1 e - n
d git-annex 5 o a 1 m 0 m
http://git-annex.branchable.com/ 2 m e (
o b t c C y e a e j v o m i r
t p h a 4. Amanda: Install, set up, and use c e s i i r h h C T w “ The text below explains how the backup tool Amanda can be installed, set up, and used in a Ubuntu
e 14.04 LTS Desktop Linux environment. The same procedure is likely to work on most other Linux s u distributions and other versions of the Ubuntu Linux distribution. y n a r o First, if Ubuntu 14.04 is not already installed, install it by downloading an appropriate binary at f e l http://releases.ubuntu.com/14.04/ and by following the installation steps provided by the installer. b i s n o Install Amanda in Ubuntu by using: p s e r
d sudo apt-get update l e h
sudo apt-get install amanda-server amanda-client e b t o To operate the sudo command you may need to enter your administrator credentials. If you have n n a
c installed Ubuntu desktop yourself this should not be a problem since you are the administrator of the n
o machine by default. i s s i m During installation of Amanda, the user "backup" has been created (the user may possibly also be m o "amanda" or "amandabackup"). C e h t A couple of directories need to be created. d n a
, r sudo mkdir /amandasudo chown backup /amanda o h t sudo mkdir /etc/amanda u a e sudo chown backup /etc/amanda h t
f sudo mkdir /dir_to_backup o y l n You can put some files to backup in the "dir_to_backup" for testing purposes. o s w e i sudo mkdir -p /amanda/vtapes/slot{1,2,3,4} v e chown backup /amanda/vtapes/slot{1,2,3,4} h t s
t sudo mkdir -p /amanda/holding c e l chown backup /amanda/holding f e r sudo mkdir -p /amanda/state/{curinfo,log,index} n o i t chown backup /amanda/state/{curinfo,log,index} a c
i l sudo mkdir -p /etc/amanda/MyConfig b u
p chown backup /etc/amanda/MyConfig
. ) s / i 0 h . T 4
/ .
a The /amanda directory is where the data will be put. n s o - i y s s b i / s m e Next, a configuration file amanda.conf needs to be created that holds information about how the s m n o e backup will be performed. Create a file /etc/amanda/MyConfig/amanda.conf with this content: c C i
l / n a g r e o p . org "MyConfig" o s r n u o infofile "/amanda/state/curinfo" E
m e m h logdir "/amanda/state/log" t o
c m e indexdir "/amanda/state/index" o v r i t f
a dumpuser "backup" t e r r o c p / / p : s u
s tpchanger "chg-disk:/amanda/vtapes" p
t t h
t h i labelstr "MyData[0-9][0-9]" ( w ”
l d autolabel "MyData%%" EMPTY VOLUME_ERROR a e n d
o . i n tapecycle 4 t n u i a f e
n r dumpcycle 3 days r n e e e t h
e t n amrecover_changer "changer" b I
d s e 0 a . n i h 4
a ) t e
8 tapetype "TEST-TAPE" n k i 5 o l 8 c
A define tapetype TEST-TAPE { 5 n e 1 r o 0 i a
- t length 100 mbytes h a 2 S
0 - m filemark 4 kbytes 2 r n o o A f
i
t } n K i u -
b 1
e i 0 r h t t S
t f E
A define dumptype simple-gnutar-local { o -
s 1 e
- n
d auth "local" 5 o a 1
m 0 m
compress none 2 m e (
o b
t program "GNUTAR" c C y e a e j v o } m i r
t p h a
c e s i i r h h C
T w “ holdingdisk hd1 { directory "/amanda/holding"
e use 50 mbytes s u chunksize 1 m byte y n
a
} r o
f e l b
i change owner to "backup" for the file. s n o p s e r There is also a need for a disk list entry by creating the file /etc/amanda/MyConfig/disklist containing the d l e
h following line: e
b t o n localhost /dir_to_backup simple-gnutar-local n a c n o i s s i The amcheck command can be used to check the configuration of Amanda: m m o C ~$ amcheck MyConfig e h t Amanda Tape Server Host Check d n a
------, r o NOTE: tapelist will be created on the next run. h t
u
a Holding disk /amanda/holding: 324476928 kB disk space available, using 51200 e h kB as requested t f o
slot 1: contains an empty volume y l n Will write label 'MyData01' to new volume in slot 1. o s NOTE: skipping tape-writable test w e i NOTE: host info dir /amanda/state /curinfo/localhost does not exist v
e h NOTE: it will be created on the next run. t
s t NOTE: index dir /amanda/state/index/localhost does not exist c e l f NOTE: it will be created on the next run. e r
n Server check took 0.574 seconds o i t a c i l Amanda Backup Client Hosts Check b u p
. ------) s / i 0 h
. Client check: 1 host checked in 2.028 seconds. 0 problems found. T 4
/ . a n s o - i y s
s (brought to you by Amanda 3.3.3) b i /
s m e s m n o e c C i
l / n
a Note: If there are problems with permissions for the "backup" user, it is possible to change the g r e o p . "dumpuser" to root and use "sudo" (or log in as root) to perform the backup related commands (in a real o s r n u o situation the problem with permissions for "backup" will need to be solved) E
m e m h t o
c m e To perform the backup, just type: o v r i t f
a t e r r o c p
/ ~$ amdump MyConfig / p : s u s p
t t h t h i To see if the operation was successful, type: ( w ”
l d a e n d o . i n ~$ echo $? t n u i a f e
n r r n e e e t h e t n If a 0 is returned, the operation was successful, otherwise it was not. b I
d s e 0 a . n i h 4
a ) t e
8 To get a report from the backup operation, type: n k i 5 o l 8 c
A 5 n e 1 r o 0 i a
- t ~$ amreport MyConfig h a 2 S
0 - m 2 r n o o A f i
t The report could for example look like this: n K i u -
b 1 e i 0 r h t t S
t f E
A Hostname: gamaz-HP-EliteBook-8440p o -
s 1 e
- n
d Org : MyConfig 5 o a 1
m 0 m
Config : MyConfig 2 m e (
o b
t Date : October 31, 2016 c C y e a e j v o m i r
t p h a
c e s These dumps were to tape MyData02. i i r h h
C
T w “ The next tape Amanda expects to use is: 1 new tape. e s u STATISTICS: y n
a
Total Full Incr. Level:# r o
f
------e l b
i Estimate Time (hrs:min) 0:00 s n
o Run Time (hrs:min) 0:00 p s e Dump Time (hrs:min) 0:00 0:00 0:00 r
d l Output Size (meg) 0.0 0.0 0.0 e h Original Size (meg) 0.0 0.0 0.0 e b
t Avg Compressed Size (%) 100.0 -- 100.0 o n n DLEs Dumped 1 0 1 1:1 a c
n Avg Dump Rate (k/s) 588.2 -- 588.2 o i s s i
m Tape Time (hrs:min) 0:00 0:00 0:00 m o Tape Size (meg) 0.0 0.0 0.0 C
e Tape Used (%) 0.0 0.0 0.0 h t d DLEs Taped 1 0 1 1:1 n a
, Parts Taped 1 0 1 1:1 r o h
t Avg Tp Write Rate (k/s) 100.0 -- 100.0 u
a e h t
USAGE BY TAPE: f o
y Label Time Size % DLEs Parts l n o MyData02 0:00 10k 0.0 1 1 s w e i v
NOTES: e h t
planner: Last full dump of localhost:/dir_to_backup on tape MyData01 s t c overwritten in 3 runs. e l f e taper: Slot 1 with label MyData01 is not reusable r
n o taper: Slot 2 without label can be labeled i t
a
c taper: tape MyData02 kb 10 fm 1 [OK] i l
b u p
. ) s / i 0 h . T
4 DUMP SUMMARY:
/ . a n s o
- DUMPER STATS TAPER i y s s b i / STATS s m e s
m HOSTNAME DISK L ORIG-kB OUT-kB COMP% MMM:SS KB/s MMM:SS n o e c C i
KB/s l / n a g r e ------o p . o s r ---- n u o
E
m localhost /dir_to_backup 1 10 10 -- 0:00 556.9 0:00 e m h t o 100.0 c m e o v r i t f
a t e r (brought to you by Amanda version 3.3.3) r o c p / / p : s u s p
t t h t h i (
In this case the data from the backup was written to the " " folder. The reason
w /amanda/vtapes/slot2 ”
l d a e
n why the MyData02 tape was used and not MyData01 is because the backup operation was performed d o . i n t n u i
a twice by the user. f e
n r r n
e e e t h e t n b I
d s e 0 a . n i h 4
a ) t e 8 n k i 5 o
l Exercises: 8 c
A 5
n e 1 r o 0 i a - t h a 2 Install Amanda, and test the statements above to perform a backup. Play with the Amanda configuration S 0 - m 2 r n
o file and modify it to get a feel for how it works. o A f i t n K
i u -
b 1 e i 0 r h t t S
Implement the procedure of recovering backups using inspiration from the example described here: t f E A o -
s
1 https://wiki.zmanda.com/index.php/GSWA/Recovering_Files e - n d 5 o
a 1 m 0 m
2 m e ( Also test backing up using other source folders and other destination folders (or e.g. flash disks).
o b t c C y e a e j v o
m Also experiment with setting up cronjobs that schedule backup at different different times. For example, i r
t p h a
c e s the lines i i r h h C T w “ 0 18 * * * amanda /usr/sbin/amcheck -m MyConfig 15 3 * * * amanda /usr/sbin/amdump MyConfig
e could be added to /etc/crontab. s u y n You can also test to add email notification at time of backup by adding a line in the amanda.conf file a r o " ". f mailto [[email protected]] e
l b i s n o p s e r
5. Sources d l e h The material in section 2-3 is partially based on information at: e b
t https://en.wikipedia.org/wiki/Backup o n n https://en.wikipedia.org/wiki/List_of_backup_software a c n o Links of relevance for section 4: i s s i Amanda main Wiki page: https://wi ki.zmanda.com/index.php/Main_PageAdditional material on Amanda: m
m https://wiki.zmanda.com/index.php/Amanda_chapter_in_Backup_and_Recovery#Real_life_examplesAman o C
manual pages: http://wiki.zmanda.com/man/amanda.8.htmlPaper on Amanda: e h t
http://wiki.zmanda.com/images/9/9b/Lisa-vii.pdfAmanda tutorial: d n
a http://www.ece.virginia.edu/cheetah/links/helali/amanda.pdf
, r o h t u a e h t f o y l n o s w e i v e h t s t c e l f e r n o i t a c i l b u p
. ) s / i 0 h . T 4
/ . a n s o - i y s s b i / s m e s m n o e c C i
l / n a g r e o p . o s r n u o E
m e m h t o
c m e o v r i t f
a t e r r o c p / / p : s u s p
t t h t h i ( w ”
l d a e n d o . i n t n u i a f e
n r r n e e e t h e t n b I
d s e 0 a . n i h 4
a ) t e 8 n k i 5 o l 8 c
A 5 n e 1 r o 0 i a - t h a 2 S 0 - m 2 r n o o A f i t n K i u -
b 1 e i 0 r h t t S
t f E A o -
s 1 e - n d 5 o a 1 m 0 m
2 m e (
o b t c C y e a e j v o m i r
t p h a
c e s i i r h h C T w “ Licensed under the Creative Commons Attribution Share Alike License 4.0 e s u
y This project (2015-1-ES01-KA202-015858) has been funded with support from the European Commission. n a
r This publication reflects the views only of the author, and the Commission cannot be held responsible for o f any use which may be made of the information contained therein. e l b i s n o p s e r d l e h e b t o n n a c n o i s s i m m o C e h t d n a
, r o h t u a e h t f o y l n o s w e i v e h t s t c e l f e r n o i t a c i l b u p
. ) s / i 0 h . T 4
/ . a n s o - i y s s b i / s m e s m n o e c C i
l / n a g r e o p . o s r n u o E
m e m h t o
c m e o v r i t f
a t e r r o c p / / p : s u s p
t t h t h i ( w ”
l d a e n d o . i n t n u i a f e
n r r n e e e t h e t n b I
d s e 0 a . n i h 4
a ) t e 8 n k i 5 o l 8 c
A 5 n e 1 r o 0 i a - t h a 2 S 0 - m 2 r n o o A f i t n K i u -
b 1 e i 0 r h t t S
t f E A o -
s 1 e - n d 5 o a 1 m 0 m
2 m e (
o b t c C y e a e j v o m i r
t p h a
c e s i i r h h C T w “