Skip navigation links
3.3.6 Backing Up In-Memory Database Data »
Section Navigation      [Toggle]

3.3.5.2. Backing Up to Tape with Oracle Secure Backup

Tape drives are affordable, high-capacity storage devices for backup data. The MySQL Enterprise Backup product can interface with media management software (MMS) such as Oracle Secure Backup (OSB) to drive MySQL backup and restore jobs. The media management software must support Version 2 or higher of the System Backup to Tape (SBT) interface.

On the MySQL Enterprise Backup side, you run the backup job as a single-file backup using the --backup-image parameter, with the prefix sbt: in front of the filename, and optionally pass other --sbt-* parameters to the mysqlbackup command to control various aspects of the SBT processing.

On the OSB side, you can schedule MySQL Enterprise Backup jobs by specifying a configurable command that calls mysqlbackup. You control OSB features such as encryption by defining a “storage selector” that applies those features to a particular backup, and passing the name of the storage selector to OSB using the MySQL Enterprise Backup parameter --sbt-database-name=storage_selector.

To back up MySQL data to tape:

  • Specify the --backup-image=sbt:name parameter of the mysqlbackup command to uniquely identify the backup data. The sbt: prefix sends the backup data to the MMS rather than a local file, and the remainder of the argument value is used as the unique backup name within the MMS.

  • Specify the --sbt-database-name parameter of the mysqlbackup command to enable the OSB operator to configure a storage selector for backups from this MySQL source. (This parameter refers to a “storage selector” defined by the OSB operator, not to any MySQL database name.) By default, mysqlbackup supplies a value of MySQL for this MMS parameter. The argument to this option is limited to 8 bytes.

  • If you have multiple media management programs installed, to select the specific SBT library to use, specify the --sbt-lib-path parameter of the mysqlbackup command. If you do not specify the --sbt-lib-path parameter, mysqlbackup uses the normal operating system paths and environment variables to locate the SBT library, which is named libobk.so on Linux and Unix systems and ORASBT.DLL on Windows systems. When you specify --sbt-lib-path, you can use a different filename for the library in addition to specifying the path.

To restore MySQL data from tape:

  • Specify the --backup-image=sbt:name parameter of the mysqlbackup command as part of the restore operation. Use the same name value as during the original backup. This single parameter retrieves the appropriate data from the appropriate tape device.

  • Optionally use the --sbt-lib-path option, using the same values as for the backup operation.

For product-specific information about Oracle Secure Backup, see the Oracle Secure Backup documentation.

Example 3.16. Sample mysqlbackup Commands Using MySQL Enterprise Backup with Oracle Secure Backup

# Uses libobk.so or ORASBT.DLL in standard places):
mysqlbackup --port=3306 --protocol=tcp --user=root --password \
  --backup-image=sbt:backup-shoeprod-2011-05-30 \
  --backup-dir=/backup backup-to-image

# Associates this backup with storage selector 'shoeprod':
mysqlbackup --port=3306 --protocol=tcp --user=root --password \
  --backup-image=sbt:backup-shoeprod-2011-05-30 \
  --sbt-database-name=shoeprod \
  --backup-dir=/backup backup-to-image

# Uses an alternative SBT library, /opt/Other-MMS.so:
mysqlbackup --port=3306 --protocol=tcp --user=root --password \
  --backup-image=sbt:backup-shoeprod-2011-05-30 \
  --sbt-lib-path=/opt/Other-MMS.so \
  --backup-dir=/backup backup-to-image
Copyright © 2003, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices