Creative scheduling deliberately places a full database backup in an available capacity period, avoiding competition with resource-intensive ETL work. section 12.5
Data warehouse with a long ETL window
A warehouse may have no overnight gap for a full backup. If daytime throughput remains well below capacity while data is read but not modified, schedule the backup during business hours instead. If that capacity does not exist, consider weekend full backups with daily differentials, while checking whether nightly ETL and index rebuilds make the differentials too large. section 12.5
Use these checks before scheduling:
- Measure disk throughput across the day rather than assuming business hours are unavailable. section 12.5
- Treat filegroup backups as a last resort because they add complexity and risk. section 12.5
Figure 12.5 Disk throughput over 24 hours
Use the 24-hour throughput view to identify capacity periods for backup operations. section 12.5
