![]()
Data SpoolingBacula allows you to specify that you want the Storage daemon to initially write your data to disk and then subsequently to tape. This serves several important purposes. First it can take a long time for data to come in from the File daemon during an Incremental backup. If it is directly written to tape, the tape will start and stop or shoe-shine as it is often called causing tape wear. By first writing the data to disk, then writing it to tape, the tape can be kept in continual motion. The second major purpose is that while the spooled data is being written to the tape, the despooling process has exclusive use of the tape. This means that you can spool multiple simultaneous jobs to disk, then have them very efficiently despooled one at a time without having the data blocks from several jobs intermingled, thus substantially improving the time needed to restore files.The remainder of this chapter explains the various directives that you can use in the spooling process. Data Spooling Directives
The following directives can be used to control data spooling.
SpoolData = yes/no SpoolData = yes/no Maximum Spool Size = mmmm Maximum Job Spool Size = mmmm Spool Directory = directory
|