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