On 07/25/2013 10:51 PM, Emilien Klein wrote: > I'm working on the upgrade steps needed for GNU Health 2.0. > Their README file lists making a copy of the database as the second > step, which seems like a very good idea: > > pg_dump gnuhealth181 > backup181.sql > > My question is where in the filesystem on Debian should I put these > backup copies? I would say /var/lib/gnuhealth/backups or something like
> Is there another package part of Debian Med that is making backups of > it's data[base] before upgrading? How is that handled? > > Or would backing up before upgrading be a feature already baked into > dbconfig-common and I'm just not opening my eyes enough? ([0] mentions > backing up, but I can't find any other mention elsewhere) As far as I know, there is no automatic step for this. All db stuff has to be manually managed with upgrade/backup failure detection. Olivier > > +Emilien > > [0] > http://people.debian.org/~seanius/policy/examples/dbconfig-common/doc/dbapp-policy.html > <http://people.debian.org/%7Eseanius/policy/examples/dbconfig-common/doc/dbapp-policy.html> -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
