W7A Back-up and Recovery Plan in Data Warehousing Essay

W7A Back-up and Recovery Plan in Data Warehousing - Essay Examplele backups (5) synchronization of the backups with the daily additive loads (and finally, (6) saving of the incremental load files to be included as part of recovery if applicable (p. 507).For the recovery options, Ponniah (2010) provided suggestions that would assist data warehouse administrators in designing which options would cater to the schemes requirements. One of the recovery options would be to use best practices through an examination of various disaster scenarios and how the organization managed to recover the information. The recovery procedure would thereby be adjusted according to the needs of the organization, as hygienic as the time required to recover crucial data. From the strategies recommended for back-ups (separating schedules for static and active data, as well as differential and log file back-ups with daily incremental loads), the data warehouse administrator should be able to recover the need ed information inwardly clearly stipulated time frames.The scope of back-up functions actually depends on the volume and kind of data that requires backing-up. As noted, there are active and static data where the relative frequency of back-up schedules would differ (more frequent back-up schedules for active data in conjunction with less frequent back-up schedules for static data) (Ponniah, 2010). Likewise, depending on the incremental data that the organization puts in on a daily basis, the scope of the back-up function follows accordingly.To ensure readiness to recover from disasters, the back-up files must be stored in strategic areas that are safe and secure. Likewise, point persons who could be authorized and assigned to perform relevant functions pertinent to back-up and recovery should be aware of their respective roles and responsibilities in the process. As emphasized, the data warehouse administration should be prepared in addressing the following questions and concerns (1) downtime that users could tolerate during the recovery