There are 7 steps to restoring a backup into a new site or a new server.
Make sure the site you’re restoring to is running the same webserver as when you backed up! You can’t restore OLS sites into NGINX sites or vice-versa.
While it might be obvious, we do need to mention that you should have a site already created with the same domain you’re trying to restore.
If your original site no longer exists then just create a new site with the same domain name – it will be overwritten during the restore anyway.
Download three files from AWS (or your AWS S3 compatible service). For example, if the site you’re restoring has a domain of ems01.vnxv.com, the three files that need to be downloaded will be:
ems01.vnxv.com_2022-07-31-11h25m44s_db.gz ems01.vnxv.com_2022-07-31-11h25m44s_nginx.tar.gz ems01.vnxv.com_2022-07-31-11h25m44s_fs.tar.gz
Note: the date and time stamps for the three files are the same (or for large files, they’ll be slightly different since each part will be backed up at a different time).
Log into server via ssh.
Check to see if a folder called .wp-backup exists
sudo ls ~/.wp-backup
If not, make one:
sudo mkdir ~/.wp-backup
Then, check to see if a folder with the domain name exists:
sudo ls ~/.wp-backup/yourdomain
If it does not, make one:
sudo mkdir ~/.wp-backup/yourdomain
Note: Replace yourdomain in the commands above with your actual domain. For example, if your actual domain is ems01.vnxv.com then your commands will be:
sudo ls ~/.wp-backup/ems01.vnxv.com
sudo mkdir ~/.wp-backup/ems01.vnxv.com
You can use any sFTP tool to upload the backup files to the folder from step 3 above.
Use the REFRESH button on the BACKUP tab for the site to let WPCD know that there are new backup files.
Use the RESTORE button on the BACKUP tab to start the restore process.
If you’re doing the restore into a new server you’ll need to do things like change DNS, remove/update caching and so on.