| Backup & Restore information | Article ID:76 |
No backup solution is 100% reliable for all situations. As such, 3Essentials strongly encourages it’s customers to maintain local copies (on their own systems) of their site for backup/recovery purposes. The general rule for managing web application changes is, don't publish a change to your site, if you don't have a local copy to roll back to (i.e., an unchanged copy of your site files to republish in order to un-do the changed files you just published).
Further, 3Essentials strongly recommends that before customers make changes to their site, they ensure they have a local copy of their functional site. Then, make your changes, test, and publish. If you have undesired results, restore/republish from the unchanged copy you made before your changes. This is a standard best-practice for site development and deployment. Prepare yourself to rollback your changes before you make the changes.
If you do not have a local copy of your site, 3Essentials is glad to assist by making a zip copy of your site as it resides on the server, and placing that zip archive in your directory for you to download via FTP. You can request this by submitting a Support ticket - be sure to specify if you have MSSQL or MySQL databases which you would like included in that zip archive.
The following describes 3Essentials backup/restoration services for Shared Hosting Plans:
The following describes 3Essentials backup/restoration services for Dedicated Server and VPS plans:
|
|
| Downloads associated with this article: | |
| No downloads associated with this article | |
 Back
to Search or Browse |
|