Re: couple issues

I wrote:

> I'll ask one of our horde of backup and storage management experts
> for an opinion.

I did, and in short: The days when it was considered a Good Thing for
backup tools to know about the semantics of a database are long gone. If
your backup app is running locally on the server, it's much faster to
copy whole files or even whole volumes. Anything else just burns resources.

Incremental database backups these days are done by having the
/database/ tell the backup app what and when to copy out; after all, the
database knows best what's ready and when. Some especially smart backup
agents can pull data directly out of the database's shared memory cache,
thereby reducing the number of copy ops even more.

Given that, let's worry about online incremental backups once we need
subversion on high-availability servers. We'd probably have to implement
the filesystem on somethig other than DB3 by then, too.

-- 
Brane �ibej
    home:   <brane_at_xbc.nu>             http://www.xbc.nu/brane/
    work:   <branko.cibej_at_hermes.si>   http://www.hermes-softlab.com/
     ACM:   <brane_at_acm.org>            http://www.acm.org/