TECHNOLOGY DATABASE BACKUP AND DISASTER RECOVERY

Posted by Winnie Melda on January 22nd, 2019

Introduction

        Disaster recovery and database backup maintenance are two vital aspects of planning for a backup recovery and integration implementation. AX system of Microsoft Dynamics just like any other software requires continuous maintenance and monitoring. The routine maintenance activities include the following: application file recovery and backup, Database recovery and backup. It also involves monitoring of alerts for any event that is from the infrastructure components, the database, or the Microsoft Dynamics components. Finally is also involves monitoring applications and infrastructure so as to ensure the meeting of the required service-level agreements.

a.)    Database Backup

        Backups are copies of the organizational database that are useful for recovering and storing data after the failure of a system. Through the use of proper backup, it is possible for the business to recover and ensure the continuity of its business after an unexpected failure. These failures can be in the form of natural disasters, failures of hardware, user errors and media failures. Database backups are vital for routine purposes (Maheshwari, & Jain, 2012).

        Backups are essential in ensuring that a business recovers its database in the case of their damage or any other unexpected event. Database backup is vital for any routine work such as setting up mirroring of a database, copying databases from a server to another and for the archival purposes for governmental use (Maheshwari, & Jain, 2012).

           Backing up and storing data has to be tailored to suit a specific environment and should ensure that the resources of an organization are available when needed. A backup and recovery strategy has to be well designed to maximize the availability of data and to minimize any loss of data. The strategy also has to take into consideration the requirements of a specific business. The backup component of this strategy examines the frequency and types of backup, speed, and nature of hardware that they require and how to test the effectiveness of the backup (Maheshwari, & Jain, 2012).

        The component of the backup aspect of the strategy also looks at the storage of backup media including its security aspect. The same strategy also has the recovery component. This component defines the restoring of databases and ensures that the businesses goals to attain database availability. This component also looks at ways of minimizing loss and who are the responsible individuals for recovering the database. Thus, every organization has to document its procedures for backup and recovery and maintain a copy of this documentation as part of its operations manual (Mishra, & Dubey, 2013).

        Careful planning is critical when designing an effective recovery and strategic backup plan. It also calls for careful testing and implementation. In such a case, there is need to consider a range of factors such as; the organization’s production goals for the databases mainly in protecting data from loss and ensuring the availability of all requirements. There is also need to consider the resources constraints such as personnel, hardware, storing space for backup media, and physical security of the stored media. Lastly, it is also crucial to consider the databases nature. Such as which are the most critical database production periods? Are there tables that frequently get modified more than others? What are the usage patterns of these databases? And what are the changes made on each of the databases? It is also crucial to note how the database has heavy use that lead to frequent updates and inserts (Mishra, & Dubey, 2013). It Will prompt the IT personnel to schedule log backups and differentials during the periods or invest in the heaviest use. The expert will also have to schedule for full backups at the off-peak period (Khurana, & Gupta, 2012).

b.)    Describe Disaster Planning

            To ensure quick restoration of all the business data and systems to return to normal operation after a failure, it is crucial to forming a plan for disaster recovery. By establishing a plan, it is vital to consider various ranges of scenarios that may occur (Khurana, & Gupta, 2012). These scenarios are disasters that may happen such as technical disasters, fire, natural disaster, and failure of two-disk within the RAID-5 array. Having a well-developed disaster plan will enable a business owner to prepare and identify all the vital steps necessary to respond to a given type of a disaster. It is also crucial to test the entire step for every scenario to determine the effectiveness of the disaster plan. According to Microsoft’s recommendations, it is crucial to verify the plan for disaster recovery through the use of simulation for every catastrophic event (Karnowski, 2010).

         The simulations help planners to consider all the elements in the planning for disaster recovery within the context of a business or environmental needs (Karnowski, 2010). For example, fire can occur and sweeps away the entire data center that operates all day and night. There is a need for planners to ask if it is possible for them to recover the entire database after this event and how long it will take them to ensure the availability of the system. In considering the period of recovery, it is crucial for planners to ask how long their customers can tolerate them (Mishra, & Dubey, 2013). Therefore, planners have to work within the shortest time possible in ensuring the system is up and running before making excessive losses or losing clients for good (Karnowski, 2010).

               The disaster recovery plan should therefore, include aspects of the period it takes to recover and the system’s final condition. For example, one can specify the hardware acquisition, that the system will recover after 48 hours and the database originality is guaranteed (Das, Mahapatra, & Pradhan, 2013). It is possible to structure a disaster recovery plan in many ways and can also have a wide range of information. The various types of recovery plans include a communication plan; acquisition of hardware plan, the list of contacts of individuals who will be responsible for the disaster, administration ownership information of the plan and checklists for all the tasks that need to during the recovery scenario (Das, Mahapatra, & Pradhan, 2013).

c. Importance of Integration

              It is crucial to integrate reductionism-holism, data backup and disaster planning and SDLC Models to optimize information systems and Enterprise function. It is of great importance for these technologies of information systems so as to meet the demands of the organization. Data integration plays a crucial role in ensuring the technology dependent businesses continue to flourish even after a major disaster. The integration of backups and recovery plans ensure an efficient and effective resumption of vital functions of a business (Das, Mahapatra, & Pradhan, 2013). The interdependence of information security and business processes call for the need to ensure all aspects of business functions are in safe hands so as to support business continuity and growth. Additionally the complexities of businesses need to be recorded sufficiently for the purpose of attaining their recovery in case of an unexpected occurrence.

        System thinking integration is part of design management and planning (Maheshwari & Jain, 2012). For recovery, the integration enables viewing of the integral connections of the complex nature of businesses that are present in supervising the various units of the business. Systems integration is all about assessing and identifying the interoperability and integration challenges and. It loss involves an effective interface management, and assessing the various approaches to testing the integration (Khurana, & Gupta, 2012).

              The increase in technology complexity also presents new challenges to the architecture, networks, software and hardware engineering and the integration of human systems. Thus, business has to consider the requirements of engineering, concept development, system development and design, system architecture as being part of system integration. The integration is crucial since problems do not stand alone, but they affect many other areas of a system. Failure to integrate will lead to losing vital data that can assists a business recover from a disaster.

References

 Das, T, Mahapatra, D, & Pradhan, G. (2013). Towards large scale software project development and management. Journal of Computer Engineering, 8(6), 20-35. 

Karnowski, S. (2010). The database can crack missing person cases -- if used. Associated

Khurana, G., & Gupta, S. (2012). Study & Comparison of Software Development Life Cycle

Models. International Journal of Research in Engineering & Applied Sciences, 2(2),

1513-1521.

Maheshwari, S., & Jain, D. C. (2012). A Comparative Analysis of Different Types of Models in

Software Development Life Cycle. International Journal of Advanced Research in

Computer Science and Software Engineering, 2(5), 285-290.

Mishra, A., & Dubey, D. (2013). A Comparative Study of Different Software Development Life

Cycle Models in Different Scenarios. International Journal, 1(5), 64-69.

Sherry Roberts is the author of this paper. A senior editor at MeldaResearch.Com in Online Writing Services if you need a similar paper you can place your order from free essay writing services.