On Friday, September 1, 2017 at 4:49:44 PM UTC-7, James Lampert wrote:
>
> What I finally ended up with was a shell script, running on the local
> machine to which we are backing up:
> 1. Use ssh with a remote command to hotcopy the trac project to the home
> directory on the cloud box.
> 2.
What I finally ended up with was a shell script, running on the local
machine to which we are backing up:
1. Use ssh with a remote command to hotcopy the trac project to the home
directory on the cloud box.
2. Use rsync to synchronize the cloud box's hotcopy with a copy in the
local box's home
On Friday, September 1, 2017 at 10:55:22 AM UTC-7, RjOllos wrote:
>
> I'd use rsync on the Trac environment.
>
> If using SQLite this might result in large transfers for small changes to
> the database. I'm unsure if it's a compressed file. I'd suggest logging the
> data transfer size.
>
From: James Lampert
Sent: Friday, September 1, 09:59
Subject: [Trac] Local backup of a Trac server running in the cloud
To: Trac Users
We currently have our active Trac and SVN servers running in the cloud. And
(naturally) there's a data egress charge for the cloud servers.
I've just started
We currently have our active Trac and SVN servers running in the cloud. And
(naturally) there's a data egress charge for the cloud servers.
I've just started backing up the SVN server locally, using svnsync to
mirror the active SVN server locally (and incrementally), and then backing
up the
