Hi Greg, Maybe similar features to that of bacula (my current backup software of choice for my wifes business servers). This is a very comprehensive open source solution that has many of the features requested below. eg. multiple servers, pooling, aging etc. It is a good example of what my own requirements would be.
Is the intention to have a MySQL type plugin? eg. will it have an api that will be open to other backup solutions being able to utilise what will be written? It would be nice to be able to utilise a standard XBSA solution giving access to the database from any one of the major enterprise backup solutions, eg. Legato Networker, Veritas Netbackup, HP Dataprotector etc. etc. This would allow an enormously simple and straightforward integration into many of the existing corporate solutions that exist around the world. Regards --------------------------------------------------------------- ********** _/ ********** David Logan ******* _/ ******* ITO Delivery Specialist - Database ***** _/ ***** Hewlett-Packard Australia Ltd **** _/_/_/ _/_/_/ **** E-Mail: [EMAIL PROTECTED] **** _/ _/ _/ _/ **** Desk: +618 8408 4273 **** _/ _/ _/_/_/ **** Mobile: 0417 268 665 ***** _/ ****** ****** _/ ******** Postal: 148 Frome Street, ******** _/ ********** Adelaide SA 5001 Australia i n v e n t --------------------------------------------------------------- -----Original Message----- From: Duzenbury, Rich [mailto:[EMAIL PROTECTED] Sent: Tuesday, 9 May 2006 6:39 AM To: mysql@lists.mysql.com Subject: RE: Backups with MySQL/InnoDB > -----Original Message----- > From: Daniel da Veiga [mailto:[EMAIL PROTECTED] > Sent: Monday, May 08, 2006 1:55 PM > To: mysql@lists.mysql.com > Subject: Re: Backups with MySQL/InnoDB > > On 5/8/06, David Hillman <[EMAIL PROTECTED]> wrote: > > On May 7, 2006, at 11:29 PM, Robert DiFalco wrote: > > > Fast, incremental, compressed, and no max-size > limitations. Must be > > > transaction safe; able to run while transactions are going on > > > without including any started after the backup began; the > usual stuff. > > > > Incremental, transaction safe, compressed, fast, no-max-size. > > ( In order ) > > > > Those are certainly the most important features (and I'll be > glad to beta-test it ;) I'll add: manage multiple servers, > deal with replication (using the replicated server as a > backup would be cool), manage binlogs (date and purge) and be > compatible with version 4.1 and above (I don't plan on using > the 5 version any time soon). > > > -- > > David Hillman > > LiveText, Inc > > 1.866.LiveText x235 > > > > > > > In addition, I'd like to see a configurable option for how often to take a full and or incremental backups, a mechanism to age the backups and drop them after a certain amount of time. For example, I want a simple way to keep four weekly near line backups each month, then age off and keep one backup for each of the previous 11 months, and then just one backup per year. This would be about 1T of data for us. It would then be really sweet to be able to say 'restore a full backup of x database as of April 2, 2005 at 8:42 am' and have it create a new instance on a user defined port, then restore the closest previous full, then apply the binlogs up to the correct point in time. Thanks. Regards, Rich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]