[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Unexpected backups
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] Unexpected backups |
Date: |
Fri, 9 Aug 2013 11:10:16 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Aug 09, 2013 at 08:15:27AM +0000, Jim Busser wrote:
> I have started to work with the backup scripts in the debian environment
> which I created around July 18th.
>
> Despite that yesterday (Aug 8th) was the first and only time AFAICT that I ran
>
> sudo sh gm-backup_database
>
> I discovered via sudo ls -al in
>
> /var/lib/gnumed/server/backups
>
> more than just the suitably sized ...
>
> -rw-r--r-- 1 root root 41707520 Aug 8 17:33
> backup-gnumed_v18-GNUmed_Team-debian-2013-08-08-17-32-57.tar
>
> … but, rather, also the following:
>
> total 40776
> drwxrwx--- 2 root root 4096 Aug 8 17:33 .
> drwxr-xr-x 6 root root 4096 Jul 18 13:41 ..
> -rw-r--r-- 1 root root 6940 Jul 21 13:19
> backup-gnumed_v18-GNUmed_Team-debian-2013-07-21-13-19-06-roles.sql
> -rw------- 1 root root 1292 Jul 21 13:19
> backup-gnumed_v18-GNUmed_Team-debian-2013-07-21-13-19-06.tar.bz2
> -rw-r--r-- 1 root root 6940 Jul 26 08:02
> backup-gnumed_v18-GNUmed_Team-debian-2013-07-26-08-02-07-roles.sql
> -rw------- 1 root root 1297 Jul 26 08:02
> backup-gnumed_v18-GNUmed_Team-debian-2013-07-26-08-02-07.tar.bz2
> -rw-r--r-- 1 root root 6940 Aug 7 00:04
> backup-gnumed_v18-GNUmed_Team-debian-2013-08-07-00-04-20-roles.sql
> -rw------- 1 root root 1286 Aug 7 00:04
> backup-gnumed_v18-GNUmed_Team-debian-2013-08-07-00-04-20.tar.bz2
>
> and while I seemed to recall some mention of backups being
> generated as part of database upgrading, and so I wondered
> whether the above originated (July 21) from my original
> bootstrap and then again (July 26 and August 7th) from
> fixups, I wondered about the tiny sizes of these files. Even
> after the last-named .tar.bz2 is untarred, it expands only
> from 1286 to 10240 byles. Did a more substantial data file
> exist, but only temporarily, such that when the upgrade
> completed successfully, the more-substantial (temporay) file
> was deleted?
Installing the Debian server package helpfully creates a
cron job for you running once per day:
/etc/cron.daily/gnumed-server
That script first runs the backup script and then the
zip+sign script. Both will read configuration from
/etc/gnumed/gnumed-backup.conf
Setting the database name to "" will render dysfunctinal
(all !) runs of the backup script.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346