For the first part of this series, please read “Website Backup: Part 1: Planning”

With the continuous growth of data stored within web applications, there are now several free and paid backup options/types available in the maurket, that can be chosen based on requirements and affordability.

Methods to backup the files

Unless explicitly mentioned, the methods listed and explained below are generally used to backup all the required files except the database

RAID (Redundant Array of Inexpensive Disks) - This is one of the standard backup methods that is provided as a standard feature by most of standard webhosting companies. RAID is the method where the data in the main hard disk is mirrored or replicated into one or more hard disks. It generally provides protection only against hard disk failures where, when the main hard disk fails, the data is available in the other hard disks and can be easily recovered. However, it does not help in the case of accidental deletions and complete server crashes. Since the complete hard disk is mirrored, RAID also automatically backs up the database as well.

Backup server - Backup server is usually used in cases where the amount of data is huge. A backup server is nothing but a server dedicated only for taking backups. The backup server may or may not be in the same location of the main server. The backup server may also take backups from several servers (for various applications). Having and maintaining a backup server is expensive. A dedicated backup server is also not required when the amount of data being backed up is relatively less.

Offsite backup using FTP – This is a new service which is now being offered by most of the web hosting companies to its customers. The web hosting companies set up backup servers in locations far away from the location of the actual servers (off site). Backup of data is done via FTP from the main server to the backup server automatically at durations that are setup by the customer. When the customer purchases the Offsite backup via FTP option, the data transfer and sometimes the space used in the backup server is unlimited thus giving the customer a freedom of multiple backups and snapshots whenever necessary not worrying about space or data transfer. Since the server is in a remote location, the backup is not affected during times of natural disasters or accidents (ex. fire) when the main server and its data may be lost

Backup and send to E-mail – This method can be useful only when the amount of data is very small. This suits backup of small blogs and content management websites. Using freely available custom scripts, daily backups of website files can be sent as an email attachment. Here backups are stored in the Inbox and it is cheapest (free!) method of backup.

Backup via FTP / SCP – FTP is the standard method/protocol through which files are uploaded and downloaded from the webhost. Using free software like FileZilla, WinSCP and several such others, one can connect to the web server via FTP and download the required files for backup and store the files in a hard disk, CD, DVD or any storage medium. Even though this method of backup is primitive, it is very effective for small websites, especially static ones where a weekly backup of the files in this method serves the purpose.

Amazon S3 - Amazon S3 (owned by Amazon Web Services) is a cheap and effective pay as you go online storage solution. This solution can be effectively used as a backup medium for a web application. Using freely available scripts, the data that needs to be backed up can be copied regularly into the Amazon S3 storage. For restoration, the data can also be quickly restored. This is very good option if the amount of data that needs to be backed up is huge.

How to backup a MySQL Database?

Unlike website files backup, a database backup is different. MySQL the most widely used database for web applications and most other database platforms can be easily backed up by taking a physical dump of the database where the database structure and all the data stored in the database are converted to SQL queries and stored in a SQL file (text file with .sql extension). When the data needs to be restored, the SQL queries stored in the text file are run in the database thereby restoring the database.

The various methods available for backing up the database are.

MySQLdump – This is a command line utility which is available within the MySQL server. This tool as mentioned earlier, exports the database data along with the database structure as sql text files. Since the database is converted to a normal text file by MySQLdump, the text file can backed up using any of the methods that are used to backup required files. There are scripts widely available that export database into sql and stores it into specific folders. The stored files in turn are backed up using the backup method used to backup regular files

phpMyAdmin – This is similar to MySQLdump in a way. The difference is this is a web based menu driven utility where the database can be converted into sql file and downloaded and stored into hard drive/CD/DVD or any other storage media as required. The drawback in this method is that this method cannot be used if the database is huge i.e. contains a lot of data. There are other tools similar to phpMyAdmin which can be used for the same purpose, like sqlyog, sqlmanager etc.

Automatic MySQL backup and email script – Using freely available scripts, databases can be baked up as sql text files, compressed and emailed the file as an attachment. This method is very cheap (free!) however it can be used only when the size of the database is very small.

Backup by Copying Table Files – This is a physical backup method (requires shutdown of MySQL server) where a raw backup of the /var/lib/mysql (MySQL data directory) directory which contains .frm, .myd files done. These files are the files used by MySQL to store data internally, thus cleverly backing up these files is equivalent of backing up the MySQL databases.

However, problems may occur in some cases during database restoration. Say, the MySQL database server crashes and a new MySQL database server is installed and the backed up .myd and .frm files are restored. If the version of the MySQL server which crashed and the version of the MySQL server which has been re-installed do not match or other configurations do not match exactly, restoring the .myd and .frm files may not actually work thus creating data loss.

MySQL Replication Slaves – This method is expensive but highly effective when the database of the application is huge and has several transactions happening at any given time (high traffic). This method is similar to mirroring seen in RAID but the backup data is stored in another MySQL server. Here a replication slave MySQL server maintains a mirror copy of the main database. The mirror is updated real-time and up to the second data is saved in the replication slave

Since the replication is real-time, if required the slave server can be exported as a sql file and backed up which is backing up of the master database.

Types of Backup

The methods of storing backed up files are of different types. Each method stores files differently and each method has its own uses, advantages or disadvantages.

Full Backup - Full backup can be termed as normal backup. In full backup all the files are copied from the original location to the backup location. At the end of the backup a complete copy of the original location is available in the backup location. The disadvantage of this method is the space required by the backup increases exponentially equivalent to the size of the source, every time a backup is made. In practice a full backup is taken only for the first time a backup operation is done. Future backups are incremental backups

Incremental Backup - Incremental backup is used to back up files which are modified or changed after taking the last backup (the last backup may have been either a full backup or an incremental backup). This backup saves time and cost because each backup takes the space equivalent to the size of only the modified files and not all files.

Differential Backup - This is slightly different from incremental backup. Differential backup takes the back up of files which are modified or changed since last full backup (not last incremental backup).

Mirror Backup - A mirror backup is similar but slightly different from full backup. Files are generally compressed and backed up in full backup but mirror backup take backups without compressing. Also an incremental or differential backup of only modified backup is not possible after a mirror backup.

Backup Strategy along with backup schedule

Backups become outdated very quickly as the live data keeps changing. New data are added, removed or modified. An old backup which is several weeks old may be obsolete and may be of no use at all. It is absolutely necessary to formulate a backup strategy and schedule to ensure at the time of data loss, the most recent data is available in the backup thereby causing very minimal or absolutely no loss of data.

Owners of applications or implementation team or the person in charge must have a clear backup strategy. Strategy can be formed by taking into account the following factors.

• Priorities: The data based on its importance. Database and source files should be the top priority.
• Data retention policy: How long should an old backup be stored before being purged.
• Estimation of the size of the backup required. This has to be calculated before the type and medium for backup is decided.
• Planning Backup type. After how many incremental or differential backups would a full backup be executed etc

Also, the most important part of the backup strategy is the schedule. It is nothing but how often and when the backup will be executed and who will be executing the backup (if it’s not automated)

As a general rule:

• Important application files such as user uploaded files and databases must be backed up every day or night or both, but less important source files which don’t often change can be backed up every 2 days or a week.
• Apart from the regular backups in one storage media, on a weekly or bi-weekly basis, a secondary backup of the primary/regular backup must be taken at least for business critical data. This adds a second layer of protection in case the backup media / server fails
• Backups up to a minimum 3 versions old should be retained before purge. For example 1st, 2nd, and 3rd daily backups must remain till the end of 4th.

There are several software products, free and commercial widely available which automate the whole process of backing up of data. Everything from the type of backup to what should be backed up, when should be backed up and even purging schedule. It is advisable to have such a setup in place to ensure trouble free and smooth backup. No one ever knows when data loss can occur, so for data, like everything else in life “it’s always necessary to have a backup”.

Backup is the process of making copies of the original data, so that the copies can be restored after a data loss. Regular data backup is very important for data which are business critical, loss of which will affect the business and its operations directly or indirectly.

With the increase of usage of online web applications for business operations, backing of the web application data is as important as backing up any other business related data. A web application can be anything from a company’s online portal, community or a social networking website, private web applications like accounting, inventory applications etc or even a simple website.

How can a data loss occur in a web application?

1. Server crash – Server hardware or software crash such as hard disk crash or corruption, Operating system crash, memory or SMPS burnout etc. which may cause irrecoverable loss of data
2. Malware or Virus – The application may be infected with a malware or virus resulting data loss
3. Accidental deletion – Due to human error of the system administrator or developer, data may be accidentally deleted
4. Sabotage / Hacking – Hackers (cyber criminals) , business rivals who want to sabotage business operations may break into the system and delete the data
5. Webhosting companies – The web server host or ISP who owns the web server in which the web application is hosted, may go out of business without notice, making the online data permanently inaccessible and lost
6. Natural disasters – The webhosting company or ISP where the servers are located may be affected by natural disasters or calamities thus causing irrecoverable damage to the servers and data within

When such data loss occurs, a backup will come in as a life saver and the data can be restored easily quickly and business operations can resume without any disruptions, saving time and money.

What needs to be backed up?

What needs to be backed up entirely depends on the type of web application. Backing up unwanted data is going to add up to wasted space. Failing to backup important data/files affects the restoration process after a data loss, resulting in partial or non-working restoration. It is very important to backup the necessary data properly.

For simple static website, the backup will may contain just the html pages that contain all the information displayed in the website. But nowadays most of the web applications are way more complex than a simple static website. It is very difficult to list out what needs to be backed up in a web application without a clear understanding of how the system is built and how it operates. However for ALL web applications in general, the following need to be backed up.

1. Source Code and related files: This is nothing but the programming code which makes the web application to work. The source code and other relates files that need to be backed up are
   1. Source code and scripting files ( ex .php, .jsp or .asp files, depending on the technology and platform of the application) and also JavaScript files (if used)
   2. HTML, CSS files
   3. Image files (.jpg, .png, .gif etc)
2. Database: The database is where the web application stores all the data generated or entered and is the heart of the application. For example in an ecommerce application the database stores customer information, product information and order information. In an accounting application the database stores all information about transactions, sales etc. Regularly backing up the ever-changing database is very important as it contains the most important business critical data.
3. User uploaded files: Files that are uploaded by the user or created by the system like photos, documents, pdf reports and other similar files which are stored in the server.

Apart from the above list, there may be several other files like configuration and setting files that needs to be backed and may be essential during a data restore. It is very important to come up with the list of data items to be backed up after consulting with the development team / implementation team and also the web hosting / ISP.

Where to backup?

Where to backup? This is as important as what to backup? The backed up data must be easily and quickly retrievable when it is required for a data restore. If the backup itself is lost or corrupted, or it is not accessible or un available when required for a restore, then the situation is as bad as not doing a backup at all.

It is also very important that the backup needs to be stored in a location away from the location of the main data, such that the backup location and the backup data is not be affected by the same reason affecting the main location and it’s data. For example if the backup location and the original data location are one and the same, there are chances both can be destroyed together due to a fire in the premises.

For continuation of this particle, please read “Website Backup: Part 2: Available methods”

Asynchronous JavaScript and XML (AJAX) which is the most spoken about technology on the web today is actually not a technology in itself but a term which describes a new approach which looks into using a number of existing technologies like XHTML, CSS, Java Script, DOM, XML and the XMLHttpRequest object to develop quick website user interfaces which not only avoids reload of entire browser page but also offer lots of other responsive features.

The core component of Ajax is XMLHttpRequest that enables execution of server side code without any page refresh. Ajax can send asynchronous requests to the server using JavaScript and XMLHttpRequest object and mapping functions that will be executed when response is received.

The beauty of Ajax is that, you can execute server side code with out any page refresh. Ajax is a world of “No Page Refresh” and rich user interface like windows applications. In traditional web applications, the user actions in the user interface invoke an HTTP request to the web server. Then the server will do lot of process on the server and then returns an HTML page to the client. In Ajax applications, the request is not for GUI or HTML, It is only for data. After fetching the data, you can create the user interface from the client using JavaScript and DOM. Ajax is a client-side technology and can interact with any server side technologies such as PHP, ColdFusion, ASP.net, JSP, and others.

Advantages of Ajax

Rich User Interface
Ajax allows us to create highly interactive user interface. A user don’t like page refresh continuously like typical webpages but they act more like desktop applications thus increasing the usability and interactivity.

Higher Performance
With reduction of page refresh comes reduction of loading times and faster response to actions. There’s no requirement of post back to HTML thus creating a refresh and reload of the whole page.

Who is using Ajax?
Huge web corporations like Yahoo, Google and MSN are making huge investments into develping new websites and converting their existing services to Ajax. The latest version of Google Groups, Google Live Search, Google Maps, Gmal, Flickr, Amazon’s A9, Live Mail, Yahoo mail all are Ajaxified and use Ajax extensively.

Ajax and Kliotech
We at kliotech have been using Ajax in our web development projects ever since the evolution of Ajax. Ajax is used extensively at several situations to avoid un-necessary page refresh, Simplify functionality and where a fast responsive interface is required.

Web 2.0 generally refers to a second generation of services available on the World Wide Web that let people collaborate, and share information online. Unlike the first generation, Web 2.0 gives users an experience closer to desktop applications than the traditional static Web pages. The term web2.0 was popularized by O’Reilly Media and MediaLive International as the name for a series of web development conferences that started in October 2004. Web 2.0 applications often use a combination of techniques devised in the late 1990s, including public web service APIs (dating from 1998), Ajax (1998), and web syndication (1997). They often allow for mass publishing (web-based social software), the term may include blogs and wikis. To some extent Web 2.0 is a buzzword, incorporating whatever is newly popular on the Web (such as tags and podcasts), and its meaning is still in flux.

With its allusion to the version numbers that commonly designate software upgrades, Web 2.0 was a trendy way to indicate an improved form of the World Wide Web, and the term has been in occasional use for several years. For examples — “DoubleClick was Web 1.0; Google AdSense is Web 2.0. Ofoto is Web 1.0; Flickr is Web 2.0″ — rather than definitions.

What is now termed “Web 1.0″ often consisted of static HTML pages that were updated rarely, if at all. They depended solely on HTML, which a new Internet user could learn fairly easily. The success of the dot-com era depended on a more dynamic Web where content management systems served dynamic HTML web pages created on the fly from a content database that could more easily be changed.

Proponents of the Web 2.0 approach believe that Web usage is increasingly oriented toward interaction and rudimentary social networks, which can serve content that exploits network effects with or without creating a visual, interactive web page. In one view, Web 2.0 sites act more as points of presence, or user-dependent web portals, than as traditional websites. They have become so advanced new internet users cannot create these websites; they are only users of web services, done by specialist professional experts.

Overview of Web 2.0 techniques

A website could be said to be built using Web 2.0 technologies if it features a number of the following techniques:

Technical

• Unobtrusive Rich Internet Application techniques (such as Ajax)
• CSS
• Semantically valid XHTML markup and/or the use of Microformats
• Advanced User Interface languages such as XUL and SVG
• Flash Remoting
• Syndication of data in RSS/Atom
• Aggregation of RSS/Atom data
• Clean and meaningful URLs
• Weblog publishing
• REST or XML Webservice APIs

General

• The site should not act as a “walled garden” - it should be easy to get data in and out of the system.
• Users usually own their data on the site and can modify at their convenience
• Mainly web-based - most successful Web 2.0 applications can be used almost entirely through a web browser
• Data returns should be dynamic, not static, changing depending on variables associated with the user’s query (e.g. keywords, location).