Here we will cover the steps to follow if BoldGrid backups via Total Upkeep are showing up in the same folder for both live and staging sites. We will cover creating separate BoldGrid backup folders for the live and staging sites and setting the backup location path within the Total Upkeep plugin settings.
Related Articles
BoldGrid: What Is It?
Install BoldGrid Using Softaculous
Retrieve BoldGrid Connect Key from AMP
Changing the BoldGrid Backup Location for the Staging Site
IMPORTANT: While we always want to encourage you to create backups, we do recommend that, for safekeeping, you download any backups to your local computer within a week. In an emergency, we may need to remove backups on our Shared servers to prevent the server from running out of disk space. Please note we will never remove a backup without sending out a notification of any actions taken. More information on this can be found in our Terms of Service.
- Log into cPanel
- Navigate to File Manager, located in the Files section
- Create a folder for the staging site's backups
- From the home directory /home/userna5, select the +Folder button
REPLACE: userna5 with the appropriate cPanel username. - Add the folder name to the New Folder Name: field
EXAMPLE: staging.domain.com_Backups - Leave the New Folder will be created in: field blank
- Click Create New Folder
- From the home directory /home/userna5, select the +Folder button
- Log into the WordPress dashboard for the staging site
- On the left, click the Total Upkeep tab
TIP: For screenshot guidance of steps 5 - 8, all buttons can be seen in step 8 below. - Click the Backups tab
- Click Backup Storage
- Look for Web Server and click the update button to the right of it
- Under the Directory to store backup archives: field, type the full path of the directory where backups should be stored
EXAMPLE:/home/userna5/boldgrid_backup
-->/home/userna5/staging.domain.com_Backups
REPLACE: userna5 with the appropriate cPanel username, and replace the following folder name with the folder name created in step 3.
Comments
0 comments
Article is closed for comments.