How to Back Up Your WordPress Database Before Upgrading

Before upgrading your WordPress software installation, make sure you back up your database. This step safeguards your website and ensures that you have a complete copy of your website data in the event that your upgrade goes wrong.


The best way to back up your database is to use the MySQL administration interface provided to you by your web hosting provider.


The following takes you through the steps of creating a database backup, using the same phpMyAdmin interface:



  1. Browse to http://yourdomain.com/cpanel to bring up the login screen for your cPanel. Enter your specific hosting account username and password in the login fields and click OK to log in.


    cPanel is a web hosting interface provided by many but not all web hosts as a web hosting account management tool that contains phpMyAdmin as the preferred tool to use to manage and administer databases.



  2. Click the phpMyAdmin icon.


    The phpMyAdmin interface opens and displays your database.



  3. Click the name of the database that you want to back up.


    If you have more than one database in your account, the left-side menu in phpMyAdmin displays the names of all of them. Click the one you want to back up; the database loads in the main interface window.



  4. Click the Export tab at the top of the screen.


    The page refreshes and displays the backup utility page.


    This compiles the database backup file in a .zip file and prepares it for download.


    A pop-up window appears, allowing you to select a location on your computer to store the database backup file.



  5. Click the Save button to download it and save it to your computer.


    After you install WordPress and log in for the first time, you can see the version number at the bottom-right corner of the WordPress Dashboard. Therefore, if anyone asks what version you’re using, you know exactly where to look to find out.






dummies

Source:http://www.dummies.com/how-to/content/how-to-back-up-your-wordpress-database-before-upgr.html

No comments:

Post a Comment