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