How reliable is CodeGuard?
CodeGuard’s systems perform at 99.9% levels. Today, 1 out of 1000 websites encounters a problem on a daily basis which can be caused due to various reasons. Hosting providers may perform maintenance on servers or customers may change their FTP login credentials. Additionally, the IP whitelisting settings for a database connection can change, based upon admin activity from the hosting provider’s end. These are common instances which can occur and are not a cause for concern. CodeGuards’ technology will determine the root cause for the lack of connectivity and will immediately email you for clarification on the same.
How secure is CodeGuard?
CodeGuard follows the industries best practices to protect your data. CodeGuard makes sure that all backups as well as passwords are encrypted to provide the highest possible security. Secure connections like SFTP/SSH/SSL are used wherever possible. An annual vulnerability testing is carried out by an independent agency, for more accurate results.
To date, there has not been any data breach, or a successful hack on CodeGuard. Rest assured your information is in safe hands.
Where are the backups stored?
The backups of your data are stored on Amazon Web Services Simple Storage System, also known as S3. S3 boasts durability levels of 99.999999999% which is achieved by distributing storage of data across multiple locations and facilities. Although S3 is not the cheapest form of data storage, we firmly believe it is the most reliable method to keep your data secure.
Are the backups encrypted?
Data on Amazon Web Services (AWS) is stored utilizing Server Side Encryption (SSE). Essentially, AWS handles the key management and key protection for us. This utilizes one of the strongest block ciphers available, 256-bit Advanced Encryption Standard (AES-256), ensuring the highest level of protection.
How are passwords stored?
There are two types of passwords that are stored on the system - customer account passwords which are passwords used to log into CodeGuard, and passwords for your credentials (FTP/SFTP, MySQL). Your passwords are stored using a one-way salted hash. These passwords are stored in Amazon’s Relational Database Service (RDS). Your server credential passwords are stored in RDS with RSA 2048-bit key encryption.
How does it work?
All file data is procured for the first backup using the GET command, over FTP or SFTP. Disk I/O is utilized as each file is fetched and transported to the servers. The CPU and memory needed for these processes are minimal. Subsequent backups differ in that they do not require transferring the entire content. This is accomplished by using the “ls – list” command and examining the relevant metadata stored for each file. These elements include: name, size, timestamp, file type, permissions, and last modified date. If any of these fields have been altered, or a new field has been created, CodeGuard will transfer the changed or added file to its servers. In case a file has been deleted, CodeGuard takes stock of this and accordingly adjusts its repository. Once again, since only the updated data files are transferred, the load on memory, CPU and other processes are minimal.
How does the restore/undo work?
If you ever want to go back to a previous version of your website, CodeGuard will go through your website and ascertains what content is on it. Consequently, it will then push (or pull) the differences which were made to or from your site. This is useful in instances where you might experience a hack that may have affected only your .htaccess. Codeguard’s technology simply replaces the infected file, and leaves everything else unchanged.
Will it bog down my server?
Short answer: No.
Long answer: Please refer to the "How It Works" section on this page.
Is it an easy process? Will I have to set up cron jobs?
It is a simple process which does not require you to setup any cron jobs.
Do you backup databases?
Yes. However, at the moment CodeGuard only supports MySQL Database backup. CodeGuard’s systems connect directly to your MySQL database, usually through Port 3306, or by tunneling over SSH with your FTP credentials or different credentials.
How does it work?
A MySQL dump command is carried out every time you need to retrieve your database content. The load on your server will be minuscule as MySQL databases aren’t large.