It's not something I had considered for this use case as the files in question are uploaded site files (for example, images) as opposed to site code, and can sometimes total up to 10GB+. I'm assuming you thought I was talking about code files which is why you suggested a VCS?
On 17 June 2015 at 15:28, Les Mikesell <[email protected]> wrote: > On Wed, Jun 17, 2015 at 8:01 AM, Andy Taylor <[email protected]> wrote: > > > > The 'big picture' is that our developers use the > > restored files on the network file share server as copies of live website > > files, so when they are developing they can be sure they are looking at > > relatively up-to-date copies of the files which are on our live servers. > We > > could have rsynced those files directly from the live server, but using > > BackupPC saves on duplication and has the added benefit of testing our > > backups. > > Have you considered using a central version control system like > subversion for this instead? You would need to have a process to > ensure that the live system was always updated from a tagged/known > revision, but then updating all the development workspaces to stay in > sync becomes easier and more efficient. > > -- > Les Mikesell > [email protected] > > > ------------------------------------------------------------------------------ > _______________________________________________ > BackupPC-users mailing list > [email protected] > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ >
------------------------------------------------------------------------------
_______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
