Make suggestions and request new features for any product in the InnoDB family. http://forums.innodb.com/list.php?7 Tue, 07 Sep 2010 14:51:26 +0300 Phorum 5.2.13 http://forums.innodb.com/read.php?7,978,978#msg-978 http://forums.innodb.com/read.php?7,978,978#msg-978
There is two things that can be really wonderfull about backup:

** innodb hot backup

t1 : start ibbackup
t2 : end ibbackup ( ibdata and other ibd files are generated, but no ib_logfile)
t3 : start ibbackup --apply-log
t4 : end ibbackup --apply-log (ibdata and others ibd are consistant, and ib_logfile are generated)

so at t4, the databases backup are identical as the originals at the t3 time.

Instead of the --apply-log at t3, a command like --unapply-log would may rollback modifications to make the databases backup identical to the originals at time t1.

** .ibd files, innodb_file_per_table mode

it would be great if we can detach an ibd file of a table dans attach it on any other,
it would be easy to backup and copy tables.

especially on a SAN storage with SAN Snapshot

- the procedure to make a copy of a table would be :

# CREATE TABLE mytable_save LIKE mytable;
# ALTER TABLE mytable_save DISCARD TABLESPACE; -- dettach and drop ibd files
# ALTER TABLE mytable DETTACH TABLESPACE; -- dettach and NOT drop ibd files
# cd /data/database/ ; cp mytable.ibd mytable_save.ibd -- copie the tablespace
# ALTER TABLE mytable_save IMPORT TABLESPACE; -- attach

- the procedure to make a backup of the full database stored on a SAN :

# flush tables with read lock
# snapshot
# unlock tables

So we could easily mount the snapshot, copy the ibd files and then restore a table.

I think these two fonctionnality can make MySQL and innodb really powerfull.


Victor
DBA MySQL]]> vtaing Suggestion Box Wed, 06 Jan 2010 19:55:41 +0200 http://forums.innodb.com/read.php?7,713,713#msg-713 http://forums.innodb.com/read.php?7,713,713#msg-713
This would probably be helpful for all options but it is particularly relevant for the --apply-log option because it is likely to be run on a server with a different hostname.]]> Ladadadada Suggestion Box Tue, 24 Aug 2010 18:15:06 +0300 http://forums.innodb.com/read.php?7,591,591#msg-591 http://forums.innodb.com/read.php?7,591,591#msg-591
Thanks,

-Ryan]]> rhuddleston Suggestion Box Thu, 14 May 2009 08:23:40 +0300 http://forums.innodb.com/read.php?7,375,375#msg-375 http://forums.innodb.com/read.php?7,375,375#msg-375
I stumbled upon the suggestion of "table-wide encryption", which, if I'm not mistaken, involves encrypting the entire table at storage time, and decrypting it when it's loaded for use. Which brings me here - could I get some input from someone here on this matter? And would I be wasting my time opening up the source code when there's already a suitable solution available in MySQL/InnoDB which I've overlooked?
I'm also weighing up, should it come to modifying source code, whether to work on modifying InnoDB, or learn enough of MySQL's storage engine API to build my own (inevitably primitive, but hopefully suffficient) storage engine to suit my needs. Neither really sounds pleasant or approachable, but which way should I go?

A few things to note: the suggestion of drive encryption at the OS level has been made, and I don't like it; and whilst performance would be nice, this project can eschew it if necessary.]]> Fenrisulvur Suggestion Box Tue, 30 Jun 2009 19:29:18 +0300 http://forums.innodb.com/read.php?7,333,333#msg-333 http://forums.innodb.com/read.php?7,333,333#msg-333 cjgrillo Suggestion Box Fri, 05 Dec 2008 00:06:37 +0200 http://forums.innodb.com/read.php?7,154,154#msg-154 http://forums.innodb.com/read.php?7,154,154#msg-154
I have a need when backing up databases/tables to be more specific than the POSIX EREG rules allow. Particularly, I need the ability to exclude certain tables from backups; it is not possible to do so. I need either a '--exclude' flag to the binary, or preferably an (optional) perl-conpatible regex (PREG) support so that lookahead/lookbehind assertions and other more complex matching is possible on the table/database names.

One easy example is on a 24GB innodb database. 18GB of the data is stored in only 8 tables (of the 72 in this db), and I need to periodically not back up these large tables. With a '--exclude' I could pass in '--exclude "dbname\.history_*"', and if PCRE regex support was added I could just do something like '--include "(mysql|zabbix)/(?!history)"'.

This is a really necessary addition, I won't go into why you're using only POSIX EREG and have no equivalent --exclude, but with such expensive/niche commercial software, that's a big failing and an extremely easy addition.

Thanks,

/eli]]> eli.stair Suggestion Box Fri, 01 Aug 2008 02:51:18 +0300 http://forums.innodb.com/read.php?7,117,117#msg-117 http://forums.innodb.com/read.php?7,117,117#msg-117 * backup writes to a socket rather than staging files locally
* multiple threads used to read *.ibd files on backup
* multiple threads used to copy in *.ibd files on restore

Is there any chance we will get them? If you publish the source, I will add them.]]> mdcallag Suggestion Box Sat, 07 Jun 2008 03:16:01 +0300 http://forums.innodb.com/read.php?7,94,94#msg-94 http://forums.innodb.com/read.php?7,94,94#msg-94
This is roughly 8MB of data.

If you have queries like:

SELECT * FROM FOO WHERE ID = X;

These can either use the index, or they could be ignored if you have a bloom filter.

The filter would just include known records.

This just used by MySQL to ignore the SQL and return an empty result set if there's no possibility that the record is on disk.

With about an 800k bloom filter you can remove 97% of these checks.

The worse case scenario is that you end up falling through to disk for some of the false positives.

Thoughts?]]> burtonator Suggestion Box Sat, 24 Jan 2009 03:07:18 +0200 http://forums.innodb.com/read.php?7,64,64#msg-64 http://forums.innodb.com/read.php?7,64,64#msg-64
It will be nice if InnoDB team can extend the SHOW TABLE STATUS to show the compression details. Right now the Information schema.cmp will only lists general compression statistics but not on per table basis.

Also, it will be added advantage if they can support the following two config variables:

innodb_default_row_format (default compact or dynamic and making innodb_default_row_format=compact by default).
innodb_default_key_block_size (optionally, and make sure it does not raise a warning on default row_format)]]> KenJacobs Suggestion Box Sat, 26 Apr 2008 22:24:34 +0300