How to restore your Hypernode from a backup

in Troubleshooting

Some hands-on experience is required! If you have never used the command line, please contact one of our partners to get some assistance.

To restore your Hypernode from a backup use the steps below.

Restore on DigitalOcean

Restore a database backup on DigitalOcean

When we restore a database backup, you’ll find a database dump compressed with gzip.
The name of this backup has the format database_name_date_timezone.sql.gz

To restore this backup you can use either n98-magerun or use the MySQL client utility:

Using n98-magerun:

For Magento 1:

n98-magerun db:import --root-dir=~/public <backup_filename>

For Magento 2:

n98-magerun2 db:import --root-dir=~/magento2 <backup_filename>

Using MySQL client:

zcat <backup_filename> | mysql <database_name> -u <magento db user> -p'<magento db pass>'

And then wait until the database is fully imported.

This might take a while for large databases, so get yourself some coffee in the meantime.

Restore a file backup on DigitalOcean

When you request a file backup on a Hypernode at DigitalOcean, we create a directory in your homedir in which we restore from a certain point in time.

To restore this backup, remove the old file or directory and copy the file(s) and/or directories in place in your /data/web/public directory.

IE: if you need to restore the media directory, use the command:

rm -rvf /data/web/public/media/ && mv restore/media /data/web/public/

If you need some visual assistance, you can use mc (midnite commander).

Restore on Amazon (AWS)

On Amazon (AWS) we use snapshots to create backups. Snapshots are a static copy of all data present on the disk that can be mounted on your AWS Hypernode as a new file system on /data/backup/.
When the file system is mounted, you can easily restore your files by copying them from the file system.

For databases we start an extra instance of MySQL running om port 3307 so you can easily create a dump of the database or load the data from the backup instance to the production instance.

When the restore is finished the backup snapshot is not automagically detached/unmounted. There is a second MySQL instance running so you’ll lose some resources. Please contact Support so we can remove your snapshots manually.

Restore a database on AWS

Create a database dump

To create a database dump from the backup instance, connect to port 3307 with the mysqldump utility and create a dump:

mysqldump $DATABASE -p 3307 | gzip > /data/web/dump.sql.gz

When the export is created, a backup file can be found in /data/web as dump.sql.gz

Dump the data from the backup MySQL instance into the production database.

To restore the backup and immediately import it in the production database use the following command:

mysqldump $DATABASE -p 3307 | mysql $DATABASE

Restore a file backup on AWS

To restore your files, copy the files from /data/backup/current to your public/ or magento2/ directory.