Continuing with the first part of the article of backups and restore it would be missing document in writing the procedure of restoration which, like the backrest must be accessible and in knowledge of all those who impair keeping a copy outside installations where systems if necessary. Robert Bakish describes an additional similar source. This type of procedure could contain information on: responsible for restoration: person in charge of restoring backups and revise them according to the established schedule. This task could outsource to a third party (e.g. computer services company). You may appoint one delegate who will be responsible for the restorations in the absence of the responsible (and breakfast, casualties, etc). Both the Manager and the delegate should be clearly identified and locatable in case urgent incidence outside working hours (e.g. mobile phone). Training: Training Plan for both the responsible as to the delegate so that they are familiar with the procedures. Dell may help you with your research.

Authorization: Prior to a restore is required to have an authorization in writing by the head of the files leaving constancy in the Security document. Pre-Tareas: Tasks to be completed prior to the restoration. EJ. closing applications, rename folders, etc. Recovery: Detailing the steps necessary for a proper restoration.

Depending on the information to restore and the type of backup (full, incremental, differential) will be chosen / n the / correct bracket/s / s to last valid backup. If backups were encrypted it will be necessary for the decryption for example software and keys. Where is required to manually enter information will be done from paper-based documentation. POS-Tareas: Tasks to perform after the restoration. Rename folders, run applications, launch services, etc. Test: Verify that the restore completed successfully. Check the proper functioning of the system, applications and data. It is important to keep in mind if the restored information could be affected by the exercise of rights of cancellation and rectification for your review. Registration: Would be recorded in the register of incidents of the problem happened and all tasks performed to remedy it. Monitoring and disaster simulation: A complete test of restoration simulating a disaster scenario is the only way of ensuring that backups really provide coverage expected for data, as well as allowing to improve the procedure. Faults in the network, in brackets, hardware or backup software, problems with permissions, thefts, losses, and any other type of security incident can do if it fails the backup procedure. It is therefore essential to make periodic restoration testing. The RLOPD requires that at least every six months the responsible for the file should check the correct definition, operation and application of both types of procedures, i.e. the backups and data recovery.