 | 
04-22-2010, 09:16 AM
| | Junior Member | | Join Date: Apr 2010 Location: U.K
Posts: 10
| | 5 Tips on Preparing for Disaster Recovery Hi
1. Recognize that your business can suffer a natural disaster. Small businesses the world over have been affected by disasters such as hurricanes, tornadoes, floods, earthquakes, tsunamis, volcanic eruptions and fire.
2. Develop your recovery plan before disaster strikes. Make sure everyone in your company is familiar with the plan and knows what steps to take in emergencies.
3. Have adequate insurance. You’ll need coverage not only for property damage and loss (including inventory), but also for business interruption.
4. Draw up a list of telephone numbers for all employees. Assign certain employees to call others if disaster strikes. That way, you can learn who is all right and who needs help, and you can quickly communicate instructions about your business.
5. Don’t forget your computer system. Keep backup programs and duplicate records (accounts receivable, client information, and the like) at a different, safe site.
Thanks |  Sponsored Ads | | Member | | Join Date: LongTime Location: Here Posts: 1100 | | New Sponsored Ads This message will go away once you are registered. Also, by registering, you will have access to all post topics, communicate privately with other members (PM), respond to polls, upload graphics, and access other special features! Registration is fast, simple and absolutely free so please Click Here to join our Web Hosting community today! | 
04-30-2010, 05:59 AM
| | Junior Member | | Join Date: Apr 2010 Location: U.K
Posts: 11
| | Hello
Thanks for sharing this nice information.
This is very interesting post.
Please keep sharing more and more information.
Thanks | 
06-22-2010, 05:03 AM
| | Senior Member | | Join Date: Jun 2010 Location: u.k
Posts: 285
| | Hello
Essentially, the key to Disaster Recovery success is having a realistic and well understood set of objectives that are based on the business needs. This involves planning and preparation, from the business impact analysis, to understanding and quantifying risks, to classifying and prioritising applications and data for recover ability.
Additionally, there is the need for preparing systems to be able to recover, and then documenting everything, especially the Disaster Recovery plan. Another factor for success is to make Disaster Recovery less than an exception by integrating Disaster Recovery hardware components into production. The dynamic nature of IT requires continuous review and updates of the process and the plan. It must be part of the day-to-day operations. | 
07-07-2010, 10:21 AM
| | Junior Member | | Join Date: Jun 2010
Posts: 20
| | Hi
1. Store your system passwords in at least two separate secure locations. only one of which is in the same building as your IT equipment. At least two staff have should have access to them.
2. Document, document, document! Make sure that the whole recovery process to get you up and running again is documented, and includes the locations of system recovery and other critical discs. Make sure that key key staff are familiar with with these.
3. Establish an automated system to notify critical staff of disaster by text. These staff should be thoroughly trained so that they can perform basic disaster recovery/back-up tasks unsupervised. You may be able to do this through an arrangement with a third-party service provider.
4. Practice your disaster recovery plan on a quarterly basis or more. This not only hones your disaster recovery team's skills but it will also familiarize new staff with the procedure, and ensures that your disaster recovery strategy is kept up to date by revealing any issues with new equipment or software.
Thanks | 
07-16-2010, 12:18 PM
| | Junior Member | | Join Date: Jul 2010 Location: uk
Posts: 21
| | Additionally, there is the need for preparing systems to be able to recover, and then documenting everything, especially the Disaster Recovery plan. Another factor for success is to make Disaster Recovery less than an exception by integrating Disaster Recovery hardware components into production. The dynamic nature of IT requires continuous review and updates of the process and the plan. It must be part of the day-to-day operations.
1. Business and IT need to be linked
Creating a Disaster Recovery plan is a compromise and while people are aware of best practices, they face issues related to cost. When best practices are pitted against cost, cost needs to be the second and not first priority.
3. Keep the Disaster Recovery Plan current
Disaster Recovery planning needs to be part of the day-to-day operations of the IT environment and even though it is an exception, it should always be at the forefront of people’s minds.
4. Test the Disaster Recovery Plan
The Disaster Recovery plan needs to be tested regularly to ensure the business can recover the operation successfully and in a timely fashion. Disaster Recovery testing is a major challenge for most IT departments, but if recovery has not been tested all the way to the application level, it is very likely that problems will occur. | 
08-03-2010, 10:15 AM
| | Junior Member | | Join Date: Jul 2010 Location: uk
Posts: 12
| | One of the most talked about but least implemented initiatives concerning IT infrastructure is the design and execution of a Disaster Recovery (DR) plan. This is particularly relevant as hurricane season gets underway in the Atlantic.
Whether man-made or natural, disasters of all shapes and sizes represent costly disruptions to business practices. Fortunately, their long-term effects can be diminished with a DR plan.
An especially crucial business tool in today’s increasingly electronic world, a DR plan enables a company to effectively coordinate people and resources to mitigate downtime or any other interruption to services and operations in the event of a disaster. | 
08-09-2010, 05:25 PM
| | Junior Member | | Join Date: Aug 2010
Posts: 14
| | Hi
Ten Tips for Disaster Recovery Planning
1. Devise a disaster recovery plan: IT disaster recovery planning can be a daunting undertaking, with many scenarios to analyze and options to pursue. It is important to start with the basics and add to the plan over time. To begin, define what is important to keep the business running - i.e., email and application access, database back-up, computer equipment - and the "recovery time objective" or how quickly the company needs to be up and running post-disaster. Other key plan components to consider are determining who within the organization declares the disaster, how employees are informed that a disaster has occurred, and the method of communication with customers to reassure them that the company can still service their needs.
2. Monitor implementation: Once a disaster recovery plan has been established, it is critical to monitor the plan to ensure its components are implemented effectively. A disaster recovery plan should be viewed as a living, breathing document that can and should be updated frequently, as needed. Additionally, proactive ongoing monitoring and remediation of processes, such as back-up data storage and data replication, results in fewer IT issues and less downtime should a crisis occur.
3. Test disaster recovery plan: A 2007 eWeek survey of more than 500 senior IT professionals revealed that a whopping 89% of companies test their disaster recovery/failover systems only once per year or not at all, leaving their enterprises vulnerable to massive technology and business failures in the event of a disaster. An under-tested plan can often be more of a hindrance than having no plan at all. The ability of the disaster recovery plan to be effective in emergency situations can only be assessed if rigorous testing is carried out one or more times per year in realistic conditions by simulating circumstances that would be applicable in an actual emergency. The testing phase of the plan must contain important verification activities to enable the plan to stand up to most disruptive events.
4. Perform off-site data back-up and storage: Any catastrophe that threatens to shutter a business is likely to make access to on-site data back-up impossible. The primary concerns for data back-up are security during and accessibility following a crisis. There is no benefit to creating a back-up file of valuable data if this information is not transferred via a secure method and stored in an offsite data storage center with foolproof protection. As part of establishing a back-up data solution, every company needs to determine its "recovery point objective" (RPO) - the time between the last available back-up and when a disruption could potentially occur. The RPO is based on tolerance for loss of data or reentering of data. Every company should back-up its data at least once daily, typically ove
Thanks | 
08-23-2010, 11:36 AM
| | Junior Member | | Join Date: Aug 2010 Location: U.k
Posts: 20
| | Hi
1. Business and IT need to be linked
Creating a Disaster Recovery plan is a compromise and while people are aware of best practices, they face issues related to cost. When best practices are pitted against cost, cost needs to be the second and not first priority. Even more important, though, is that capabilities needs to be matched to expectations. Responding to a disaster is an exception, but preparing for it should not be a burden but integrated with day-to-day priorities.
2. There needs to be a Disaster Recovery plan
The Disaster Recovery plan needs to represent all functional areas within IT prior to, during, and after a disaster. It needs to include applications, networks, servers & storage.
Contingencies, such as “what-if” scenarios should be considered as part of planning process. Decisions need to be made regarding levels of disruption that will constitute a disaster, downtime and loss tolerances.
3. Keep the Disaster Recovery Plan current
Disaster Recovery planning needs to be part of the day-to-day operations of the IT environment and even though it is an exception, it should always be at the forefront of people’s minds. Once the Disaster Recovery plan is created, it needs to be maintained and updated every time an element within the IT environment changes. The dynamic nature of IT environment ensures that the Disaster Recovery plan will fail if the management of the plan is not part of change management.
Thanks | 
09-01-2010, 10:39 AM
| | Junior Member | | Join Date: Aug 2010 Location: U.K
Posts: 19
| | Hi
Devise a disaster recovery plan – To begin, define what is important to keep the business running and the “recovery time objective” or how quickly the company needs to be up and running post-disaster. Other key plan components to consider are who within the organization declares the disaster, how employees are informed that a disaster has occurred, and what method of communication to use with customers to reassure them that the company can still service their needs.
Monitor implementation – Once a disaster recovery plan has been established, it is critical to monitor the plan to ensure its components are implemented effectively. A disaster recovery plan should be viewed as a living, breathing document that can and should be updated frequently.
Test disaster recovery plan – A 2007 eWeek survey of more than 500 senior IT professionals revealed that a whopping 89% of companies test their disaster recovery/failover systems only once per year or not at all, leaving their enterprises vulnerable to massive technology and business failures in the event of a disaster. The effectiveness of the disaster recovery plan can only be assessed if rigorous testing is carried out one or more times per year in simulated realistic conditions.
Thanks | 
09-02-2010, 05:09 AM
| | Junior Member | | Join Date: Sep 2010 Location: uk
Posts: 14
| | hello
Recognize that your business can suffer a natural disaster. Small businesses the world over have been affected by disasters such as hurricanes, tornadoes, floods, earthquakes, tsunamis, volcanic eruptions and fire.
Develop your recovery plan before disaster strikes. Make sure everyone in your company is familiar with the plan and knows what steps to take in emergencies.
Have adequate insurance. You’ll need coverage not only for property damage and loss (including inventory), but also for business interruption.
Draw up a list of telephone numbers for all employees. Assign certain employees to call others if disaster strikes. That way, you can learn who is all right and who needs help, and you can quickly communicate instructions about your business.
Don’t forget your computer system. Keep backup programs and duplicate records (accounts receivable, client information, and the like) at a different, safe site.
Thanks |  Sponsored Ads | | Member | | Join Date: LongTime Location: Here Posts: 1100 | | New Sponsored Ads This message will go away once you are registered. Also, by registering, you will have access to all post topics, communicate privately with other members (PM), respond to polls, upload graphics, and access other special features! Registration is fast, simple and absolutely free so please Click Here to join our Web Hosting community today! | | Thread Tools | | | | Display Modes | Linear Mode |
Posting Rules
| You may not post new threads You may not post replies You may not post attachments You may not edit your posts HTML code is Off | | | All times are GMT. The time now is 11:17 AM. |  | |