Please complete all required fields!
Conclusion: The disaster recovery plan (DRP) should be seen as significantly more than a technical document for IT resources to be accessed only in times of crisis restoration. Use regular IT DRP updates and testing as a valuable marketing tool and keep the DRP ready for when disaster strikes.
A recently released survey revealed nearly one-quarter of all respondents cited lack of budget as a major challenge for BCP/DRP funding. This challenge will be even more daunting after the anticipated post-coronavirus budget cuts, so it is critical to remember the DRP is not just required to be technically savvy; it contains useful information to suit the non-technical audience when attaching the DRP to support funding to keep it current.
Read more ...
Conclusion: Australian organisations must have strong disaster recovery plans, be it for natural disasters or man-made disasters. The plans need to deal with the protection and recovery of facilities, IT systems and equipment. It is also critical that the plan deals with the human side of the impact of a disaster on the workforce. What planning needs to be done, what testing will be done, what will happen during a disaster and what needs to be done after a disaster?
This planning can be complex and confronting. Whilst testing the failover of IT systems can be relatively straightforward, testing the effectiveness of the workforce side of a plan will be difficult, and may even disturb employees who may prefer to think “surely it will never happen to us”.
"ICT disaster recovery plan challenges" IBRS, 2019-08-03 20:43:12
"What are the important elements of a Disaster Recovery Plan?" IBRS, 2016-08-30 01:17:08
Conclusion: when considering Cloud based email (Microsoft or Google) organisations should critically re-evaluate the need for third party Email Archive add-ons. Since Cloud-based email has virtually unlimited mailbox capacity the archive/storage management features of third party Email Archive add-ons many not be needed.
For many organisations the native compliance and eDiscovery features in Cloud based email are satisfactory and will rapidly mature and improve over time. Organisations that are very large, highly regulated, or at risk of litigation should evaluate the benefit of the more comprehensive, and more polished, third party Email Archive add-ons, whether that be Cloud or On-premises.
Conclusion: While many IT organisations believe that using public IaaS (e.g. AWS, Microsoft Azure, Google) to host business applications is a cost-effective strategy, they still require to manage the hosted environment themselves or select an external service provider to manage it for them. Towards this, it is critical to understand the current service management maturity level prior to choosing an in-house or outsourced solution. This note provides a self-assessment service management maturity model to create a solid foundation for selecting sourcing options. IBRS recommend that IT organisations with maturity level 3 or higher retain the service management function in-house, whereas, IT organisations below maturity level 3 should outsource the service management function.
Conclusion: 80% of traditional outsourcing contracts established in Australia during the last 25 years were renewed with the same service provider. However, with the emergence of public Cloud, IT organisations should examine the feasibility and cost-effectiveness of migrating to public Cloud prior to renewing the existing outsourcing contracts.
Conclusion: Disaster recovery continues to be an issue for many clients. Approaches based on tape have a low cost benefit but often recovery takes too long to meet the business’ requirements. The popular new approach of replicating data to a secondary data centre enables rapid recovery but at a cost which is prohibitive for some applications or smaller organisations.
An emerging third approach is to use Cloud infrastructure (IaaS) as a warm standby. This is attractive both in terms of cost and recovery time and can also be used as a strategic stepping stone for adopting IaaS.
Conclusion: With most organisations now completely dependent on IT systems for their day-to-day operations, and ongoing viability, ensuring the availability and recoverability of these systems is one of the IT organisation’s most important responsibilities. However, like many other forms of insurance, disaster recovery planning is not seen to be urgent by IT or the business, and often fails to meet the requirements of the business.
IT executives need to look for the early warning signs that their disaster recovery plan is compromised, and if found, take action to defuse this ticking time-bomb that could blow up their career.
Conclusion: Most branch office data is poorly protected by the organisation’s existing backup strategy. Recent improvements in network connectivity, and the commoditisation of advanced deduplication techniques, fundamentally change the landscape and make highly automated, reliable and cost effective branch office affordable to most organisations.
Organisations with extensive branch office data that is not adequately protected should revaluate their branch office backup strategy.
Conclusion: Organisations with existing Business Continuity Plans (BCPs) may find them to be a poor fit when dealing with the unique circumstances surrounding a pandemic. The chief characteristic is massively depleted numbers of available workers, with as many as 25-40% of staff absent throughout the entire government and business eco-system. Those without effective plans face the prospect of severe disablement that may take many months of recovery. For them, urgent action is required to draft pandemic-specific BCPs or to modify, then test, existing BCPs.
Conclusion: Consistent with its belief that the global financial crisis has heralded a new era in IT, IBRS has identified a series of management maxims to serve as a source of reference for IT executives navigating economic uncertainty.
Conclusion:In our November 2008 survey1we found many organisations are using archiving to manage their rapidly growing unstructured data. On further in-depth research we found that these archiving projects are mostly IT driven, focused on silos of data, and are largely limited to automating storage tiering (HSM) to control storage costs. While this is a sensible starting point, IT organisations could extract more value from archiving by offering enterprise search and eDiscovery to the data owners.
Conclusion: Many organisations do not distinguish between backup and archive and assume their backup data is also their archival data. This makes the backup environment overly complex and difficult to operate and creates a very poor archival platform.
Organisations that separate these processes find that backups shrink significantly, resulting in much smaller backup windows and much faster recovery times. This also enables the archival data to be optimised to meet desired business requirements. That is, cost, retrieval time, compliance, discovery and so on.
Conclusion: In recessionary economies, as in war, values and behaviours change in response to the times. Formerly valued business success factors may no longer apply; management thinking once considered outmoded may now have new relevance. At an organisational level, focus is likely to be on the lower strata of Maslow’s hierarchy of needs1. Indeed, C-level executives will be appraised on their ability to contribute to meeting these needs.
Conclusion: Economic downturns alter organisational dynamics and can herald changes in the executive power hierarchy. IT can be particularly vulnerable if seen as a cost centre and order taker. As economic forecasts darken, a common scenario is for the balance of power to swing to the CFO. Then, an economic austerity agenda is usually pursued, characterised by a program of across-the-board cost cuts that have Chief Executive imprimatur.
Conclusion: The International Standards Organisation has just released a new International Standard that focuses on Disaster Planning for IT1. This new standard reflects the changed/outsourced IT world. It provides guidelines for information technology disaster recovery services as part of business continuity management that apply to both “in-house” and “outsourced” ICT environments. This new approach for Disaster Recovery (DR) Standards should stimulate organisations to re-examine their IT DR plans to ensure that they meet current best practice and that the processes they are using to maintain their DR planning are satisfactory.
Conclusions: While there is now an increasing emphasis on Business Continuity Management (BCM), many organisations still focus on disaster recovery planning. Unwisely they restrict their focus to restoring IT infrastructure, giving only a “cursory nod” towards a more holistic business orientation that focuses on all critical business operations. Some create an artificial air of confidence by developing their business continuity plans and then not proving them. Others have little appreciation of the quality of their Business Continuity Plans (BCP) and whether or not they meet good practice. In all these cases there can be no assurance that the BCPs will be of any practical use if and when they are needed. The outcome will be, at least, serious and could be catastrophic.
Login to read your premium content.