| Website maintenance is often written only on paper | | | | includes dealing with issues of life safety, emergency |
| and never implemented. The result is a gamble where | | | | policies and server rules and website functioning |
| there is every chance of your website being | | | | guidelines. |
| damaged and inaccessible. | | | | Resumption: This stage refers to the actual stage of |
| Causes | | | | planning and implementing the website recovery plan. |
| Server Problems: Sometimes, websites run into | | | | The recovery plan should be time-sensitive, |
| problems when the host network server is running | | | | cost-effective and enable a user or business to |
| redundant sites and backups. Apart from analysing | | | | resume normal business activity. |
| personal location risks, a user has to consider certain | | | | Recovery: The phase of recovery can be described |
| factors about servers: | | | | as the timeline of expanded operations after a |
| · Does your host server have redundancy | | | | website loss. The phase helps a user to deal with |
| backups? | | | | time-sensitive business operations after resumption. |
| · How often does the host server perform | | | | Restoration: This can be classified as the final stage in |
| backups? | | | | website recovery planning. It involves pre-planning the |
| · Can the host server handle 'denial of service | | | | repair or relocation of the primary site and its |
| attacks'? | | | | contents. It also ensures that the repaired website is |
| · Does the host server provide a program of | | | | functional including latest tools and processes to |
| virus scans and firewall protection systems checking | | | | detect sluggish speed. |
| all data and website material released to your | | | | The Recovery Plan: Every website is made up of |
| network? | | | | three parts: |
| Physical Problems: Sometimes, a user gets | | | | · What you need in order for users to view the |
| disconnected from the web because the contact | | | | website |
| service provider was running an illegal operation. It | | | | · The tools you need to maintain the website |
| could also be that the network connections got | | | | · The things you need for new development on |
| faulty due to sudden power surges of lightning. This | | | | your website |
| could affect your system and make your website | | | | Thus, a user has to first consider the things that are |
| inaccessible. | | | | available which relate to and deal with the live |
| Natural Disasters: A user also runs the risk of losing | | | | operation of the website. This includes all hardware, |
| website access due to natural disasters of | | | | operating system, network connectivity and all files |
| earthquakes and floods. These natural disasters could | | | | and scripts that make up the website. A user has to |
| occur at the service provider location or host location. | | | | have hosting package i.e. regular backups. This |
| Either way, website access is lost. Sometimes, limited | | | | ensures that the website does not use or run on |
| and minimal LAN connectivity also restricts the user in | | | | redundant mechanisms. It is recommended not to |
| opening up personal website. | | | | depend solely on the host service provider. Develop |
| Human Error: Usually human error is accidental in | | | | personal service contents installing regular backups |
| nature. Maybe the user forgot to renew the domain | | | | and updates. |
| name. It could also happen that the user accidentally | | | | Next in line is content management or analysing all |
| input the wrong date and time. Usually, this happens | | | | the web tools and mechanisms that are available. A |
| for online business that input 2003 instead of 2007 or | | | | user has to update them regularly. Sometimes, |
| 01/07 instead of 07/08. | | | | updates including virus scans may take a long time. |
| How to Plan for Website Loss | | | | But, a user needs to install for website protection. |
| Risk Assessment: In order to plan for any eventuality | | | | The last step involves analysing the tools a user will |
| of website loss, every user -- whether a business or | | | | need for future development and maintenance of |
| a home user -- has to conduct an analysis of risks | | | | website. This includes documenting digitally and in |
| and vulnerabilities. This includes documenting financial, | | | | paper format, all the tools of your browser, host |
| server and human error risks and prioritising them. | | | | provider and business guidelines. A user also needs to |
| Prevention: This usually includes activities which | | | | develop and store a web log in a data storage |
| minimise the possibility of an emergency occurring in | | | | device. This device documents in detail the exact |
| your organization. The main aim of prevention is to | | | | procedure followed when opening the website initially. |
| protect user assets minimising risk and loss. | | | | This helps the user to retrieve the website and make |
| Response: Response deals with reacting to loss and | | | | necessary changes for the future. |
| disaster situations in a practical and safe manner. It | | | | |