By default, CodeGuard excludes many types of files that can unnecessarily take up space in our customers' backups. Below we have listed the patterns we use to exclude these files. If you would like to remove or add an exclusion rule for your website, please contact support.
Note: In the patterns below, asterisks (*) are used to represent wildcard characters.
Cache files are temporary files that are generated dynamically to reduce bandwidth usage and server load. They help speed up your website, but they can also unnecessarily take up space in your backups. Because cache files are temporary and can be regenerated as needed, we exclude many types of cache files from your backups.
Log files can be a useful tool for debugging when things go wrong, but they are not needed to restore a website. To reduce the size of backups, we exclude the following types of log files from your backups.
Operating systems often create files to keep track of OS-specific metadata that are not necessary to restore your website. We exclude these files to reduce the size of your backups.
In addition to excluding log, OS, and cache files, CodeGuard also excludes other temporary files as well. These are files that are only used for a short period of time or that are generated dynamically by your server.
In order to avoid duplication and avoid potential conflicts, we do not back up directories created by other backup solutions.
During a test restore, CodeGuard stores a temporary file to your server. We do this to ensure that we will be able to read from and write to your server in case we need to perform an actual restore. After the test restore, we remove the file. We exclude this file from your backups because it is not a part of your website.
CodeGuard relies on the Git revision control system for much of our differential backup logic. We exclude certain Git files that can cause issues with our backup processes. The content of Git repositories will still be backed up.