Split exercise 6 into its own repository
This commit is contained in:
parent
d5d5df65b0
commit
487785080a
3
Labb5/ovning6.md
Normal file
3
Labb5/ovning6.md
Normal file
@ -0,0 +1,3 @@
|
||||
# Exercise 6, lab 5 #
|
||||
This exercise now lives in it's own repository at
|
||||
[Proxmox-backup](https://github.com/jackbenny/proxmox-backup).
|
@ -1,50 +0,0 @@
|
||||
# Serverbackup #
|
||||
This is exercise 6 on lab 5 which is about writing a backup script for your
|
||||
server.
|
||||
For this exercise I've chosen to make a backup script for Proxmox, ie take all
|
||||
the backup files (vzdump-openvz-111-2013\_11\_19-08\_20\_20.tar.lzo and so on)
|
||||
and copy them to a tape device and an external harddrive.
|
||||
|
||||
## Short introduction on usage ##
|
||||
At the top of the script there are several variables which you need to set
|
||||
to match your system. The most important ones are __BackupDir__ which
|
||||
is where your Proxmox server places it's backup files. On my system this is
|
||||
/mnt/backup/dump (note: no trailing slash should be entered in the variables).
|
||||
Then we have __TapeDev__ which is your Tape device. Most tape devices show up
|
||||
as st0, st1, st2 and so on (st = SCSI Tape).
|
||||
Next is the __ExtHDD__ variable which you should set to your external HDD if
|
||||
you want to backup to an external harddrive. After this you set __MntPoint__
|
||||
which is where you would like to mount your external harddive.
|
||||
Next variable is __ExtHDDdir__ which you set to where you would like your
|
||||
backup-files on your external harddrive.
|
||||
A very important variable is __Where__. Here you'll define if you would place
|
||||
your backup on your tape device or an external harddrive, or both. If you set
|
||||
__Where__ to Tape only a tape backup will be performed. If you set it to HDD
|
||||
the backup files will only to copied to your external harddrive. If you set it
|
||||
to Tape&HDD your backup files will be placed on both an external harddrive and
|
||||
on your tape device.
|
||||
|
||||
You can place your script wherever you on your system. When the script runs it
|
||||
will cd into your Proxmox backups files and perform it's action from there.
|
||||
|
||||
All error messages are printed to STDERR and all normal messages are printed to
|
||||
STDOUT. Because of this you can run this script headless and save the output
|
||||
in separate logfiles depending on whatever it's an error or normal messages.
|
||||
For example you can run it like this:
|
||||
```bash
|
||||
./serverbackup.sh > backupmessages.log 2> backuperrors.log
|
||||
```
|
||||
|
||||
### Taperotate ###
|
||||
This is just a small complementary script to serverbackup.sh. The script keep
|
||||
track on which tape you last used for your backup so you'll know which tape
|
||||
to use next. Either you can run the script by itself or include it on the same
|
||||
line as serverbackup such as `./serverbackup.sh && ./taperotate.sh`. Each time
|
||||
taperotate is run a new line is printed in the tapefile.txt file which contains
|
||||
the tape used. The next time the script is run it automatically increases the tape
|
||||
number by one.
|
||||
|
||||
The first time you run taperotate.sh you'll have to initialize it with the -i N
|
||||
option where N is the tape you start with. If you change the order of the tapes
|
||||
later on you can use the -i option again to start over with tape N (the old lines
|
||||
will be kept though to keep track on the old backups).
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user