[Gnumed-devel] Unexpected backups

[Busser, Jim]

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?

-- JIm