6 Disaster Recovery Tips for Arizona Law FirmsBeits Livneh
According the FEMA, 40% of businesses are affected following a serious storm, earthquake, flood, or hurricane. As a law firm, experiencing downtime due to a server crash, power outage or the like, and causing the inability to work, that would mean significant lost to revenue.
When evaluating the need for a disaster recovery planning, law firms must address their backup and continuity needs based both on compliance and regulation issues as well as potential lost revenue. Typically for law firms, the cost of downtime is based on:
- Cost of continuing without the data
- Cost of recreating the data
- Cost of notifying users in the event of a compromise
- Loss of reputation
- Fees incurred due to compliance breach
The potential for lost is a big reason why preparing for the worst and making proactive decision before disaster strikes will increase the chances that the worst disaster will have a minimal impact on your firm’s ability to continue operating.
Use the below checklist to both plan and prepare for a disaster:
- Assess the problem and its impact on your firm
Every disaster is different. Before doing anything, understand the underlying issue and how it will impact your client.
- Is the issue local to one machine, or does it affect your entire system?
- Have files been deleted or are servers /workstations down?
- Establish recovery goals
Recovery is what makes a BDR solution different from a simple backup product. Be sure to plan out your law firm’s road to recovery.
- Restore the system, the data, or both? Should time be spent recovering files and folders before system recovery?
- Identify critical systems and prioritize recovery tasks.
- What date/time should you recover from?
- Select the appropriate recovery type(s)
To get to your “road to recovery”, the appropriate recovery procedure must be followed. Think about which approach will best get you to your end goal.
- File restore
- Local virtualization
- Off-site virtualization
- Business Continuity Devices/Services
- Verify the recovery and confirm functionality with users
Once a recovery is verified, confirm that it interacts positively with users.
- Test network connectivity.
- Ensure all users can access resources and applications in the virtual environment.
- Restore the original system(s), if needed
If the original system(s) needs to be restored, decide which restoration process will work best.
- Bare metal restore.
- Virtual machine restores.
- Self-assess afterwards
After it’s all said and done, take a step back and think about it: How well did your team do? What could you have done differently?
- What precipitated the failure?
- What ongoing issues need to be addressed?
- What can be done better in future DR scenarios?