W3 Safe
Is Your Website Safe?
- Do you rely on your website for income?
- Are you prepared for your website to crash?
- Do you have a current backup of your website and it's database?
- Are you a web developer who relies on 3rd party servers to host your client websites? Those clients are going to blame you for any data loss if their site crashes.
Did You Know...
- Digital files are only considered safe if they exist in at least two or three places.
- Keeping a recent copy of your website files does not mean that your website is safe. Almost all websites including Joomla!, WordPress, Drupal, and other blogs or content management systems use a database that is forever changing. Without a recent copy of your database your site is gone.
- E-commerce websites store all of their important information in a database. This includes your product inventory, customers, and order history. For a busy website, each day of data loss can be substantial.
- If you use a content management system such as Joomla!, WordPress, Drupal, or any other system that allows you to install addons, insert images, etc, your local copy of your website is almost certainly missing files.
- Many hosting providers have daily backups already in place but those backups are typically stored on the same server as your website. If your server crashes, which it certainly can, often those backups are unusable and the hosting company is unable to restore your website. I've seen this happen first-hand more than once.
Automatic website backup, database backup, and peace of mind with W3 Safe.
Features
- Automatically backup your website files and database(s) as often as you'd like. You control the frequency with UNIX cron jobs or the Windows Task Scheduler.
- Only files that don't exist locally or have changed are downloaded (incremental backups).
- Backup unlimited websites and they will all be safe.
- W3 Safe is perfect for backing up a personal blog or for web developers with hundreds of clients.
- By design, your files are always stored in at least two locations (the FTP server and your local copy). You can go even further with up to four locations using Amazon S3 and/or a Version Control System.
Easy Restore
A backup system is useless if you can't restore your data. Restoring your website after a crash is simple and takes just a few clicks. Your files will be restored and your database will be reset to the date you choose.
Disaster Recovery
Using the easy restore feature can also help you quickly recover from files being deleted or malicious code being injected into your website files.
No Proprietary Formats
Your backups are stored as regular files on your filesystem. No proprietary formats are used to encapsulate your backup. Even the configuration file is simply XML and can be edited on the command line if desired.
Website Transfer
Transfer websites from one server to another effortlessly using the website transfer feature. A wizard will prompt you for some information about the new server and that's it. Your existing site files and database(s) will be downloaded and then uploaded to the new server automatically. You can simply set it up and walk away until its done. The new site is automatically added to your site list so that you never miss a backup.
Command Line Interface
W3 Safe fully supports managing your site list, performing website backups, and restoring websites from the command line. This is ideal for using W3 Safe on a headless server where you probably want to store your backups anyway.
Amazon S3
W3 Safe always maintains a local copy of all sites you've configured. For added security you can also configure your local copies to be pushed out to Amazon S3 cloud storage. Again, only files that have changed are sent in order to minimize bandwidth, transfer time, and Amazon S3 transfer fees.
Using Amazon S3 means that your files are now stored in three locations (the FTP server, your computer, and Amazon S3). Now, in the unlikely event that your FTP server and computer both crash, you've still got a copy of everything on Amazon S3.
* An Amazon S3 account is required and carries its own additional fees. These fees are nominal and well worth it. Click here for Amazon S3 prices.
Version Control Systems (CVS, SVN, and GIT)
CVS, SVN, and GIT support allows you to backup straight to your working copy and automatically commit new or modified files as they are downloaded. Your working copies will always be up to date when files on the server change.
W3 Safe will not download files if your local copy is newer than the file being downloaded. This protects your working copies from being overwritten and losing your unpublished work.
W3 Safe can also be configured to ignore metadata files that have inadvertently been uploaded to your server. You can ignore .cvs, .svn, .git, Thumbs.db, and .DS_Store files to avoid corrupting your working copy.
Cross Platform
W3 Safe is built with Java and therefore runs on Windows, Mac, Linux, and probably others. A command line version also allows you to run W3 Safe on a headless server.
 |
 |
 |
FTP Server Compatibility
Currently Windows servers running ASP are not able to backup databases. The servers you are backing up must be running PHP in order to support database backups. It is expected that ASP will be supported in a future release.
| Linux/Unix (PHP) | Windows (PHP) | Windows (ASP) | |
|---|---|---|---|
| Files | • | • | • |
| MySQL Database(s) | • | • | Future |
| SQL Server Database(s) | • | • | Future |
| PostgreSQL Database(s) | • | • | Future |
Pricing
| Personal License | Business License | |
|---|---|---|
| Backup | • | • |
| Restore | • | • |
| # of Sites | Unlimited | Unlimited |
| # of Users | 1* | Unlimited** |
| Site Transfer | • | |
| Amazon S3 | • | |
| CVS | • | |
| SVN | • | |
| GIT | • | |
| Price | $20 USD | $80 USD |
| Free Trial | Pre-order | ||
* A personal license is restricted to use by one (1) user on as many computers as he or she owns and is the primary user of.
** A business license may be used by any number of users on any number of computers that the registered company owns and uses.
