This is the most rudimentary of all disaster recovery plans for a mainframe. It contains just the fundamental comparisons that underlies the DRP for a cold site, sometimes called the "current requirements" and "future requirements" comparisons. These are necessary because technology changes over time. It uses the calculations contained in the current requirements model. See
A Software Licensing Agreement for the transfer under licence of intellectual property in the form of software and related documentation in the Australian Capital Territory where the transfer is temporary for a period in which the Service Provider provides both the license and software support. It includes an agreement for signing by the Service Provider and the Customer, a non-transferable, non-exclusive software licence and a warranty limited as far as possible plus the terms of support.
Following the September 11 phenomenon, the Board of Directors has asked the DRP Manager to identify the options available to them for protecting the LAN from a major disaster and prepare a strategic plan for arriving at a formal DRP which will guarantee readiness. This simple white paper discusses 10 different DRP options for three different types of networks, and gives a model that can be used for generating the DRP based on 6 levels of readiness. This is just the headings; you have to give it meaning. But from this simple model, a full DRP can be built.
An on-site service agreement for a computer system or a network in the State of New South Wales, in return for an annual service fee. Smaller system, no penalties. Australian legal agreement.
This logbook records all errors notified to the systems administrator, either from those in charge of the server or from the user's workstation. This information is invaluable for assessing the net worth of systems, for reporting errors to suppliers for patches and fixes, and for remembering how to deal with errors when they occur in the future.
The disaster recovery manual is a set of agreed actions that will be implemented at the declaration of a disaster. The idea is that, upon such a declaration, you can open up the manual and follow the procedures agreed within it, precisely, without having to negotiate the details. It is done that way because usually at the moment of a disaster it is not appropriate to begin such negotiations. It therefore differs from contingency plans and risk management.
Daily Backup Logbook designed for the year 2004. Alternating Friday set. International planning worksheet.
A Software Licensing Agreement for the transfer under licence of intellectual property in the form of software and related documentation in the State of Victoria where the transfer is temporary for a period in which the Service Provider provides both the license and software support. It includes an agreement for signing by the Service Provider and the Customer, a non-transferable, non-exclusive software licence and a warranty limited as far as possible plus the terms of support.
This logbook records the issue of temporary access passwords and access level assignment.
