Sun Microsystems X4540 User's Manual
Contents
1. EXTINTO TETU Restore What would you like to restore r Restore To __ _ Restore From Date 2008 09 11 Restore will be done from last full backup 2008 09 11 14 46 22 Time 14 46 22 r What to restore Restore Type All Databases v Figure 8 Restore What Page Depending on how you determined the RPO you can launch the restore page in several ways e Click one of the timestamp links included in any successful backup report e Identify the recovery point in the Database Events Viewer and click the timestamp of the given event e Open the Restore What page and restore from the last full backup or any other date on which a successful backup was completed You can restore to a MySQL server that differs from the original backup source You can also use restores to instantiate new MySQL replication slaves This simplified restore work flow is the same regardless of the storage engine and backup method used When recovering mission critical data having a unified recovery procedure for all MySQL servers helps ensure efficient dependable and stress free recoveries Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 17 Summary Sun Microsystems Inc Summary This guide was a quick introduction to configuring the Sun Fire X4540 server as a backup server for Zmanda Recovery Manager 2 2 It provides examples for installing the Zmanda2. The ZRM for MySQL software e Zmanda Management Console with MySQL PHP Apache PHPmyadmin Perl and various Perl modules and their dependencies These are installed under the opt zmanda zrmand opt zmanda common directories Zmanda Management Console In addition to a powerful command line interface CLI ZRM also provides the Zmanda Management Console ZMC ZMC is a browser based user interface for setting up and managing all backup and recovery activities It is integrated with the Zmanda Network which provides certified ZRM binaries white papers demos technical support and a knowledge base to help you to deploy your backup solution ZMC provides context sensitive help and the most current information about ZRM from the Zmanda Network Using ZMC a backup administrator can accomplish all day to day backup activities including the following e Configure backup policies and schedules for each MySQL server Start immediate backups e Monitor ZRM activities and access reporting about backups and media Create edit and delete backup users and backup sets e Recover databases Browse the MySQL transaction logs To configure ZRM backups all you need to do is specify the following What to back up specify server databases and tables to back up Where to store the backup specify a destination When to perform the backup specify scheduling options for full and incremental backup How to perform the backup specify copy m
3. cluster Backup What displays options that are different from what is shown in Figure 2 The Server Parameters section lets you specify the connection details for the MySQL server to back up Choosing Port lets you enter a port number for communication with the MySQL server choosing Socket File lets you enter a path to the socket file You need to specify the host name or IP address of the MySQL server being backed up or localhost if the MySQL server and the ZRM server are on the same machine If you installed the same versions of MySQL client commands on the ZRM server and the MySQL server typically in usr bin use the factory Or Site Settings defaults for all backup sets If you installed different versions of MySQL software on the ZRM server and the MySQL server that is the backup client enter the full path to where MySQL binary commands are installed on the backup client In the MySQL User Parameters section enter the user name and password of the MySQL user on the MySQL server If no user is specified here ensure that you have the MySQL backup user with appropriate privileges specified explicitly as a Site Default or ensure that the MySQL user specified in the my cnf or options file has the necessary privileges described in System Requirements If the connection from the ZMC server to the remote server is via SSL specify the MySQL SSL parameters here If you are backing up databases on the localhost leave this field empty For
4. import laws in other countries Nuclear missile chemical biological weapons or nuclear maritime end uses or end users whether direct or indirect are strictly prohibited Export or reexport to countries subject to U S embargo or to entities identified on U S export exclusion lists including but not limited to the denied persons and specially designated nationals lists is strictly prohibited Sun Microsystems Inc Table of Contents VEO lurede a PAPAA EAE EEE bees send ae ass ES ak aban E sas 5 aes ae eee ae Bae I EBS 1 Configura IAO a ssi aces RA AA A Sas ad A A AS eh ee 2 QUE OW sz AE ds dock vcs crea td A AA das 2 Solaris COMMGUPAT OM AEA E ET E cece did A de E 3 ZNOOUCONTIGU CAL OM A A E ER E IEE E E A REES 3 ZES CONTIGUEA ION EAE EAE AAAA EE AA A A A A A A AES ET OAA EE 5 ZRIM CONTIGUE ALON rata da a RR E EA E Eaa EE 263 5 Installind the ZAMiscaiin a E PE O EAA AAT E A E P A A E AE A E 6 Zmanda Management Consoli ad 6 Contiguring BACKUP Seti A tas aabaaden cad Sus daa a owes oaths aa aa aE 7 GONTIGUFING SO A A a tai 10 Contiguring ZES SNapShOts ida AAA AA A de a Ri Lada dea 11 ZRM Monitoring and REPOrting c sssscccccssseccccsseccccensecccceseececeeeecceeaseeecceuseeceeeusecceeeuseeecsuseceecueceseeueecessaeeeeeegeeees 13 Database Events MI Wer iia 14 Recovery Using the ZIM Cores a a Un You ousgeecueebaguden gues Aensodesusbaevannet iaeileas teas 15 SUMMA a A A A ee wale Haas Edda 17 FOr Morelia idos 17 1 Int
5. remote MySQL backups the UID and GID of the MySQL user need to be the same on the ZRM client machine where the MySQL software runs as on the ZRM server ZRM allows you to back up the following All Database s Choosing this option includes all databases and all tables for backup e Specific Database s Choosing this option displays a list of databases available for backup on the MySQL server Select all the databases that you want to add to this backup set Specific Table s Choosing this option displays a drop down menu that lets you select a database from which to select tables to backup followed by the list of tables in the selected database select all the tables that you want to add to this backup set Clicking Save commits any changes you made to the currently selected backup set You can then proceed to the Backup Where page to select a target device or directory to store the backup image Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 10 Sun Microsystems Inc Configuring Storage Figure 4 shows the Backup Where page which specifies where the backup images for the backup set will be stored and how long to retain them zmanda MySQL Backup TIO ION Where would you like to make a backup admin Log Out Si Demo Y Values entered on this page will override Site Settings r Backup Where Parameters Destination Directory Wvarilib mysql zrm Tem
6. the network Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 4 Zpool Configuration Example zpool creation commands for a pool zmanda bash 3 bash 3 bash 3 NAME zmanda bash 3 bash 3 NAME zmanda bash 3 pool state scrub config errors OO OO OO zpool list OO OO zpool list 00 zpool status zmanda zmanda ONLINE none requested NAME STATE zmanda ONLINE raidz2 ONLINE cotodO0 ONLINE c1t0dO0 ONLINE c2t0dO0 ONLINE c3todo ONLINE c4todO0 ONLINE c5t0d0 ONLINE raidz2 ONLINE cot2d0 ONLINE c1t2d0 ONLINE c2t2d0 ONLINE c3t2d0 ONLINE c4t2d0 ONLINE c5t2d0 ONLINE spares cOt7d0 AVAIL c1t7d0 AVAIL No known data errors Sun Microsystems Inc zpool create f zmanda raidz2 cOt0OdO c1t0d0 c2t0d0 c3t0d0 c4tod0 cstodo zpool add zmanda raidz2 cOt2d0 c1t2d0 c2t2d0 c3t2d0 c4t2d0 c5t2do zpool add zmanda spare cOt7d0O c1t7d0 SIZE 10 9T SIZE 10 9T USED 204K USED 210K o OR CR o On ORO On On Onn On Onn Onn One AVAIL 10 9T AVAIL 10 9T o o 0 0 0000 0 0 000 00 000 READ WRITE CKSUM OR OR OR On On On On OR On On On On On Ome CAP 0 CAP 0 HEALTH ONLINE HEALTH ONLINE ALTROOT ALTROOT First we created the RAIDZ2 pool zmanda with six drives Then we added six more drives and verified that we had a pool with 10 9 Tbyte of physical space Depending on which RAIDZ configuration you choose the actual available capacity might b
7. 0 Server With Zmanda Recovery Manager 2 2 for MySQL Database 11 Configuring Storage Sun Microsystems Inc ZMC creates temporary files and directories during backup on both the ZRM server and the MySQL server The temporary directory specified here should exist on both machines and should have sufficient space to hold at least one full backup on the MySQL server during backup and on the backup host during restore plus 10 How much space this requires in practice depends on the backup method If mysqlhotcopy or the InnoDB Hot Backup plug in are used a full backup equals the size of the databases being backed up 10 With logical or snapshot backups only a few gigabytes of temporary space is typically required The temporary directory must exist on both the ZRM and MySQL server and have permissions set to allow read write access to the MySQL backup user A retention policy sets the limit of the period for which the backup set will be retained on the hard disk For example in Figure 3 the retention policy is set to 7 days and all backup images older than 7 days will be automatically purged Configuring ZFS Snapshots Figure 4 shows the Backup How page ZRM supports logical raw and snapshot based backups of MySQL databases Currently the following snapshot technologies are supported Solaris ZFS snapshot Linux LVM snapshot Symantec Veritas VxFS storage checkpoints Network Appliance snapshots e Microsoft Windows VSS Volume Sn
8. Recovery Manager for MySQL and configuring a zpool and the ZFS file system on the Solaris OS to utilize the Sun Fire X4540 server for storing MySQL backups For More Information Here are additional resources Documentation for Zmanda Recovery Manager from Zmanda Network requires registration http network zmanda com documentationEnterprise php e ZRM datasheet http www zmanda com zrm datasheet pdf e ZRM Guide to MySQL Backup 8 Recovery and Backup and Recovery Benchmark for MySQL with ZRM requires registration http network zmanda com zrm whitepapers php The following Sun documents at http docs sun com Sun Fire X4540 server document collection http docs sun com app docs prod sf x4540 hic ZFS Administration Guide part of the Solaris 10 System Administration Collection http docs sun com app docs doc 819 5461 e System Administration Guide IP Services part of the Solaris 10 System Administration Collection http docs sun com app docs doc 816 4554 MySQL documentation site http dev mysql com doc ZFS Best Practices Guide on the Solaris Internals web site http www solarisinternals com wiki index php ZFS Best Practices Guide Sun training courses at http www sun com training such as Sun Fire X4540 Server Administration WET 6179 MySQL training courses http www sun com software products mysql training jsp MySQL download sites O http www sun com software products mysql getit j
9. ZRM on Sun Fire X4540 Server Notes X4540 here refers to Sun Fire X4540 Server All figures reprinted with permission from Zmanda The complete ZRM deployment consists of the following e ZRM Server and Zmanda Management Console ZMC to centralize all backup and recovery operations for MySQL databases You need at least one ZRM server for your environment In Figure 1 ZRM is configured on the Sun Fire X4540 server e Zmanda ZRM clients installed on remote Solaris Linux or Microsoft Windows systems where you run MySQL Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 3 Overview Sun Microsystems Inc Solaris Configuration For this guide the Sun Fire X4540 server used for ZRM certification was running the Solaris 10 8 07 OS This is the minimum recommended version to use because various ZFS improvements were introduced in this build The Sun Fire X4540 server is powered by up to 8 CPUs operating at 2300 MHz and provides 48 SATA drives with a total capacity close to 50 Tbytes in a 4U enclosure The two boot drives are mirrored using Solaris Volume Manager with UFS The rest of the drives are available for backup data The default NIC configuration on the Sun Fire X4540 server allows up to four physical Gigabit Ethernet connections to be attached The connections provide backup ability for up to four separate subnets Alternatively the links can be aggregated together using dladm 1M for improved throughp
10. apshot Service also known as Volume Shadow Copy Service snapshots e EMC CLARIION snapshots admin Log out E gt P Y u How would you like to backup Configuration parameters have been saved for this backup set r Backup Parameters r Plugin Parameters Backup Mode y Compression Oves Ono O Default N Email Address OTF Compression OYes Ono O Default N Pre Backup O custom Default On The Fly Compression only for Logical Backup Plugin Path perj Binary Log Path arliblmysql Plugin Option s Encryption OYes Ono O Default N Po Pis rs Post Backup O custom Default r MySQL Integration Settings Plugin Path Use MySQL Replication Oyes Ono etauit ny COPY O custom Default A Include Stored Routines Yes Ono O Default N Copy Plugin SSH Force InnoDB Backup Oves Ono O Default Y SSH User mysql Snapshot O custom O Default Default Character Set utie Remote MySQL Binary Path usrbin Snapshot Type IT m Backup Type Standard Copy v Figure 4 Backup How Page Showing Snapshot Options Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 12 Configuring ZFS Snapshots Sun Microsystems Inc To take advantage of ZFS snapshots all MySQL database files data log indexes belonging to the backup set must be stored in ZFS volumes to ensure consistency If any of the files are not on ZFS volumes a raw backup u
11. atabase events list As you move your cursor up and down this vertical bar a tool tip displays the date and time of the events in that relative location Clicking the tool tip jumps to the given date and time 2mando _ sm 1000 IAS MySQL ERA TN Report ESTO e m men i RA a Demo Iv Jm i A E Backup Date 2008 09 17 Go Database Events la a Page1of54 gt OQ September2008 Time stamp 2008 09 17 133173 Searem S Page 25 AAA ASA 2008 09 17 11 05 08 Query FLUSH PRIVILEGES A om 2 pp j4 5 8 2008 09 17 11 06 06 Stop DELIMITER DELIMITER E 7 12 13 2008 09 17 11 06 08 Startb ROLLBACK I a e u 2008 09 17 11 13 00 Stop DELIMITER DELIMITER 14 7 19 20 2008 09 17 11 13 15 Start b ROLLBACK 2008 09 17 11 25 06 Query PIC latin1 1 GRANT ALL PRIVILEGES ON TO root localhost IDEN 21 26 27 2008 09 17 11 25 13 Query FLUSH PRIVILEGES 28 a 2008 09 17 11 25 25 Query use mysql GRANT ALL PRIVILEGES ON TO root localhost IDENTIFIE 2008 09 17 11 25 27 Query FLUSH PRIVILEGES 2008 09 17 13 06 21 Query INSERT INTO mysql user Host User Password Select_priv Insert_priv 2008 09 17 13 06 36 Query flush privileges Pre 5 or v use mysql GRANT ALL PRIVILEGES ON TO root localhost IDENTIFIED BY zmanda WITH GRANT OPTION 17 Legend Backup Level Multiple Level 0 g L
12. e at http blastwave org Once the archive have been downloaded use the gtar 1M command to extract the prerequisite packages Next use the pkgadd 1M utility to install the packages Installing ZRM The installation program for ZRM is called the Rapid Installer The Rapid Installer contains the ZRM Server and ZRM Client as well as the ZMC web user interface Note The following tasks must be performed as super user the root user To run the Rapid Installer first make sure that the binary file is executable chmod x ZRM enterprise 2 2 installer intel bin If you are installing from within a graphical environment simply run the installer by double clicking it or executing it directly from the command line ZRM enterprise 2 2 installer intel bin If you are installing from a text console or remotely for example via SSH you can run the Rapid Installer in text mode ZRM enterprise 2 2 installer intel bin mode text The Rapid Installer then starts Follow the on screen instructions The installer performs several tasks after creating and populating the Zmanda directories These tasks are completed after the progress bar which tracks only the archive extraction shows 100 completion These tasks take time Please wait until they are completed Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 7 ZRM Configuration Sun Microsystems Inc The following software components are installed
13. e different See the zpoo1 1M man page for more details Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 5 Zpool Configuration Sun Microsystems Inc The next step was adding two spare drives Lastly we checked the pool status and verified the availability of the zmanda pool for configuring ZFS RAIDZ2 is a natural choice for a backup server which contains information vital to business operations RAIDZ2 can survive up to two drive failures regardless of whether they are due to corrupt data coming off the drives a physical failure of the drives or drives that are missing With a suitably large number of disks RAIDZ2 does not impose a greater penalty in capacity or performance than RAIDZ ZFS Configuration The Zmanda Recovery Manager on the Sun Fire X4540 server Backup Server is configured to write backup images to a directory For this sample installation we chose to put the backup images for all backup sets on a single ZFS file system On a system where multiple backup sets might be running simultaneously it would be advantageous to have separate ZFS file systems and pools for each backup set in order to spread reads and writes around the available disks Example of ZFS file system creation bash 3 00 zfs create o mountpoint var lib mysql zrm zmanda zrm bash 3 00 zfs list NAME USED AVAIL REFER MOUNTPOINT zmanda 203K 7 13T 49 0K zmanda zmanda zrm 49 0K 7 13T 49 0K var lib mysql zrm ZRM C
14. echanisms to use The ZRM user interface is organized into these tasks and includes a corresponding page Backup What Backup Where Backup When and Backup How to accomplish each task as described in the sections that follow Configuring Backup Sets To get started with ZRM you need to first configure backup sets A backup set is a key policy concept of ZRM that simplifies and optimizes the database backup and recovery process ZRM lets you manage multiple backup sets so you can protect different MySQL servers and databases with settings appropriate for the respective applications The backup set defines the following List of servers and their databases tables that are to be backed up Location where a given backup set should be stored Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database Sun Microsystems Inc e Backup time and parameters for backup level scheduling OPTIONAL Snapshot technology used to make backups e OPTIONAL Local storage location of snapshots for near CDP protection of MySQL databases Each backup set contains at least one database or database table Backup sets are easy to copy add and modify All backup reporting monitoring and restore actions are performed on the backup sets This enables the backup administrator to abstract the backup policies and apply the same policy for multiple databases When creating backup sets for an application such as Customer Relationship Manag
15. ect a snapshot plug in from the Backup How page The ZFS snapshot does not require additional parameters Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 13 Configuring ZFS Snapshots ZRM Monitoring and Reporting The complexity of backup operations for MySQL databases makes it difficult to estimate how well you meet the business objectives of data protection The comprehensive monitoring and backup reporting provided by ZRM helps you to ensure your MySQL data is protected well Figure 5 shows the Monitor page admin Log Out sla S Sun Microsystems Inc Bel Level Mode Read Locks Time Time Taken Size Replication Compressed Encrypted Size after compression encryption 2008 09 11 14 15 02 Nanilib Imysql zrm localhost i Full raw 00 00 00 00 00 08 20 45 MB No Yes No Time Taken Messages Initialization Running pre backup plugin Flushing logs Creating snapshot based backup Calculating backup size amp checksums Compression Encryption Running post backup plugin Cleanup 00 00 01 00 00 00 00 00 00 00 00 06 00 00 00 00 00 01 00 00 00 00 00 00 Location of Backup var lib mysql zrm Demo 20080911141502 Databases Backed Up world Figure 5 Monitor Page Showing Backup Progress Figure 6 shows the Summary view on the Reports page with an easy to understand visual cal
16. ement CRM remember to include all the databases and tables required to maintain the referential integrity and consistency of the application Put all the related databases in the same backup set The Backup What page shown in Figure 2 simplifies backup source selection by automatically discovering all the databases and tables on a given MySQL server zmanda f admin Log Out Se Slo 9 ls MySQL fa eee mid MS A E E Tale What would you like to backup Values entered on this page will override Site Settinas r MySQL Server Parameters r MySQL User Parameters Server Type MySQL Sever y Username root Connection Type O Port O Socket File Password eesse Port Number 3306 SSL Options Host remote mysql server MySQL Client Utilities Path usribin r What to backup Backup Source Type Specific Database s Y Select Database s Select All None O mysql Ditest M world Figure 2 Backup What Page Figure 2 shows an example of configuring a backup set called Demo for the MyISAM database world on a remote MySQL server Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 9 Sun Microsystems Inc Note For many ZMC forms the fields change depending on the context selecting different values can change the options that are displayed For example if you choose to back up the MySQL
17. endar of your backups for a month at a time with color coded indicators of success failure or warning Multiple squares indicate several backup runs that day In case of a problem you can quickly drill down to a report with details about any backup run Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 14 ZRM Monitoring and Reporting Sun Microsystems Inc Backup Monitor port RA Backup Date 2008 09 11 Backup Summary a a 2008 09 11 September 2008 Timestamps 02 00 m 14 46 m s 7 E TimeStamp 14 46 22 4 BACKUP SUMMARY Backup Type Copy Backup Level 0 MySQL Version 5 0 67 log Host localhost Comment Demonstration Databases backed up in raw mode using snapshot world InnoDB shared data files backed up var lib mysql ibdatal InnoDB logs backed up var lib mysql ib_logfile Retention policy 7D Compress Yes Encrypted No STATISTICS Size of backup 20 45 MB Size of backup after compression encryption 0 15 MB Time taken for backup 00 00 06 Time taken for compression encryption 00 00 10 Success Time duration for which read locks were held 00 00 01 Time taken for flushing database pages to disk 00 00 00 Backup Runs Single Multiple Warning Failure mM Figure 6 Calendar View of Recent Backup Reports ZRM provides nine pre defined reports all o
18. evel 1 g Figure 7 Database Events Viewer These features let you choose a recovery point right down to the transaction level You can set the recovery point right from the Database Events Viewer Just click the date and timestamp link next to the last transaction you wish to recover ZRM then directs you to the Recover screens with all the appropriate values filled in to recover the database to that exact date and time Recovery Using ZMC The R in ZRM stands for Recovery which of course is the primary objective of ZRM simple dependable and efficient recovery of data To restore data simply use the Restore What page shown in Figure 8 to select the backup set the database or individual tables to recover You can restore individual tables only if logical backups have been run Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 16 Recovery Using ZMC Sun Microsystems Inc After selecting what to restore from choose a recovery point objective RPO ZRM catalogs all full and incremental backups performed When you request a point in time restore ZRM automatically finds the full backup and all the incremental backups required to restore your database to the requested RPO ZRM allows you to restore to a point in time regardless of whether logical raw or snapshot based backup was executed the only requirement is that you have set up incremental backups as well zmanda MySQL
19. f which can be easily customized e Backup report e Backup application performance report e Backup status report Backup methods report e Backup retention policies report e Backup performance report e Incremental backup report e Backup replication report Cluster backup report In addition to the pre defined reports you can create and save for future use highly customized reports on more than 30 different backup and MySQL parameters Reports can be generated and delivered in a variety of ways The output can be either text or HTML Reports can be delivered as RSS feeds or as email These options let you integrate ZRM reporting with the monitoring dashboard you are already using Database Events Viewer The Database Events Viewer Visual Log Analyzer shown in Figure 7 lets you visually browse the MySQL binary logs used for incremental backup so you can select exactly what point in time you wish to restore Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 15 Database Events Viewer Sun Microsystems Inc The date and time of each database event is shown as an individual record You can easily scroll through the entries and search the logs with queries Using the search you can locate any event that caused harm to your database You can also jump to a given date and timestamp To help you navigate through events there is a special vertical orange tool bar to the left of the date and timestamps in the d
20. icrosystems Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database Thomas Hanvey Sun Microsystems Dmitri Joukovski and Ken Crandall Zmanda October 2008 Copyright O 2008 Sun Microsystems Inc 4150 Network Circle Santa Clara California 95054 U S A All rights reserved U S Government Rights Commercial software Government users are subject to the Sun Microsystems Inc standard license agreement and applicable provisions of the FAR and its supplements Use is subject to license terms This distribution may include materials developed by third parties Parts of the product may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark in the U S and in other countries exclusively licensed through X Open Company Ltd X Open is a registered trademark of X Open Company Ltd AMD Opteron the AMD logo the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation in the United States and other countries Sun Sun Microsystems the Sun logo MySQL Solaris Sun BluePrints Sun Fire Sun StorageTek and SunSolve are trademarks or registered trademarks of Sun Microsystems Inc or its subsidiaries in the United States and other countries This product is covered and controlled by U S Export Control laws and may be subject to the export or
21. in Storage Resource Collection http www sun com bigadmin collections storage html e Sun Storage web site http www sun com storagetek index jsp e Storage Stop Blog http blogs sun com storage Support Sun resources e Register your Sun gear https inventory sun com inventory e Services http www sun com service index jsp e SunSolve Online http sunsolve sun com e Community system administration experts http www sun com bigadmin content communityexperts e Events of interest to users of Sun products e Sun and MySQL Around the World Meetup Mashup http www sun com events mysqltour index jsp e Find a MySQL Meetup Group near you http mysgql meetup com e Worldwide developer events and Sun Tech Days http developers sun com events e Current events http www sun com events index jsp Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 19 Licensing Information Sun Microsystems Inc Licensing Information Unless otherwise specified the use of this software is authorized pursuant to the terms of the license found at http www sun com bigadmin common berkeley license html Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database
22. int in time or to any particular transaction for example just before a user made an error e Centrally manage all backup and recovery operations for a single or multiple MySQL servers from a web based management console e Schedule full and incremental backups of your MySQL database e Define retention policies and automatically delete backups that have expired e Visually review MySQL logs for operational and security reasons e Easily identify recovery points e Choose flexible logical or faster raw backups of your database e Provide hot backups of online MySQL databases via various snapshot technologies e Back up your remote MySQL database through a firewall e Configure on the fly compression and or encryption of your MySQL backups to meet your storage and security needs e Get email or RSS notification about the status of your backups and receive MySQL backup reports Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 2 Configuration Sun Microsystems Inc Configuration Overview Figure 1 shows an example of Zmanda Recovery Manager ZRM running on the Sun Fire X4540 server and protecting remote MySQL servers running on Solaris OS Linux and Microsoft Windows machines with MyISAM and InnoDB tables and a MySQL Cluster with NDB storage engine Zmanda Recovery Manger for MySQL x4540 InnoDB Solaris gt MyISAM Linux MyISAM Windows Figure 1 Centralized Backup of MySQL Server With
23. onfiguration The Sun Fire X4540 server is configured as a ZRM server with Zmanda Management Console ZMC To install ZRM and ZMC follow these overall steps which are explained in more detail in subsequent sections 1 From the Zmanda Network web site which requires registration download the following e ZRM installer binary for Solaris 10 systems with Intel or AMD Opteron processors ZRM enterprise 2 2 installer intel bin e Prerequisite packages solaris 10 zrm dependency intel tar gz 2 Extract the prerequisite packages solaris 10 zrm dependency intel tar gz and install all the included packages 3 Extract the binary package and run the Zmanda Rapid Installer to install ZRM 4 After the installation is complete the ZMC Welcome Page is displayed and you can begin configuring backup sets Installing the Required Dependencies The required dependency packages are provided in a compressed tar archive file solaris 10 zrm dependency intel tar gz that you can download from the Zmanda Network http network zmanda com Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 6 ZRM Configuration Sun Microsystems Inc The dependency packages provided are as follows e SMCcoreu e CSWgcc3corert e CSWgcc3g rt MCgpgme Ss Q Q H 0 jo MClgcc346 Ss 8 a A Rh op H Q a Y Oo Q 5 0 lt HE These packages are also available from Sunfreeware at http sunfreeware org and from Blastwav
24. porary Directory imp Retention Policy 7 days M Figure 3 Backup Where Page for Configuring Storage Regardless of where the remote MySQL server is hosted backups are stored under the backup directory of the local machine where ZMC runs The default is var 1ib mysql zrm If you specify another directory you must create it yourself on both the ZRM server and the MySQL server and ensure that its permission settings allow read write access to the MySQL backup user We already configured a ZFS volume at var 1ib mysql zrm asa repository for MySQL backup archives For extra protection the MySQL backup data can be migrated to other storage devices for example to a Sun StorageTek SL48 Tape Library using network based backup and recovery software such as Amanda Enterprise You must allocate sufficient disk space to store backup copies of all your MySQL databases In the unlikely event that the Sun Fire X4540 server does not have sufficient disk space allocated the backup run will fail The destination directory should have at least 150 of uncompressed backup space available for a successful backup run This additional space is required even when backups are configured for compression since the additional space is used for compression during the backup run The additional space is freed after the backup run It must also have permissions set to allow read write access to the MySQL backup user Using Sun Fire X454
25. roduction Sun Microsystems Inc Introduction This paper discusses how to quickly configure and deploy the Sun Fire X4540 server with Zmanda Recovery Manager 2 2 for MySQL databases For more information on ZRM Enterprise see http zmanda com zrm mysql enterprise html MySQL software has become the world s most popular open source database because of its ease of use high performance and high reliability see http www sun com software products mysql Regardless of how you use MySQL software for example with a web site or a custom MySQL application you must ensure successful secure and consistent backups with minimal impact on applications The Sun Fire X4540 server can deliver massive storage capacity and remarkable throughput so it is well suited as a nearline storage platform for backup and restore applications Combining the power of the Solaris 10 Operating System with the data integrity and simplified administration of ZFS the Sun Fire X4540 server can be an ideal candidate for streamlining and improving backup and restore operations Zmanda Recovery Manager ZRM for MySQL provides comprehensive backup and recovery capabilities for MySQL databases It simplifies database administration by providing an easy to use flexible and robust backup and recovery solution With ZRM you can e Perform backups that are optimized for your storage engine and your MySQL configuration e Recover a database easily to any po
26. sing mysqlhotcopy or a logical backup using mysqldump is performed depending on the storage engines of the tables in each of the databases Refer to the ZFS documentation mentioned in the For More Information section at the end of this document for details on ZFS administration Here are some valid scenarios for database storage on ZFS All MySQL data is stored on a single ZFS Volume e Specific database directories are stored on different volumes Note For databases containing InnoDB based tables the snapshot can be used only if the database directory the InnoDB data files and the InnoDB logs are all on the same ZFS volume Choose the preferred method of snapshot backup using the drop down menu The Standard Copy option specifies that the snapshot should be copied to a specified earlier backup location on the Sun Fire X4540 server The Quick No Copy option specifies that the snapshot itself should be used as a nearline backup Quick backups are convenient because they provide faster backups and restores but because they remain on the MySQL server they do not protect against disk or server failure Quick snapshot backups can be converted to standard backups stored on the ZRM server using the Convert Backup option available from the Reports menu tab To enable backup via a snapshot Backup Mode selected from the upper left of the Backup How page must be Raw If the current backup mode for the set is Logical you cannot sel
27. sp O http dev mysgl com downloads Discussions e Zmanda forums http forums zmanda com e MySQL forums http forums mysql com e Sun Storage forums http forum java sun com category ispa categoryID 66 e Sun Hardware Servers forums http forums sun com forum jspa forumID 830 Using Sun Fire X4540 Server With Zmanda Recovery Manager 2 2 for MySQL Database 18 For More Information Sun Microsystems Inc e Wikis e Sun BluePrints wiki http wikis sun com display BluePrints Main especially the following e Storage BluePrints page http wikis sun com display BluePrints Storage BluePrints e Sun BluePrints article Optimize MySQL Server on Sun x64 Servers and Storage http wikis sun com display BluePrints Optimize MySOQL Servert ton Sunt x 64 Servers and Storage e Sun Storage Administration wiki http wikis sun com display StorageAdmin Home BigAdmin Storage Tech Tips wiki http wikis sun com display BigAdmin Storage Tech Tips Other resources e Zmanda Recovery Manager for MySQL web site http mysqlbackup zmanda com e Sun Fire X4540 server web site http www sun com servers x64 x4540 e MySQL site on sun com http www sun com software products mysql index jsp e mysql com web site http www mysql com e BigAdmin article Sun Fire X4540 Server as Backup Server for Zmanda s Amanda Enterprise 2 6 Software http www sun com bigadmin features articles zmanda sfx4540 jsp e BigAdm
28. ut to a single subnet Zpool Configuration The decision about how to configure zpools needs to be based on a number of factors What is the required performance needed IOPS throughput What is the required data protection level needed RAIDZ RAIDZ2 mirror e What is the required capacity After gathering and analyzing the requirements a configuration that balances the needs of those requirements can be chosen When configuring the system for network backups the ability of the Sun Fire X4540 server to receive data over the network is also a factor For example a 500 Mbyte sec backup speed requirement cannot be met solely by using the 4 pre installed Gigabit Ethernet ports Additional network cards would be required to accommodate such throughput Care should be taken that a system is not over configured for disk performance at the expense of space or data protection when the entire system encompassing MySQL backup clients and network infrastructure is not able to send data at adequate levels Likewise a system should not be over configured for space at the expense of performance or data protection For the purposes of this guide the Sun Fire X4540 server was configured with one zpool consisting of 12 drives and 2 spares in a RAIDZ2 configuration This provided 7 Tbyte of capacity for backups with a very high level of protection against drive failure and performance sufficient to handle 300 to 350 Mbyte sec of backup traffic over
Download Pdf Manuals
Related Search