Today’s mobile-focused and cloud-based business apps are impacting the IT department’s efforts to create sound Disaster Recovery (DR) practices. Learn how to provide access to cloud-based apps to more people in more locations via more devices, while managing a robust DR framework. In Part one of this blog we look at mobile phones and their place in DR.
The massive uptake of smart mobile devices and social media platforms has changed the way that people live and work, while introducing new levels of complexity around managing and securing corporate data and systems.
Mobile consumption and usage has never been higher in Australia. Like all contingency planning, the secret to managing mobile devices, third party apps and other security risks is to research well, then set down and stick to strong policies.
An Identity Services Engine (ISE) can help identify the size of the problem. It’s a tool that stands guard at all the digital entry points into your organisation, automating the process of scanning a request and enforcing the rules about letting it in. An ISE can give you at-a-glance visibility over devices, data and users who try to connect with your systems and spot potential threats much faster than you can.
Any disaster recovery plan that includes mobile phone support must restore:
- Text messaging capabilities
- Email to text and text to email linking mechanisms
- Email access is high on the priority list, and should be subject to short recovery time objectives (RTOs)
- Web browsing and internet access is now critical
In the wake of a catastrophic failure or outright disaster, the following requirements will come into play:
- Restoring email servers, so that mobile phone users can regain access to email stores, and the ability to send and receive messages;
- Restoring directory services and CRM applications for vital contact information, including customer history, order information and notes;
- Restoring sufficient internal network infrastructure to provide mobile users with access to email, Web services, and other mobile-based applications and services.
During disaster recovery exercises, you should carefully monitor and actively test mobile phone use to help identify where roadblocks are for users. Any bottlenecks or problems specific to mobile phone use and access should inform your updated DR plans to ensure the right servers, services and infrastructure elements are restored during the recovery period immediately after a disaster.
Are you also including mobile phone data backups as part of your existing backup plans? While they’re now considered critical business tools, mobile phones themselves are rarely included in data safety nets.
This doesn’t mean restoring any and all mobile phones, but recognising that restoring mobiles for key recover members should be made high priority.
You may also enjoy Lessons from a Cyclone: how fixed wireless networks can save your business in a natural disaster and Disaster Recovery in the cloud: which model best supports digital transformation?