Re: after migration: question about recommended backup procedure

I have been doing a two-step back, as you suggest, to backup our trackers. Instead of using 'roundup-admin export' I have been using 'tar -pczf' (preserve permissions, create, compress, output file) to capture the files and 'pg_dump --format=tar... && gzip -9...' to capture the PostgreSQL database tables. Each tracker has this pair of files. Adding the output from 'date +%w-%a' (day number of week and 3 character day of week) to the filename pairs gives a 7 day rolling backup. The whole process took 31 minutes to perform this morning on all 33 of our trackers.

Restoring is likewise quick using 'tar -xf' to the appropriate directory and pg_restore to restore the database tables.

Tom Ekberg
Senior Computer Specialist, Lab Medicine
University of Washington Medical Center
1959 NE Pacific St, MS 357110
Seattle WA 98195
work: (206) 598-8544
email: [email protected]

On Tue, 26 Jan 2016, Ralf Schlatterbeck wrote:

> Date: Tue, 26 Jan 2016 17:41:08 +0100
> From: Ralf Schlatterbeck <[email protected]>
> To: [email protected]
> Subject: Re: [Roundup-users] after migration: question about recommended
>     backup procedure
> 
> On Tue, Jan 26, 2016 at 04:45:34PM +0100, Peter Funk wrote:
>> We had during the past 11 years a cron script running hourly
>> which simply copied the tracker home directory using the
>> rsync program.  I'm aware of the fact that this was probably
>> a little bit risky if a transaction happened to the sqlite db
>> file during the process of copying of this file.
>>
>> Now with mysql as our backend I assume we should use mysqldump
>> to take snapshot backups of the RDBMS.  Am I right?
>
> Yes, a combination of rsync (for the tracker code and the messages and
> files that roundup puts in the filesystem) and a database dump is the
> way to go.
>
> Note also that roundups export format can take *ages* to import for
> large databases. I have used roundup export for quite some time as a
> backup and did a re-import after every backup. In the end that simply
> didn't finish in 24 hours. In addition csv records can get huge and you
> need workarounds like "csv_field_size" in the trackers config.ini to
> make export/import work for your database...
> It's good to convert from one backend to another but too brittle for
> regular backup use.
>
> Ralf
> -- 
> Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
> Open Source Consulting                  www:   http://www.runtux.com
> Reichergasse 131, A-3411 Weidling       email: [email protected]
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
> _______________________________________________
> Roundup-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/roundup-users
>


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140