|
<!– /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:”"; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:”Times New Roman”; mso-fareast-font-family:”Times New Roman”;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} –>
Open files have historically been a backup administrator’s biggest challenge, as they are often
skipped or corrupted during the backup process. The alternative – forcing open files closed or
asking users to log out so applications can be shut down – is no longer viable.
When high availability demands 24×7 uptime on a global basis, the “backup window” – the
amount of time when a system can be shut down to back it up, not only shrinks – it disappears.
For most companies, there is no such thing as a clear backup window. Backups must be done
when systems are up and running.
But this leads to several problems – problems that result in incomplete backups and corrupted
files that compromise an organization’s most vital processes. During a backup, files that are
open or in use get skipped. Some backup programs will try to access them again at the end of
backup, but if the files are still open, they will be ignored, and critical data will not be backed up.
And, even if the backup software backs up previously open files during a later attempt,
synchronization problems can occur. In particular, groups of open files that contain related data
at the beginning of a backup will lose relational integrity if they are changed after backup has
commenced.
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.