We use cookies to give you the best online experience. By using our website you agree to our use of cookies
Cookies Policy

Wish a different language?

To navigate through this site in another language
please select it from the dropdown menu above.

Register a domain as the first step to have a Web presence!

Domain name:   

Register a domain name! It will take only a couple of minutes!

Site Backups in the Cloud - Backup Again

Article Index

Page 5 of 6

Backup Again

After monitoring we continuously backup your site again and again if we detect changes.

Backup Overview

If the monitoring process detects any changes to the website source code, the files that changed or were added are transmitted to the CodeGuard repository. If any files are deleted, a record of the deletions is also transmitted to the repository. For deletions, those files are removed from the repository; additions are added and changed are overwritten to form a new version of the backup, which is shown within the user’s dashboard.

Since database files can be reduced to small sizes, CodeGuard transmits the entire database, which is compared with the previous version; if changes are found, a new version appears in the user’s dashboard.

To know what plan is best for you, prices, etc. Please contact us.

Backup Overview

If the monitoring process detects any changes to the website source code, the files that changed or were added are transmitted to the CodeGuard repository. If any files are deleted, a record of the deletions is also transmitted to the repository. For deletions, those files are removed from the repository; additions are added and changed are overwritten to form a new version of the backup, which is shown within the user’s dashboard.

Since database files can be reduced to small sizes, CodeGuard transmits the entire database, which is compared with the previous version; if changes are found, a new version appears in the user’s dashboard.

To know what plan is best for you, prices, etc. Please contact us.

Backup Comparisons

FTP/SFTP SOURCE MYSQL DATABASE

All backups after the first only retrieve the the files that were marked as changed during the monitoring process. If no changes are detected, the process ends after the monitoring step. This is roughly the same process as the initial backup with a few exceptions. This process also includes the monitoring step which is detailed above. Steps that differ from the initial backup are in italics:

  1. Test the connection to the site using the same protocol (FTP/SFTP) that the backup will use
  2. Download the existing repository archive from S3 and extract it on the local server instance (i.e. EC2)
  3. Build a list of files for the site using the methods described previously
  4. Monitor the files, add only the changed ones to the download queue
  5. Download each file to the Git repository (on the local machine)
  6. Commit all of the downloaded files to the Git repository
  7. Create a tarred and gzipped archive of the Git repository (which contains all of the backed up site files)
  8. Upload the archive to Amazon S3 which simultaneously encrypts the archive and all of its content
  9. Remove any previous versions of this backup that exist on S3
  10. Build the file mix data
  11. Record the statistics from the backup

This process is the similar to the initial backup, with the addition of these two steps:

  1. Instead of creating a new Git repo -- Download the existing repository archive from S3 and extract it on the local server instance (i.e. EC2)
  2. After uploading to S3 -- Remove any previous versions of this backup that exist on S3