File: gm-move_backups_offsite.8

package info (click to toggle)
gnumed-server 22.15-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 46,556 kB
  • sloc: sql: 1,217,005; python: 15,469; sh: 1,553; makefile: 20
file content (46 lines) | stat: -rw-r--r-- 1,148 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
.TH GM-MOVE_BACKUPS_OFFSITE 8 "2011 May 10th" "GNUmed backups offsiting"

.SH NAME
.B gm-move_backups_offsite
- move GNUmed backups to elsewhere

.SH SYNOPSIS
.B gm-move_backups_offsite

.SH DESCRIPTION
The
.B gm-move_backups_offsite
script can be used to move backups to another host, IOW
storing them "offsite" in the loosest sense of the word.

.SH EXAMPLE

Imagine the following situation:

1) a laptop running client and database which is
   taken to the office, to patients, etc

2) a desktop at home with some spare storage

3) the laptop is occasionally connected to the home
   network and thus has access to the desktop machine

Given appropriate configuration of
.B gm-move_backups_offsite
one could add the following two lines to the cron
script on the laptop to make sure database backups
are replicated to the desktop whenever the laptop
has access to it:

@reboot         /usr/bin/gm-move_backups_offsite.sh

5 0-23 * * *    /usr/bin/gm-move_backups_offsite.sh


.SH SEE ALSO
.B /etc/gnumed/gnumed-backup.conf


.SH AUTHOR
This manual page was written by Karsten Hilbert, for the
Debian GNU/Linux system (but may be used by others).