On 12/17/2010 08:44 AM, Matt Shields wrote: > > > The ability for it to work not only through it's native communication > method (usually custom port/protocol), but also be able to run over an > SSH tunnel. Sometimes you don't want to open up that port to the > outside world even if it is encrypted, so being able to tell it to > start an SSH tunnel. Have that be part of the configuration where you > can specify the username/password or keypair to let it establish it's > own SSH tunnel. Also, be able to specify a bandwidth limit on transfers. I'm not sure that applies to the market I'm targeting, I need to think about it. > > Ability to do full, differentials and incremental backups. Absolutely, compression as well. > > Like Chris mentioned, the ability to easily browse the backups and > pull out specific files/directories. Already planned. > > Since it's not a good practice to touch the raw files for MySQL > (probably not for PostgreSQL either), be able to exclude path's. But > also be able to specify there is a database and do a db backup. For now, I'm going to punt on databases. That may be a version 1.1 feature. > > -matt > >
_______________________________________________ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss
