MySQL Backup - Restoring from a Zmanda backup

-

How To Restore A MySQL Database from a Zmanda Backup


  • Backups are written round robin daily by each of the xxxxctrl01-04mqp backup servers to autofs mapped volumes u05md1,u05md2,u05fc1,u05fd1.  Using the mysql backup schedule determine which mapped volume the latest backup will reside on, or do a search through the successful zmanda backups emails to get the latest.
  • SSH onto one of the 4 mysql backup control servers as root user.
  • cd into the backup location to verify the backup file is there.  As an example "cd /u05md1/mysql/xxxmyq7r_3317_B1/20171015060001/" "ls" then verify that there is a "backup-data" and "index" file within the folder.  In this example the "B1" means schedule B and backup server 1.  The "20171015060001" refers to the date/time the backup was taken,  "backup-data" is the actual backup file zipped up.  "index" contains information about the backup.
  • Perform the restore by using the "mysql-zrm-restore" command. This can be run from any on the control servers and will be in the format as follows in the below example where host should be replaced with the target host, databases should be the databases being restored (can be multiple separated by a space), port is the port of the target and password is the password of the target.  Source is the location of the backup we are restoring from:
    mysql-zrm-restore --verbose --databases "eventsplanning" --host xxxxxx.xxxx.xxx.xxxxx.xx --port 3307 --user root --password h0rnet40 --source /u05md1/mysql/xxxmyq7r_3317_B1/20171015060001/
  • After carefully checking your mysql-zrm-restore command hit return, and the restore procedure will start by verifying your parameters, it will then unzip the backup-data file, then restore the database.  Any existing database / tables will be overwritten.  Zmanda is a logical restore and behind the scenes is doing a standard mysqldump restore.  It is possible to manually unzip the backup-data file and restore using mysqldump using source command but we should always use zmanda unless there is a good reason not too (e.g. a partial restore of a table).
  • On completion there should be a successful message.

Comments

Post a Comment

Popular posts from this blog

SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

-
SQL SERVER – Event ID 107- Report Server Windows Service cannot connect to the report server database. Error with Report Server One of my clients reported an error which is the subject of the blog. In the event viewer they were seeing below error:     Event Type: Error Event Source: Report Server Windows Service (MSSQLSERVER) Event Category: Management Event ID: 107 Computer: SQLSERVER Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database The error is generic because it doesn’t tell the exact error which is causing a connectivity error. My immediate question was that, are there any more errors? So, I asked them to look at Reporting Service Log file. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. The application domain WindowsService_17 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report se
Read more

SQL Server Builds Information

-
Image
Very Useful information about SQL Server Builds .  It is nicely presented in the blog . Please see  below for our reference . Microsoft SQL Server Version List What version of SQL Server do I have? This unofficial build chart lists all of the known Service Packs ( SP ), Cumulative Updates ( CU ), patches, hotfixes and other builds of MS SQL Server 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released. Useful articles: How to identify your SQL Server version and edition SQL Server Internal Database Versions Microsoft SQL Server Support Lifecycle Microsoft SQL Server Home Microsoft SQL Server Developer Center Microsoft TechNet: Microsoft SQL Server Microsoft Knowledge Base Sqlservr.exe versions   Quick summary:   RTM (no SP ) SP1 SP2 SP3 SP4   SQL Server 2017      codename vNext 14.0.1000.169 *new           SQL Server 2016 13.0.1601.5 13.0.4001.0 or 13.1.4001.0 13.0.5026.0 or 13.2.5026.0   S
Read more

Using DBCA silent install and disabling automatic memory management

-
Image
Avoid issue [DBT-11211] /app/oracle/product/12.2.0/dbhome_1/bin=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -memoryPercentage 20 -emConfiguration NONE [FATAL] [DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB.    CAUSE: The current total physical memory is 11GB. Solution : disable automatic memory management with in the response file and you will be fine :) .  /app/oracle/product/12.2.0/dbhome_1/assistants/dbca/templates=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -automaticMemoryManagement FALSE -memoryPercentage 20 -emConfiguration NONE Enter SYS user password: Enter SYSTEM user password: [WARNING] [DBT-06208] The 'SYS' password entered does not conform to the Oracle recommended standards.    CAUS
Read more