MySQL Enterprise Backup 8.0.16 has been released
MySQL Enterprise Backup 8.0.16, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 8.0.16 supports only the MySQL Server 8.0.16. For earlier versions of MySQL 8.0, use the MySQL Enterprise Backup version with the same version number as the server. For MySQL server 5.7, please use MySQL Enterprise Backup 4.1, and for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.16 is given below. -- Changes in MySQL Enterprise Backup 8.0.16 (2019-04-25, GA) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * mysqlbackup now supports encrypted InnoDB undo logs (http://dev.mysql.com/doc/refman/8.0/en/innodb-tablespace-encryption.html#innodb-tablespace-encryption-undo-log). The encrypted undo tablespaces are handled the same way as the encrypted tablespaces for InnoDB tables. See Working with Encrypted InnoDB Tablespaces (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-encrypted-innodb.html) for details. * Near the end of the backup process, instead of locking the whole server instance for a brief period of time, mysqlbackup now applies these locks consecutively: 1. A backup lock (http://dev.mysql.com/doc/refman/8.0/en/lock-instance-for-backup.html) on the server instance, which blocks DDLs (except those on user-created temporary tables), but not DMLs on InnoDB tables. 2. A FLUSH TABLES tbl_name [, tbl_name] ... WITH READ LOCK (http://dev.mysql.com/doc/refman/8.0/en/flush.html#flush-tables-with-read-lock-with-list) operation on all non-InnoDB tables, for copying the relevant ones among them into the backup. This step is skipped if no user-created non-InnoDB tables exist. 3. A brief blocking of logging activities on the server, for collecting logging-related information. See The Backup Process (https://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-backup-process) for details. The removal of the lock on the whole server instance reduces disruption to the database service by the backup operation. Important The change requires that the BACKUP_ADMIN (http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_backup-admin) and SELECT (http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_select) privileges on all tables be granted to the user by which mysqlbackup connects to the server (the BACKUP_ADMIN (http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_backup-admin) privilege is automatically granted to users with the RELOAD (http://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_reload) privilege when an in-place upgrade to MySQL Server 8.0 from an earlier version is performed). * mysqlbackup now supports dynamic changes to undo tablespaces (http://dev.mysql.com/doc/refman/8.0/en/innodb-undo-tablespaces.html) on the server being backed up. During a restore, the default undo tablespaces, as well as any non-default undo tablespaces resided in the backed-up server's data directory, are restored to the location pointed to by the mysqlbackup option --innodb_undo_directory. Non-default, external undo tablespaces are restored to the locations they were found on the backed-up server. See undo log files (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-files-backed-up-summary.html#meb_file_undo-log-files) for details. * In addition to the requirement that the target data directory for a restore specified by the --datadir option must be non-existent or empty, mysqlbackup now enforces the same rule for the --innodb_data_home_dir, --innodb_log_group_home_dir, and --innodb_undo_directory options (the --force option cannot be used to override the requirement on the three options). Bugs Fixed * Zip packages of mysqlbackup contained duplicate files, which have now been removed. (Bug #29497272, Bug #94683) * mysqlbackup might quit unexpectedly if it lost its connection to the server at the middle of a backup operation. With this fix, mysqlbackup exits gracefully in the situation after throwing the appropriate errors. (Bug #29376006) * Restore of an incremental backup failed if, on the server, some binary log files had been purged in between the times the incremental backup
MySQL Enterprise Backup 3.12.4 has been released
Dear MySQL users, MySQL Enterprise Backup v3.12.4, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.12.4 is given below. Changes in MySQL Enterprise Backup 3.12.4 (2019-02-15) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Information on the executed GTIDs is now includfed in the mysqlbackup output and the backup log when the backed-up server has GTIDs enabled. (Bug #25978803) * A backup became corrupted if, during the backup process, a DDL operation that took advantage of MySQL server's online DDL feature (http://dev.mysql.com/doc/refman/5.6/en/innodb-online-ddl.html) occurred. This was because mysqlbackup did not support the server feature---and it still does not. This fix avoids the error by having mysqlbackup turn the server's system variable old_alter_table to "1" at the beginning of a backup if it is "0," so that any DDL operations that take place during the backup are handled with the old table copy method. mysqlbackup then turns the variable back to "0" near the end of the backup operation. Important Notice that in cases where mysqlbackup quits unexpectedly and does not turn old_alter_table back to its original value, the user will have to turn the value back to "0" manually on the server, in order to return the server to its original configuration. This should be performed if the statement "Server system variable 'old_alter_table' was set to '0'. Setting it to '1'" appears in the early output of mysqlbackup, but the statement "Setting server system variable 'old_alter_table' back to '0'" does not appear before mysqlbackup quits. (Bug #25217215) * A new option, --skip-final-rescan, makes mysqlbackup skip the final rescan for InnoDB tables that are modified by DDL operations after the database has been locked near the end of a backup operation. This potentially shortens the duration for the lock and reduces the backup's impact on the server's normal operation. See the description for --skip-final-rescan for details. (Bug #21094221) * The output by mysqlbackup, which goes to the stderr stream and the message log, has now been improved to include the timestamps and thread IDs for all steps taken by mysqlbackup, in order to provide more information for debugging purposes. (Bug #20142619) * When there were no tables matching the regular expression specified with the --include-tables option during a backup operation, mysqlbackup still created a backup, which contained an empty folder for each database on the server. mysqlbackup now throws an error when --include-tables selects no tables to be backed up. (Bug #18114353) * During the final stage of a backup when MySQL Enterprise Backup tried to temporarily put the database into a read-only state using the FLUSH TABLES WITH READ LOCK statement in order to copy non-InnoDB files, if a long query was running on the server at the same time, the FLUSH TABLES WITH READ LOCK statement could be taking too long to finish, holding up further queries and eventually bringing down the server. A new mysqlbackup option --lock-wait-timeout can now be used to specify the timeout in seconds for the FLUSH TABLES WITH READ LOCK statement. If the timeout is exceeded, the statement is failed and the lock on the tables is released, so that queries held up by the lock can then be executed. mysqlbackup then retries the statement and continues with the backup. Default value for --lock-wait-timeout is 60 [seconds]. (Bug #14339483) * In order to minimize the impact of a hot backup on the MySQL server, the copying of the buffer pool dump files and some of the metadata files is now performed before the final phase of the backup in which the server instance is locked. This shortens the duration for the lock and reduces the backup's impact on the server's normal operation. Also, to minimize the resource used on a backup, the copying of the buffer pool dump files is no longer performed for partial and offline backups, for which the buffer pool dump is usually not very useful. Bugs Fixed * While MySQL Server interprets the system v
MySQL Enterprise Backup 8.0.15 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.15, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 8.0.15 supports only the MySQL Server 8.0.15. For earlier versions of MySQL 8.0, use the MySQL Enterprise Backup version with the same version number as the server. For MySQL server 5.7, please use MySQL Enterprise Backup 4.1 and for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.15 is given below. Enjoy! -- Changes in MySQL Enterprise Backup 8.0.15 (2019-02-01) This release contains no functional changes and is published to align version number with the MySQL Server 8.0.15 release. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 8.0.14 has been released
MySQL Enterprise Backup 8.0.14, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 8.0.14 supports only the MySQL Server 8.0.14. For earlier versions of MySQL 8.0, use the MySQL Enterprise Backup version with the same version number as the server. For MySQL server 5.7, please use MySQL Enterprise Backup 4.1 and for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.14 is given below. -- Changes in MySQL Enterprise Backup 8.0.14 (2019-01-21, General Availability) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * mysqlbackup now supports encrypted binary and relay log. See Working with Encrypted Binary and Relay Logs (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/advanced.encrypted-binlog-relaylog.html) for details. * mysqlbackup now supports the --ssl-fips-mode option, which controls whether mysqlbackup operates in FIPS mode. See FIPS Support (http://dev.mysql.com/doc/refman/8.0/en/fips-mode.html) for details. Bugs Fixed * An apply-incremental-backup operation failed with an error (RDR1 ERROR: Unable to remove relaylog files from full backup) when the incremental backup was created with the --compress option. (Bug #28366241) * mysqlbackup quit unexpectedly during an apply-incremental-backup operation if the backed up server had been started using relative paths for --datadir and --log-bin. (Bug #28334521) * Attempts to restore a backup of a MySQL 5.7 Server to a MySQL 8.0 Server resulted in a strange error message (Server_version is not obtained). With this fix, mysqlbackup now indicates that the operation is not supported. For related information, see Restoring a Backup with a Database Upgrade or Downgrade (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/restore-upgrade.html). (Bug #27952379) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 8.0.13 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.13, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 8.0.13 only supports MySQL Server 8.0.13. For earlier versions of MySQL 8.0, use the MySQL Enterprise Backup version with the same version number as the server. For MySQL server 5.7, please use MySQL Enterprise Backup 4.1 and for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.13 is given below. Changes in MySQL Enterprise Backup 8.0.13 (2018-10-22) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * mysqlbackup now supports backup compression (the use of the --compress and --uncompress options) for incremental backups (except for incremental backups created with the --incremental-with-redo-log-only option). * mysqlbackup now supports transparent page compression for InnoDB tables. The support is enabled by setting the mysqlbackup option --compress-method=punch-hole; see description for the option for details. Bugs Fixed * mysqlbackup hung when a backup operation failed due to a full disk. With this fix, mysqlbackup quits gracefully in the situation by throwing an error. (Bug #28399821) * A mysqlbackup operation on an image stored on an OpenStack cloud storage service sometimes failed with a segmentation fault or a bad URL error. It was because of a race condition caused by an uninitiated variable, which has been eliminated by this fix. (Bug #28189239, Bug #28183729) * Backups for databases with encrypted InnoDB tables failed when the --compress option was used. (Bug #28177466) * A mysqlbackup operation on an image stored on an OpenStack cloud storage service failed with a 401 Unauthorized error when the operation took a long time and the authentication token for the cloud access expired. With this fix, a separate thread in mysqlbackup requests a new token from the OpenStack cloud service in that situation, so that the operation can continue. (Bug #27893174) * When an incremental backup was restored without using the --log-bin option, the binary log was not restored to its original location on the backed up server, but to the location specified by --log-bin earlier during the restore of the base backup. The same occurred for relay logs of incremental backups for slaves when the --relay-log option was not used. (Bug #27545745) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 8.0.12 has been released
Dear MySQL users, MySQL Enterprise Backup 8.0.12, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 8.0.12 supports only the MySQL Server 8.0. For any earlier versions of the MySQL server 5.7, please use MySQL Enterprise Backup 4.1 and for MySQL Server 5.6 and 5.5, please use MySQL Enterprise Backup 3.12. For additional MySQL Enterprise Backup 8.0 documentation, see the MySQL Enterprise Backup User's Guide (Version 8.0.12) (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/). A brief summary of the changes in MySQL Enterprise Backup (MEB) version 8.0.12 is given below. Changes in MySQL Enterprise Backup 8.0.12 (2018-07-27) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * Important Change: Starting from release 8.0.12, the storage engine of the mysql.backup_history table on a backed-up server has switched from CSV to InnoDB. For a MySQL 8.0.12 server that has its database restored from a backup of an earlier server version, MySQL Enterprise Backup 8.0.12 automatically migrates the table when it performs its first backup task on the server. See After restoring an earlier backup to MySQL 8.0.12 or later (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html#meb-restore-to-8.0.12) for the new user privileges required by mysqlbackup for the mandatory migration to happen. * Important Change: When working with a Group Replication (http://dev.mysql.com/doc/refman/8.0/en/group-replication.html) setup, mysqlbackup now makes the backup history available to all members of the server group by making sure that the backup_history table is updated on a primary node after each mysqlbackup operation. With the implementation of this feature, the new user privilege of SELECT on performance_schema.replication_group_members is now required by mysqlbackup to work with any server, even when it does not belong to a Group Replication setup. See Grant MySQL Privileges to Backup Administrator (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/mysqlbackup.privileges.html) for details. * Version information for mysqlbackup is now printed to the stdout instead of the stderr stream when the --version or --help option is used. (Bug #27253989) * OAuth is now supported for Oracle Cloud Storage client authentication. Two new options, --cloud-storage-url and --cloud-oauth-token, have been introduced for the purpose. See Cloud Storage Options (http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/backup-cloud-options.html) for details. Bugs Fixed * Backups for a server failed when it had ANSI_QUOTES in its values for sql_mode. (Bug #27939774) * The maximum value that could be set for the --safe-slave-backup-timeout option was 2700 (seconds), which automatically replaced any larger value. With this fix, there is no longer a maximum limition, even though a high value is not recommended; see the description of --safe-slave-backup-timeout for details. (Bug #27883020) * Restoring an incrementation backup on top of a data directory restored using a compressed backup failed. It was because mysqlbackup did not set is_compressed=0 in the backup_variables.txt file inside the restored data directory. (Bug #27787988) * When mysqlbackup performed sanity checks on InnoDB tablespaces and found a space ID mismatch for an FSP header and a page header, the name of the problematic tablespace was not given in the error report. (Bug #27752703) * If an ALTER TABLE (http://dev.mysql.com/doc/refman/8.0/en/alter-table.html) statement was executed on the server before an incremental backup was taken, a server restored with the backup on which the incremental backup was applied (using the apply-incremental-backup command) could not be started, as the .ibd file of the altered table was missing in the restored data. (Bug #27735134) * After a server has been restored using an incremental backup created with the --incremental-with-redo-log-only option, it could not be started. (Bug #27722525) * mysqlbackup issued a warning whenever the number of files specified in the system variable innodb_data_file_path of the server to be backed up exceeded 100. With this fix, a warning is issued only if the number of InnoDB data files to be opened exceeds the number specified
MySQL Enterprise Backup 8.0.11 has been released
Dear MySQL users,
MySQL Enterprise Backup 8.0.11, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS)
website
as our latest GA release. This release will be available on eDelivery
(OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.
A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 8.0.11 is given below.
Changes in MySQL Enterprise Backup 8.0.11 (2018-04-19, General
Availability)
MySQL Enterprise Backup 8.0.11 is the latest release for
MySQL Enterprise Backup. It only supports MySQL Server
8.0.11. For MySQL server 5.7, please use MySQL Enterprise
Backup 4.1, and for MySQL Server 5.6 and 5.5, please use
MySQL Enterprise Backup 3.12.
* Functionality Added or Changed
* Bugs Fixed
Functionality Added or Changed
* Offline backups are no longer supported by mysqlbackup.
As a result, a number of options used for offline backup
operations have been removed. See What's New in MySQL
Enterprise Backup 8.0?
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/what-is-new.html)
for details. (Bug #27429244)
* The server option --secure-auth, deprecated since MySQL
5.7.5, is no longer supported by mysqlbackup. (Bug
#27265328)
* Servers' use of the keyring_encrypted_file
(http://dev.mysql.com/doc/refman/8.0/en/keyring-encrypted-file-plugin.html)
and keyring_aws
(http://dev.mysql.com/doc/refman/8.0/en/keyring-aws-plugin.html)
plugins is now supported. See Working with
Encrypted InnoDB Tables
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-encrypted-innodb.html)
for details. (Bug #27127898)
* Information on the executed GTIDs is now included in the
mysqlbackup output and the backup log when the backed up
server has GTIDs enabled. (Bug #25978803)
* The backup_history table now includes a server_uuid
column, which stores the value of the server_uuid of the
backed up server.
* The options --ssl and --ssl-verify-server-cert, already
deprecated in MySQL Enterprise Backup 4.1, have now been
removed. Use the --ssl-mode option instead to configure
the security mode of your connection to the server.
* MySQL Enterprise Firewall
(http://dev.mysql.com/doc/refman/8.0/en/mysql-enterprise-firewall.html)
is now supported.
* A new option, --tls-version, specifies the protocols
mysqlbackup permits for encrypted connections to MySQL
servers.
* A file now tracks information of external tablespaces
(http://dev.mysql.com/doc/refman/8.0/en/tablespace-placing.html)
for a backup or restore in JSON format. See
description for tablespace_tracker
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-files-backed-up-summary.html#meb_file_tablespace-tracker)
in Types of Files in a Backup
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/meb-files-backed-up-summary.html#meb-backup-files)
for details.
* The relay log for a backed-up slave server, instead of
being restored always to the data directory on the target
slave server, is now restored by default to the same
location it was found on the backed-up slave server. It
can also be restored to a different location specified
with the new --relay-log option.
* The binary log for a backed-up server, instead of being
restored always to the data directory on the target
server, is now restored by default to the same location
it was found on the backed-up server. It can also be
restored to a different location specified with the new
--log-bin option.
* The buffer size for cloud transfers can now be specified
using the new --cloud-buffer-size option. See Cloud
Storage Options
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/backup-cloud-options.html)
for details.
* HTTP Basic Authentication and non-chunked transfer are
now supported for backup and restore using OpenStack
Swift-compatible object storage services. Two new
options, --cloud-basicauth-url and
--cloud-chunked-transfer, have been introduced for these
purposes. See Cloud Storage Options
(http://dev.mysql.com/doc/mysql-enterprise-backup/8.0/en/backup-cloud-options.html)
for details.
Bugs Fixed
* After restoring a full backup, if the following restore
of an incremental backup changed the restore location of
the undo log, either mysqlbackup hung, or the restored
server failed to start. With this fix, mysqlbackup quits
with a proper error ("Undo tablespace in the base backup
not found") in the situation.
Users should make sure the undo log location does not
change between successiv
MySQL Enterprise Backup 4.1.0 has been released
Dear MySQL users, MySQL Enterprise Backup v4.1.0, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup 4.1.0 supports only the MySQL Server 5.7.9 and above. For any earlier versions of the MySQL server, please use MySQL Enterprise Backup 3.12 instead. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 4.1.0 is given below. Changes in MySQL Enterprise Backup 4.1.0 (2017-03-03) Functionality Added or Changed * MySQL Enterprise Backup now supports the --ssl-mode option, which enables you to specify the security state of the connection to the server. It replaces the client side --ssl and --ssl-verify-server-cert options, which are now deprecated. See the description of the --ssl-mode option in MySQL 5.7 Reference Manual (http://dev.mysql.com/doc/refman/5.7/en/) for details. (Bug #23508228) * A new option, --skip-final-rescan, makes mysqlbackup skip the final rescan for InnoDB tables that are modified by DDL operations after the database has been locked near the end of a backup operation. This potentially shortens the duration for the lock and reduces the backup's impact on the server's normal operation. See the description for --skip-final-rescan for details. (Bug #21094221) * The output by mysqlbackup, which goes to the stderr stream and the message log, has now been improved to include the timestamps and thread IDs for all steps taken by mysqlbackup, in order to provide more information for debugging purposes. (Bug #20142619) * During the final stage of a backup when MySQL Enterprise Backup tried to temporarily put the database into a read-only state using the FLUSH TABLES WITH READ LOCK statement in order to copy non-InnoDB files, if a long query was running on the server at the same time, the FLUSH TABLES WITH READ LOCK statement could be taking too long to finish, holding up further queries and eventually bringing down the server. A new mysqlbackup option --lock-wait-timeout can now be used to specify the timeout in seconds for the FLUSH TABLES WITH READ LOCK statement. If the timeout is exceeded, the statement is failed and the lock on the tables is released, so that queries held up by the lock can then be executed. mysqlbackup then retries the statement and continues with the backup. Default value for --lock-wait-timeout is 60 [seconds]. (Bug #14339483) * A full set of exit codes have now been implemented for MySQL Enterprise Backup. Also, a new mysqlbackup command, print-message, returns an exit message for any given exit code supplied with the new option --error-code. See Exit codes of MySQL Enterprise Backup (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/ <http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/meb-exitcodes.html> meb-exitcodes.html <http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/meb-exitcodes.html>) for details. * To increase the performance for hot backups, mysqlbackup now shortens the final phase of the backups by resizing the MyISAM key cache before it locks the database with a FLUSH TABLES WITH READ LOCK statement. The resize triggers a flush of the MyISAM key cache, which reduces the time it takes to run the FLUSH TABLES WITH READ LOCK statement. The MyISAM key cache size is changed back to its original value afterward. * Apply-log operations can now be performed with multiple worker threads in parallel, which can improve performance for the operations. The number of threads to be used can be specified with the --process-thread option. * The copying of redo log files into backups has been made faster, shortening the overall backup time in some cases and making it less likely that a backup fails because a redo log file has been overwritten before it is copied. * MySQL Enterprise Backup now supports optimistic incremental backup, in which mysqlbackup scans only those InnoDB data files that have been modified since the last backup for changed pages and then saves them into the incremental backup. It potentially makes incremental backups faster, and is performed by specifying --incremental=optimistic. See Full-scan versus Optimistic Incremental Backup (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/ <https://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/mysqlbackup.i
MySQL Enterprise Backup 4.0.2 has been released
Dear MySQL users, MySQL Enterprise Backup v4.0.2, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup v4.0.2 supports only the MySQL Server 5.7.9 and above. For any earlier versions of the MySQL server, please use MySQL Enterprise Backup 3.12 instead. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 4.0.2 is given below. Changes in MySQL Enterprise Backup 4.0.2 (2016-07-26) Functionality Added or Changed * When there were no tables matching the regular expression specified with the --include-table option during a backup operation, mysqlbackup still created a backup, which contained an empty folder for each database on the server. mysqlbackup now throws an error when --include-tables selects no tables to be backed up. (Bug #18114353) * MySQL Enterprise Backup can now backup and restore encrypted InnoDB tables. See Working with Encrypted InnoDB Tables and Options for Working with Encrypted InnoDB Tablespaces for details. Bugs Fixed * When trying to restore a compressed image backup of a server that had separate undo tablespaces residing in the data directory with the copy-back-and-apply-log command, the operation failed at the apply-log phase, as mysqlbackup could not load the undo tablepaces. (Bug #23583961) * Attempts to restore an image backup from the cloud using the --skip-binlog option failed with a "global tail magic mismatch" error. This was because mysqlbackup failed to perform a non-sequential read from the cloud with gaps caused by the skipping of the binary logs. This fix makes sure mysqlbackup can perform such reads. (Bug #23534700) * When a compressed backup was being restored, if the undo logs had been put into separate tablespaces outside of the data directory on the backed up server, they got restored twice, once mistakenly as general tablespaces with the .ibd extension, and once as undo tablespaces without a file extension. This fix makes sure they are restored normally as undo tablespaces only. (Bug #23179194) * An extract operation for an image backup failed with a checksum mismatch error in cases when, during the backup, an InnoDB tablespace file kept growing in size, and mysqlbackup failed to put the correct file size in its file header. (Bug #22905984) References: This issue is a regression of: Bug #22613568. * During a mysqlbackup operation on a compressed backup (that is, the --uncompress option was used), mysqlbackup, in some situations, wrote to the log file multiple instances of the message "ERROR: InnoDB: file write at offset > 4 GB," even though the operation was actually successful. (Bug #22733760) * Occasionally, some files were missing from an image backup created by the --backup-to-image command. It was due to an internal race condition, which this fix eliminates. (Bug #19600687) The complete manual for MEB 4.0.2 is at http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html The tool is available for download from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). You can also download the binaries from MOS, https://support.oracle.com Choose the "Patches & Updates" tab, and then use the "Product or Family (Advanced Search)" feature. If you haven't looked at MEB recently, please do so now and let us know how MEB works for you. Your feedback is greatly appreciated! Please report any problems you have at https://bug.oraclecorp.com/ for the product "MySQL Enterprise Backup" Thanks, On behalf MySQL RE team at Oracle Sreedhar S -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Workbench MySQL Enterprise Backup Error
The beauty of running enterprise versions is that you have support from Oracle. I would gently point you in their direction if not to get what you paid for but also because most of us in this list are unequipped to help you because we don't use the software you have problems with. Good luck On 22 Mar 2016 8:15 pm, "Lisa Smith" <lea...@gmail.com> wrote: > Hello all, > > I have not run across this problem where Workbench will not let me access > the "Online Backup" > link and claims that my version of MySQL Enterprise Backup is 0.0.0 (it is > 4.0.0). > > I had backups running and scheduled through Workbench previously. Yesterday > I changed my data files to another drive and when I restarted Workbench I > was no longer able to access Online Backup. > > I feel like I may be missing something obvious so any suggestions would be > greatly appreciated. > > I am running MySQL Enterprise 5.7 on Windows Server 2012. > > Thank you for reading. >
Workbench MySQL Enterprise Backup Error
Hello all, I have not run across this problem where Workbench will not let me access the "Online Backup" link and claims that my version of MySQL Enterprise Backup is 0.0.0 (it is 4.0.0). I had backups running and scheduled through Workbench previously. Yesterday I changed my data files to another drive and when I restarted Workbench I was no longer able to access Online Backup. I feel like I may be missing something obvious so any suggestions would be greatly appreciated. I am running MySQL Enterprise 5.7 on Windows Server 2012. Thank you for reading.
MySQL Enterprise Backup 4.0.0 has been released
Dear MySQL users, MySQL Enterprise Backup v4.0.0, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. MySQL Enterprise Backup v4.0.0 supports only the MySQL server 5.7.9 and above. For any earlier versions of the MySQL server, please use MySQL Enterprise Backup 3.12 instead. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 4.0.0 is given below. Changes in MySQL Enterprise Backup 4.0.0 (2015-10-21) Functionality Added or Changed * MySQL Enterprise Backup 4.0 supports MySQL server 5.7, on which: + Tables in general tablespaces (http://dev.mysql.com/doc/refman/5.7/en/glossary.htm l#glos_general_tablespace <http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_general_tablespace>) can be backed up and restored. + InnoDB tables with page sizes (http://dev.mysql.com/doc/refman/5.7/en/glossary.htm l#glos_page_size <http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_page_size>) of 32 and 64K can be backed up and restored. + Partitioned tables can be selectively backed up or restored using the --use-tts, --include-tables, and --exclude-tables options. See What's New in MySQL Enterprise Backup 4.0? (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/ what-is-new.html <http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/what-is-new.html>) for details. * MySQL Enterprise Backup now writes tape information onto the MySQL server when a backup is made to a tape using the System Backup to Tape (SBT) API. See What's New in MySQL Enterprise Backup 4.0? (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/ what-is-new.html <http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/what-is-new.html>) for details. Bugs Fixed * When restoring an incremental backup image, if the binary log in the backup was larger than 16MB, the restored binary log would become corrupted. (Bug #20915642) * When the --password option was used without an argument with the copy-back-and-apply-log command, mysqlbackup did not prompt user for a password, but either took the password from the defaults files, or took it to be an empty string when no value was specified in the defaults files. (Bug #20915642) The complete manual for MEB 4.0.0 is at http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html The tool is available for download from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). You can also download the binaries from MOS, https://support.oracle.com Choose the "Patches & Updates" tab, and then use the "Product or Family (Advanced Search)" feature. If you haven't looked at MEB recently, please do so now and let us know how MEB works for you. Your feedback is greatly appreciated! Please report any problems you have at https://bug.oraclecorp.com/ for the product "MySQL Enterprise Backup" Thanks, On behalf MySQL RE team at Oracle Sreedhar S
MySQL Enterprise Backup 3.11.1 has been released
Dear MySQL users, MySQL Enterprise Backup v3.11.1, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension to the MySQL family of products. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.11.1 is given below. Changes in MySQL Enterprise Backup 3.11.1 (2014-11-05) Bugs Fixed * The copying of the relay log files from a MySQL slave server into a backup (which has been the default behavior of MySQL Enterprise Backup since 3.11.0) crashed MySQL Enterprise Backup when the server is of version 5.5. (Bug #19904912) * The copying of the binary log files from the server into a backup (which has been the default behavior of MySQL Enterprise Backup since 3.11.0) caused some databases to be silently skipped over during the backup process when (1) the binary log files are located in the server's data directory, and the name of any database matches the data directory's base name or (2) the binary log files are located in a subdirectory of the data directory. (Bug #19883801) You can also find more information on the contents of this release in the change log: http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/meb-news.html The complete manual for MEB 3.11.1 is at, http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/index.html The tool is available for download from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). You can also download the binaries from MOS, https://support.oracle.com Choose the Patches Updates tab, and then use the Product or Family (Advanced Search) feature. If you haven't looked at MEB recently, please do so now and let us know how MEB works for you. Your feedback is greatly appreciated! Please report any problems you have at https://bug.oraclecorp.com/ for the product MySQL Enterprise Backup Thanks, The MySQL build team at Oracle -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL Enterprise Backup 3.10.2 has been released
Dear MySQL users, MySQL Enterprise Backup 3.10.2, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.10.2 is given below. Changes in MySQL Enterprise Backup 3.10.2 (2014-07-01) Security Note * Security Fix: The linked OpenSSL library for MySQL Enterprise Backup 3.10 has been updated from version 1.0.1g to version 1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are reported to be vulnerable to CVE-2014-0224 (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224). (CVE-2014-0224) Functionality Added or Changed * MySQL Enterprise Backup now supports creation and restoration of single-file backups using a cloud storage. See Section 5.1.15, Cloud Storage Options for details. Bugs Fixed * After a table backed up using the transportable tablespace option (--use-tts) was restored to a server, queries on the table did not make use of its indexes. That was because the cardinalities of the indexes were not properly updated after the table's restoration. This fix adds an ANALYZE TABLE (http://dev.mysql.com/doc/refman/5.6/en/analyze-table.html) step towards the end of the restoration process for tables backed up with the --use-tts option, in order to update the indexes' cardinalities. (Bug #18682317) * When cloning a slave for a GTID-enabled server using MySQL Enterprise Backup, the backup_gtid_executed.sql script created and stored in the backup directory was not copied onto the slave by the copy-back-and-apply-log operation. This fix has the script copied into the data directory of the slave. (Bug #18674861) * The maximum number of memory buffers that could be created for a mysqlbackup operation was hard-coded to be 100, making it impossible to set the number of buffers to a larger value using the number-of-buffers option. This fix removes the hard-coded maximum number for buffers. (Bug #18560870) * mysqlbackup threw an error if a table was dropped when the backup process was running. With this fix, the dropped table is ignored (as it does not need to be restored) and mysqlbackup finishes without throwing an error. (Bug #18358912, Bug #71865) * A segmentation fault occurred when a backup image created from a backup directory was restored using the copy-back-and-apply-log subcommand. It was because copy-back-and-apply-log was not able to extract backup-my.cnf from the image and get the value for innodb_data_file_path. (Bug #18242586) * After an apply-log operation was performed on a compressed backup (with the --uncompress and --apply-log options), when a copy-back-and-apply-log was applied on the backup, the restored data was inconsistent. That was because the first operation did not delete the compressed, .ibz backup file and did not mark the data as uncompressed at the end of the operation. The subsequent copy-back-and-apply-log operation than acted on the still existing, raw, compressed file, but thought that an apply-log operation had already been performed on it. This fix makes mysqlbackup delete the compressed, raw backup file once decompression and apply-log are finished and properly mark the backup as uncompressed and up-to-date. (Bug #18005786, Bug #18005732) * After an incremental backup was applied to a full backup, a second incremental would fail if the same incremental backup directory was used and if the --incremental-base=dir:directory_path option was pointing to the full backup's directory. This was because MySQL Enterprise Backup checked the end LSN in the full backup directory against the end LSN in the MySQL history table (which might not have been updated yet) and failed the process when there was a mismatch. This fix removes that check, so user in the described situation can proceed with creating more incremental backups. (Bug #16249018) You can also find more information on the contents of this release in the change log: http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/meb-news.html The complete manual for MEB 3.10.2 is at, http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/index.html The tool is available for download from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). You can also download the binaries from MOS, https://support.oracle.com Choose the Patches Updates tab, and then use
MySQL Enterprise Backup 3.10.0 has been released
Dear MySQL users, MySQL Enterprise Backup v3.10.0, a new version of the online MySQL backup tool, is now available for download from the My Oracle Support (MOS) website as our latest GA release. This release will be available on eDelivery (OSDC) after the next upload cycle. MySQL Enterprise Backup is a commercial extension. A brief summary of the changes in MySQL Enterprise Backup (MEB) version 3.10.0 is given below. Changes in MySQL Enterprise Backup 3.10.0 (2014-03-10) Functionality Added or Changed * When using the --skip-unused-pages option for backup operations, MySQL Enterprise Backup now displays, besides the number of pages of data skipped, the total amount of memory saved by using the option. (Bug #15915315) * In order to enhance security for backed up data, MySQL Enterprise Backup now provides encryption function for single-file backups. See Section 7.3, Encryption for Backups and Section 5.1.14, Encryption Options for details. * The compression feature of MySQL Enterprise Backup has been enhanced by the addition of two compression algorithms: the LZ4 method (the default for MySQL Enterprise Backup 3.10 and after) and the LZMA method. Because the LZ4 algorithm, though faster, produces larger files than the ZLIB algorithm used in MySQL Enterprise Backup 3.9 and earlier, users of MySQL Enterprise Backup 3.10 will find an increase in the size of the compressed files if they use the default values for the compression options. * Backups created with the --use-tts option can now be restored in a single step using the copy-back-and-apply-log subcommand. * When the apply-log or apply-incremental-backup operation was performed repeatedly on a backup without using the --force option, an error message was thrown. From MySQL Enterprise Backup release 3.10.0 onward, the same action just causes a message to be returned, saying the operation has already been performed. * MySQL Enterprise Backup can now validate data integrity of a backup directory as well as a backup image file. The validation function in 3.10 has also become more robust, as it tries to verify the checksum value of every data page. * MySQL Enterprise Backup 3.10 introduces two new options for partial backup: --include-tables and --exclude-tables. The new options are intended for replacing the older options of --include, --databases, --databases-list-file, and --only-innodb-with-frm, which will be deprecated in the near future. Bugs Fixed * mysqlbackup could not read the value of innodb_data_file_path from the server when it was more than 1024-character long. It was because mysqlbackup could not read the value from the configuration files and relied on the SHOW VARIABLES command (which reads no more than 1024 characters) to access the parameter. With this fix, innodb_data_file_path can now be read from the configuration files. (Bug #18038409) * A backup taken with both the --use-tts=with-full-locking and --skip-unused-pages options could not be restored. This was because with --use-tts=with-full-locking used, the apply-log operation was always skipped (the command did nothing to the backup), while the expansion of the unused pages was part of the apply-log operation. This fix separates the expansion from the apply-log operation, so that the backup can be restored. (Bug #17764917) * When a database was initialized with --innodb-file-per-table=0 and had a fixed-size system tablespace, all non-InnoDB files backed up had zero size. (Bug #17793020) * After a server restoration from an incremental backup with the copy-back-and-apply-log subcommand, mysqlbackup returned a success code even after a file renaming failed during the restoration process. The restored server thus failed to start with an assertion error. This fix makes sure a proper error is thrown when a file renaming fails during a restoration. (Bug #17539568) * In a replication setup, when a backup was performed on a master, the modifications of the tables mysql.backup_history and mysql.backup_progress were propagated to the slaves, causing a wrong backup status for the slaves to be registered. This fix makes MySQL Backup Enterprise disable binary logging by setting set sql_log_bin=0 during a backup on the master, so that the backup information will not get replicated to the slaves. (Bug #17449449) * When the --messages-logdir option was used and the --trace option was set to 2 or 3 for an apply-log operation, MySQL Enterprise Backup created an extra log file. (Bug #17271318) * When copy-back
Re: MYSQL DB BACKUP
There are some of backup scripts written by me.You can find it at: http://blog.chinaunix.net/u/29134/article_71953.html On Wed, Oct 22, 2008 at 4:52 PM, Mad Unix [EMAIL PROTECTED] wrote: Any one tried the script from HowToForge http://www.howtoforge.com/shell-script-to-back-up-all-mysql-databases-each-table-in-an-individual-file-and-upload-to-remote-ftp #!/bin/sh # System + MySQL backup script # Copyright (c) 2008 Marchost # This script is licensed under GNU GPL version 2.0 or above # - # ##TO BE MODIFIED# ### System Setup ### BACKUP=YOUR_LOCAL_BACKUP_DIR ### MySQL Setup ### MUSER=MYSQL_USER MPASS=MYSQL_USER_PASSWORD MHOST=localhost ### FTP server Setup ### FTPD=YOUR_FTP_BACKUP_DIR FTPU=YOUR_FTP_USER FTPP=YOUR_FTP_USER_PASSWORD FTPS=YOUR_FTP_SERVER_ADDRESS ##DO NOT MAKE MODIFICATION BELOW# # ### Binaries ### TAR=$(which tar) GZIP=$(which gzip) FTP=$(which ftp) MYSQL=$(which mysql) MYSQLDUMP=$(which mysqldump) ### Today + hour in 24h format ### NOW=$(date +%d%H) ### Create hourly dir ### mkdir $BACKUP/$NOW ### Get all databases name ### DBS=$($MYSQL -u $MUSER -h $MHOST -p$MPASS -Bse 'show databases') for db in $DBS do ### Create dir for each databases, backup tables in individual files ### mkdir $BACKUP/$NOW/$db for i in `echo show tables | $MYSQL -u $MUSER -h $MHOST -p$MPASS $db|grep -v Tables_in_`; do FILE=$BACKUP/$NOW/$db/$i.sql.gz echo $i; $MYSQLDUMP --add-drop-table --allow-keywords -q -c -u $MUSER -h $MHOST -p$MPASS $db $i | $GZIP -9 $FILE done done ### Compress all tables in one nice file to upload ### ARCHIVE=$BACKUP/$NOW.tar.gz ARCHIVED=$BACKUP/$NOW $TAR -cvf $ARCHIVE $ARCHIVED ### Dump backup using FTP ### cd $BACKUP DUMPFILE=$NOW.tar.gz $FTP -n $FTPS END_SCRIPT quote USER $FTPU quote PASS $FTPP cd $FTPD mput $DUMPFILE quit END_SCRIPT ### Delete the backup dir and keep archive ### rm -rf $ARCHIVED On Wed, Sep 17, 2008 at 10:18 AM, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Thanks a lot. I am writing script which will take backup and copy it to another box. On Wed, Sep 17, 2008 at 11:14 AM, Ananda Kumar [EMAIL PROTECTED] wrote: Can u mount that file system on the slave db and take the backup so that u can avoid Network latency. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Yes On Tue, Sep 16, 2008 at 6:39 PM, Ananda Kumar [EMAIL PROTECTED] wrote: Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati MySQL DBA, Ed Ventures e-Learning Pvt.Ltd. 1-8-303/48/15, Sindhi Colony P.G.Road, Secunderabad. Pin Code: 53 Office Number: 040-66489771 Mob: 9912924044 URL: ed-ventures-online.com Email-id: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- I'm a MySQL DBA in china. More about me just visit here: http://yueliangdao0608.cublog.cn
Re: MYSQL DB BACKUP
Any one tried the script from HowToForge http://www.howtoforge.com/shell-script-to-back-up-all-mysql-databases-each-table-in-an-individual-file-and-upload-to-remote-ftp #!/bin/sh # System + MySQL backup script # Copyright (c) 2008 Marchost # This script is licensed under GNU GPL version 2.0 or above # - # ##TO BE MODIFIED# ### System Setup ### BACKUP=YOUR_LOCAL_BACKUP_DIR ### MySQL Setup ### MUSER=MYSQL_USER MPASS=MYSQL_USER_PASSWORD MHOST=localhost ### FTP server Setup ### FTPD=YOUR_FTP_BACKUP_DIR FTPU=YOUR_FTP_USER FTPP=YOUR_FTP_USER_PASSWORD FTPS=YOUR_FTP_SERVER_ADDRESS ##DO NOT MAKE MODIFICATION BELOW# # ### Binaries ### TAR=$(which tar) GZIP=$(which gzip) FTP=$(which ftp) MYSQL=$(which mysql) MYSQLDUMP=$(which mysqldump) ### Today + hour in 24h format ### NOW=$(date +%d%H) ### Create hourly dir ### mkdir $BACKUP/$NOW ### Get all databases name ### DBS=$($MYSQL -u $MUSER -h $MHOST -p$MPASS -Bse 'show databases') for db in $DBS do ### Create dir for each databases, backup tables in individual files ### mkdir $BACKUP/$NOW/$db for i in `echo show tables | $MYSQL -u $MUSER -h $MHOST -p$MPASS $db|grep -v Tables_in_`; do FILE=$BACKUP/$NOW/$db/$i.sql.gz echo $i; $MYSQLDUMP --add-drop-table --allow-keywords -q -c -u $MUSER -h $MHOST -p$MPASS $db $i | $GZIP -9 $FILE done done ### Compress all tables in one nice file to upload ### ARCHIVE=$BACKUP/$NOW.tar.gz ARCHIVED=$BACKUP/$NOW $TAR -cvf $ARCHIVE $ARCHIVED ### Dump backup using FTP ### cd $BACKUP DUMPFILE=$NOW.tar.gz $FTP -n $FTPS END_SCRIPT quote USER $FTPU quote PASS $FTPP cd $FTPD mput $DUMPFILE quit END_SCRIPT ### Delete the backup dir and keep archive ### rm -rf $ARCHIVED On Wed, Sep 17, 2008 at 10:18 AM, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Thanks a lot. I am writing script which will take backup and copy it to another box. On Wed, Sep 17, 2008 at 11:14 AM, Ananda Kumar [EMAIL PROTECTED] wrote: Can u mount that file system on the slave db and take the backup so that u can avoid Network latency. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Yes On Tue, Sep 16, 2008 at 6:39 PM, Ananda Kumar [EMAIL PROTECTED] wrote: Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati MySQL DBA, Ed Ventures e-Learning Pvt.Ltd. 1-8-303/48/15, Sindhi Colony P.G.Road, Secunderabad. Pin Code: 53 Office Number: 040-66489771 Mob: 9912924044 URL: ed-ventures-online.com Email-id: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MYSQL DB BACKUP
Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati
Re: MYSQL DB BACKUP
Yes On Tue, Sep 16, 2008 at 6:39 PM, Ananda Kumar [EMAIL PROTECTED] wrote: Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati
Re: MYSQL DB BACKUP
Can u mount that file system on the slave db and take the backup so that u can avoid Network latency. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Yes On Tue, Sep 16, 2008 at 6:39 PM, Ananda Kumar [EMAIL PROTECTED] wrote: Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati
Re: MYSQL DB BACKUP
Thanks a lot. I am writing script which will take backup and copy it to another box. On Wed, Sep 17, 2008 at 11:14 AM, Ananda Kumar [EMAIL PROTECTED] wrote: Can u mount that file system on the slave db and take the backup so that u can avoid Network latency. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Yes On Tue, Sep 16, 2008 at 6:39 PM, Ananda Kumar [EMAIL PROTECTED] wrote: Hi Krishna, When u say remote server, do u mean the file system storing the backup is on a different machine. regards anandkl On 9/16/08, Krishna Chandra Prajapati [EMAIL PROTECTED] wrote: Hi, Currently, i am taking production server backup on hourly basis on the slave server. Is it feasible to take 15G backup on remote server on hourly basis. It takes 10 minutes on slave server. How much time it will take on remote server. Thanks, -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati -- Krishna Chandra Prajapati MySQL DBA, Ed Ventures e-Learning Pvt.Ltd. 1-8-303/48/15, Sindhi Colony P.G.Road, Secunderabad. Pin Code: 53 Office Number: 040-66489771 Mob: 9912924044 URL: ed-ventures-online.com Email-id: [EMAIL PROTECTED]
Problems with mysql scheduled backup
Hi All, I'm trying to take scheduled backup from mysql administrator and it always gives me a popup with this message. Enter user name and password for the account under which the task will be executed. it shows me username and password for my windows account and when I click ok on the pop up window, it saves the project . But it never takes the backup at scheduled time or any other time. I can take backups manually by clicking on Execute backup now without any problems. I did all the configuration settings mentioned in the Mysql administrator help. I went in options changed the password setting to obscured. I saw a similar posting for this issue, so I tried the solution mentioned as creating a new connection before taking scheduled backups and that didn't work either. I'm working on windows XP with Mysql server 4.1 and my computer is in a workgroup. Any suggestions will be appreciated. Thanks, Reema Duggal Troiana Senior Software Developer BitArmor Systems, Inc. 357 North Craig Street Ground Floor Pittsburgh, PA 15213 [TEL] 412-682-2200 Ext 314 [FAX] 412-682-2201
Re: Problems with mysql scheduled backup
Hello. These are some active bugs with different versions of MySQL Administrator. Check if your problem remains with the latest one. Hi All, I'm trying to take scheduled backup from mysql administrator and it always gives me a popup with this message. Enter user name and password for the account under which the task will be executed. it shows me username and password for my windows account and when I click ok on the pop up window, it saves the project . But it never takes the backup at scheduled time or any other time. I can take backups manually by clicking on Execute backup now without any problems. I did all the configuration settings mentioned in the Mysql administrator help. I went in options changed the password setting to obscured. I saw a similar posting for this issue, so I tried the solution mentioned as creating a new connection before taking scheduled backups and that didn't work either. I'm working on windows XP with Mysql server 4.1 and my computer is in a workgroup. Any suggestions will be appreciated. rtroiana [EMAIL PROTECTED] wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: A question about mysql database backup.
Fred, Jim, Thank you very much for your kind help! I still have other questions about the MySQL operation. If a service host is redundant, one is in active status, the other is standby. I want to make the following operation . 1. database backup. This is done on the standby one with the following command. mysqldump --opt --quote-names --flush-logs database_name database.backup 2. database restore. Restore the database with the previous backup. I am not sure what to do. I guess there will be two methods to finish this. * disconnect the two host and make operation on each one individually as following mysql database_namve database.backup Then restart Mysql. * do restore on the active one with the following command. Because the standby host are the backup of the active one. So the data on both of the hosts will finally be identical in the end. I don't know whether it will be in such case. mysql database_namve database.backup If my description is wrong, Would you please let me know the correct methods? Thanks! Lenny Li == LSS-MI Development, RD, Lucent Qingdao [EMAIL PROTECTED] 86-532-8702000-5033 http://gdcsr60.gdc.lucent.com/~lennyli -Original Message- From: Frederic Wenzel [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:13 PM To: Li, Lenny Yong Bo (Lenny) Cc: [EMAIL PROTECTED] Subject: Re: A question about mysql database backup. Li, Lenny Yong Bo (Lenny) wrote: Now I am assigned to do the backup of a whole mysql database (version: 3.23.36). I want to make sure whether the following procedures are correct for database backup. 1. mysqldump -F --opt database_name database_name.backup In my opinion, you should generally add the -Q option which quotes table and row names. Otherwise, restoring data can be really hard in case of perhaps only one complicated row name... Regards, Fred -- Condense soup, not books! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: A question about mysql database backup.
on 02/27/2004 12:11 AM, Li, Lenny Yong Bo (Lenny) at [EMAIL PROTECTED] wrote: 1. database backup. This is done on the standby one with the following command. mysqldump --opt --quote-names --flush-logs database_name database.backup How does this operations handle binary fields, password fields, blob fields etc? -- - Scott HanedaTel: 415.898.2602 http://www.newgeo.com Fax: 313.557.5052 [EMAIL PROTECTED]Novato, CA U.S.A. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: A question about mysql database backup.
On 02/25/2004 09:13 AM Frederic Wenzel wrote: Now I am assigned to do the backup of a whole mysql database (version: 3.23.36). I want to make sure whether the following procedures are correct for database backup. 1. mysqldump -F --opt database_name database_name.backup In my opinion, you should generally add the -Q option which quotes table and row names. Otherwise, restoring data can be really hard in case of perhaps only one complicated row name... Are back-ticks actually part of ANSI SQL? Adam -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: A question about mysql database backup.
Li, Lenny Yong Bo (Lenny) wrote: Now I am assigned to do the backup of a whole mysql database (version: 3.23.36). I want to make sure whether the following procedures are correct for database backup. 1. mysqldump -F --opt database_name database_name.backup In my opinion, you should generally add the -Q option which quotes table and row names. Otherwise, restoring data can be really hard in case of perhaps only one complicated row name... Regards, Fred -- Condense soup, not books! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: A question about mysql database backup.
Fred, Thanks for your quick response! Do you mean that only one step is enough for a backup mysqldump -F --opt --quote-names database_name database_name.backup? The second step is not needed at all. Am I right? I added the option -Q, it failed, but the --quote-names option works well. Maybe the version number is not high enough. Regards, Lenny Li == LSS-MI Development, RD, Lucent Qingdao [EMAIL PROTECTED] 86-532-8702000-5033 http://gdcsr60.gdc.lucent.com/~lennyli -Original Message- From: Frederic Wenzel [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 25, 2004 4:13 PM To: Li, Lenny Yong Bo (Lenny) Cc: [EMAIL PROTECTED] Subject: Re: A question about mysql database backup. Li, Lenny Yong Bo (Lenny) wrote: Now I am assigned to do the backup of a whole mysql database (version: 3.23.36). I want to make sure whether the following procedures are correct for database backup. 1. mysqldump -F --opt database_name database_name.backup In my opinion, you should generally add the -Q option which quotes table and row names. Otherwise, restoring data can be really hard in case of perhaps only one complicated row name... Regards, Fred -- Condense soup, not books! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
A question about mysql database backup.
Ms./Sir, Now I am assigned to do the backup of a whole mysql database (version: 3.23.36). I want to make sure whether the following procedures are correct for database backup. 1. mysqldump -F --opt database_name database_name.backup 2. stop mysqld if is running. Then start it with --log-bin option. The purpose of the second step is to update the database from the binary log file since the point I began to do backup. Then it will work normally. Am I right? But I once did a test on the database. I used command LOCK TABLES table_name READ to lock a table as root login, and then insert one row as lss login in another terminal. The insert operation hang there until the table was unlocked. I run command select * from table_name in both terminal finding the result are the same and new row was inserted. So I am confused about the functionality of the second step. If the above procedure is not correct, Would you please let me know the correct ones? I once read the mysql administration document and found some command about backup. But they are executed on mysql prompt like mysql LOCK TABLES, I need the procedures that can be run on command line. Thanks! Regards, Lenny Li == LSS-MI Development, RD, Lucent Qingdao [EMAIL PROTECTED] 86-532-8702000-5033 http://gdcsr60.gdc.lucent.com/~lennyli -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysql Online Backup.
Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
A very good question! One which I will attempt to provide a half-decent answer for. Trying to execute a transaction that involves grabbing massive amounts of data from various tables while still allowing updates to be committed can be tricky. At best, this means performance problems. Please don't get me wrong - MySQL is the fastest database on the planet (and it looks to only get faster, with additional query caches, better designed caches and a helper thread architecture in the works) but there are certain things that are just hard to do quickly, even if you are the demigods that work at Innobase Oy and MySQL AB. The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. In summary, it's not a question as to whether the current methods work, it's a question as to how well suited they are to your needs. For mine they work well, but if I was processing 600 queries / second, I think I'd want ibcopy to help me out. Regards, Chris quote who=P Srinivasulu If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
Hi All, my $0.0.2... anybody correct me please if you know it better...;-) 2003 8 27 23:22P Srinivasulu : If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. mysqldump --single-transaction is backing up all tables in a single transaction, see the remark MUTUALLY exclusive with lock tables, meaning that NO other client can modify the tables/ data at that time (which may take some time for big databases ). mysqlhotcopy is only working on MyISAM table formats yet and again locking the whole table. But as its a read lock other clients can still read the data. However, this perl script runs only local (must be run on the server). As for the question about the online backup facility, I believe what meant is that you can run an online backup from a tool like phpmyadmin, xoops, basically a normal webpage, etc. The difference of all these tools is a) how they accesss and lock the tables/data you want to backup b) the format of the output file (txt,sql format, binary etc. c) the supported features I hope this answers some of your questions. Let me know if you need more details. Best regards Nils Valentin Tokyo/Japan Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
Hi Chris, 2003 8 28 00:54Chris Nolan : A very good question! One which I will attempt to provide a half-decent answer for. Trying to execute a transaction that involves grabbing massive amounts of data from various tables while still allowing updates to be committed can be tricky. At best, this means performance problems. Please don't get me wrong - MySQL is the fastest database on the planet (and it looks to only get faster, with additional query caches, better designed caches and a helper thread architecture in the works) but there are certain things that are just hard to do quickly, even if you are the demigods that work at Innobase Oy and MySQL AB. The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. Wouldn't that break the ACID ? The backup data would not be fully consistent, integrated anymore. Anyway thats my understanding. I understand that the InnoDB Hot Copy product is providing this feature by using the actual row locks to make sure that ACID is taken care of while creating a consistent backup. Best regards Nils Valentin In summary, it's not a question as to whether the current methods work, it's a question as to how well suited they are to your needs. For mine they work well, but if I was processing 600 queries / second, I think I'd want ibcopy to help me out. Regards, Chris quote who=P Srinivasulu If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
Hi Chris, 2003 8 28 00:54Chris Nolan : A very good question! One which I will attempt to provide a half-decent answer for. Trying to execute a transaction that involves grabbing massive amounts of data from various tables while still allowing updates to be committed can be tricky. At best, this means performance problems. Please don't get me wrong - MySQL is the fastest database on the planet (and it looks to only get faster, with additional query caches, better designed caches and a helper thread architecture in the works) but there are certain things that are just hard to do quickly, even if you are the demigods that work at Innobase Oy and MySQL AB. The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. You made an interesting point there with the locking mechanism. I double checked the innodb homepage. http://www.innodb.com/hotbackup.html While it says at the top as you stated no locks are written it also says under 3) how it locks and unlocks the tables. I guess thats best explained by Heikki ;-) - I copied her. Best regards Nils Valentin Tokyo/Japan In summary, it's not a question as to whether the current methods work, it's a question as to how well suited they are to your needs. For mine they work well, but if I was processing 600 queries / second, I think I'd want ibcopy to help me out. Regards, Chris quote who=P Srinivasulu If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
2003 8 28 01:43Nils Valentin : Hi Chris, 2003 8 28 00:54Chris Nolan : A very good question! One which I will attempt to provide a half-decent answer for. Trying to execute a transaction that involves grabbing massive amounts of data from various tables while still allowing updates to be committed can be tricky. At best, this means performance problems. Please don't get me wrong - MySQL is the fastest database on the planet (and it looks to only get faster, with additional query caches, better designed caches and a helper thread architecture in the works) but there are certain things that are just hard to do quickly, even if you are the demigods that work at Innobase Oy and MySQL AB. The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. You made an interesting point there with the locking mechanism. I double checked the innodb homepage. http://www.innodb.com/hotbackup.html While it says at the top as you stated no locks are written it also says under 3) how it locks and unlocks the tables. I guess thats best explained by Heikki ;-) - I copied her. Best regards Nils Valentin Tokyo/Japan In summary, it's not a question as to whether the current methods work, it's a question as to how well suited they are to your needs. For mine they work well, but if I was processing 600 queries / second, I think I'd want ibcopy to help me out. Regards, Chris quote who=P Srinivasulu If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup functionality will be provided in Mysql-5.1. I think its already there in the form of mysqlhotcopy. Is Mysql going to extend the functionality of mysqlhotcopy so that it works for Innodb tables also? or they are going to provide independent online backup functionality. Please clarify me. http://www.mysql.com/doc/en/TODO_MySQL_5.1.html Thanks, Srinivasulu. -- --- Valentin Nils Internet Technology E-Mail: [EMAIL PROTECTED] URL: http://www.knowd.co.jp Personal URL: http://www.knowd.co.jp/staff/nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Mysql Online Backup.
The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. Wouldn't that break the ACID ? The backup data would not be fully consistent, integrated anymore. Anyway thats my understanding. I understand that the InnoDB Hot Copy product is providing this feature by using the actual row locks to make sure that ACID is taken care of while creating a consistent backup. The algorithm as I understand it is something like this: 1) Tell InnoDB engine to flush the transaction journal to the data pool. 1) Tell InnoDB engine to NOT flush the transaction journal to data pool until further notice. 2) Make a flat copy of the data pool (analogous to just cp'ing the files). 3) Make a copy of pending transactions in the transaction journal. 4) Tell InnoDB engine to resume normal behavior. Transactions can still continue to write to the DB because everything goes through the transaction journal anyway. The journal simply stores a list of changed DB pages associated with a particular transaction, and is flushed to the data pool asynchronously. The data pool always represents a consistent-state snapshot of the DB thanks to the double-write buffer. The only risk is that the backup procedure may take such a long time that the transaction journal becomes full. I don't know how InnoDB handles this -- I suspect transactions simply start failing at that point although I suppose it's possible that they simply block until space becomes available. You can avoid this by ensuring that your transaction journals are sufficiently large to accommodate the copy process in the face of the heaviest possible DB write load. Estimating with any precision is difficult but it's usually fairly straightforward to come up with a definitely safe guess. (Our production DB runs 3 transaction journals of 20MB each for example -- plenty of space for us, even assuming very substantial growth in write traffic) -JF -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Mysql Online Backup.
Hi! A hot backup (= online backup) means backing up your database without locking anything for more than a few milliseconds. If you back up a massive, fast changing, database with mysqldump --single-transaction, then -- at least in some theoretical settings -- InnoDB can run out of space in the tablespace, because it cannot purge history in the tablespace before that big mysqldump ends. If you use InnoDB Hot Backup http://www.innodb.com/hotbackup.html, the only limit is the size of the disk(s) where you take the backup. The size of InnoDB's transaction logs, ib_logfiles, does NOT limit the size of transactions you can run during the backup procedure. InnoDB Hot Backup (ibbackup) works like similar tools for Oracle. It copies the tablespace, page by page, and at the same time archives the log that InnoDB writes during the backup process to its log files. The archived log becomes the file ibbackup_logfile in your backup. ibbackup does not communicate with mysqld in any way during the backup process. It does not set any locks. It just reads the data and log files. When we want to take the backup into use, ibbackup applies the archived log to the data files in the backup and in that way rolls the backup forward to a consistent single point in time. When Nils talks about setting table locks, he probably means a new Perl script innobackup http://www.innodb.com/hotbackup.html#innobackup_perl_script. innobackup calls ibbackup and takes a backup of both InnoDB and MyISAM type tables, as well as the .frm files. To back up MyISAM tables it has to call FLUSH TABLES WITH READ LOCK at the end of the backup run, because there is no hot backup procedure available for MyISAM tables. If the MyISAM tables are small, like the 'user' and 'host' system tables in the 'mysql' database, then the locked phase only lasts a couple of seconds, and we can call also innobackup essentially a 'hot backup' tool. Note that mysqldump takes a 'logical' backup of your database, because it dumps the rows into a file in a human-readable form. ibbackup, on the other hand, takes a binary backup of your database. Even if you use ibbackup, you should sometimes make logical dumps because you can easier check that data in a human-readable file is not corrupt. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for MySQL - Original Message - From: Nils Valentin [EMAIL PROTECTED] To: [EMAIL PROTECTED]; P Srinivasulu [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 7:47 PM Subject: Re: Mysql Online Backup. 2003 8 28 01:43Nils Valentin : Hi Chris, 2003 8 28 00:54Chris Nolan : A very good question! One which I will attempt to provide a half-decent answer for. Trying to execute a transaction that involves grabbing massive amounts of data from various tables while still allowing updates to be committed can be tricky. At best, this means performance problems. Please don't get me wrong - MySQL is the fastest database on the planet (and it looks to only get faster, with additional query caches, better designed caches and a helper thread architecture in the works) but there are certain things that are just hard to do quickly, even if you are the demigods that work at Innobase Oy and MySQL AB. The advantage of other methods is that you avoid all sorts of nasty locking on various parts of your database. The advantage of the Hot Copy product that Innobase Oy sell is that it doesn't place any locks on your InnoDB table space when it runs. You made an interesting point there with the locking mechanism. I double checked the innodb homepage. http://www.innodb.com/hotbackup.html While it says at the top as you stated no locks are written it also says under 3) how it locks and unlocks the tables. I guess thats best explained by Heikki ;-) - I copied her. Best regards Nils Valentin Tokyo/Japan In summary, it's not a question as to whether the current methods work, it's a question as to how well suited they are to your needs. For mine they work well, but if I was processing 600 queries / second, I think I'd want ibcopy to help me out. Regards, Chris quote who=P Srinivasulu If the backup solutions are there already, why is that a future requirement for Mysql? Thanks, Srinivasulu. Chris Nolan [EMAIL PROTECTED] 8/27/2003 6:41:27 PM Hi! You can currently do this with InnoDB with mysqldump (look at the --single-transaction switch). I use it for backing up a 12 GB mail database without problems. Regards, Chris P.S. Keep up the great work over there at Novell! Tell us where to send the expensive bottles of alcohol for when you help put SCO out of their misery! P Srinivasulu wrote: Hi All, The link below says that online backup
Re: Mysql And Backup
sunil sharma said: Dear Friends I am new in this list I am using mysql on linux My problem is about the backup of mysql database We are having 50 Databases and each database is of minimum of 300 MB in size and maximum of 2 G.B size I am planning to take incremental backup of the database For that i am planning to use mysqldump,But i m bit doughtful about the mysqldump because the size of the database is very huge I tried but it's taking a lot of time funny you asked that my question is similar so I'll group it with this one, hope you don't mind. Hello all, I have been using mysqldump -a to backup my clients sites. I have discovered a problem with this aproach. I decided to try and restore it with mysqlimport on my local hd and it'll restore it up to a certian point then stop. What I'm looking for is any other recomendations to backup and restore 71 databases. Any scripts for backing it all up will of course be welcom as well. second off, how do I wipe these old databases off my puter :) thnx, -- Jerry M. Howell II - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Mysql And Backup
Jerry M. Howell II wrote: sunil sharma said: Dear Friends I am new in this list I am using mysql on linux My problem is about the backup of mysql database We are having 50 Databases and each database is of minimum of 300 MB in size and maximum of 2 G.B size I am planning to take incremental backup of the database For that i am planning to use mysqldump,But i m bit doughtful about the mysqldump because the size of the database is very huge I tried but it's taking a lot of time funny you asked that my question is similar so I'll group it with this one, hope you don't mind. Hello all, I have been using mysqldump -a to backup my clients sites. I have discovered a problem with this aproach. I decided to try and restore it with mysqlimport on my local hd and it'll restore it up to a certian point then stop. What I'm looking for is any other recomendations to backup and restore 71 databases. Any scripts for backing it all up will of course be welcom as well. second off, how do I wipe these old databases off my puter :) thnx, Hi, You should not use mysqlimport to restore a backup made with mysqldump; use mysql instead. Check: http://www.mysql.com/doc/en/mysqldump.html I am quite surprised that you could restore anything with mysqlimport :( Regards, Joseph Bueno - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Mysql And Backup
I have been using mysqldump -a to backup my clients sites. I have discovered a problem with this aproach. I decided to try and restore it with mysqlimport on my local hd and it'll restore it up to a certian point then stop. What I'm looking for is any other recomendations to backup and restore 71 databases. Any scripts for backing it all up will of course be welcom as well. second off, how do I wipe these old databases off my puter :) You can run the dumpfile against a newly created database: mysql -u admin_user_name -p name_of_database ./dump_file.sql If you want to update another database then you should add --add-drop-table to the mysqldump command. On the box where you need to update the database you can run the command mentioned above. http://www.mysql.com/doc/en/Backup.html B. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Mysql And Backup found a solution
sunil sharma said:
Dear Friends
I am new in this list
I am using mysql on linux
My problem is about the backup of mysql database
We are having 50 Databases and each database is of
minimum of 300 MB in size and maximum of 2 G.B size
I am planning to take incremental backup of the
database
For that i am planning to use mysqldump,But i m bit
doughtful about the mysqldump because the size of the
database is very huge
I tried but it's taking a lot of time
So can anybody guide me regarding the mysql backup
policies?
Hello and thnx for your answers. Actually I found an alternative
solution. Was searching through the ftp site of the ppl. that we
lease our server from and found this script. Of course if anyone
has any feedback, good or bad let me know, but I tested it and
it seems to work for me. Might also come in handy when it comes
time for an acquaintance of mine to migrate 100+ clients onto our
servers. It's a Little Perl script that I think will help answer
this first persons question as well. when you need to restore it
simply untar them in the /var/db/mysql directory or where ever
your mysql db lies. I'll pate it simply becuse I don't think
the mysql list will suport atachments,
---begin code---
#!/usr/bin/env perl
# $Id: mysql-backup.pl,v 1.1.1.1 2002/12/31 17:33:45 smerkel Exp $
# Author: Steve Merkel
# Email:[EMAIL PROTECTED]
# Date: 12.29.2002
# Notes: This is a new implementation of the mysql_backup script.
# This version uses mysqlhotcopy and works with all control panels
# and no control panels. It also doesn't add the full path to the
# compressed database. Since it doesn't use mysqldump, the
# resulting backup simply needs to be copied into /var/lib/mysql
# under whatever name you want to give the database and restart
# mysql. No import of data is needed.
# There are several global variables that need to be set below.
# TODO:
#
# (12.29.2002)
#
# - Add the ability to define everything via a command-line
#option.
#
# - Make it work with Ensim. (Test with ensim anyway.)
use strict;
# Configuration Data
# ---
# Location where the live databases live.
my $LIVEDBDIR = '/var/lib/mysql';
# Directory where to store the backup data. This directory
# and the above directory can't be the same.
my $DATADIR = '/root/mysql-backup/';
# This defines which control panel is installed on the server.
# Current choices are: cpanel,psa,none
my $CP = 'none';
# Admin password. Set these if the control panel isn't a supported
# control panel and you need a username and password to connect to the
# database.
my $sqlpass = '';
my $sqluser = 'mysql';
# Control Panel Specific Values
# ---
# The location of the PSA shadow file.
my $psa_shadow = '';
# Subroutines
# ---
# Function: getPSAPass
# This function grabs the admin password out of the PSA shadow file.
sub getPSAPass {
# Open the shadow file
open(PSASHADOW,$psa_shadow) || die Can't open $psa_shadow\n;
# Get the PW.
my @psapw=PSASHADOW;
# Close the file.
close(PSASHADOW);
# Return the password.
return $psapw[0];
}
# Function genDBList
# This function uses the mysql client to generate a file with a list of
# databases. Cheap hack. No depend.
sub genDBList {
# Get the user and password passed into the function.
# Get the user and password passed into the function.
my $sqluser = shift;
my $sqlpass = shift;
# This array will contain the list of mysql databases.
my (@dblist);
# Bust out some mad system calls to get the db names.
if (($CP =~ /psa/) or (($sqluser ne '') and ($sqlpass ne ''))){
@dblist = `/usr/bin/mysql --user=$sqluser --password=$sqlpass -e show
databases;`;
}
else {
@dblist = `/usr/bin/mysql -e show databases;`;
}
# Return our list.
return(@dblist);
}
# Function: copyDB
# This function will use the mysqlhotcopy command to copy the databases
# listed in @dblist to $DATADIR.
sub copyDB {
# Get the user,password and database name info.
my ($sqluser,$sqlpass,@dblist) = @_;
# Check to make sure $DATADIR is defined.
if ($DATADIR eq '') {
die You must define \$DATADIR\n;
}
# Check to see if the datadir exists, and create it if not.
if (! -d $DATADIR) {
mkdir($DATADIR) || die Can't create . $DATADIR . . Error: . $!
.. \n;
}
# Just in case someone desides to put the location of the existing
databases in.
# Assumes default location.
if ($DATADIR eq $LIVEDBDIR) {
die You want to overwrite your databases?\n;
}
# Run mysqlhotcopy against all databases.
foreach my $line (@dblist) {
# Drop the eol char.
$line =~ /^(.*)$/;
my $db = $1;
# Make sure the db is there. Won't die if it isn't, it just looks
# like I'm not error checking if I omit this.
if ( ! -d
Mysql and Backup
Dear Friends I am new in this list I am using mysql on linux My problem is about the backup of mysql database We are having 50 Databases and each database is of minimum of 300 MB in size and maximum of 2 G.B size I am planning to take incremental backup of the database For that i am planning to use mysqldump,But i m bit doughtful about the mysqldump because the size of the database is very huge I tried but it's taking a lot of time So can anybody guide me regarding the mysql backup policies? or can anybody suggest me the url from where i can get the information? Thanx in advance __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Mysql And Backup
Dear Friends I am new in this list I am using mysql on linux My problem is about the backup of mysql database We are having 50 Databases and each database is of minimum of 300 MB in size and maximum of 2 G.B size I am planning to take incremental backup of the database For that i am planning to use mysqldump,But i m bit doughtful about the mysqldump because the size of the database is very huge I tried but it's taking a lot of time So can anybody guide me regarding the mysql backup policies? or can anybody suggest me the url from where i can get the information? Thanx in advance __ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MYSQL DATABASE BACKUP
Yes and no If you are taking info from a live database you would have it in a steady state to copy it. This means locking the tables. But once you have a copy of the table all you would need to do is update the changes from the logs. Using replication for this I is the most simple way but would mean a second copy of MySQL but you would only need a low spec system.. I hope this helps... Simon -Original Message- From: Kathy Reyes [mailto:[EMAIL PROTECTED]] Sent: 19 March 2002 21:37 To: mysql Subject: MYSQL DATABASE BACKUP I am trying to backup a table in mysql without locking my tables it this posible - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MYSQL DATABASE BACKUP
I am trying to backup a table in mysql without locking my tables it this posible - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MYSQL DATABASE BACKUP
Yes. Setup replication and peform the backup on the slave. Provided this is your only purpose for having a slave, and there are no queries running on the slave, the specs can be a lot lower than your master/production machine. -Original Message- From: Kathy Reyes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 1:37 PM To: mysql Subject: MYSQL DATABASE BACKUP I am trying to backup a table in mysql without locking my tables it this posible - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MYSQL DATABASE BACKUP
not quite sure what you mean by locking. each table will be locked during readout for the dump automaticly for the time the select runs and delivers data to the dumping program. it is not needed to lock the tables (more than one) in advance for a dump, but that, might better for dataintegrety. Lars Kathy Reyes wrote: I am trying to backup a table in mysql without locking my tables it this posible - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL redundancy/backup
Hello, I would like to hear your opinions, recommendations, ideas, etc., about the following subjects: I have two servers. Both of them have MySQL, PHP, Apache. The first server is used as SQL server and the second server is used as Web sever. The problem is that it is mission critical and very busy (!) website, and I want full MySQL redundancy. I want to start using MySQL on a Web server and have it synchronized with SQL server. Another problem: I would like to backup my critical tables every hour, but the tables are big and updated all the time, and can not be locked. How can it be implemented without affecting users ? Thank you for your time, Igal. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL redundancy/backup
Hi. You can use the built-in replication feature to sync a MySQL instance on the web server (slave) with the database server (master). Then you always have a recent snapshot of the database. You can also use the database on the slave to make your backups. Temporarily halt replication, make your backup and afterwards let it continue. It will automatically catch up with the current content. You'll want to compare the database content once or twice until you trust the replicated copy enough, before relying on it. This will usually work fine, because the slave only will have to execute the queries, which modify the database, which usually are only a fraction of the full traffic. The only question is whether your web server will stand up alone as web and database server, when your database server fails. But it will definitely be better than having no redundancy at all. Bye, Philemon. On Mon, Dec 10, 2001 at 11:57:26AM +0200, [EMAIL PROTECTED] wrote: Hello, I would like to hear your opinions, recommendations, ideas, etc., about the following subjects: I have two servers. Both of them have MySQL, PHP, Apache. The first server is used as SQL server and the second server is used as Web sever. The problem is that it is mission critical and very busy (!) website, and I want full MySQL redundancy. I want to start using MySQL on a Web server and have it synchronized with SQL server. Another problem: I would like to backup my critical tables every hour, but the tables are big and updated all the time, and can not be locked. How can it be implemented without affecting users ? Thank you for your time, Igal. -- [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql database backup issue
Hello, could anyone explain me how to backup and in case of system crash restore the mysql database (main database where data about other databases, grants,users, etc. is kept)? Thanks in advance ! Regards, Saulius Gurklys mailto:[EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
