On Tue, Aug 7, 2012 at 9:47 AM, Tyler J. Wagner <ty...@tolaris.com> wrote:
> On 2012-08-07 15:07, Tobias Stroh wrote:
>> 2) Database
>>
>> I would suggest not abusing the file system as database and using something
>> like SQLite. This gives you features like transactions, atomic operations,
>> etc. and also improves speed.
>
> I do not understand why people object to MySQL for this. If you're going to
> use a database, use a good one. Sqlite is fine for small, simple apps doing
> a small number of transactions. BackupPC is not that. MySQL is fast
> (enough), reliable (enough), and well understood with tons of useful HOWTOs
> and software tools (phpmyadmin, mytop, mysqldump, webmin).
My experience with trying to scale mysql up has not been that great,
but it is from several years ago and maybe things have gotten better.
The suggestion for sqllite was probably just to handle metadata
operations (directory lists, mapping to chunks, reference counts of
chunks, etc.) rather than the file content itself. While it could
probably do that, you still need to tie the db transactions to the
filesystem operations in some sort of transaction-managed steps that
will at best slow everything down.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
